[cisco-voip] Unity Connections (Native Transcoding)

Pat Hayes pat-cv at wcyv.com
Tue Jan 25 18:29:41 EST 2011


You are saying that when you have UC setup to advertise G711 and G729,
your G729 calls to it work, but when it is setup to only advertise
G711, G729 calls fail? That sounds like UC is transcoding just fine
and the problem is with your hardware transcoders. Have you verified
that the transcoders are listed in the device pool/MRGL associated
with the voicemail ports and that other devices with that same device
pool are able to complete similar call flows?


On Tue, Jan 25, 2011 at 4:39 PM, Mark Marquez <MMarquez at goldsys.com> wrote:
> I hope someone can provide some help. Below is an explanation of my  iissue.
>
>
>
> In Unity Connections I've set the Port Group settings to only advertise G711
> mu-law.  From reading I found that Unity Connections does Native
> Transcoding. My remote branch devices are set to use G729 over the WAN.
> When I dial voicemail from remote branch phones using either the Pilot
> number or by using the Messages button calls get a fast busy.  If I re-add
> the G729 codec to the advertised codec list on the Unity Connections Port
> Group then calls complete. Apparently Native Transcoding on the Unity Server
> is not working. I do have hardware transcoding resources available to the
> phones in question but they are not getting invoked. My understanding is
> that this is normal since Unity Connections should do the transcoding
> natively via its CPU.  Any help is appreciated.
>
> BTW, phones at headquarters which are set to use G711 do work when Unity
> Connections is set to only advertise G711.  Remote branch phones connecting
> over the WAN using G729 fail.
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>



More information about the cisco-voip mailing list