Created by: Roland Russwurm on 08-12-2009 08:43:21 AM Hi, we have an application that receives calls from CUCM by SIP-Trunk and the application also monitors phones using JTAPI. The information in the SIP invite does not include all information we need (e.g. last redirecting party, ...) and we want to get this from JTAPI but I find no way for a common call-id in the SIP Invite header and a CiscoCall in JTAPI. Is there a way to achieve this? Here some lines from the SIP INVITE header we receive which may be used to find the JTAPI call: INVITE sip:7778@192.168.5.231:5060 SIP/2.0 Call-Info: <sip:192.168.5.17:5060>;method="NOTIFY;Event=telephone-event;Duration=500" From: <sip:7998@192.168.5.17>;tag=b2b4ebca-d6b3-409d-848a-48964dd3afd6-21009858 Remote-Party-ID: <sip:7998@192.168.5.17>;party=calling;screen=yes;privacy=off User-Agent: Cisco-CUCM7.1 To: <sip:7778@192.168.5.231> Contact: <sip:7998@192.168.5.17:5060> Call-ID: fcac6a80-b1e109b2-1006-1105a8c0@192.168.5.17 Via: SIP/2.0/UDP 192.168.5.17:5060;branch=z9hG4bK10a01dc780bc
Subject: RE: Matching Call-ID between SIP-trunk and JTAPI Replied by: David Staudt on 08-12-2009 09:02:53 PM Having investigated this request previously, it appears there is no matchup between the SIP header info and the JTAPI callID.
Subject: RE: Matching Call-ID between SIP-trunk and JTAPI Replied by: Roland Russwurm on 18-01-2010 09:33:21 AM
Having investigated this request previously, it appears there is no matchup between the SIP header info and the JTAPI callID.
This is really a problem since the SIP header does not even include the information of the other party when recording a call. So we must get the information from JTAPI. This is an error prone procedure when there is no unique id in both APIs which can be used to match them. It would really help to get some more information about the call directly in the SIP header because then it would even be possible to record calls without monitoring the phone by JTAPI.
Subject: RE: Matching Call-ID between SIP-trunk and JTAPI Replied by: David Staudt on 21-01-2010 12:12:07 AM In discussing this with the UCM Product Management team, the good news is that it looks like enhancements in this area are already targeted for an upcoming release (not yet committed.)
Subject: RE: Matching Call-ID between SIP-trunk and JTAPI Replied by: Mohan Potluri on 27-01-2010 09:29:37 AM SIP header send to recorder has a CallReferenceID which can be used to find the call at agent. Applications can extract the callreferenceID from the header get the call using prov.getCall(int CallreferenceID). JTAPI application should have a call observer on the agent address to get the correct call.
Subject: RE: Matching Call-ID between SIP-trunk and JTAPI Replied by: David Staudt on 08-02-2012 01:36:58 PM UCM 8.5(1) now includes additional headers that should make matching calls much easier. From the ' Cisco Unified CM Silent Monitoring & Recording Specification.pdf' document available here (Cisco.com login with associated CDN membership or Developer Support contract required):
Cisco Unified CM Silent Monitoring & Recording Specification.pdf ---------------- When establishing the two recording calls to the recorder, Unified CM includes the following meta-data in the From header to the recorder: 1. A parameter indicating the party whose voice stream is forked (the near-end or the far- end) 2. The near-end party call leg reference CI (refCI) 3. Near-end party device name (nearEndDevice) The near-end party address is part of the From header. The following are the examples of the INVITES for the two recording calls where the near-end party has a directory number 3005 and recorder¿s address is 1111@10.89.81.52: For near-end party voice stream: INVITE sip:1111@10.89.81.52:5060 SIP/2.0 Via: SIP/2.0/TCP 10.89.81.56:5060;branch=z9hG4bK4ceac0a3 From: <sip:3005@10.89.81.56;x-nearend;x-refci=25471846;x- nearenddevice=SEP001B535CDC62>;tag=f13601c4-7f9b-4b9d-84d9- ba23306d0846-25471850 ...
Subject: RE: Matching Call-ID between SIP-trunk and JTAPI Replied by: Stefania Oliviero on 08-02-2012 11:31:08 AM
In discussing this with the UCM Product Management team, the good news is that it looks like enhancements in this area are already targeted for an upcoming release (not yet committed.)
Have you some information e about the upcoming release ? We are also interested in this feature.
Subject: RE: Matching Call-ID between SIP-trunk and JTAPI Replied by: Stefania Oliviero on 08-02-2012 11:31:08 AM
In discussing this with the UCM Product Management team, the good news is that it looks like enhancements in this area are already targeted for an upcoming release (not yet committed.)
Have you some information e about the upcoming release ? We are also interested in this feature.
Has there been any new information regarding ways to match the CTI events with the SIP call?
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:
