Voice Networking stopped working

[esauve]

We recently installed a new IPO 406 to complement our 412. It worked fine until some networking changes stopped Voice Networking from functioning. Long distace calls between the sites redirected by short codes work fine but not extension-to-extension . Does anyone know what ports need to be open between sites for Voice Networking to work properly?

 

[SuperJenks]

The system uses random ports from like 5000 to 9000 something. Did you change any gateways or routers?

 

[esauve]

Thanks for taking the time to answer.

Yes, we are cleaning up the network at the other end so we changed the gateway. It was changed accordingly in the Manager and both IPO's were rebooted several times. Extension-to-extension still won't work.

 

[SuperJenks]

Some times its difficult to get the boxes to sink up. Did the IP address of either IP office change?

 

[esauve]

Not since it had started working last week. When we first installed the new IPO last week it was configured to another IP which we changed and everything had been working fine for about five days. Three days after implementation the default gateway was changed and two days after that the Voice Networking stopped working. The link in between the IPO's is wide open, except for a Packet Shaper whose settings haven't changed since the gateway change, but the Voice Networking still won't come up. We are considering turning off the Packet Shaper for test purposes.

 

[SuperJenks]

Yes, that would be one thing to try. I would do a reboot on both ends. Also, there is the program called monitor. This always proves to be a very useful tool. This will show you what is going on in the backround of the system. Every operation of the IPO passess through monitor capturing software. When we had this same problem, we would have the monitor running on both sites, then do a reboot on both ends. Watch in the monitor to see why they are not communicating. Also, double check your default IP routes in the manager.

 

[esauve]

I've used the monitor and got this when checking routing;

13322mS AVRIP Tx: v=192.168.12.222 send=4934 receive=0
requiresvoicemail 0 operational 1 version 2 recordsupported 1
IPaddr 255.255.255.255 hops=0 voice=0

I've rebooted with the monitors running but I don't always know what I should be looking for. Any hints?

And the default routes are correct.

 

[SuperJenks]

Hmmm, ok check somthing for me. Go into the manager under lines. There you should have a IP route for scn that you numbered manually. The icon will be a black Plug. In the voip tab, is the gateway set to the remote IPO address or is it set to 255.255.255.255 The monitor trace you displayed tells me that scn is trying to connect via broadcast. Now that youve implemented a new gateway, the broadcast may not work. You must enter the remote IPO systems IP address in the gateway field. Try and check on this and let me know.

 

[esauve]

I have the remote IP in the field. Maybe the IPaddr field is a subnet mask. The first line, 13322mS AVRIP Tx: v=192.168.12.222, refers to the remote IPO.