SupportDude
Technical User
Hello!
500v2 8.1(65)
Licensed for 20 SIP channels.
SIP trunks provided by Telepacific.
I am unable to get the SIP trunks to use the WAN/LAN2 port on the IPO.
I think it is related to the setup engineered by the customer and Telepacific.
This is not my first rodeo when it comes to SIP trunking, but I do still lack knowledge on the internal workings of the IP Office.
LAN1 has a private network address, 192.168.110.10.
Telepacific requested a private IP on the customer network for their equipment and got 192.168.110.18.
Telepacific wants to direct the SIP trunks to the private IP address, but the customer doesn't want to use LAN1, so we configured LAN2 IP as 192.168.110.17 (I think this is what is causing the problem).
I am a bit ignorant on the data and internal router workings of the IP Office, but I'm pretty sure I just configured the interfaces of the internal router into the same subnet?
Now, if I enable SIP trunks on LAN2 and disable SIP trunks on LAN1, monitor we tell me the SIP trunks are out of service.
If I enable SIP trunks on LAN1 and LAN2, I will see OPTIONS packets being sent from LAN1, of course I don't see a reply from the Telepacific equipment because its looking for packets from the LAN2 address.
I tried building a static route to 192.168.110.18 using LAN2. No go.
No matter what, I cannot get LAN2 to send OPTIONS packets, and if I disable SIP trunks on LAN1, it seems to shut down the SIP trunking completely.
Will this ever work with this configuration?
Are there some rules that must be followed when using both of the LAN interfaces, like LAN1 for private IP's only and LAN2 for public IP's?
Does each interface need to be in a unique subnet?
Thanks in advance for your time!
-SD-
500v2 8.1(65)
Licensed for 20 SIP channels.
SIP trunks provided by Telepacific.
I am unable to get the SIP trunks to use the WAN/LAN2 port on the IPO.
I think it is related to the setup engineered by the customer and Telepacific.
This is not my first rodeo when it comes to SIP trunking, but I do still lack knowledge on the internal workings of the IP Office.
LAN1 has a private network address, 192.168.110.10.
Telepacific requested a private IP on the customer network for their equipment and got 192.168.110.18.
Telepacific wants to direct the SIP trunks to the private IP address, but the customer doesn't want to use LAN1, so we configured LAN2 IP as 192.168.110.17 (I think this is what is causing the problem).
I am a bit ignorant on the data and internal router workings of the IP Office, but I'm pretty sure I just configured the interfaces of the internal router into the same subnet?
Now, if I enable SIP trunks on LAN2 and disable SIP trunks on LAN1, monitor we tell me the SIP trunks are out of service.
If I enable SIP trunks on LAN1 and LAN2, I will see OPTIONS packets being sent from LAN1, of course I don't see a reply from the Telepacific equipment because its looking for packets from the LAN2 address.
I tried building a static route to 192.168.110.18 using LAN2. No go.
No matter what, I cannot get LAN2 to send OPTIONS packets, and if I disable SIP trunks on LAN1, it seems to shut down the SIP trunking completely.
Will this ever work with this configuration?
Are there some rules that must be followed when using both of the LAN interfaces, like LAN1 for private IP's only and LAN2 for public IP's?
Does each interface need to be in a unique subnet?
Thanks in advance for your time!
-SD-