08-14-2014 04:52 AM
Hello - I am struggling to find the direction of an on-going call, The scenarios is
1. Made a call from Terminal1's DN1 to Terminal2's DN2
2. Started my JTAPI application and added Observers for Terminal1& Terminal2
3. Receiving CallEvents and processing, but not setting Direction properly for call on Terminal2's DN2
JTAPI version: 6.1(2.1000)-12
CUCM: 9.1
Is there any sample application or doc that can direct me in right direction which can provide all the required information of on-going call like direction, current state(state i can get from events but). Tried on CiscoConnection#getReason, but this getting different results on different scenarios.For instance, after adding monitors, making an outbound call getting reason=99, but for the same call, if I add monitor on-going call getting reason=1
Basically I would like to Set the Correct State, direction and CLI on on-going calls
Thanks
Best,
Chiru
Solved! Go to Solution.
08-15-2014 04:01 PM
May be I did not get the issue. Can you explain what you mean by direction of the call?
If user's phone is 600018, in this call where CallingAddress is 600018 and CalledAddress is 600019, user made the call. Only called parties can answer the call. From user (600018) perspective the call is an out bound call to called party (600019).
08-14-2014 08:45 AM
The state of the call can be determined by the state of the terminal connections for Terminal1 and terminal2.
callControlCall.getCallingAddress() and callControlCall.getCalledAddress() will give the calling and called parties (direction) of the call.
08-14-2014 09:50 AM
Thanks, will give it a try
08-14-2014 09:53 AM
Also, what would be right class or interface to fetch all call data mentioned like direction, state, caller & called parteis ? Will CallControlCall useful or do I need to query specific api for specific data ?
08-15-2014 03:43 AM
Hi mohan - I was not able to determin the direction of a call with callControlCall, am I missing something here. I am getting DN numbers on callingAddress & calledAddress. Like said I need to determine if user made an outbound call or answered an Incoming call. parsting out put of test scenario if this can be helpful to you to analyse
Made a call from 600018(on SEPB000B4D82DD8) to 600019, and answered on (SEPB000B4D82AB7)
Incoming:
************
Terminal Event: 1073745924 - CiscoTermOutOfServiceEv
Terminal Event: 1073745923 - CiscoTermInServiceEv
Address Event: 1073750018Address: null
CiscoAddrInServiceEv - Address: 600021
Address Event: 1073750019Address: null
Address Event: 1073750018Address: null
CiscoAddrInServiceEv - Address: 600020
Address Event: 1073750019Address: null
CallEvent: CallActiveEv callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: ConnCreatedEv callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: ConnConnectedEv callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: CallCtlConnEstablishedEv callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: TermConnCreatedEv SEPB000B4D82AB7 callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
State of Call: 88
CallEvent: TermConnActiveEv SEPB000B4D82AB7 callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: CallCtlTermConnTalkingEv SEPB000B4D82AB7 callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: ConnCreatedEv callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: ConnConnectedEv callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: CallCtlConnEstablishedEv callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
Address Event: 1073750018Address: [Ljavax.telephony.Connection;@794baafe
CiscoAddrInServiceEv - Address: 600019
Address Event: 1073750018Address: null
CiscoAddrInServiceEv - Address: 600021
Address Event: 1073750018Address: null
CiscoAddrInServiceEv - Address: 600020
Outgoing:
************
Incoming:
************
Outgoing:
************
Terminal Event: 1073745924 - CiscoTermOutOfServiceEv
Terminal Event: 1073745923 - CiscoTermInServiceEv
Address Event: 1073750018Address: null
CiscoAddrInServiceEv - Address: 600017
Address Event: 1073750018Address: null
CiscoAddrInServiceEv - Address: 600018
CallEvent: CallActiveEv callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: ConnCreatedEv callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: ConnCreatedEv callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: ConnConnectedEv callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: CallCtlConnEstablishedEv callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: TermConnCreatedEv SEPB000B4D82DD8 callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
State of Call: 88
CallEvent: TermConnActiveEv SEPB000B4D82DD8 callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: CallCtlTermConnTalkingEv SEPB000B4D82DD8 callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: ConnConnectedEv callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
CallEvent: CallCtlConnEstablishedEv callControlCall#getCallingAddress: 600018 callControlCall#getCalledAddress: 600019
08-15-2014 04:01 PM
May be I did not get the issue. Can you explain what you mean by direction of the call?
If user's phone is 600018, in this call where CallingAddress is 600018 and CalledAddress is 600019, user made the call. Only called parties can answer the call. From user (600018) perspective the call is an out bound call to called party (600019).
08-19-2014 03:41 AM
Thanks mohan, that helped, how ever yet to try on shared line scenario.
08-18-2014 11:12 PM
CallAlerting event & CallInitiated event will help u to get direction of the call.
Regards,
Umesh
08-19-2014 03:43 AM
I am adding observers on an on-going calls, so CallAlerting & CallInitiated event wont be availble Umesh
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide