Jump to content

pbx support

Members
  • Posts

    2,081
  • Joined

  • Last visited

Posts posted by pbx support

  1. You can set the "Remote Party/Privacy Indication:" to "Custom Headers" and then set "P-Charging-Vector:" to "Don't use header". That should take the unwanted header out.

     

    A question before we can go ahead.

     

    1. What is 7188888888 - domain/trunk/extension ANI?

     

    Depending on the answer, you can look at the http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers and http://wiki.snomone.com/index.php?title=Custom_Headers_on_the_Trunk to set your trunk too.

  2. Wow! that seems very strange. We haven't heard this basic issue so far.

    I remember there was some state update issue with the ACD calls (long time ago). But the if the call was disconnected, calls list was cleared. What is the version number?

     

    Is it possible to run the wireshark (or some packet tracing) to get a full capture and see what's happening with the SIP messages?

  3. There will not be any more pbxnsip builds. That was the decision made and announced around late 2010.

     

    The pbxnsip customers still can use non-snom phones under the snomONE versions. They just have to contact sales for updating their licenses.

  4. Interesting.. we are now going back and forth here

     

    INVITE from Sangoma to PBX

     

    [7] 2012/04/23 14:49:29: SIP Rx udp:127.0.0.1:5066:
    INVITE sip:6478474640@localhost:5060;transport=udp;user=phone SIP/2.0

     

    Reply from PBX to Sangoma

    [7] 2012/04/23 14:49:29:	SIP Tx udp:127.0.0.1:5066:
    SIP/2.0 180 Ringing

     

    Repeat reply from PBX to Sangoma

    [7] 2012/04/23 14:49:30: SIP Tr udp:127.0.0.1:5066:
    SIP/2.0 180 Ringing

     

    Answer reply from PBX to Sangoma

    [7] 2012/04/23 14:49:34: SIP Tx udp:127.0.0.1:5066:
    SIP/2.0 200 Ok

     

    Looking at the PBX log, Sangoma is not seeing any of the replies that PBX is sending to 127.0.0.1:5066.

     

    Now, only thing is to make sure that these packets are not being dropped by Sangoma.

  5. I assume 192.168.0.12 does not have 'localhost' as the alias.

    So, try adding @domain name for the calling device & called devices. Ex: 8024@192.168.0.12.

     

    Make sure that 192.168.0.12 is the domain name for 8024 & 8025.

×
×
  • Create New...