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: 
gsibley
New Contributor

Interface Configuration SIP to T1

I'm having an issue configuring the interfaces on a 3rd gen TA-916e.  The device is behind my firewall and I don't want to use the firewall in the Adtran.

I'm trying to set up a SIP trunk to T1 conversion with Feature Group D and figured I'd use the Gigabit port for management, Eth 0/1 for the SIP trunk, and T1 0/1 for my T1.  For the SIP trunk on Eth 0/1 I plan on using an IP address on my LAN and setting up a NAT on my existing firewall to route to my external IP address

I started out with the default 3rd gen config and configured the Gigabit port for 10.10.10.10 through the craft port and can log into the web interface.  My problem is when I try to assign 10.10.101.90 to Eth 0/1 I get an error "%Resultant broadcast address overlaps with giga-eth 0/1".

I'm not sure how to get around this, or if what I think I want to do is even correct. I've attached my current config if anyone has any suggestions.

I'll also welcome any information on the SIP to T1 w/Feature Group D config.

Thanks.

0 Kudos
2 Replies

Re: Interface Configuration SIP to T1

Sounds like a subnetting issue. What mask are you trying to assign to Eth 0/1?

In global config, try adding:

int eth 0/1

ip address 10.10.101.90 255.255.255.0

no shut

 

 

You will also want to update your IP default gateway to the gateway on that subnet once you add the IP address. 

 

 

Re: Interface Configuration SIP to T1

I will add to the reply here.  If you are using a router/firewall in front of the TA 916e, it has to be SIP aware.  If it is not, you will likely only get inbound calls to work.  The firewall has to be SIP aware and able to NAT the layer 3 IP information that is inside the SIP message itself.  NAT'ing the source IP address and port isn't enough - the L3 information in the SIP message HAS to be NAT'd as well.  There are some firewalls capable of this, but I have seen plenty not work.  Just be aware of this.

 

Thanks,

Geo