Snom Template File

[Bronko]

Hi Community,

just stumbled over:

At the end of section:

<!--########################################################-->
    <!--###            Snom 8XX Series Settings             ###-->
    <!--########################################################-->

...

    {IF ua=snom870}
        <goto_virtual_keys_state_on_activity perm="">off</goto_virtual_keys_state_on_activity>
    {ENDIF}

    <!--# When one of the virtual p-keys shows a monitored line that is not idle, the phone will automatically show the virtual key state. (8X0 Phones)-->
    <goto_virtual_keys_state_on_activity perm="">off</goto_virtual_keys_state_on_activity>
....

This will result in a double entry for "virtual_keys_state_on_activity" on my snom870, because no {IF ua=...} here. It's worth to delete last two lines in your default template?
Just commented out in my custom template...

Best.

 

[JohnS_3CX]

Hi Bronko,

If this does not happen in the default template, and instead it happens in the modified one, then you may have changed or removed something which "breaks" functionality.

You can do more trial and error to find out why, or you can leave the template as default and not change or remove things that do not affect your desired goal. It's ok if you leave things in you don't need.

 

[Bronko]

Hi John,

ok, this is for sure. But in case of diving into default template we have some option to configure phone settings. A lot of them not directly manageable by 3CX MC, this is what reliable default settings means...

When you decide to change behavior of "goto_virtual_keys_state_on_activity" for a Snom 870 phone then you will edit the matching {IF...} lines and the resulting config file will switch ON and OFF this option.

Summarized: why we have two config points, with AND without {IF...} statements?

Config by default template:

<!--########################################################-->
    <!--###            Snom 8XX Series Settings             ###-->
    <!--########################################################-->

    

    

    
        <goto_virtual_keys_state_on_activity perm="">off</goto_virtual_keys_state_on_activity>
    

    <!--# When one of the virtual p-keys shows a monitored line that is not idle, the phone will automatically show the virtual key state. (8X0 Phones)-->
    <goto_virtual_keys_state_on_activity perm="">off</goto_virtual_keys_state_on_activity>

 

[Bronko]

Ok, NEW Provisoning AFTER phones deleted in extension and both phones (snom370 and snom870) reseted to factory defaults, PBX rebooted too. Coming up as new phones in list (each with own MAC) and assigned + provisioned by Default Template as described in docs.

At the phone list both have same MAC (these of first assigned phone, snom370):



At Extension in Phone Provisioning Tab both phones listed by unique MAC and working fine.

Additionally, comparing both +Config's (at phoine list) they are equal. No parsing of model name?

 

[JohnS_3CX]

Hi Bronko,

Can you please send me a private message with a screenshot showing the mac clearly?

 

[Bronko]

done...

 

[JohnS_3CX]

Ok in this case I would recommend to use Chrome (if not already) and open the phones tab again, but in Incognito mode to ensure nothing is held in the browser cache. You should not be seeing the same MAC for 2 distinct devices.

Also to be sure, provision them using the default 3CX template rather than your custom one, on 3CX V16.0.7.1078

 

[Bronko]

. You should not be seeing the same MAC for 2 distinct devices.

But I do, John.

As mentioned above, I'm on default 3CX template on:

Version Number

16.0.1078

Any further hints for me?

 

[JohnS_3CX]

Hi Bronko,

Thanks for confirming your version. Just for clarification, did you try it with Chrome incognito mode like I suggested?

This is just to be sure we are not looking at cached information or anything along those lines.

 

[Bronko]

Not in Chrome, but Firefox and Web (never seen 3CX MC before)

 

[JohnS_3CX]

Could you kindly test with the latest version of Chrome (not Chromium) and tell us if you see the same thing as in Firefox?

 

[Bronko]

Sorry John, but I'm currently missing the time to test browsers... ;-(

Let's point back:

Additionally, comparing both +Config's (at phoine list) they are equal. No parsing of model name?

and

Summarized: why we have two config points, with AND without {IF...} statements?

Could you kindly assist me here?

 

[JohnS_3CX]

1. It is possible to have the same config file for two different models. This is normal as most parameters are shared across multiple models. There will not be a reference in the config saying "this config is for model A" except for some specific model's features.

2. Regarding the line that exists outside the IF statement, we will look further into it and if needed revise the template in a future release. For now if you are unsure, leave it as is.

3. Regarding the MAC appearing twice, this is a visual artifact and can happen sometimes when you provision two phones under the same extension. It should not cause any harm to worry about.


If ever in doubt and you want to see what the normal behavior is, provision phones using our default templates (not custom) and see what to expect. Keep a copy of that config so you can do your comparisons.

 

[Bronko]

1. It is possible to have the same config file for two different models. This is normal as most parameters are shared across multiple models. There will not be a reference in the config saying "this config is for model A" except for some specific model's features.

Exactly, please double check my first post here. It seems {IF ua=snom870} will not be checked in config file creating process.

2. Regarding the line that exists outside the IF statement, we will look further into it and if needed revise the template in a future release. For now if you are unsure, leave it as is.

Thanks for doing that!

3. Regarding the MAC appearing twice, this is a visual artifact and can happen sometimes when you provision two phones under the same extension. It should not cause any harm to worry about.

Nope, it doesn't. Phones working very well...

If ever in doubt and you want to see what the normal behavior is, provision phones using our default templates (not custom) and see what to expect. Keep a copy of that config so you can do your comparisons.

That's why I'm here... ;-)