we have a 3rd Party Attendant Console connected with a SIP Trunk to CUCM with a Route Pattern pointed to SIP Trunk.
Here is first the Call Flow:
1. External/Internal call to main number 2. Attandant Console Software and Cisco Phone Ring and the call is not be answered 3. Another Cisco Phone gets Call Pickup Notification and push Pickup 4. The External/Internal hear Queue music from Attendant Console and the 2nd Cisco Phone rings 5. 2nd Phone Answer now the Call and the external/internal Call Disconnects 6. 2nd Cisco Phone looks like its connected and time is counting
From the SIP trace of the 3rd Party Attendant Console i see a BYE Message from the Route Pattern Extension to the EXTERNAL/INTERNAL Caller and thats the reason why the 2nd Phone and the Caller are not connected.
This is most likely an MTP issue. The reason you are experiencing this is due to the break in media transimission when the call is put on hold for subsequent transfer to the second phone that has pressed the pick up soft key. During this process the call is "inactive" in sip terms and some 3rd partys do not deal well with this. It is advisable to enable MTP in sip trunks to 3rd party devices..
Please rate all useful posts
"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...