New OXO releases degrades H323 voip comm.

[mozsert]

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.

[enio.eltz]

Hi

H323 problem on R10.2_034.001. Upgrade to 10.2_035.001 is needed.

[mozsert]

Now I am checking.
Many thanks.

[mozsert]

Yes. The version R102/035.001 is OK.

[enio.eltz]

[mozsert]

Dear Enio Eltz
Do you recommend any new release? Because every system which loaded 102/035 suffers many VOIP problems.
102/031 : DSP stuck.
102/034 : previously described.
102/035 : many ARS lines works as expected. But some of lines goes to wrong IP adresses. For example in ARS table; xyz prefix goes @IP1, yzx prefix goes @IP2, zyx prefix goes @IP3. when you dial xyz call established with @IP1, but when you dial zyx it goes to @IP2 instead of @IP3. I think it has an indexing or prefix positioning failure.
102/039 : H323 completely down.
Another hint, if you downgrade a system from 102 to 101, data saving doesn't occur. You have to start from the beginning.
Am I in a nightmare?