Avaya S8510 to CMS over NATd address

[RVelle]

Howdy,

Have a big issue here going on, less than a week from going live with a Client of our getting an install of an S8510 with G450s that needs to connect to a CMS v880 in a seperate location, keep in mind that the client is on their network and we are on ours, which means that we are connected via dedicated Ts and firewalled from each other, so as usual would need to use NATd addressing to communicate.

Issue is that the PBX is up and almost live, CMS connection is giving error messsages tring to connect to the PBX across the firewall(telnet via supervisor/emulator works fine) - Again the PBX and CMS are, and need to, communiate via NATd addresses.

The kicker is that Avaya is stating THEY DO NOT SUPPORT NATing... HOW in the heck can you not support NATing in this day and age of mergers and acquisitions??!

I really need some possible resolves from ANYONE out there... Our BP is trying to work it, but we had no clue from the begininng that Avaya would not give support to get this working.......

Thanks in adavance

RVelle

 

[4merAvaya]

It may be a question of what ports you are using. Typically the CMS links use port 5001. Is that blocked by the firewall?

Kevin

 

[RVelle]

Thanks for that, but 23, 5001-5008 are opened up (bi directional) within both Networks..... Multiple BP calls going on trying to get this to work, Sniffers tracing the connection, but still no link up on the CMS....

Ill take any other ideas as well??

Thanks again!

RVelle

 

[Mitch672]

you could setup a site to site VPN, that is probably your only hope.



Mitch

AVAYA Certified Expert

 

[RVelle]

Looks to be resolved, The issue was the second nic, which is IP address x.x.x.59, and married to NAT x.x.x.232, was sending the packets out the seceond NIC rather than the first nic, x.x.x.58 (NAT: x.x.x.226). Once the CMS/MIS link was programmed to accept the traffic out the second nic, the CMS link came up and has been steady since 11:40AM on Tuesday August 18, 2009.

Info from our BP posted above, IPs obscured to protect the innocent

Thanks

So we are going across via NAT, but again Avaya will not support this setup... I cant believe they wouldnt support this, or assist......Yea Avaya again