[cisco-voip] cisco-voip Digest, Vol 182, Issue 5

[Brian Meade]

Looks like it's a problem with the way H.323 to H.323 calls work.

Unlike SIP, H.323 uses TerminalCapabilitySet messages to advertise to both
sides all possible capabilities/codecs between the 2 sides then the master
gets to pick.

On the call leg between Avaya and SME, Avaya gets chosen as master and
picks G.711a.

On the call leg between SME and CUCM 11.5, CUCM 11.5 is chosen as master
and picks G.711u.

You then don't have any universal transcoding/MTP resources I assume to
handle the mismatch.

You need a way to force a codec across the full call path.  I'd suggest
using SIP between SME and CUCM 11.5 rather than H.323 ICT.

If it has to be H.323 ICT, you may be able to try forcing MTP Required on
the H.323 gateway config for Avaya in the SME cluster.

On Wed, Dec 5, 2018 at 2:07 PM Nilson Costa <nilsonlino at gmail.com> wrote:

> Hello all
>
> I´m facing another type of issue now, it´s about call drop on inbound calls
> I have the following new scenario
>
> Avaya --H.323--> CUCM SME(8.5(1)) --ICT trunk--> CUCM 11.5 --SIP--> CIPC
>
> In this case when I call to one Avaya extension the call goes normally
> the problem comes when a Avaya extension calls me the call drops as soon
> as I answer the call drops
>
> attached the call logs
>
> Calling - 57841
> called - 20000
>
>
> Can someone help me find out why is it failing?
>
> Nilson Lino da Costa Junior
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20181205/c1d5b409/attachment.html>