Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
After digging into this I have found that the gateway IP in the system is 192.168.46.245 which is the WOW Adtran and the internet isn't coming from the Adtran , if I change the gateway to the customers firewall the SIP trunks stop working ??
This is a touch and go situation. If the new SIP providers adtran has an inside interface that you utilize for a SIP peer and it's on the same network as the IPedge you should be alright going back to the original gateway. If you peer with a fqdn or a public IP and put back the old gateway your traffic won't pass through the Adtran without using a static route which is a setting on later software releases of the IPedge.
Not sure I understand what your saying , the customers firewall is a 192.168.46.1. Currently bond 0 is set for 192.168.46.254 , Ihad posted that is was 192.168.46.245 it is 254
I'm not sure how much I can offer on this without breaking the rules of this board. Are you able to get support from a Toshiba vendor?
If your domain name and/or sip server are an internal IP, likely the adtran, you can switch the next hop back to the firewall. If the domain name and/or sip server or a public address or a fqdn name that won't work. Understanding how IP traffic works here is necessary.
Even without knowing the mask the SIP Peer address and the phone system are not going to be in the same network, therefore the default gateway will come into play. You'll need to setup a static route to get SIP traffic to get across the adtran.
