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

Line not registering with Meta

Jump to solution

Have a TA924, built a voice user on the TA924 and Meta, but it is not registering.  Have attached output from the debug sip trunk-reg:

07:56:42.446 SIP.TRK-REG T01 5153696381 AcquireClient   Requesting permission to acquire RegisterClient.

07:56:42.456 SIP.TRK-REG T01 5153696381 AcquireClient   Permission granted - proceeding.

07:56:42.457 SIP.TRK-REG T01 5153696381 State change >> AcquireClient -> Registering

07:56:42.457 SIP.TRK-REG T01 5153696381 Registering     Stopping RetryTimer.

07:56:42.458 SIP.TRK-REG T01 5153696381 Registering     Stopping RolloverTimer.

07:56:42.463 SIP.TRK-REG T01 5153696381 Registering     RegClient -> REGISTERING

07:56:42.463 SIP.TRK-REG T01 5153696381 Registering     Starting RolloverTimer (3000 ms).

07:56:42.475 SIP.TRK-REG T01 5153696381 Registering     RegClient -> UNAUTHENTICATED

07:56:42.475 SIP.TRK-REG T01 5153696381 State change >> Registering -> Unauthenticated

07:56:42.476 SIP.TRK-REG T01 5153696381 Unauthenticated Stopping RolloverTimer.

07:56:42.486 SIP.TRK-REG T01 5153696381 Unauthenticated RegClient -> REGISTERING

07:56:42.486 SIP.TRK-REG T01 5153696381 Unauthenticated Starting RolloverTimer (3000 ms).

07:56:42.495 SIP.TRK-REG T01 5153696381 Unauthenticated RegClient -> UNAUTHENTICATED

07:56:42.496 SIP.TRK-REG T01 5153696381 Unauthenticated Stopping RolloverTimer.

07:56:42.506 SIP.TRK-REG T01 5153696381 Unauthenticated RegClient -> REGISTERING

07:56:42.506 SIP.TRK-REG T01 5153696381 Unauthenticated Starting RolloverTimer (3000 ms).

07:56:42.517 SIP.TRK-REG T01 5153696381 Unauthenticated RegClient -> UNAUTHENTICATED

07:56:42.517 SIP.TRK-REG T01 5153696381 Unauthenticated Stopping RolloverTimer.

07:56:42.528 SIP.TRK-REG T01 5153696381 Unauthenticated RegClient -> REGISTERING

07:56:42.528 SIP.TRK-REG T01 5153696381 Unauthenticated Starting RolloverTimer (3000 ms).

07:56:42.539 SIP.TRK-REG T01 5153696381 Unauthenticated RegClient -> UNAUTHENTICATED

07:56:42.539 SIP.TRK-REG T01 5153696381 Unauthenticated Stopping RolloverTimer.

07:56:42.540 SIP.TRK-REG T01 5153696381 State change >> Unauthenticated -> Failed

07:56:42.540 SIP.TRK-REG T01 5153696381 Failed          Stopping RolloverTimer.

07:56:42.541 SIP.TRK-REG T01 5153696381 Failed          Starting ReregistrationTimer (180000 ms).

07:56:42.541 SIP.TRK-REG T01 5153696381 State change >> Failed -> ReleaseClient

07:56:42.542 SIP.TRK-REG T01 5153696381 ReleaseClient   RegClient -> TERMINATED

07:56:42.543 SIP.TRK-REG T01 5153696381 State change >> ReleaseClient -> Idle

07:56:42.543 SIP.TRK-REG T01 5153696381 Idle            No Pending Events are waiting.SJC-TA924e-1#

Tags (2)
0 Kudos
Reply
1 Solution

Accepted Solutions
Highlighted
Valued Contributor
Valued Contributor

Re: Line not registering with Meta

Jump to solution

Mr. Shelton,

Thanks for posting to the Support Community!  First, you may want to make sure you can "ping" or "traceroute" to the SIP registrar from the Adtran unit..  Next, verify the egress interface has "media-gateway ip primary" configured, your associated SIP trunk has a SIP server defined, and the voice user has a SIP-Identity configured that specifies authentication settings for the registration.  If these items appear to be correct, we will likely need a bit more information to find out exactly what is happening.  Generally, we would need to see the complete configuration and the output of the following debug commands when you issue "sip trunk-registration force-register".


debug sip stack message


debug voice verbose


Thanks!

David

View solution in original post

0 Kudos
Reply
2 Replies
Highlighted
Valued Contributor
Valued Contributor

Re: Line not registering with Meta

Jump to solution

Mr. Shelton,

Thanks for posting to the Support Community!  First, you may want to make sure you can "ping" or "traceroute" to the SIP registrar from the Adtran unit..  Next, verify the egress interface has "media-gateway ip primary" configured, your associated SIP trunk has a SIP server defined, and the voice user has a SIP-Identity configured that specifies authentication settings for the registration.  If these items appear to be correct, we will likely need a bit more information to find out exactly what is happening.  Generally, we would need to see the complete configuration and the output of the following debug commands when you issue "sip trunk-registration force-register".


debug sip stack message


debug voice verbose


Thanks!

David

View solution in original post

0 Kudos
Reply
Highlighted
Valued Contributor
Valued Contributor

Re: Line not registering with Meta

Jump to solution

Mr. Shelton,

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 and unmark it.  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,

David

0 Kudos