katerina

Yes, take just take the .4014 version as pbx support mentioned before (http://forum.snomone.com/index.php?/topic/4633-snom-8xx-series-scrolls-through-whol-addressbook-before-making-a-call/page__view__findpost__p__20213) .Or if you don't use win32, let us know for which operating system you need the fix.

Are you sure you sent the exact same xml from the example, except for the login data? Can you post a pcap trace with the request and reply?

Hi, Please go to the Logging page and set: Log Level (0-9): 9 Log Length: 500 Log SIP events: Yes Log REGISTER: Yes Log SUBSCRIBE/NOTIFY: Yes Log other messages: Yes Log call messages: Yes When you dial the number from an external network, check if a SIP packet called INVITE arrives to the snom ONE. If you see no SIP packet called INVITE arriving, then it might be that the phone lost its registration, and I would suggest you set Proposed Duration and Keepalive Time to 60 in the Trunk settings. If an INVITE does arrive, you could post the log here and we will take a look.

Hi Bill, The following example works, please try it: http://wiki.snomone.com/index.php?title=CSTA_example

When bria starts up, check if it is sending a SUBSCRIBE message to the snom ONE. The SUBSCRIBE should look something like this: SUBSCRIBE sip:202@sip.training.com;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.11.111.10:1025;branch=z9hG4bK-ogjlmb98l5jo;rport From: <sip:202@sip.training.com>;tag=zrotsfy9ah To: <sip:202@sip.training.com;user=phone> Call-ID: 3c2676d5f23f-tjbm3hy50hz8 CSeq: 1 SUBSCRIBE Max-Forwards: 70 Contact: <sip:202@10.11.111.10:1025;line=ymf7estq>;reg-id=1 Event: message-summary Accept: application/simple-message-summary User-Agent: snom370/8.4.18 Proxy-Require: buttons Expires: 3600 Content-Length: 0 The server should reply with "200 OK" to this SUBSCRIBE. Then leave a message to the extension, and check that the server is sending a NOTIFY message to the phone. The NOTIFY should look somthing like this: NOTIFY sip:202@10.11.111.10:1025;line=dtuy2001 SIP/2.0 Via: SIP/2.0/UDP 10.11.111.201:5060;branch=z9hG4bK-9b835b266fb6c3639051f4e887befe09;rport From: <sip:202@sip.training.com>;tag=803cb9d743 To: <sip:202@sip.training.com> Call-ID: kl3qz5v6@pbx CSeq: 8248 NOTIFY Max-Forwards: 70 Contact: <sip:10.11.111.201:5060;transport=udp> Event: message-summary Subscription-State: terminated;reason=noresource Content-Type: application/simple-message-summary Content-Length: 93 Messages-Waiting: yes Message-Account: sip:8202@sip.training.com Voice-Message: 1/0 (0/0) Please check these messages, and if you still don't find the problem, post your sip traces here and we will take a look.

Ok, I could reproduce the problem just as you explained and I registered it in our bug tracking system. We will let you know when this is fixed

Hallo Dexter91, Um Ihre 2 Geräte zu registrieren, müssen Sie 2 Nebenstelle von snom ONE benutzen. Sie können zB die default Nebenstelle nehmen. Um snom ONE mit den Gateway zu verbinden, müssen Sie eine Leitung(Trunk) in snom ONE erstellen, und auch die Rufschemata(Dialplan) konfigurieren, um die externe Anrufe durch die Leitung zu schicken. Bitte schauen Sie sich mal unser Manual an: http://downloads.snom.net/snomONE/docs/snomONE_online_book.pdf

If you look in the SIP Trace, you should see which host replies with a failure code to the call (sending a reply of type 3xx, 4xx, 5xx or 6xx, for example "404 Not found"). Once you know the originator of the failure reply (snom ONE or the SBC), you should check the logs and debug. If you want, you can post the log here and we will take a look at it.

It's the other way around. You configure the buttons in the web interface of the snom Vision, and there you also specify the IP address of the phone. See more info here: http://wiki.snom.com/Vision#Configuration

You should also set the following, to be sure we catch all SIP messages: Log REGISTER: Yes Log SUBSCRIBE/NOTIFY: Yes Log call messages: Yes Log other messages: Yes

Here is an example: http://wiki.snomone.com/index.php?title=CSTA_example

http://downloads.snom.net/snomONE/docs/snomONE_online_book.pdf , Chapter 11

Please see our user manual: http://downloads.snom.net/snomONE/docs/snomONE_online_book.pdf , Chapter 11

I tried a similar test (2 trunks, iptables rule to drop all packets) and both my channels turned to "408 Request Timeout" and then back to "200 Ok". There must be something specific happening in your case. Can you post the log with SIP debug here?

Please try: Account: user@gmail.com Did you the certificate as server root CA? See details here: http://forum.snomone.com/index.php?/topic/3993-cannot-send-email-via-gmail-on-4203958/page__p__17173#entry17173 If it still doesn't work, please printscreen your Certificates page and post it here

You can replace the certificates with your own, just make sure the common name matches the domain name.

Hi, Can you enable SIP Logging, set log level to 7, and post the log here so we can see more details?

Hi, Can you enable SIP Logging and post the logs here?

Hi scheronimo, Man kann verschiedene Dialplans ("Rufschemata") erstellen, und dann für jede Konto bei "Rufschema" das gewünschte Dialplan wählen.

For snom 370, make sure the color depth of the picture is 5-bit (i.e. 32 colors; preferably grey scale for better results and less loss of detail), otherwise it will not work. I attached a test picture that should work. Mrs-1.bmp

Hi Ganesh, If the preference in your dial plan is to always send calls to 10.10.11.9 first, then the call routing will only get to 10.10.11.10 when 10.10.11.9 already failed. After 10.10.11.10 also fails, why do you want it to try 10.10.11.9 again (since we already know it fails)? Anyway, if you do want this, you can try to simply add one more dialplan rule for 10.10.11.9, after ther rule to 10.10.11.10.

Hi reco, Why can't the receprionist just look at the current ongoing calls list in the user interface?

sandsvoip, can you try to change the language to English and tell me if the problem still occurs? We had another customer who had the same problem and it seems there is a bug in the Dutch translation (possibly also in other languages)

I tested on my 870 and it worked fine. Can you attach a PCAP Trace made on the snom 870 while the monitored extension is making/receiving a call?

Tested with the same name: snom370.bin, and it worked: [root@localhost snomONE]# ls /usr/local/snomONE/tftp/ snom370.bin Under 'Firmware for snom 370:' i just wrote 'snom370.bin' (without the quotes) Can you post the log?