[cisco-voip] CUCM - MOH Silence

[Anthony Holloway]

Thanks Ryan.  The region relationships is fine as the MOH is in a special
MOH region which is 64kbps to every other region, including the one in
question.  All traces indicate that the media caps are a match at g711ulaw.

On Thu, May 14, 2015 at 6:45 PM Ryan Huff <ryanhuff at outlook.com> wrote:

> Another common source of this is codec mismatch.
>
> So if your ingress region isn't related to the region that MoH is in with
> the G.711/G.722 bandwidth profile, you'll get this issue. If you get
> tone-on-hold then it is usally partition/css/tftp related but dead silence
> is usually codec related.
>
> Thanks,
>
> -r
>
>
>
>
> ------------------------------
> Date: Thu, 14 May 2015 23:13:40 +0200
> From: roger.wiklund at gmail.com
> To: avholloway+cisco-voip at gmail.com
> Subject: Re: [cisco-voip] CUCM - MOH Silence
> CC: cisco-voip at puck.nether.net
>
>
> Not sure about the trace but I would start with basic config
> check/troubleshooting.
>
> Are you running unicast or multicast MOH?
> Is the IP Voice Media Streaming App running on all nodes? (If yes try
> restarting the service)
> Is the MOH resource in the MRG/MRGL?
> Are all devices using that MRGL?
> Is MOH selected for your codec? (System, Service Parameters, <server>, IP
> Voice Media Streaming App)
> Have you uploaded a new MOH file? If so try with the default.
>
> I would start there, or try basic ip-phone to ip-phone calls, exclude
> voice gateways etc and work my way forward.
>
> On Thu, May 14, 2015 at 10:50 PM, Anthony Holloway <
> avholloway+cisco-voip at gmail.com> wrote:
>
> All,
>
> So, I'm a bit rusty this year on trace analysis and I need a second
> opinion.
>
> From the below screenshot snippets out of TranslatorX, it would appear as
> though the MOH_3 gets selected, then an AuConnectRequest gets issued, and
> not but a few seconds later, I see an AuDisconnectRequest.  The caller
> experience is simply silence on the line while the call is connected (or
> not connected) to MOH.
>
> If there was another key piece of information I could look for to help
> myself understand why it disconnected so quickly, what should I look for?
> Thanks.
>
> [image: Inline image 1]
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
> _______________________________________________ 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/20150515/ee2bfdc6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 73223 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150515/ee2bfdc6/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 73223 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150515/ee2bfdc6/attachment-0001.png>