This can be caused by many issues, however it is unlikely to be a routing issue as for the phone to register (which it must have to in order for one way voice to be detected) it would have to have correct routes.
I would investigate whether the phone is being NAT'd, and then check firewalls for blocked traffic, and that protocol fixups are enabled if required.
Also before you can troubleshoot any firewall issues, you have to make sure the routing is in place. Can't troubleshoot access if you're not sure if the packet is being routed.
How is the Site connected
Site A is connected to Site C
Site A is connected to Site B
in order for Site B to communicate with Site C it must pass through Site A
Site A has a call manager publisher
Site B has a call manager publisher
These two call manager are not on the same cluster.
I have established a connection with Site A and Site B with an inter-cluster trunk (non-gatekeeper controller). I was having one way audio communication between Site A and Site B until I check the MTP required then I receive two way audio communication.
At Site C one IP Phone is connected for communication to Site A and Site B.
The IP phone is register to the Site A call manager and one way audio communication is being established. Site A and hear Site C but Site C cannot hear Site A.
However when Site B calls Site C I am getting a two way communication.
I think this might be a routing issue. We also got a similar problem with almost the same set up. However it was a single cluster and three sites and we finally managed to resolve it. It was a routing issue.
Make sure tcp port 2000 for Skinny (sccp)protocol is passed bi-directional between the various subnets. and udp RTP uses ports 16384-32767. if the end device is a softphone.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.