[cisco-voip] Call goes to MoH the disconnect

[Wes Sisk]

Was it an inbound call or an outbound call?  The direction of the call 
determines who is the 'destination'. The destination definitely threw 
the error based on the information below.  Temp fail mid call usually 
means either:
* origination, destination, or transit device(mtp,..) unregistered and 
call was eligible for call preservation (h.323?)
* if it is h.323 then a device such as a firewall inspecting and then 
terminating the idle h.245 session would certainly cause this user 
experience.  Watch out for "CSCsq17141    CUCM - Allow TCP KeepAlives 
for H.323 should enable H.245 TCP KAs also" as before this change only 
h.225 TCP session used keepalives with the service parameter enabled.  
If it is h.323 then comments from CSCte10813 and CSCsm26355 identify key 
strings in CM traces.

/Wes

On Monday, August 09, 2010 12:47:24 PM, Scott Voll 
<svoll.voip at gmail.com> wrote:
> So user states that she is talking to customer.  She hears some kind 
> of MoH then the call gets disconnected.  She doesn't think it's our 
> MoH but this has happened to her before.
>
> I look at the CDRs and I find the call and I have a value 41 = Temp 
> failure on the DestCause_Value.
>
> I show a value 12 = normal device clear for DestCallTerminationOnBehalfOf.
>
> I'm not sure if this is on my side or not.  What other stuff should I 
> be looking at?
>
> Scott
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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/20100809/1bd08003/attachment.html>