The Cisco Unity Express Auto Attendant fails to transfer inbound calls from the PSTN to the IP phone intermittently. The caller hears a failsafe that says "The system is experiencing a problem and cannot take the call right now. Try again later". The SIP/2.0 500 Internal Server Error is seen in traces.
The issue is addressed in Cisco bug ID CSCse39392.
From the trace log, there are SIP/2.0 500 Internal Server Errors after the call is transferred, after 202 accepted messages are in the traces. The 500 internal server error occurs when the Cisco CallManager Express terminates the call legs to the Cisco Unity Express, in order to finish the transfer and map the disconnect cause 16 to the SIP 500 status message.
Because the 500 and 202 messages are received in a very short time amount of time 202 accepted first, and 500 later sometimes the Cisco Unity Express processes the 500 before 202 message. This can cause the Cisco Unity Express to think that the transfer failed and play the failsafe prompt.
In order to resolve this issue, perform one of these steps:
Change the transfer-mode to blind bye-also.
Upgrade the Cisco Unity Express to version 2.3.2, which fixes the problem.
Greetings, I was wondering if anybody has any guide or something for CUCM migration from v8.x to the newest version of the CUCM (v14).Looking forward to your replies, thanks a lot in advance. Kind regards, Ermir.
I'm trying to figure out how to use Programmable Feature Buttons as described here. Specifically I'm wondering how to assign such features, for example: Call Forward All, to a line button. The phone I'm dealing with is an 8851 and I've put it in enhanced ...
Curious if anyone has built or setup a solution that allowed you to bridge multiple FXS ports in one simultaneous call? We have a paging system with a unique campus setup where each of the units is a master for that building but does not connect to ...
We have a handful of 7962 phones that overnight seem to have their ringer go silent so when a call comes in the light flashes but makes no sound. We are able to turn the volume back up but we need to figure out the root cause for this issue. I...