katerina

Maybe you can check this also: http://wiki.snomone.com/index.php?title=What_to_do_if_my_snomONE_suddenly_stops_answering_requests_from_phones

Hello Martyn, I am not sure but I think I know what you mean. snom ONE plays some conform noise on external outgoing calls using the file noise.wav, you can see it in the snom ONE log: [8] 2012/09/21 18:16:00:Play audio_moh/noise.wav, caching true I could remove the noise by deleting - or renaming - the file noise.wav from the audio_moh directory (which you can find in the snom ONE working directory (http://wiki.snomone.com/index.php?title=Where_is_the_snomONE_working_directory%3F ) . Make sure you restart snom ONE after you do this, and after this the noise should be gone.

Hi Martyn, To disable TLS you just need to change an option in snom ONE, see here: http://wiki.snomone.com/index.php?title=How_to_deactivate_TLS To disable SRTP you need to look in Web Page Control (Phone Pnp -> snom_3xx_phone.xml) for the following line: <user_srtp idx="{lc}" perm="RW">on</user_srtp> and change it to: <user_srtp idx="{lc}" perm="RW">off</user_srtp>

Try also to change from user mode to admin mode in the template provisioning file from Web Page Control (Phone Pnp -> snom_3xx_phone.xml) by changing line: <admin_mode perm="">off</admin_mode> to <admin_mode perm="">on</admin_mode And then reboot the phone. After you do this, if the phone is still in admin mode then there must be something wrong with your provisioning because the phone is not taking the settings correctly from snom ONE.

Oh, ok in this case you will need to wait for the next release. You can PM me if you want to try a test version.

But does the password work? (does it get you in the advanced menu?) It is normal to be presented with the box because the phone is provisioned in user mode for security reasons. To access advanced settings you must first enter the password. You can however change from user mode to admin mode in the template provisioning file from Web Page Control (Phone Pnp -> snom_3xx_phone.xml) by changing line: <admin_mode perm="">off</admin_mode> to <admin_mode perm="">on</admin_mode>

Hi Martyn, You need to enter the Administrator PIN here (the one you set in snom ONE under Domain Settings -> Authentication PIN) and then click Save. In case you don't know it then just change it in snom ONE and then restart the phone so that it gets the provisioned with the new password.

Afaik there was one more case that needed to be fixed on the phone firmware: bug ID SCPP-4186: "If <prioritise_pbx_number_lookup> is off and the initial caller ID is found in LDAP, the phone no longer updates caller ID as in rfc4916". This was fixed and the fix will be included in the next firmware release for the snom phones (planned this month). Until then, please also change the line in the PnP template: <prioritise_pbx_number_lookup>off</prioritise_pbx_number_lookup> to <prioritise_pbx_number_lookup>on</prioritise_pbx_number_lookup>

Versuchen Sie bitte in den Trunkeinstellungen das "CLIP Standard/Anzeige von Nummern:" auf "Keine Anzeige" zu setzten. Wenn das auch nicht geht bitte das snom ONE Log nochmals machen wie hier beschrieben: http://wiki.snomone.com/index.php?title=Snom_ONE_log

Great

Try this one too: http://wiki.snomone.com/index.php?title=Ports_to_open

In my test it worked. Which firmware version are you using for the snom 760? And what are the "correct phones" ? Could you post or pm me the snom ONE log ? Please see here for instructions: http://wiki.snomone.com/index.php?title=Snom_ONE_log

Hello, A way to do this would be to send calls to this number to a hunt group and direct the calls to extensions from there. Then you can use the "From-Header:" setting from the Hunt Group to decide what will be set as caller ID.

I guess some xml file got messed up there and that's why resetting to default helped.

Vance, what I could reproduce was also with a call that comes in on a trunk and gets sent out to another trunk, as I read your trace I really think we are talking about the same issue. In your trace the PBX is also trying to play "Press 1 to dial a number" (aa_call_number.wav) but you just have an older version of the audio files and the wav file is missing that's why you don't hear anything: [8] 2012/07/12 23:29:56: Play audio_en/aa_call_number.wav, caching false [8] 2012/07/12 23:29:56: call port 2: state code from 200 to 200 [6] 2012/07/12 23:29:56: Could not read file audio_en\aa_call_number.wav (error code ERROR_FILE_NOT_FOUND)

I tested this could not reproduce. Are you sure it is the snom ONE answering and not some other server? Also are you sure your snom ONE version is 4.5.0.1090? Can you post a more detailed snom ONE Log like explained here: http://wiki.snomone.com/index.php?title=Snom_ONE_log ?

You could send it as a private message (Use full editor) it or open a Support Ticket under support.snom.com (go to Ask for support and then when you get to Forum link enter the link for this forum)

I could reproduce something similar. But in my case the initial caller not only gets no BYE, but also after the hangup he hears "Press 1 to dial a number". Does this happen to you too? I just want to make sure that we are talking about the same problem.

We have a fix in which the P-asserted header has been removed. Would you like to test it (which OS)? You will no longer need the ignore_asserted_in_gui workaround.

Hello, The issue was reproduced in our lab and a bug report was done (internal ID SONE-186) . We hope to have a fix soon.

Für internal und external, bitte versuchen Sie in ringtones.xml die "tone name="internal"" und "tone name="external"" editieren damit die wie folgendes aussehen: <tone name="internal" type="internal"> <vendor><http://127.0.0.1/Ringer1></vendor> </tone> <tone name="external" type="external"> <vendor><http://127.0.0.1/Ringer2></vendor> </tone> Ich verstehe noch nicht genau wann Sie Klingel 3 benutzen möchten .

Mittlerweile hat sich das Problem gelöst. Ich habe auch ein FAQ dafür geschrieben: http://wiki.snomone.com/index.php?title=How_to_fix_the_missing_ringback_tone%3F (in Patrick#s Fall hat "Usage 1" funktioniert)

Hi Nathan, This text appears on the display so that you are informed that a secure call is made (SRTP => secure voice, TLS => secure SIP) . I understand that this text is annoying to you and thus I added a request to change it (internal ID SCPP-3335, will appaer in release notes when fixed). You could disable TLS but this would make your calls insecure: http://wiki.snomone.com/index.php?title=How_to_deactivate_TLS . If your phones are within LAN this is not such a bug problem though.

Also try this solution: http://forum.snomone.com/index.php?/topic/5740-outbound-calls-cannot-be-heard-by-receiver/page__view__findpost__p__24153

Ich glaube ich kenne das. In den Trunkeinstellungen bitte bei "Adressen für eingehende Anrufe explizit angeben:" die "127.0.0.1" eingeben