katerina

Hallo, Haben Sie das Quick Start schon durchgeführt? Was passiert wenn Sie versuchen zu telefonieren? Benutzen Sie Anlageanschluss oder Mehrgeräteanschluss ? Bitte kontrollieren Sie bei Sangoma -> NetBorder Express Gateway -> Configuration -> PSTN config -> Call control -> ISDN Configurations -> BRI L2 Configuration -> Topology, das sollte POINT-TO-POINT für Anlageanschluss oder MULTIPOINT für Mehrgeräteanschluss stehen. Wenn das nicht hilft können Sie bitte debug aktivieren wie hier erklärt http://wiki.snomone.com/index.php?title=Snom_ONE_log ? Und dann die Logs posten, für ein- und ausgehende Gespräche ?

Can you post a PCAP trace and also the phone settings? (or if you prefer to send it you can PM me)

Das Problem wurde gelöst, hier sind die Einstellungen die funktioniert haben: Request-URI: Let the system decide From: Other und dann in den Textfeld eingeben: "{ext-display}" <sip:{ext-ani}@pbx.tretwerk.local;user=phone> To: Same like Request-URI P-Asserted-ID: Dont use header P-Preferred-ID: Dont use header Remote-Party-ID: Other und dann in den Textfeld eingeben: "{ext-display}" <sip:{ext-ani}@pbx.tretwerk.local;user=phone>;party=calling;screen=yes P-Charging-Vector: Dont use Privacy Indication: Dont use

Bitte probieren Sie die folgende Lösung: http://forum.snomone.com/index.php?/topic/5740-outbound-calls-cannot-be-heard-by-receiver/page__view__findpost__p__24153

Hallo, Haben Sie ein snom ONE Plus gekauft oder haben Sie selber snom ONE installiert? Das könnte Ihnen helfen: http://wiki.sangoma.com/wanpipe-windows-nbe-snom-one Und wenn Sie snom ONE Plus haben, können Sie sich einloggen, dann bei Admin -> Server console -> Help finden Sie die snom ONE Plus Dokumentation. Was genau funktioniert nicht?

Könnten Sie bitte die Einstellungen Ihres snom ONEs exportieren (Admin -> System -> Um die aktuelle Konfiguration zu speichern, klicken Sie hier) und mir als Private Message schicken? Wenn es mit Private Message nicht klappt, bitte öffnen Sie ein Ticket in unserem Ticket-System unter support.snom.com , und da die exportierte Einstellungen hinzufügen. Ich würde die Einstellungen bei mir importieren, um genau Ihre Konfiguration zu testen.

You could try a workaround: leave all the files in the default location first, set the language you want, and then move the files and create the simlink. In my case it worked.

Entschuldigung für das Missverständnis, aber ich meinte das snom ONE SIP Log, so wie Sie vorher gepostet haben: http://wiki.snomone.com/index.php?title=Snom_ONE_log

Hallo, Wäre es möglich, dass Sie kurz eine ältere Version, die funktioniert hat, nochmals testen und den SIP Log auch hier posten? So können wir mit der neue vergleichen und sehen, ob es Unterschiede gibt.

Yes Last week I asked them and they said they have no estimation yet

Ich habe einmal das Problem gelöst, in dem ich bei der Trunk Einstellungen einfach nochmals auf Save gedrückt habe - dann hat es funktioniert. Können Sie das bitte auch probieren?

There is one solution that I know to fix some audio problems with the snom ONE plus. In the snom ONE Web interface, click on Admin -> Server Console -> Sangoma -> NetBorder Express Gateway -> Configuration -> Advanced -> look for the "netborder.net.primaryIPAddress" parameter. - if it is set to 127.0.0.1, set it to 192.168.168.1 - if it is set to 192.168.168.1, set it to 127.0.0.1 - if it is set to another value, change it either to 127.0.0.1 or to 192.168.168.1 (try one, if that doesn't work try the other) After this change click on "Apply" and then on "Status and Controls" -> "Restart Gateway" Let us know if this helps.

Hello, we have a new fix-snapshot for the pnp problem that you can try if you want. The 720 version is here: http://downloads.snom.net/tmp/snom720-8.7.3.201202132240-SIP-r.bin

No need for trace, we found the problem. The password problem with http provisioning is now fixed, but now the Plug and Play SUBSCRIBE no longer works. I informed our development team and they are working on it. Until we can provide a new fix for testing, please make the provisioning manually by entering http://snom_ONE_IP_address/prov/snom720.htm under Advanced->Update->Setting URL

It seems the Plug and Play SUBSCRIBE got no answer. Can you also post the phone's SIP trace after reboot?

This should work with the latest M9 software (starting with 9.5.12). All is documented here: http://wiki.snomone.com/index.php?title=How_can_I_integrate_the_phonebook_into_the_M9%3F

You can try this one: http://downloads.snom.net/tmp/snom720-8.7.3.5-SIP-r.bin . It has the same fixes as 8.7.3.2 but also the fix to the provisioning/menu bugs.

Oh, sorry I didn't understand that. In this case there is no need for any logs, your solution is to upgrade. The only problem is that version 8.7.3.2 still has these provisioning/menu bugs. We also built 8.7.3.3 last week, but I just tested it and the provisioning/menu bug is still there. So I suggest you wait a few days, and as soon as we fix this I can give you a test version with the fix.

Hello, You are right, there is a menu issue with version 8.7.3.2, and also a problem on provisioning, our development team is currently working on it. Anyway, we tested your initial problem with 8.7.2.9 and with 8.7.3.2 and could not reproduce any issue, which leads me to believe this is not a version problem. So if you could please go back to version 8.7.2.9 (download from here: http://provisioning.snom.com/download/fw/snom720-8.7.2.9-SIP-r.bin), and then make some extra debugging to help us find the problem: - are you using a Scheduled Conference or Ad-hoc conference? - please make the logs again but enable all logs, and set everything as explained here: http://wiki.snomone.com/index.php?title=Snom_ONE_log - make the log for the working case (call to conference 501 from external) - make the log for the non-working case (call to conference 501 from internal) - please also deactivate TLS (steps here: http://wiki.snomone.com/index.php?title=How_to_deactivate_TLS), then make a PCAP Trace on the snom ONE server, following these instructions: http://wiki.snom.com/FAQ/How_can_I_capture_packets_on_a_computer If you prefer to send these logs to us instead of posting them in the forum, please open a Support Ticket in our ticket system https://support.snom.com .

Hi Pond Group, We opened a request to Sangoma for the same problem (our Sangoma ticket number for reference: ). First they said to use the routing rules, like this: <condition param="pstn.in.isdn.setup.ie.0x0.0x6c" expr="1.*"/> Then they explained that this solution will not work because, unfortunately, the pstn.in.isdn.setup.ie.0xZZ.0xYY fields are not populated correctly. This is a bug in their software and they said they are planning a Jan27th release of NBE 4.2.1 which will expose this variable directly instead of using the setup.ie method of retreiving this information. Let's keep our fingers crossed and hope it will work.

The setting is documented here: http://wiki.snom.com/Settings/display_method . You can change it from the phone interface first to check if it fits your needs and then if you are using snom ONE provisioning you can edit snom_3xx_phone.xml from the snom ONE admin web interface -> Web Page Control

Hello, I would say there are several ways you could try: - CSTA is one http://wiki.snomone.com/index.php?title=CSTA_api - general documentation http://wiki.snomone.com/index.php?title=CSTA_example - some examples. You could use the monitor events example to find out when the extension is in a call - for general numbers you can use SNMP: http://wiki.snomone.com/index.php?title=SNMP_Ports

Hello, Regarding the button remaining red, try the latest beta for the phone (http://wiki.snom.com/Firmware/V8/Beta), 8.4.33 . This should fix the problem

We opened an issue in our bug tracking system, with ID SCPP-3412 . We will do our best to solve it as soon as possible.

I could reproduce this. Seems to be a bug in the snom software. We are analyzing the problem and will let you know