Unsupported Templates. Aaargh!

[prfindlay]

Yes, I know custom templates are not supported, but can anyone help with this frustrating situation?

I have a template that works, it's just not got the correct name to be picked up by my phones

I'm using a modified SNOM template and have just changed

<deviceconfig filename="cfg%%mac_address%%">

to be

<deviceconfig filename="MN_%%mac_address%%.cfg">

but when I provision the phone, the link is doggedly sticking to cfg{mac}

Provisioning Link: https://myserver.3cx.uk:5001/provisioning/ytyw65ith2/cfg{mac}

Looking at other supported templates e.g. grandstream, that has a config filename of

<deviceconfig filename="cfg%%mac_address%%.xml">

Yet when I provision one of those, the filename seems to be ignored and shows as

Provisioning Link: http://myserver.3cx.uk:5000/provisioning/ytyw65ith2

Same story with HTek.

It's like 3CX is doing its own thing based on some other criteria rather than following what's in the template.

 

[JohnS_3CX]

It's actually the reverse: each manufacturer has their own naming convention for their config files, the phone knows to request its config files on its own once a URL is provided.

 

[prfindlay]

It's actually the reverse: each manufacturer has their own naming convention for their config files, the phone knows to request its config files on its own once a URL is provided.

yes I know, but the 3cx is not creating the config file with the name I told it to

 

[SweetAction]

Even if 3CX did, the phone is hardcoded (I think, could be wrong) to only look at 1 specific filename.

What's the actual issue to be solved here?

 

[prfindlay]

I'm using the snom template as a basis, I'm wanting to template a mitel phone, which looks for several files, one of them being based on its Mac address.

I've potentially got hundreds of them to transfer over to 3cx and I don't want to have to hand copy/paste the sip login information, username etc for each one