snom 7/D7 Series | Configuration Guide

[KaterinaK_3CX]

Supported models:

• snom 710
• snom 715
• snom 720
• snom 725
• snom 760
• snom D712
• snom D713
• snom D715
• snom D717
• snom D725
• snom D735
• snom D745
• snom D765
• snom D785

Read the guide.

 

[bkburley]

installed Snom D735's on a 3CX. the external call ring was not acceptable to the client. Had to modify the template to find an acceptable ring. now you say the phones are unsupported. How about adding the external ring to your provisioning?

 

[Summa College]

I think there is a weird value in the snom template.

user_expiry is set at 120 sec.
While the SNOM default setting is 3600 (1 hour)

Any reason why this value is so much different ?

Currently we are experiencing that the SNOM D717 is losing it's registration every 120 sec. (20 sec. later it is registred again.)
This happens at the re-register moment.

However like bkburley... creating an custom template makes it look like there is something wrong with the phones.
With the red and warnings, so this is no option, because now I can not see anymore if there is a real problem with a phone.


Same for all the other adjustments that are different from what 3CX thinks is good.
I understand that there should be some indicator that there is a difference with the default/supported values.
However, now you are disabling the entire function off the warning indicators.

 

[JohnS_3CX]

I think there is a weird value in the snom template.

user_expiry is set at 120 sec.
While the SNOM default setting is 3600 (1 hour)

Any reason why this value is so much different ?

Currently we are experiencing that the SNOM D717 is losing it's registration every 120 sec. (20 sec. later it is registred again.)
This happens at the re-register moment.

However like bkburley... creating an custom template makes it look like there is something wrong with the phones.
With the red and warnings, so this is no option, because now I can not see anymore if there is a real problem with a phone.


Same for all the other adjustments that are different from what 3CX thinks is good.
I understand that there should be some indicator that there is a difference with the default/supported values.
However, now you are disabling the entire function off the warning indicators.

It should be noted that the values in our templates are provided from Snom.

Since you were looking at the template, you will also notice this comment from Snom above the time value:

<!--# The "user_expiry" field specifies the length of time (in seconds) the phone will be registered with 3CXPS. The phone will attempt to re-register with 3CXPS before this time expires. The provisioning template sets the value to 120 sec (2 minutes). Valid values are any positive integer.-->

And I can confirm that the phone has been tested on the latest V20 firmware and will refresh registration at the half the timer, way ahead of the expiration time.

To conclude, the reason you are noticing them losing their registration should not really be due to the timer, but it may be an indication of some other underlying issue. We would recommend to speak with your 3CX Partner and get help investigating this, and if necessary they can open a case with our 3CX Support for further investigation.

 

[Summa College]

I think there is a weird value in the snom template.

user_expiry is set at 120 sec.
While the SNOM default setting is 3600 (1 hour)

Any reason why this value is so much different ?

Currently we are experiencing that the SNOM D717 is losing it's registration every 120 sec. (20 sec. later it is registred again.)
This happens at the re-register moment.

However like bkburley... creating an custom template makes it look like there is something wrong with the phones.
With the red and warnings, so this is no option, because now I can not see anymore if there is a real problem with a phone.


Same for all the other adjustments that are different from what 3CX thinks is good.
I understand that there should be some indicator that there is a difference with the default/supported values.
However, now you are disabling the entire function off the warning indicators.

I managed to resolve this issue.
It appears it has nothing to do with the user_expiry setting.


There was a Cisco Firewall that still did SIP inspection in the Global Policy.
This also uses a value of 2 minutes, so likely this was interupting with the SIP traffic.

Using below guide I managed to disable SIP inspection.
https://wrmem.net/index.php/2020/05/08/disable-sip-inspection-on-firepower-through-flexconfig/


However, it still remains weird for me that there is such a big difference between SNOM default value from their wiki and the value that they apparently use with the 3CX server.
https://service.snom.com/display/wiki/user_expiry

 

[MatsW]

The beginning of the article says "If you don't want to use RPS, you have to enter the provisioning URL into the phone via its web interface". I've now spent 3 hours searching thru the Snom D765 web interface, and I have not been able to find any entry that resembles something that could be a provisioning string. Is there anyone out there who has a clue where it could be entered?

Update: No I found it: Under "Advanced / Update / Setting URL". Not the most likely place to search to find what is the most basic setting