Upgrading to 8.1 (67) broke calling out from one site to another in a 4 site SCN 1

[jventresco]

I have an SCN with 4 sites, centralized VM. Two sites are at 4.2 and the other two are at 8.1(67). These two (the 8.1(67)'s) cannot talk to eachother, but do show up as "SCN Up" in system status. I triple checked the line settings and licenses. System Status shows the lines as UP and Idle, and when you make a call, it shows up momentarily, gets fast busy on the phones, then disconnects after 4 seconds. Never ringback or outgoing alerting.. only seized and dialing on the appropriate H323 trunk for these two bad boy sites. They both can make a successful call to the other two sites on 4.2 release. There are no duplicates for outgoing line ids and the conflicts for extension numbering have been resolved. It worked fine between all sites before the upgrade, and the sites are set up with a mesh scheme. I have voice networking licences and essential and preferred at the two non cooperative sites.

The customer does have a plan to upgrade the 4.2 sites...

Any ideas before I get deeper, or where to look?

 

[mforrence]

Make a shortcode to force calls over one of the non-working H323 trunks - dial whatever the far end wants and see if successful. If not, watch Monitor on far end - it will likely indicate why unhappy. FYI - this is a non-supported configuration. Doesn't mean that it definitely won't work - just means that Avaya won't help if it doesn't.

 

[jventresco]

Thanks for replying mforrence, I did have the short codes forcing those extensions over the proper H323 trunk to get to where it as needed, still did not work.

Catalyst support provided the answer. Turn OFF "Enable H323 Transformations" on the Sonicwall router. We had it enabled before as with even earlier releases (3.x and 4.0) of IPO it seemed to work with this box ticked.. with it off the calls at all sites are now fully functional. They say Avaya likes to mess with the way the SCN protocols work as the releases get higher, but do not tell anyone about the changes. When the sites are on the same subnet the issues do not occur, as when you are testing in your lab as we did. Also as a sidenote "Enable SIP Transformations" should have no effect on IPO SCN functionality per Catalyst.

 

[Westi]

have a star for providing the solution jventresco

Joe W.

TeleTechs.ca
FHandw, ACSS (SME), ACIS (SME)


“This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter