One way Communication issue since changed IP addressing on voice vlansWe have changed IP addressing of our VoIP phones from Public Range to Private 10.x.x.x. Our Main Site IP addresses change took place before I started so don't know if some configuration
We have changed IP addressing of our VoIP phones from Public Range to Private 10.x.x.x. Our Main Site IP addresses change took place before I started so don't know if some configuration change was made on CUCM 6.1.3 to make it work. I changed the IP addressing of Voip Phones on one of the Remote site connected to main site (where Publisher / Subscriber resides). At the remote site I enabled the DHCP scope to allocate IP addresses to IP phones. I created the voice vlan and configured the correct voice vlan to switchport IP phone is connected. Phone gets the IP from DHCP scope and also gets correct parameters such as gateway,option 150 etc. Phone gets registered to Subscriber call manager. I have checked the IP cache and I see the session to port 2000.When
I call from our main site to phone assigned to new VLAN ,Remote site phone can hear us but we can't hear them and issue remains the same when call is initiated from remote site to phone's on other VLAN's or sites.
At remote site I installed another phone and assisgned the switchport to new voice vlan then both new phones can communicate to each other but same issue in communication to phones on other vlans / locations
I have checked all the access-lists and FWSM but couldn't see any issues ....ANY IDEA what's causing one way communication issue cos previous team changed the IP addresses on our main site but no such one way communication issue. Interesting thing is that I picked one of the free subnet from Main site IP address planning structure and implemented at remote site and had no issues with communication at all
One way Communication issue since changed IP addressing on voice
One way voice 99% of the time indicates routing issues, make sure your new VLAN subnet is properly advertised throughout your network and reachable from the main site. "sh ip route" at the main site should show that route as available and pointing to proper destination.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.