The Adtran community holiday season is starting next week! The holiday period will span from December 21, 2024 to January 6, 2025. During this time, responses to feedback form submissions may be delayed. If you are encountering product issues, you can reach out to Adtran support at any time.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Anonymous
Not applicable

Trouble Registering Analog extensions over WAN (vpn) to NV7100

Jump to solution

Adtran,

I've had this issue before, but for whatever reason I can't get this to work. I've got the two user accounts i want to use on ta924e built on the nv7100 as SIP phone types. On both the ta924e and the nv7100 the VPN between them is working properly as i can ping from both devices in either direction. However the user accounts built on the ta924e will not register. I've added the SIP identity to them to register to the trunk. I'm thinking that perhaps my trunk is the problem. I want them to register to the vlan 2 on the nv7100 at 10.10.20.1. Should I put that in as the SIP server address or the SIP server proxy address?

thanks,

brian

0 Kudos
1 Solution

Accepted Solutions
Anonymous
Not applicable

Re: Trouble Registering Analog extensions over WAN (vpn) to NV7100

Jump to solution

brian,

Thanks for posting this to the Support Community.  To answer your question the sip-server primary address for the SIP trunk should specify the IP you want the registrations to be sent to.  As you implied you can then configure the analog voice users to register with the sip-identity command.  Here is a stripped down sample configuration of how to accomplish that:

!

voice trunk T01 type sip

  description “Trunk to 7100”

  sip-server primary 10.10.20.1

!

!

voice grouped-trunk SIP

  trunk T01

  accept <NUMBERS_ROUTED_TO_7100>

!

!

voice user 4200

  connect fxs 0/1

  sip-identity 4200 T01 register auth-name 4200 password 1234

!

NOTE:  In this example T01 would be the SIP trunk used to reach the 7100 from the TA 900.  The 7100 would need to be configured with a SIP voice user of 4200 and a sip-authentication password of 1234 .The interface that 10.10.20.1 is configured on the 7100 would need to be set as media-gateway ip primary. Also, <NUMBERS_ROUTED_TO_7100> needs to be replaced with the appropriate patterns to match your specific network setup.

Thanks,
Matt

View solution in original post

0 Kudos
2 Replies
Anonymous
Not applicable

Re: Trouble Registering Analog extensions over WAN (vpn) to NV7100

Jump to solution

brian,

Thanks for posting this to the Support Community.  To answer your question the sip-server primary address for the SIP trunk should specify the IP you want the registrations to be sent to.  As you implied you can then configure the analog voice users to register with the sip-identity command.  Here is a stripped down sample configuration of how to accomplish that:

!

voice trunk T01 type sip

  description “Trunk to 7100”

  sip-server primary 10.10.20.1

!

!

voice grouped-trunk SIP

  trunk T01

  accept <NUMBERS_ROUTED_TO_7100>

!

!

voice user 4200

  connect fxs 0/1

  sip-identity 4200 T01 register auth-name 4200 password 1234

!

NOTE:  In this example T01 would be the SIP trunk used to reach the 7100 from the TA 900.  The 7100 would need to be configured with a SIP voice user of 4200 and a sip-authentication password of 1234 .The interface that 10.10.20.1 is configured on the 7100 would need to be set as media-gateway ip primary. Also, <NUMBERS_ROUTED_TO_7100> needs to be replaced with the appropriate patterns to match your specific network setup.

Thanks,
Matt

0 Kudos
Anonymous
Not applicable

Re: Trouble Registering Analog extensions over WAN (vpn) to NV7100

Jump to solution

I went ahead and flagged this post as "Assumed Answered". If any of the responses on this thread assisted you, please mark them as Correct or Helpful as the case may be with the applicable buttons. This will make them visible and help other members of the community find solutions more easily. 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