[cisco-voip] one way voice issue

[Ryan Huff]

For the dial-peers that face the carrier (outbound and inbound), you would bind them to the interface that the carrier communicates through. If the carrier comes in over the Internet from the outside, you would bind those dial peers to the outside/Internet facing interface.


Use caution when binding inbound dial peers; recall you have two types of inbound, from the carrier and from CCM. It can be easy to create inbound overlaps, and when combined with dial-peer binding, can cause issue with sending signaling to the wrong interface.


Sent from my iPhone

________________________________
From: naresh rathore <nareh84 at hotmail.com>
Sent: Friday, September 30, 2016 9:39 AM
To: Ryan Huff; cisco voip
Subject: Re: one way voice issue


hi Ryan,



i have long weekend to resolve the issue. i can't define the hq public ip for global bind because ip sec vpn at spoke use the hq public ip to connect as well. so i have to define dial peer bind command for media and control. will start troubleshooting by binding the interface at dialpeer level.


Regards


Naresh


________________________________
From: Ryan Huff <ryanhuff at outlook.com>
Sent: Friday, September 30, 2016 6:01 PM
To: naresh rathore; cisco voip
Subject: Re: one way voice issue


One-way audio is almost always, always; one side of a call leg's media stream being blocked (ACL, NAT, Firewall ... etc).


If the PSTN hears the IP phone but the IP phone cannot hear the PSTN in the northbound direction, then the media stream is simply not getting back to the IP phone. The call sets up fine because signaling travels a different path than media.

If you're in an 'emergency' type of situation, you can probably work around this for now by checking 'MTP Required' on the CCM SIP trunk and resetting the CCM SIP trunk. This is not ideal and comes with its own set of demons (CCM cpu utilization .. etc); and if you process a high call volume, this may not even be an option for you. If you attempted this, you'd want to make sure the MRGL the SIP trunk and phones use only has access to media resources that all phone segments can reach and the media resources can reach all phone segments. This could potentially allow you to 'weather the storm' and get you to a maintenance window where you could tackle it properly.

Thanks,

Ryan

________________________________
From: naresh rathore <nareh84 at hotmail.com>
Sent: Friday, September 30, 2016 8:41 AM
To: Ryan Huff
Subject: Re: one way voice issue


hi Ryan


I havent manually bind the interface, but if cube initiate the session with ITSP, it will use public ip and for CUCM it will use the voice vlan ip.


Regards


Naresh

________________________________
From: Ryan Huff <ryanhuff at outlook.com>
Sent: Friday, September 30, 2016 5:36 PM
To: naresh rathore
Subject: Re: one way voice issue


Naresh,


I took a brief look here ... I'm not seeing where you are binding SIP in the HQ cube? That is the first issue I'd tackle. If CCM and the ITSP can see a common interface on the CUBE (i.e MPLS ... etc) then you could do a global bind on that interface under voice service voip > sip.


However, if the ITSP trunk really is over the Internet, individual dial peer binding will be more helpful (carrier peers bound to the Internet facing interface, CCM peers bound to the CCM facing interface). Just need to watch that your inbound peers don't overlap with dial peer binding.

Thanks,

Ryan
________________________________
From: cisco-voip <cisco-voip-bounces at puck.nether.net> on behalf of naresh rathore <nareh84 at hotmail.com>
Sent: Friday, September 30, 2016 8:21 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] one way voice issue


hi,


Setup: there are two sites  (HQ and spoke). Each site have their own internet and connected to each other via ipsec vpn. CUCM and CUC is at HQ site. this is centralized deployment. the internet gateway at HQ site is also acting as a CUBE and there is sip trunk up and running between CUBE and ITSP via internet both HQ and spoke site use the HQ cube to call out (using the same ITSP). now site to site calls are working ok. calls from HQ Phones to ITSP and vice versa (mobile/national etc) are working ok.  incoming calls transferred by HQ phone to spoke site phone also works well. the issue is outgoing call from spoke site, when they make outgoing call, the customer can hear their voice but the spoke site phone user cant hear them. any suggestions??. i have attached the config of both routers.


Regards


Naresh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160930/64181890/attachment.html>