cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
netcastmin
New Contributor II

Need help with SIP Registration Issue...

Jump to solution

I have been playing with this all day:

I have an ADTRAN 908. I am using the T1 for a PRI, and also have FXS ports in use. Due to the setup of the PBX on the other end of the SIP, I have to route the FXS ports to a separate SIP Trunk from the PRI. I am using ANI and Trunk lists to route the channels. The problem is, the SIP Trunks are at the same server, but use a username/password authentication to determine which trunk is which. And of course, the registrations are coming from one IP(the ADTRAN). Per the vendor, all I have to do is setup my second SIP trunk to use port 5061 instead of port 5060. I have changed the ports, but have not been able to register the SIP trunk. I'm not sure how to read the debug, but here it is:

00:38:22.873 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Idle            Received ReregistrationTimerEvent, sending external Register event.

00:38:22.874 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Idle            Received external Register event, posting to local queue.

00:38:22.874 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Idle            Posting ExecutePendingEvents event to active queue.

00:38:22.875 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Idle            1 Pending Event is waiting.

00:38:22.875 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Idle            Executing RegisterEvent.

00:38:22.876 SIP.TRK-REG T02 sip0000002_atscomfortinnwest State change >> Idle -> AcquireClient

00:38:22.876 SIP.TRK-REG T02 sip0000002_atscomfortinnwest AcquireClient   Stopping ReregistrationTimer.

00:38:22.877 SIP.TRK-REG T02 sip0000002_atscomfortinnwest AcquireClient   Requesting permission to acquire RegisterClient.

00:38:22.878 SIP.TRK-REG T02 sip0000002_atscomfortinnwest AcquireClient   Permission granted - proceeding.

00:38:22.878 SIP.TRK-REG T02 sip0000002_atscomfortinnwest State change >> AcquireClient -> Registering

00:38:22.879 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Registering     Stopping RetryTimer.

00:38:22.879 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Registering     Stopping RolloverTimer.

00:38:22.880 SIP.CLDU Looking up outbound interface to 64.94.197.237

00:38:22.884 SIP. MSG REGISTER REQ TX sip0000002_atscomfortinnwest sip0000002_atscomfortinnwest

REGISTER sip:fe-edc5-2e.coredial.com:5061 SIP/2.0

From: <sip:sip0000002_atscomfortinnwest@fe-edc5-2e.coredial.com:5061;transport=UDP>;tag=2587ab0-7f000001-13c4-6e3c-52e2858f-6e3c

To: <sip:sip0000002_atscomfortinnwest@fe-edc5-2e.coredial.com:5061;transport=UDP>

Call-ID: 25a8250-7f000001-13c4-63-19d965c2-63

CSeq: 547 REGISTER

Via: SIP/2.0/UDP 65.13.226.242:5060;branch=z9hG4bK-6e3c-1ae9dbf-59d05be5

Max-Forwards: 70

Supported: 100rel,replaces

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

User-Agent: ADTRAN_Total_Access_908_2nd_Gen/A4.11.00.E

Contact: <sip:sip0000002_atscomfortinnwest@65.13.226.242:5060;transport=UDP>

Expires: 3600

Content-Length: 0

00:38:22.886 SIP. MSGSUM REGISTER REQ TX sip0000002_atscomfortinnwest sip0000002_atscomfortinnwest sip:fe-edc5-2e.coredial.com:5061

00:38:22.890 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Registering     RegClient -> REGISTERING

00:38:22.891 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Registering     Starting RolloverTimer (3000 ms).

00:38:25.892 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Registering     Received RolloverTimerEvent.

00:38:25.893 SIP.TRK-REG T02 sip0000002_atscomfortinnwest State change >> Registering -> Rollover

00:38:25.893 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Rollover        Stopping RolloverTimer.

00:38:25.894 SIP.TRK-REG T02 sip0000002_atscomfortinnwest State change >> Rollover -> Retrying

00:38:25.895 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Retrying        RegClient -> TERMINATED

00:38:25.895 SIP.TRK-REG T02 sip0000002_atscomfortinnwest State change >> Retrying -> Registering

00:38:25.896 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Registering     Stopping RetryTimer.

00:38:25.896 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Registering     Stopping RolloverTimer.

00:38:25.897 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Registering     No more secondary servers available

00:38:25.898 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Registering     ERROR! Unable to send REGISTER.

00:38:25.898 SIP.TRK-REG T02 sip0000002_atscomfortinnwest State change >> Registering -> Failed

00:38:25.899 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Failed          Stopping RolloverTimer.

00:38:25.899 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Failed          Starting ReregistrationTimer (60000 ms).

00:38:25.900 SIP.TRK-REG T02 sip0000002_atscomfortinnwest State change >> Failed -> ReleaseClient

00:38:25.901 SIP.TRK-REG T02 sip0000002_atscomfortinnwest ReleaseClient   RegClient -> TERMINATED

00:38:25.901 SIP.TRK-REG T02 sip0000002_atscomfortinnwest State change >> ReleaseClient -> Idle

00:38:25.902 SIP.TRK-REG T02 sip0000002_atscomfortinnwest Idle            No Pending Events are waiting.

It looks like I'm connecting on port 5061, but I don't understand where the port 5060 is coming from in these lines. Can someone tell me if this is my issue with the ADTRAN, or if it's the SIP PBX?

-or-

I could send everything down one SIP trunk if the PRI from the onsite PBX (a Mitel) could send out a caller ID. The Mitel PBX is not configured to send digits on outbound calls, so I have nothing to translate. The PRI needs to only ID as their main number, but I need the FXS ports to ID as themselves.

Thank you for any help in advance.

Labels (2)
0 Kudos
1 Solution

Accepted Solutions
netcastmin
New Contributor II

Re: Need help with SIP Registration Issue...

Jump to solution

After going back and forth with the folks at ADTRAN Tech support and the technicians with the SIP provider, we found a solution that worked. By setting the "Inbound Caller ID Override" on the PRI Trunk, we were able to send a caller ID to the SIP, thus eliminating the need for multiple SIP Trunks. The SIP provider in this case did not allow for more than (1) SIP trunk to register from the same IP. Had this been allowed, the original configuration would have worked. Thanks to all that direct messaged me with ideas and comments, your help and ideas are greatly appreciated!

View solution in original post

0 Kudos
2 Replies
ftwrobert
New Contributor III

Re: Need help with SIP Registration Issue...

Jump to solution

We recently got a 908e in for testing SIP to PRI & POTS. I found that I had to use the same voice trunk (T00) for both the POTS and the PRI.

I had to configure a "default" registration on the voice trunk that the PRI would use when calling, then each voice user (for the fxs lines) had their own user/pass that would override the one set on the voice trunk.

netcastmin
New Contributor II

Re: Need help with SIP Registration Issue...

Jump to solution

After going back and forth with the folks at ADTRAN Tech support and the technicians with the SIP provider, we found a solution that worked. By setting the "Inbound Caller ID Override" on the PRI Trunk, we were able to send a caller ID to the SIP, thus eliminating the need for multiple SIP Trunks. The SIP provider in this case did not allow for more than (1) SIP trunk to register from the same IP. Had this been allowed, the original configuration would have worked. Thanks to all that direct messaged me with ideas and comments, your help and ideas are greatly appreciated!

View solution in original post

0 Kudos