New OXO releases degrades H323 voip comm.
Posted: 28 Mar 2016 08:27
Hello everyone.
We have a large VOIP H323 network. One OXE is located at central area, many OXOs are at remote areas. Central to remote, remote to central, remote to remote communication over VOIP trunks are already working in both ways.
A new OXO was added to the network with release 102/034.001. But OXE to OXO dialling could not be done. When I downgrade system to release 101/041.001, problem is isolated.
t3 traces from OXE and pcap trace pictures from OXO are attached for both releases of OXO.
I checked R9 in another site. R920/067.001 is works properly but R920/080.001 don't.
Is there any H323 parameter or numbering plan changes in new releases which prevent OXO reply the VOIP packets?
Thanks.
We have a large VOIP H323 network. One OXE is located at central area, many OXOs are at remote areas. Central to remote, remote to central, remote to remote communication over VOIP trunks are already working in both ways.
A new OXO was added to the network with release 102/034.001. But OXE to OXO dialling could not be done. When I downgrade system to release 101/041.001, problem is isolated.
t3 traces from OXE and pcap trace pictures from OXO are attached for both releases of OXO.
I checked R9 in another site. R920/067.001 is works properly but R920/080.001 don't.
Is there any H323 parameter or numbering plan changes in new releases which prevent OXO reply the VOIP packets?
Thanks.