ACME SBC to CM6 Direct SIP

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • rwallo
    Whiz
    • Dec 2013
    • 29
    #1

    ACME SBC to CM6 Direct SIP

    I am connecting SIP trunks direct to CM6.

    I'm stating this up front because I know it is not correct as a supported configuration and that it is outside my control and was determined too far back to be able to correct at this point.

    Out bound calls are 100% good.
    Inbound calls to IP phones are 100% good.

    Our issue is when we have calls that need to terminate to TDM extensions. We get nothing on a list trace tac. We get a little from the MST trace but not enough to see what is wrong. We are seeing a 488 error at the far end. We are thinking it is a codec issue but I've not seen CM care about the type of endpoint it tries to route to.

    I don't believe it is our issue but I can't rule it out either.

    Any ideas out there?

    Thanks!
    Tags: None
  • bsreddy
    Hot Shot
    .
    • Apr 2012
    • 14
    #2
    Just a couple of ideas on how you may proceed....

    488 is usually related to codec sets as you mentioned. To determine which codecs are at play, you can check the SDP of the INVITE and the 200OK messages. The media attributes of SDP will show which codecs are being offered by the CM and Far-end device. I am suspecting that the reason TDM phones and IP phones are behaving differently could be that they are in different network regions. TDM phones take the NR from the Gateway/cabinet in which they are connected.

    You could also try to toggle the IP-IP direct media parameter of the SIP signalling group. That could also help resolve the problem.

    Regards

    Comment

    • richa164
      Guru
      • Oct 2013
      • 131
      #3
      list trace

      You also could try list trace tacxxx/s the /s will or should give you sip messaging at a higher level on the TAC

      Comment

      Previous template Next
      Loading