cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
12014
Views
0
Helpful
7
Replies

One way Audio CCME cluster to CME

Soe Naing Oo
Level 5
Level 5


Appreciate any clue...

- CCME cluster site call to CME site via MPLS not able to hear from CCME cluster site. but able to hear from CME site.

- CME site call to CCME Cluster site working fine

what is possible issue?

7 Replies 7

jballari
Level 1
Level 1

Hello,

Whenever I found a one-way voice issue on an IPT system, it was due to a problem with IP routing. Check that you have IP connectivity between the endpoints you're having issues with by launching a customized ping with source and destination addresses configured to be the same as the ip phones that are trying to talk to each other.

Cheers,

Jose

Hi bro,

Same with mine ..one way audio ..every time call from CUCM to CME but CME to CUCM is fworking fine. what is this debug mean?

voip_rtp_update_callinfo: ERROR - gccb not found
voip_rtcp_stop_session: ERROR - Dest IP Addr=0, no RTCP pkt sent

voip_rtp_exchange_context_info gccb not found, context is NULL
voip_rtp_xmit:no context

N

reillyjj
Level 4
Level 4

I had the same problem with calls between a CUCM-BE system and a remote CME system. I actually had two issues. One was the one-way audio which was corrected via a routing fix. The other had to do with voicemail. If you tried to leave a voicemail on the remote CME, it didn't work. This turned out to be a codec issue. We had G.729 set up between the CME and the CUCM-BE. Unity Express requires G.711. Once we fixed that and the routing issue everything worked great. Hope this help.

Thanks, but not everyone from CUCM site .. a few random user only.

Today got another error..

Apr  7 02:11:20.134: //37037/AFA7E3138F25/CCAPI/ccCheckClipClir:
   In: Calling Number=3918(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
Apr  7 02:11:20.134: //37037/AFA7E3138F25/CCAPI/ccCheckClipClir:
   Out: Calling Number=3918(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)

Apr  7 02:11:20.134: //-1/AFA7E3138F25/RXRULE/regxrule_dp_translate: No  profile found in peer 26 for outgoing direction

oip_rtp_xmit:no context
Apr  8 01:50:49.020: voip_rtp_xmit:no context
Apr  8 01:50:49.020: voip_rtp_xmit:no context
Apr  8 01:50:49.040: voip_rtp_xmit:no context
Apr  8 01:50:49.040: voip_rtp_xmit:no context
Apr  8 01:50:49.060: voip_rtp_xmit:no context
Apr  8 01:50:49.060: voip_rtp_xmit:no context
Apr  8 01:50:49.084: voip_rtp_xmit:no context
Apr  8 01:50:49.084: voip_rtp_xmit:no context
Apr  8 01:50:49.100: voip_rtp_xmit:no context
Apr  8 01:50:49.100: voip_rtp_xmit:no context
Apr  8 01:50:49.120: voip_rtp_xmit:no context
Apr  8 01:50:49.120: voip_rtp_xmit:no context
Apr  8 01:50:49.144: voip_rtp_xmit:no context
Apr  8 01:50:49.144: voip_rtp_xmit:no context

Not being an expert in decoding traces, I do recommend that at this point you go ahead and open a TAC case. They can help you reviewing the configuration of the CME in detail and also analyzing the traces for error messages, something that goes beyond the purpose of this forum.

Cheers,

Jose

Were you able to find a solution or meaning to the error above. I am seeing similar errors in a  lab environment. I am getting no audio between PSTN and HQ via PRI. HQ is using SIP to CUCM.

Mar  1 01:39:05.727: voip_rtp_xmit:no context

Mar  1 01:39:05.747: voip_rtp_xmit:no context

Mar  1 01:39:05.767: voip_rtp_xmit:no context

Mar  1 01:39:05.787: voip_rtp_xmit:no context

Mar  1 01:39:05.807: voip_rtp_xmit:no context

Mar  1 01:39:05.827: voip_rtp_xmit:no context

Hi

I think is due of codecs mismatch

BR

Envoyé de mon iPhone

Le 24 déc. 2013 à 13:57, "elvinmorales" <community@cisco.com> a écrit :

Cisco Communities

One way Audio CCME cluster to CME

reply from elvinmorales in Technology > Collaboration > Unified Communications - View the full discussion

Were you able to find a solution or meaning to the error above. I am seeing similar errors in a lab environment. I am getting no audio between PSTN and HQ via PRI. HQ is using SIP to CUCM.

Mar 1 01:39:05.727: voip_rtp_xmit:no context

Mar 1 01:39:05.747: voip_rtp_xmit:no context

Mar 1 01:39:05.767: voip_rtp_xmit:no context

Mar 1 01:39:05.787: voip_rtp_xmit:no context

Mar 1 01:39:05.807: voip_rtp_xmit:no context

Mar 1 01:39:05.827: voip_rtp_xmit:no context

Reply to this message by replying to this email, or go to the message on Cisco Communities

Start a new discussion in Technology > Collaboration > Unified Communications by email or at Cisco Communities

Following Technology > Collaboration > Unified Communications in these streams: Email Watches

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: