View Single Post
  #1  
Old 09-25-2015, 04:40 AM
thoma417 thoma417 is offline
Member
 
Join Date: Jul 2015
Posts: 7
thoma417 has 10 reputation points
Default UC module network routing

Hi Folks,

We have had an IP Office V2 running successfully for 3 months without any issues. On Monday without warning, or any changes, the Avaya Communicator stopped connecting to One X on the UC Module and we cannot connect to either the UCM or 1X web consoles.

LAN1 of the IP Office is connected to a switch with our phones and these are fine. The switch is also connected to a DMZ on our firewall which connects to our computer LAN for the Communicator running on PCs and to the Internet for OneX mobile.

If I am connected directly to the LAN1 network then 1X and the UCM is contactable and everything is fine. However, from our PC part of the network neither are accessible and the UCM cannot be pinged. The IP of LAN1 can be pinged.

Last week everything was working. I have checked the routing on the firewall as this seemed like the obvious problem and this is fine. There is no reason why the LAN1 address should be forwarded but the UCM not be forwarded. The IP traffic does seem to be flowing in the direction of the UCM but then getting lost..

Any ideas how I can troubleshoot this further? Any help would be greatly appreciated.

Thanks,
Michelle
Reply With Quote