06-01-2011 05:50 PM - edited 03-16-2019 05:15 AM
I have several CME 7.X/CUE sites running through a gatekeeper to so they may make calles to the CUCM 4.2 cluster and for the CUCM cluster to call the CME sites. The issue is when users from the CUCM call the CME/CUE sites they get a fast busy instead of going to voice mail afer RNA. I realize this is due to a codex issues as the CUCM cluster is g729 and CUE only seems to answer g711. My issue is I have tried to change codexs in the region of the CUCM cluster and I have added g711ilaw to the dial-peer on the CUE/CUE device. When i do the codex chnages, all this all I get is fast busy right after I finish dialing the CME/CUE sites from the CUCM cluster.
I just need a little direction on where else I need to configure g711 either the gatekeeper, CME voicepeer or CUCM.
Thank you in advance for your help.
06-01-2011 06:00 PM
Hello,
You dont need to do anything from CUCM side. You need to configure transcoder on CME that has CUE. Now what you will have in CME is an incoming dial-peer with G729 codec which accpets the call from the CUCM and SIP dial-peer with G711 to CUE.
You have to make sure it matches that incoming dial-peer and also you have to make sure that the transcoder is registered with CME. You need two transcode session for one call from CUCM.
Hope this helps you.
Nizar
06-01-2011 06:45 PM
as mentioend by another post you need a transcoder in the terminating CME to send the call as g711
but try in your CME to make your inbound dialpeer form the GK with a codec of g711ulaw manully
using the command codec g711u
for example
dial-peer voice x voip
incoming called number . ---- which means match any called number ( to make this as inbound dialpeer
codec g711ulaw
and see if the works for you or not
becuase the phone can change the IP phone support multiple codecs but the CUE just one
if you enforce the call to be g711 then the phone will support change to g711 and establish the call to your CUE
anyway give it go and good luck
06-02-2011 06:33 AM
Thank you both for your answers. It prompted me to check the codec registration on my CME and I found that the DSPFarm was not assocated to the sccp. Made the nessary adds and now it works
Thank you again for your responses.
Tom
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide