Jump to content

katerina

Members
  • Posts

    153
  • Joined

  • Last visited

Posts posted by katerina

  1. 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 ?

  2. 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

  3. 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.

  4. 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.

  5. 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.

  6. 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 .

  7. 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.

×
×
  • Create New...