Topic: Help with Snom 300, please

[del]

I have built my new SAIL/Asterisk box and I am having a problem getting a Snom 300 to work. I have followed the docs wiki and plugged in the Snom 300, it said to press any button to update tftp, which I did. The funny thing is the phone gets an IP address, the user name etc. is the extension number but I don't have dial tone and SAIl doesn't show it as connected  Any ideas? I am running SME 7.4 with all updates and SAIL 2.3.2-15
Thanks in advance,
Del

[del]

OK, it seems that the Snom phone was expecting the password to be the same as the ext. number  So I just changed the secret to the ext. number and everything appears to be OK  . It's getting late so I'll check everything again in the morning.
Del

[SARK devs]

Del,

first of all... NEVER set the passsword of the phone the same as the extension number.  We see an increasing number of SIP attacks which expect just that.   Once someone is registered on your sysyem illegally, you will never know until you receive your phone bill, by which time it's too late. SARK is deliberately set up to generate a strong, unique password for each endpoint.  It really is best to use it.

Provided you have your SARK box issuing DHCP then your snom will provision itself entirely automatically, as long as you have entered the MAC address of the Snom into the corresponding extensions panel in SARK. 

You should also add the following parameters to your Snom provisioning definition (the right-hand window in the extensions edit panel...

; leave dnd codes blank
dnd_on_code!:
dnd_off_code!:

; ntp server - ip of pbx, in case it doesn't come from dhcp
ntp_server$: xxx.xxx.xxx.xxx

; locale settings
timezone!: {your timezone code}
language!: {your language}
tone_scheme!: {your country}
date_us_format&: {off/on}
time_24_format&: on

; turn off challenge-response
challenge_response$: off

; change ringers as no one seems to like the Snom descending tone!
alert_internal_ring_sound!: Ringer6
alert_external_ring_sound!: Ringer2
user_ringer1!: Ringer6
user_ringer2!: Ringer6


; don't offer encrypted rtp, needs changing it Asterisk ever supports it
user_srtp1$: off
user_srtp2$: off

; turn off long contact sip headers
user_descr_contact1$: off
user_descr_contact2$: off

; "support broken registrar" not sure this is needed any more for asterisk but do it anyway
user_sipusername_as_line1$: on
user_sipusername_as_line2$: on

; shows name & number on inbound call
display_method!: display_name_number

; resync settings hourly, ONLY on v7 firmware!!!!!
settings_refresh_timer$: 3600

; settings for easier transfers
; call_join needs to be off for receptionists though!!!
transfer_on_hangup!: on
call_join_xfer!: on

; turns off flash plugin in web gui
with_flash$: off

; stops LED lighting for missed calls, which most people prefer
message_led_other!: off


Out of the box, all Snoms have a built-in random delay which is taken after the phone comes up and before it requests its provisioning data from the TFTP server.  This is there to prevent overload on the server when mass deployments all come on-line together.  Ignore anything that appears on the Snom s creen during this phase (unless the phone is clearly hanging).

Make sure your system is set up as I have described, then factory reset and reboot your Snom.  Now, go and have a cup of cofee while the Snom sorts itself out.   

Kind Regards

S 


 

[del]

Thanks for the input, what happened was that I left the strong generated password but when I plugged in the Snom it did everything but register and I saw in the [provisioning] box that the pass was set to the ext number so I changed the secret in the left panel to match and it came up OK except for the time zone was set to GMT. So before I go and mess everything up  I need to be clear with what you are telling me to do    Do I just paste the code you've put in your reply in place of the code already in the [provisioning] box? Or do I add it to the existing code in there? Seeing as I have already messed with the code should I delete the extension and start again?

Thanks,

Del

Del,

first of all... NEVER set the passsword of the phone the same as the extension number.  We see an increasing number of SIP attacks which expect just that.   Once someone is registered on your sysyem illegally, you will never know until you receive your phone bill, by which time it's too late. SARK is deliberately set up to generate a strong, unique password for each endpoint.  It really is best to use it.

Provided you have your SARK box issuing DHCP then your snom will provision itself entirely automatically, as long as you have entered the MAC address of the Snom into the corresponding extensions panel in SARK. 

You should also add the following parameters to your Snom provisioning definition (the right-hand window in the extensions edit panel...

; leave dnd codes blank
dnd_on_code!:
dnd_off_code!:

; ntp server - ip of pbx, in case it doesn't come from dhcp
ntp_server$: xxx.xxx.xxx.xxx

; locale settings
timezone!: {your timezone code}
language!: {your language}
tone_scheme!: {your country}
date_us_format&: {off/on}
time_24_format&: on

; turn off challenge-response
challenge_response$: off

; change ringers as no one seems to like the Snom descending tone!
alert_internal_ring_sound!: Ringer6
alert_external_ring_sound!: Ringer2
user_ringer1!: Ringer6
user_ringer2!: Ringer6


; don't offer encrypted rtp, needs changing it Asterisk ever supports it
user_srtp1$: off
user_srtp2$: off

; turn off long contact sip headers
user_descr_contact1$: off
user_descr_contact2$: off

; "support broken registrar" not sure this is needed any more for asterisk but do it anyway
user_sipusername_as_line1$: on
user_sipusername_as_line2$: on

; shows name & number on inbound call
display_method!: display_name_number

; resync settings hourly, ONLY on v7 firmware!!!!!
settings_refresh_timer$: 3600

; settings for easier transfers
; call_join needs to be off for receptionists though!!!
transfer_on_hangup!: on
call_join_xfer!: on

; turns off flash plugin in web gui
with_flash$: off

; stops LED lighting for missed calls, which most people prefer
message_led_other!: off


Out of the box, all Snoms have a built-in random delay which is taken after the phone comes up and before it requests its provisioning data from the TFTP server.  This is there to prevent overload on the server when mass deployments all come on-line together.  Ignore anything that appears on the Snom s creen during this phase (unless the phone is clearly hanging).

Make sure your system is set up as I have described, then factory reset and reboot your Snom.  Now, go and have a cup of cofee while the Snom sorts itself out.   

Kind Regards

S 


 

[del]

just a thought, seeing as the Snom phones are working OK, I'm happy with the ring alerts and the can set the timezone after boot, couldn't I just generate a strong password and change it in both the panels?  Thanks,
Del

[SARK devs]

You can do anything you like. 

As long as you are happy with the outcome then all is good.

S