8 Replies Latest reply on Apr 29, 2013 11:12 AM by matt

    SIP setup troubleshooting information

    knevyn New Member

      I've been trying to connect a 7100 to a sip server.

       

      I've followed the instructions from the class labs for the 7100.

       

      I've searched the adtran support site for any documentation. Unfortunately I've found little Can't even locate an admin guide

       

      I've searched on the error from the debugs, "ERROR! Unable to send REGISTER". No hits for this search,

       

      The above is not much to go on, but does anyone have any suggestion for what to do next?

        • Re: SIP setup troubleshooting information
          markfreeman Employee

          Hello,

          There is a lot of Trunk configuration in the forums, if you go to the link below you will see config guides for configurint the 7100 to many different sip servers.

           

          NetVanta 7100_Trunk_Config_Search_Results

           

          Here is one to start with:

          Configuring the NetVanta 7000 Series for a Bandwidth.com SIP Trunk

           

          Another thing is if this SIP Server is external and coming in through the firewall, you will need to modify the firewall, see doc below:

          NetVanta 7000 Series Security Guide

           

          If you still can't get it working, then post your startup-config file and attach it to your reply. Click "Use Advanced editor" in the top right corner of the reply and then you will see an option below the reply to attach a file.

           

          -Mark

            • Re: SIP setup troubleshooting information
              knevyn New Member

              Mark,

               

              Thanks for the links. I'll read through these and hopefully find the answer.

               

              Any idea about this error message I'm getting in debug?

              "ERROR! Unable to send REGISTER"

               

              Here is the entire debug output.

               

              15:16:01.833 SIP.TRK-REG T07 201    State change >> Idle -> AcquireClient
              15:16:01.833 SIP.TRK-REG T07 201    AcquireClient   Stopping ReregistrationTimer.
              15:16:01.833 SIP.TRK-REG T07 201    AcquireClient   Requesting permission to acquire RegisterClient.
              15:16:01.834 SIP.TRK-REG T07 201    AcquireClient   Permission granted - proceeding.
              15:16:01.834 SIP.TRK-REG T07 201    State change >> AcquireClient -> Registering
              15:16:01.834 SIP.TRK-REG T07 201    Registering Stopping RetryTimer.
              15:16:01.834 SIP.TRK-REG T07 201    Registering Stopping RolloverTimer.
              15:16:01.838 SIP.TRK-REG T07 201    Registering RegClient -> REGISTERING
              15:16:01.838 SIP.TRK-REG T07 201    Registering Starting RolloverTimer (3000 ms).
              15:16:04.841 SIP.TRK-REG T07 201    Registering Received RolloverTimerEvent.
              15:16:04.842 SIP.TRK-REG T07 201    State change >> Registering -> Rollover
              15:16:04.842 SIP.TRK-REG T07 201    Rollover    Stopping RolloverTimer.
              15:16:04.842 SIP.TRK-REG T07 201    State change >> Rollover -> Retrying
              15:16:04.843 SIP.TRK-REG T07 201    Retrying    RegClient -> TERMINATED
              15:16:04.843 SIP.TRK-REG T07 201    State change >> Retrying -> Registering
              15:16:04.843 SIP.TRK-REG T07 201    Registering Stopping RetryTimer.
              15:16:04.843 SIP.TRK-REG T07 201    Registering Stopping RolloverTimer.
              15:16:04.844 SIP.TRK-REG T07 201    Registering No more secondary servers available
              15:16:04.844 SIP.TRK-REG T07 201    Registering ERROR! Unable to send REGISTER.
              15:16:04.844 SIP.TRK-REG T07 201    State change >> Registering -> Failed
              15:16:04.844 SIP.TRK-REG T07 201    Failed      Stopping RolloverTimer.
              15:16:04.844 SIP.TRK-REG T07 201    Failed      Starting ReregistrationTimer (60000 ms).
              15:16:04.844 SIP.TRK-REG T07 201    State change >> Failed -> ReleaseClient
              15:16:04.845 SIP.TRK-REG T07 201    ReleaseClient   RegClient -> TERMINATED
              15:16:04.845 SIP.TRK-REG T07 201    State change >> ReleaseClient -> Idle
              15:16:04.845 SIP.TRK-REG T07 201    Idle        No Pending Events are waiting.
                • Re: SIP setup troubleshooting information
                  markfreeman Employee

                  Your 7100 is not able to successfully register and it looks like it tries your sip server, it times out and then it fails and gives you that message.

                   

                  You might want to verify that you are using the correct username and password to register.

                   

                  Here is what a correct registration looks like:

                  13:11:32.442 SIP.TRK-REG T04 256963XXXX Idle            Executing RegisterEvent.

                  13:11:32.442 SIP.TRK-REG T04 256963XXXX State change >> Idle -> AcquireClient

                  13:11:32.443 SIP.TRK-REG T04 256963XXXX AcquireClient   Stopping ReregistrationTimer.

                  13:11:32.443 SIP.TRK-REG T04 256963XXXX AcquireClient   Requesting permission to acquire RegisterClient.

                  13:11:32.443 SIP.TRK-REG T04 256963XXXX AcquireClient   Permission granted - proceeding.

                  13:11:32.443 SIP.TRK-REG T04 256963XXXX State change >> AcquireClient -> Registering

                  13:11:32.443 SIP.TRK-REG T04 256963XXXX Registering     Stopping RetryTimer.

                  13:11:32.444 SIP.TRK-REG T04 256963XXXX Registering     Stopping RolloverTimer.

                  13:11:32.447 SIP.TRK-REG T04 256963XXXX Registering     RegClient -> REGISTERING

                  13:11:32.447 SIP.TRK-REG T04 256963XXXX Registering     Starting RolloverTimer (3000 ms).

                  13:11:32.476 SIP.TRK-REG T04 256963XXXX Registering     RegClient -> REGISTERED

                  13:11:32.476 SIP.TRK-REG T04 256963XXXX State change >> Registering -> Registered

                  13:11:32.476 SIP.TRK-REG T04 256963XXXX Registered      Stopping RolloverTimer.

                  13:11:32.477 SIP.TRK-REG T04 256963XXXX Registered      Starting ReregistrationTimer (191000 ms).

                  13:11:32.477 SIP.TRK-REG T04 256963XXXX State change >> Registered -> ReleaseClient

                  13:11:32.477 SIP.TRK-REG T04 256963XXXX ReleaseClient   RegClient -> TERMINATED

                  13:11:32.477 SIP.TRK-REG T04 256963XXXX State change >> ReleaseClient -> Idle

                  13:11:32.478 SIP.TRK-REG T04 256963XXXX Idle            No Pending Events are waiting.

                  • Re: SIP setup troubleshooting information
                    jwable Frequent Visitor

                    Can you post the results of debug sip stack message (remove any protected information)  it will give a better idea of what you are sending and what the sip server is requesting.  Off the top my guess is the IP SIP GRAMMAR is wrong for your particular provider. 

                      • Re: SIP setup troubleshooting information
                        knevyn New Member

                        I was able to get the 7100 to register. I can make out bound calls. Inbound calls fail.

                         

                        5555555555 substituted for inbound caller

                        5552223333 substituted for DID in system

                        1.1.1.1 substituted for  SIP Server's IP

                        2.2.2.2 substituted for 7100 eth0/0 WAN port IP

                         

                        10:21:44.302 SIP.CLDU Incoming CallLeg created from 5555555555@1.1.1.1:5060 to 5552223333@2.2.2.2:5060

                        10:21:44.302 SIP.CLDU Searching for a matching trunk account by Via (1.1.1.1:5060 - UDP)

                        10:21:44.302 SIP.CLDU findClduInterface: 1.1.1.1 match to configured SIP server (host/port), but trunk T06 is full

                        10:21:44.303 SIP.CLDU Searching for a matching trunk account by From (1.1.1.1:5060 - UDP)

                        10:21:44.303 SIP.CLDU findClduInterface: 1.1.1.1 match to configured SIP server (host/port), but trunk T06 is full

                        10:21:44.303 SIP.CLDU Searching for a matching trunk account by To (2.2.2.2:5060 - UDP)

                        10:21:44.303 SIP.CLDU Searching for a matching trunk account by Contact (1.1.1.1:5060 - UDP)

                        10:21:44.303 SIP.CLDU findClduInterface: 1.1.1.1 match to configured SIP server (host/port), but trunk T06 is full

                        10:21:44.304 SIP.CLDU Searching for a matching trunk account by Source IP (1.1.1.1:5060 - UDP)

                        10:21:44.304 SIP.CLDU findClduInterface: 1.1.1.1 match to configured SIP server (host/port), but trunk T06 is full

                        10:21:44.304 SIP.CLDU Request URI indicates a local address, but could not match INVITE to an available trunk

                        10:21:44.304 SIP.CLDU Default trunk is not enabled or does not exist.

                        10:21:44.304 SIP.CLDU Incoming message received from 1.1.1.1:5060 via UDP

                        10:21:44.305 SIP.CLDU Cldu::CallLegStateChangedEv: (0x5c0a5b0)->Offering

                        10:21:44.305 SIP.CLDU Using SIP global outbound policy for HMR

                        10:21:44.305 SIP.CLDU No change to message with global SIP HMR

                        10:21:44.307 SIP.CLDU Cldu::CallLegStateChangedEv: (0x5c0a5b0)->Disconnected

                        10:21:44.357 SIP.CLDU Incoming message received from 1.1.1.1:5060 via UDP

                        10:21:44.357 SIP.CLDU Cldu::CallLegStateChangedEv: (0x5c0a5b0)->Terminated

                        10:21:45.999 SIP.CLDU Cldu::CallLegCreatedEv: (0x5c0a7c8)

                  • Re: SIP setup troubleshooting information
                    Employee

                    I went ahead and flagged the "Correct Answer" on this post to make it more visible and help other members of the community find solutions more easily. If you don't feel like the answer I marked was correct, feel free to come back to this post to unmark it and select another in its place with the applicable buttons.  If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.

                     

                    Thanks,

                    Matt