CMECallConnectionFailedEvent

[cdnadmin]

This document was generated from CDN thread

Created by: Konstantin Chrispens on 05-01-2012 11:30:38 AM
Hi all,
 
is there a way to get a notification if I try to set up a call to a busy destination? In JTAPI a ConnFailedEv is thrown so I can read the event cause and take appropriate actions. In the CME SDK I found the CMECallConnectionFailedEvent. But it is not thrown if I place a call to a busy destination. I only get a CMECallConnectionDisconnectedEvent so it is not possible to distinguish between a call being dropped by user and a call being disconnected because of a busy destination.
 
Thanks in advance,
Konstantin

Subject: RE: CMECallConnectionFailedEvent
Replied by: Yaw-Ming Chen on 05-01-2012 01:17:58 PM
Do you happen know what CSTA event the SDK received (CME sent to SDK) ?

Can you please attach debug from CME

debug ccsip message
debug cti all

as well debug log from SDK

Thanks

Subject: RE: CMECallConnectionFailedEvent
Replied by: Konstantin Chrispens on 06-01-2012 02:37:39 AM
Hi Yaw-Ming Chen,
 
the CSTA event is called "FailedEvent". Below is what it looks like in wireshark:
 
INFO sip:4922429236541060_0014F29CD919@10.10.2.2:5070;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.40.0.13:5062;branch=z9hG4bK4549143D
From: <sip:4922429236541060@10.40.0.13>;tag=71F16E78-4F0
To: CME_SDK <sip:4922429236541060_0014F29CD919@csta-sdk>;tag=ds786d583b
Date: Fri, 06 Jan 2012 07:20:27 GMT
Call-ID: 132583442483823@10.10.2.2
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1325834471
CSeq: 102 INFO
Contact: <sip:4922429236541060@10.40.0.13:5062;transport=tcp>
Content-Type: application/csta+xml
Content-Disposition: signal;handling=required
Content-Length: 700

<?xml version="1.0" encoding="UTF-8"?>
<FailedEvent xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<monitorCrossRefID>00000867</monitorCrossRefID>
<failedConnection>
<callID>D7450D5A-376D11E1-8B73D83D-527A71D5</callID>
<deviceID>tel:1062</deviceID></failedConnection>
<failingDevice>
<deviceIdentifier>tel:1062</deviceIdentifier></failingDevice>
<callingDevice>
<deviceIdentifier>tel:4922429236541060;device=0014F29CD919</deviceIdentifier></callingDevice>
<calledDevice>
<deviceIdentifier>tel:1062</deviceIdentifier></calledDevice>
<lastRedirectionDevice>
<notRequired/></lastRedirectionDevice>
<localConnectionInfo>fail</localConnectionInfo>
<cause>busy</cause>
</FailedEvent>
 
The debugs you requested are attached.
 
Here are my test parameters:
 
CUCME IP: 10.40.0.13
CUCME SIP port: 1062
CSTA client IP: 10.10.2.2
CSTA client SIP port: 5070
 
Calling number: 4922429236541060
Calling device name: 0014F29CD919
Called number: 1062 (busy)
 
Please let me know if you need more info.
 
Thanks,
Konstantin

Subject: RE: CMECallConnectionFailedEvent
Replied by: Yaw-Ming Chen on 06-01-2012 06:01:51 PM
Looking for ¿not handled event ####¿ and "Session: Unrecognized event:" for the FailedEvent.
If you can see both in debug then SDK enhancement is needed to get what you like.

Thanks !

Subject: RE: CMECallConnectionFailedEvent
Replied by: Konstantin Chrispens on 09-01-2012 01:39:30 AM
Indeed it is a not handled event. Will it be handled in a future release?

Thanks

Subject: RE: CMECallConnectionFailedEvent
Replied by: Yaw-Ming Chen on 09-01-2012 03:37:51 PM
An enhancement has been requested

Subject: RE: CMECallConnectionFailedEvent
Replied by: Konstantin Chrispens on 10-01-2012 01:45:39 AM
Great,
 
Thank you!