Call release code

[yixiu0317]

Hi           There,

Is there a particular code in Call Manager or UCCX which will show whether the call was terminated by the agent or by the caller?

As my understanding, either party end the call by hangup, the Call Manager will show the code as normal release, but will tell me which party hangup first.

We are using Call Manager 8.6 and UCCX 8.5.

Cheers               

[Ayodeji Okanlawon]

Yes you can see this in the CUCM Trace. There are two ways an IP Phone can possible end a call..Either the phones goes "OnHook" or the enduser presses the "END" softkey..

If the user presses the end softkey then you will see a softkey event like the one shown below: StationInit, means the phone is telling the cucm that a softkey was pressed. StationD means that CUCM is telling the phone to stop playing any tone.

14:27:05.354 |StationInit: (1897815) SoftKeyEvent softKeyEvent=9(EndCall) lineInstance=1 callReference=477120264.|28,100,13,2834917.6203^10.34.117.200^SEP001380ADFD00

14:27:05.354 |StationD:    (1897815) StopTone.|28,100,13,2834917.6203^10.34.117.200^SEP001380ADFD00

If the phone ended the call by going onhook, then you will see this message..

14:26:48.869 |StationInit: (1916376) OnHook.|28,100,13,2861157.1356^10.64.10.150^SEP000C30F02C46

If this is an outside call, you can look at the signalling on the gateway to see when CUCM sent or received a disconnect. You then compare the timelines on the phone traces and the gateway traces to see which happened first. E.g if you see and endcall or onhook happen before you see CUCM sending a disconnect to the gateway, then you know the agent hung up the call first.

Please rate all useful posts

"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

[yixiu0317]

Hi           Mate,

Thank you for your reply.

It is quite useful for understanding the trace.

I did test by calling an external number and hangup from the IP phone and the external phone, but according to the trace file, the call manager always disconnect the call before I can see the onhook.

Here is I hangup from the IP phone

10:20:38.253 CCM|MediaManager(2344703)::wait_AuDisconnectRequest, mCleanupPreallocatedMTP=0|<:CORPORATE001><:10.199.65.33><:5><:192.168.254.239><:SEPE8046213F336><:ERROR><:0800>

10:20:39.726 CCM|StationInit: (0111087) OnHook.|<:-CORPORATE001><:10.199.65.33><:5><:10.203.160.75><:SEPE8046213F336><:STATE transition=""><:0020>

Here is I hangup from external phone

10:33:41.957 CCM|MediaManager(2345227)::wait_AuDisconnectRequest, mCleanupPreallocatedMTP=0|<:CORPORATE001><:10.199.65.33><:5><:192.168.254.239><:SEPE8046213F336><:ERROR><:0800>

10:33:43.953 CCM|StationInit: (0111087) OnHook.|<:CORPORATE001><:10.199.65.33><:5><:10.203.160.75><:SEPE8046213F336><:STATE transition=""><:0020>

As my understanding, if I hangup from the IP phone first, I should see the onhook message before the AuDisconnectRequest.

Also, since I need to trace a call happened couple of weeks ago, it is impossible to check the what has happened on the gateway, is there any particular parameter in the CUCM trace file that will show which party hangup first.

Cheers

[Ayodeji Okanlawon · Accepted solution]

You need to understand call legs in cucm. For every call leg there is a call reference. When a call is disconnected, cucm will log which call leg disconnected the call..

In this log, pstn----sip---gw---sip--cucm---scpp--ip phone

+++++++
This is an inbound call from a cell phone.

The inbound call leg has a CI ( call reference) of 478528114, the outboung leg, tha is the leg to the ip phone is 478528115

15:07:22.314 |ForwardManager - addActiveCallTableEntry - Added entry for party= 478528114 callkey= 0xC58E7|28,100,63,1.16620812^10.105.40.74^*
15:07:22.314 |Forwarding - Created! - callKey= 0xC58E7|28,100,187,809191.1^*^*

the outboung leg, this is the leg to the ip phone is 478528115
15:07:22.315 |ForwardManager - wait_SsDataInd (SETUP) - mPartyToActiveCallIndexMap Added Entry for Destparty= 478528115, callkey= 0xC58E7|28,100,63,1.16620812^10.105.40.74^*

++++++++Now this call was connected and the terminated by the ip phone.+++++
The first thing you see is the softkey event and the call reference to indicate which leg disconnected the call..

.
5:10:41.311 |StationInit: (0397874) SoftKeyEvent softKeyEvent=9(EndCall) lineInstance=1 callReference=478528115.|32,100,13,1177031.224905^10.34.92.77^SEP000C30F03714

+++Next you see a call release message on the cucm node that the call orginated from...and the source of the release..(destination or origin).Here we see that this is a destination release...and the call reference showed that its the ip phone (destination) that released the call++++

15:10:41.313 |Forwarding - awaitingCallResponse_SsDataInd - BASIC_CALL_RELEASE - Destination Release. party= 478528115

++++Next you see the audio disconnect message++++

15:10:41.313 |ARBTRY-ConnectionManager- wait_AuDisconnectRequest CI(478528114,478528115),disconnectType(1)

+++++

If the call was released by the calling part (origin) you will see something like this (origination release)

15:10:51.459 |Forwarding - awaitingCallResponse_SsDataInd - BASIC_CALL_RELEASE - Origination Release. party= 478528368

Another way to see who disconnected the call is to look at your CDR logs. You will see these two entries amongst others.

origCause_value (0)

destCause_value (16)

Whichever party has cause value code..disconnected the call

Please rate all useful posts

"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

[asafayan]

Great summary !

Amir

[yixiu0317]

You are the legend.