Sysmon: Cause = 41, Temporary Failure

[Wally1775]

I have a new installation with a 12 channel PRI and sometimes outgoing calls drop before they connect. I pulled the subject line error from a trace - can anyone translate that and save me the trouble of creating a ticket?

Thanks in advance.

 

[intrigrant]

You can find some details about these cause codes here :

http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/dbook/disdn.htm

But it will not enlighten your mind because it does not say what the problem is.

 

[jml2665]

thats exactly what the Avaya docs say too, the dreaded temporary failure

http://marketingtools.avaya.com/kno...s/manuals/manual_pdfs/apps/monitor_sysmon.pdf

 

[Wally1775]

Thanks for the replies. I had no idea that 'Off Hook Operation' would suppress a busy signal and just drop an outgoing call. Now I do. =\

 

[sizbut]

You're not alone, I even talked to guys within Avaya who are campaigning that off hook operation should at least let the user hear busy tone for a few seconds before the disconnect.

 

[CarGoSki]

No kidding. I had one this week that caused me to come in at 12am to work. It turned out that the hunt group nite svc forward number had been disconnected. The IPO would attempt to fwd:get rejected:go back to the group que then rinse-lather-repeat-forever.

The entire sequence happened real fast. It sounded like MOH was choppy. Insert>Busy or CO disconnect message would have been nice.

 

[sizbut]

Yeph, that one's another bug bear. The IP Office pulls back forwarded calls that hit busy or no answer in order to put them into voicemail. But it does this even when the user doesn't have voicemail on, so it then forwards the call again and round and round we go.