IP Office R9 SIP Trunk problem

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • roblindsey
    Member
    • Jun 2014
    • 4

    IP Office R9 SIP Trunk problem

    Hello,

    Since upgrading to R9.0.3, we have an issue with inbound SIP trunk calls to analogue and digital endpoints, and voicemail.

    Calls to IP extensions and SIP endpoints are OK, as are outbound calls over the SIP trunk using any endpoint type.

    Inbound calls to non-IP endpoints will ring at the endpoint but when answered, the caller continues to hear ringing and the line does not connect at the called extension. If the called party then hangs up, if the caller is still waiting, the handset will ring again.

    Also inbound calls over the SIP trunk are not answered by voicemail pro.

    I believe others may be having the same issue, anyone?

    Rob
    Last edited by roblindsey; 06-14-2014, 03:21 AM. Reason: quoted wrong endpoint type
  • esiddique
    Aspiring Member
    .
    • Mar 2014
    • 1

    #2
    Hi,

    Probably that the IP Office is not getting the 200 OK msg (Off hook) from IP endpoints after it has received the 180 Ringing. Since it has received the 180 ringing, IP Office is not transferring the call over to voicemail? This needs to be traced with a packet tracer mirroring the IP endpoint port. May want to look at what off hook/on hook msg going to the IP office from endpoints.

    Thanks,
    SiD

    Comment

    • roblindsey
      Member
      • Jun 2014
      • 4

      #3
      endpoints

      I mis-quoted - problem is with calls to non-ip endpoints, so wont be able to trace that.

      Comment

      • kirchenlo
        Guru
        • Nov 2010
        • 195

        #4
        If you provide a trace out of the system monitor or out of the monitor application by explaining which number dials were we would certainly able to help out.

        I would say check your FW settings, as it sounds that the 200 OK is not goign back to the SIP trunks. As it is a non IP Endpoint it will use the IP Office as "Proxy" to the SIP Trunk provider, is your IP Office in the same LAN segment as the IP phones? Make sure that all necessary ports between IPO and your SIP trunk are open, 5060 SIP and the RTP ports.

        Do you have a VCM card in your IP Office? What codec si configured for your SIP Trunks?

        Comment

        • roblindsey
          Member
          • Jun 2014
          • 4

          #5
          Monitor Trace

          Just done some traces and I'm getting:

          22:52:56 1498926976mS Stun: StunClient: ResponseTimeout in Resolve RTP, attempt 0

          So, looks like RTP is not happy. 200 response is lacking on the failing calls.

          Tried this with the firewall switched off just to see, and it makes no difference.

          There are two combo cards installed; one alog and one BRI. Preferred codec is g.711 a-law, but 729 is also enabled.

          Unsure why I would be getting different results for IP and non-IP endpoints if the issue was general IPO config on LAN/IP trunk, or firewall.

          Need to look at traces and edit before posting for security.

          Comment

          • chasse
            Aspiring Member
            • Aug 2014
            • 1

            #6
            Were you able to resolve this issue? I am experiencing the exact same problem.

            Comment

            • carte79
              Member
              • Aug 2014
              • 6

              #7
              I'm also experiencing this problem, was there any resolution?

              Comment

              • bridg18
                Member
                • Oct 2014
                • 3

                #8
                Did anyone get a fix for this. We have the same issue and it is driving me nuts.

                Comment

                • zakabog
                  Genius
                  • Aug 2014
                  • 300

                  #9
                  If it's always with 9.0.3 it might just be a known issue that was patched in a later version. Otherwise if you don't have 9.0.3 send over some SIP traces and maybe we can see what happened to the call.

                  Comment

                  Loading