[cisco-voip] Temp Fail IP Phone Message

[Kevin Thorngren]

Temp fail can happen if the MGCP GW unregisters from CCM.  I suspect 
this might be the problem here.  For example, the GW unregisters, CCM 
signals temp fail to the phone but does not disconnect the call so the 
audio stays up.  But since the GW is unregistered and CCM relays DTMF 
this stops working although the audio path is still up.

I would recommend gathering detailed CCM traces from the primary CCM 
for the MGCP GW, that corresponds to the temp fail messages, to see if 
the GW is unregistering at that time.  You can also take a quick look 
in the Application Event log for the unregister events.

Kevin
On May 26, 2006, at 1:09 AM, vemail at mac.com wrote:

>
>
> The "Temp Fail" message is a failure of the audio path connection
> usually due to DSP errors or codec issues.  There can be an issue
> with the DSP of the IP Phone (if it's only happening to one phone) or
> the DSP resources on a Voice Gateway.  If the error is occurring with
> multiple phones, before disconnecting the troubled calls, identify
> the gateway endpoint at the IP phone and check the log of the gateway
> endpoint for any DSP errors (assuming debug logging is active).  You
> can also try to query the DSP to identify which DSP is not responding.
>
> Also, the connection failure could be caused by a codec negotiation
> issue such as (for instance) the endpoint does not have G.729
> resources available however calls to the location whereupon the
> gateway is located requires the use of the G.729 codec.
>
> The issue can be hardware or software related.
>
>
> On May 25, 2006, at 11:21 PM, Michael L. Windon wrote:
>
>> All, any help you could you could provide would be greatly
>> appreciated.
>>
>>
>>
>> Environment:
>>
>>
>>
>> CallManager 4.1.3 SR3a
>>
>> 3745 14.4.6.T2
>>
>> 8 T1 – Pri MGCP Connected to a MLS-100 using Pri-NI2 ISDN type
>>
>>
>>
>> Situation:
>>
>>
>>
>> During a circuit switch bound call, the cisco IP phone which are
>> 7911 and 7960 display a Temp Fail message on the bottom of the
>> screen. Once this happens the call continues but the distant-end
>> does not hear any buttons pushed. This is not good because users
>> can’t enter in information into systems like voice mail or any
>> other prompt and collect applications.
>>
>>
>>
>> What I have tried:
>>
>> Upgrading IOS 3745
>>
>> Using the latest device pack April 2006
>>
>> Verified routing between ip phone and call manager
>>
>> Search through detail traces
>>
>> Called tac and send traces, and isdn q931 debugs, mgcp packet debugs.
>>
>>
>>
>> I have many people tell me that this message is caused when the IP
>> phone stop receiving ack of its keep alive messages to or from the
>> Call Manager, but I assure you the call manager is not down. I can
>> ping and traceroute directly to the phone from the callmanager
>> during a call. The phone is also registered with the call manager
>> and is not dropping into SRST mode. I don’t know where to go from
>> here. Does anyone know of another way to watch or detect this event
>> on the call manager other then trace logs, as I have not found
>> anything of interested in them or don’t know how to read them. Like
>> I said before any help would be greatly appreciated.
>>
>>
>>
>> Mike
>>
>> _______________________________________________
>> 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
>