cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1524
Views
0
Helpful
2
Replies

Unexpected CallCtlCause and CiscoCause in CallCtlConnDisconnectedEv

derrickgunter
Level 5
Level 5

Call flow is a simple manual conference:

  1. Inbound call from external party 3155211 to 6019
  2. 6019 answers
  3. 6019 initiates conference to 6018
  4. 6018 answers
  5. Race condition: 6019 completes conference while at the same time 3155211 releases

Result: 3155211 is gone from the call and only 6019 and 6018 are left.

There is a race condition in step 5.

Case 1 (unexpected):

If CallCtlConnDisconnectedEv 3155211 is received between CiscoConferenceStartEv and CiscoConferenceEndEv we get unexpected cause codes:

3587: Dec 01 15:58:52.985 AST %JTAPI-JTAPI-7-UNK:(P1-devuser2) 901022/1 CallCtlConnDisconnectedEv 3155211::2 [#331] Cause:100 CallCtlCause:207 CiscoCause:31 FeatReason:9

Case 2:

Compare this with the case when CallCtlConnDisconnectedEv 3155211 is received after CiscoConferenceEndEv:

4283: Dec 01 16:00:51.655 AST %JTAPI-JTAPI-7-UNK:(P1-devuser2) 901024/1 CallCtlConnDisconnectedEv 3155211::2 [#406] Cause:100 CallCtlCause:100 CiscoCause:0 FeatReason:9


The causes for 3155211 disconnection should be the same in both cases since the disconnection occurs simply because 3155211 hung up.  It has nothing to do with conference.  So we are expecting CallCtlCause:100 CiscoCause:0 for both.


CiscoJtapi_1_04.log shows both cases.


Does anyone know the reason for this?


Thanks!

Derrick



2 Replies 2

derrickgunter
Level 5
Level 5

Any ideas out there?  Thanks.

Any ideas? Thanks.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: