Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Create a new article
819
Views
0
Helpful
0
Comments

Call Correlation ID (ccid) Missing From getSessionsByDeviceRef

cdnadmin
Level 11
Level 11

on ‎01-24-2014 05:57 PM

This document was generated from CDN thread

Created by: Phi Yim on 18-10-2013 02:09:31 AM
We’ve had the requirement change for reporting that we store the Call Correlation ID (ccid) whenever a recording is paused, instead of the session id. According to the API we should get that back from getSessionsByDeviceRef but I don’t see it in the data returned to us. Do you know how it’s possible to get that?  The sample output received from Cisco says that it should show up after the callController iP.  What’s not clear though is should this value be present for CUCM/end deivce BiB configurations, or only for cube forking?
 
                "tags": [ … ],
                "sessionState": "CLOSED_NORMAL",
                "callControllerType": "Cisco-CUCM",
                "sessionId": "70141bded0cde2",
                "urls": {
                    "httpUrl": "http://10.131.144.149:8081/recordedMedia/oramedia/mp4/70141bded0cde2.mp4",
                    "rtspUrl": "rtsp://10.131.144.149/archive/70141bded0cde2"
                },
                "sessionStartDate": 1381870931491,
                "tracks": [
                    {
                        "trackStartDate": 1381870931491,
                        "trackDuration": 77638,
                        "codec": "PCMU",
                        "downloadUrl": "http://10.131.144.149:8081/mma/ExportRaw?recording=70141bded0cde2-TRACK1",
                        "trackNumber": 1,
                        "trackMediaType": "AUDIO",
                        "participants": [
                            {
                                "participantStartDate": 1381870931491,
                                "deviceRef": "7145856569",
                                "isConference": false,
                                "xRefCi": "34876351",
                                "participantDuration": 77638,
                                "deviceId": "CS_IRV_Dev_CS"
                            }
                        ]
                    },
                    {
                        "trackStartDate": 1381870931491,
                        "trackDuration": 77638,
                        "codec": "PCMU",
                        "downloadUrl": "http://10.131.144.149:8081/mma/ExportRaw?recording=70141bded0cde2-TRACK0",
                        "trackNumber": 0,
                        "trackMediaType": "AUDIO",
                        "participants": [
                            {
                                "participantStartDate": 1381870931491,
                                "deviceRef": "17501",
                                "isConference": false,
                                "xRefCi": "34876352",
                                "participantDuration": 77638,
                                "deviceId": "USATLAS002"
                            }
                        ]
                    }
                ],
                "sessionDuration": 77638,
                "callControllerIP": "10.131.144.133"
            }
 
Sample output given by Cisco:
{"responseMessage":"Success: Your request was successfully completed.","responseCode":2000,"responseBody":{"sessions":[{"sessionState":"CLOSED_NORMAL","callControllerType":"direct","sessionId":"213d5b3cbe3c1","urls":{"httpUrl":"http://14.104.1.71:8081/recordedMedia/oramedia/mp4/213d5b3cbe3c1.mp4","rtspUrl":"rtsp://14.104.1.71/archive/213d5b3cbe3c1"},"sessionStartDate":1363035340470,"tracks":[{"trackStartDate":1363035340470,"trackDuration":10376,"codec":"PCMU","downloadUrl":"http://14.104.1.71:8081/mma/ExportRaw?recording=213d5b3cbe3c1-TRACK0","trackNumber":0,"trackMediaType":"AUDIO","participants":[{"participantStartDate":1363035340470,"deviceRef":"1004","isConference":false,"participantDuration":10376}]}],"sessionDuration":10376,"callControllerIP":"14.104.1.21","ccid":"0115028864-0000065536-0000000002-0352413710C3"},{"sessionState":"CLOSED_NORMAL","callControllerType":"direct","sessionId":"113d5b23698f1","urls":{"rtspUrl":"rtsp://14.104.1.71/archive/113d5b23698f1"},"sessionStartDate":1363033680786,"tracks":[{"trackStartDate":1363033680786,"trackDuration":29712,"codec":"PCMU","downloadUrl":"http://14.104.1.71:8081/mma/ExportRaw?recording=113d5b23698f1-TRACK0","trackNumber":0,"trackMediaType":"AUDIO","participants":[{"participantStartDate":1363033680786,"deviceRef":"1004","isConference":false,"participantDuration":29712}]}],"sessionDuration":29712,"callControllerIP":"14.104.1.21","ccid":"0684898048-0000065536-0000000001-0352413710C3"}]}}

Subject: Re: New Message from Phi Yim in MediaSense (MediaSense) - Technical Discuss
Replied by: Michael Benenson on 18-10-2013 02:57:39 AM
Call Correlation ID (CCID)  is present only for the call that id recorded using media forking from CUBE
In this case, call is recorded from the forking on phone
> "callControllerType": "Cisco-CUCM",
So, there is no CCID in the event


Thanks
--------

Michael Benenson

From: Cisco Developer Community Forums <cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>>
Reply-To: "cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>" <cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>>
Date: Friday, October 18, 2013 12:09 AM
To: "cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>" <cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>>
Subject: New Message from Phi Yim in MediaSense (MediaSense) - Technical Discussion: Call Correlation ID (ccid) Missing From getSessionsByDeviceRef

Phi Yim has created a new message in the forum "Technical Discussion": -------------------------------------------------------------- We’ve had the requirement change for reporting that we store the Call Correlation ID (ccid) whenever a recording is paused, instead of the session id. According to the API we should get that back from getSessionsByDeviceRef but I don’t see it in the data returned to us. Do you know how it’s possible to get that?  The sample output received from Cisco says that it should show up after the callController iP.  What’s not clear though is should this value be present for CUCM/end deivce BiB configurations, or only for cube forking?

                "tags": [ … ],
                "sessionState": "CLOSED_NORMAL",
                "callControllerType": "Cisco-CUCM",
                "sessionId": "70141bded0cde2",
                "urls": {
                    "httpUrl": "http://10.131.144.149:8081/recordedMedia/oramedia/mp4/70141bded0cde2.mp4",
                    "rtspUrl": "rtsp://10.131.144.149/archive/70141bded0cde2"
                },
                "sessionStartDate": 1381870931491,
                "tracks": [
                    {
                        "trackStartDate": 1381870931491,
                        "trackDuration": 77638,
                        "codec": "PCMU",
                        "downloadUrl": "http://10.131.144.149:8081/mma/ExportRaw?recording=70141bded0cde2-TRACK1",
                        "trackNumber": 1,
                        "trackMediaType": "AUDIO",
                        "participants": [
                            {
                                "participantStartDate": 1381870931491,
                                "deviceRef": "7145856569",
                                "isConference": false,
                                "xRefCi": "34876351",
                                "participantDuration": 77638,
                                "deviceId": "CS_IRV_Dev_CS"
                            }
                        ]
                    },
                    {
                        "trackStartDate": 1381870931491,
                        "trackDuration": 77638,
                        "codec": "PCMU",
                        "downloadUrl": "http://10.131.144.149:8081/mma/ExportRaw?recording=70141bded0cde2-TRACK0",
                        "trackNumber": 0,
                        "trackMediaType": "AUDIO",
                        "participants": [
                            {
                                "participantStartDate": 1381870931491,
                                "deviceRef": "17501",
                                "isConference": false,
                                "xRefCi": "34876352",
                                "participantDuration": 77638,
                                "deviceId": "USATLAS002"
                            }
                        ]
                    }
                ],
                "sessionDuration": 77638,
                "callControllerIP": "10.131.144.133"
            }

Sample output given by Cisco:
{"responseMessage":"Success: Your request was successfully completed.","responseCode":2000,"responseBody":{"sessions":[{"sessionState":"CLOSED_NORMAL","callControllerType":"direct","sessionId":"213d5b3cbe3c1","urls":{"httpUrl":"http://14.104.1.71:8081/recordedMedia/oramedia/mp4/213d5b3cbe3c1.mp4","rtspUrl":"rtsp://14.104.1.71/archive/213d5b3cbe3c1"},"sessionStartDate":1363035340470,"tracks":[{"trackStartDate":1363035340470,"trackDuration":10376,"codec":"PCMU","downloadUrl":"http://14.104.1.71:8081/mma/ExportRaw?recording=213d5b3cbe3c1-TRACK0","trackNumber":0,"trackMediaType":"AUDIO","participants":[{"participantStartDate":1363035340470,"deviceRef":"1004","isConference":false,"participantDuration":10376}]}],"sessionDuration":10376,"callControllerIP":"14.104.1.21","ccid":"0115028864-0000065536-0000000002-0352413710<https://csone.my.salesforce.com/apex/XRightPaneSearch?autoSearch=0352413710>C3<http://www-tac.cisco.com/Teams/ks/c3/casekwery.php?Case=0352413710><https://techzone.cisco.com/t5/Cisco-MediaSense/Media-Sense-Poster-Tool-Cheat-Sheet-for-API-calls-to-Media-Sense/ta-p/221428>"},{"sessionState":"CLOSED_NORMAL","callControllerType":"direct","sessionId":"113d5b23698f1","urls":{"rtspUrl":"rtsp://14.104.1.71/archive/113d5b23698f1"},"sessionStartDate":1363033680786,"tracks":[{"trackStartDate":1363033680786,"trackDuration":29712,"codec":"PCMU","downloadUrl":"http://14.104.1.71:8081/mma/ExportRaw?recording=113d5b23698f1-TRACK0","trackNumber":0,"trackMediaType":"AUDIO","participants":[{"participantStartDate":1363033680786,"deviceRef":"1004","isConference":false,"participantDuration":29712}]}],"sessionDuration":29712,"callControllerIP":"14.104.1.21","ccid":"0684898048-0000065536-0000000001-0352413710<https://csone.my.salesforce.com/apex/XRightPaneSearch?autoSearch=0352413710>C3<http://www-tac.cisco.com/Teams/ks/c3/casekwery.php?Case=0352413710><https://techzone.cisco.com/t5/Cisco-MediaSense/Media-Sense-Poster-Tool-Cheat-Sheet-for-API-calls-to-Media-Sense/ta-p/221428>"}]}}
--
To respond to this post, please click the following link: http://developer.cisco.com/web/mediasense/community/-/message_boards/view_message/20350803 or simply reply to this email.

Subject: Re: New Message from Phi Yim in MediaSense (MediaSense) - Technical Discuss
Replied by: Michael Benenson on 18-10-2013 02:57:37 AM
Call Correlation ID (CCID)  is present only for the call that id recorded using media forking from CUBE
In this case, call is recorded from the forking on phone
> "callControllerType": "Cisco-CUCM",
So, there is no CCID in the event


Thanks
--------

Michael Benenson

From: Cisco Developer Community Forums <cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>>
Reply-To: "cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>" <cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>>
Date: Friday, October 18, 2013 12:09 AM
To: "cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>" <cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>>
Subject: New Message from Phi Yim in MediaSense (MediaSense) - Technical Discussion: Call Correlation ID (ccid) Missing From getSessionsByDeviceRef

Phi Yim has created a new message in the forum "Technical Discussion": -------------------------------------------------------------- We’ve had the requirement change for reporting that we store the Call Correlation ID (ccid) whenever a recording is paused, instead of the session id. According to the API we should get that back from getSessionsByDeviceRef but I don’t see it in the data returned to us. Do you know how it’s possible to get that?  The sample output received from Cisco says that it should show up after the callController iP.  What’s not clear though is should this value be present for CUCM/end deivce BiB configurations, or only for cube forking?

                "tags": [ … ],
                "sessionState": "CLOSED_NORMAL",
                "callControllerType": "Cisco-CUCM",
                "sessionId": "70141bded0cde2",
                "urls": {
                    "httpUrl": "http://10.131.144.149:8081/recordedMedia/oramedia/mp4/70141bded0cde2.mp4",
                    "rtspUrl": "rtsp://10.131.144.149/archive/70141bded0cde2"
                },
                "sessionStartDate": 1381870931491,
                "tracks": [
                    {
                        "trackStartDate": 1381870931491,
                        "trackDuration": 77638,
                        "codec": "PCMU",
                        "downloadUrl": "http://10.131.144.149:8081/mma/ExportRaw?recording=70141bded0cde2-TRACK1",
                        "trackNumber": 1,
                        "trackMediaType": "AUDIO",
                        "participants": [
                            {
                                "participantStartDate": 1381870931491,
                                "deviceRef": "7145856569",
                                "isConference": false,
                                "xRefCi": "34876351",
                                "participantDuration": 77638,
                                "deviceId": "CS_IRV_Dev_CS"
                            }
                        ]
                    },
                    {
                        "trackStartDate": 1381870931491,
                        "trackDuration": 77638,
                        "codec": "PCMU",
                        "downloadUrl": "http://10.131.144.149:8081/mma/ExportRaw?recording=70141bded0cde2-TRACK0",
                        "trackNumber": 0,
                        "trackMediaType": "AUDIO",
                        "participants": [
                            {
                                "participantStartDate": 1381870931491,
                                "deviceRef": "17501",
                                "isConference": false,
                                "xRefCi": "34876352",
                                "participantDuration": 77638,
                                "deviceId": "USATLAS002"
                            }
                        ]
                    }
                ],
                "sessionDuration": 77638,
                "callControllerIP": "10.131.144.133"
            }

Sample output given by Cisco:
{"responseMessage":"Success: Your request was successfully completed.","responseCode":2000,"responseBody":{"sessions":[{"sessionState":"CLOSED_NORMAL","callControllerType":"direct","sessionId":"213d5b3cbe3c1","urls":{"httpUrl":"http://14.104.1.71:8081/recordedMedia/oramedia/mp4/213d5b3cbe3c1.mp4","rtspUrl":"rtsp://14.104.1.71/archive/213d5b3cbe3c1"},"sessionStartDate":1363035340470,"tracks":[{"trackStartDate":1363035340470,"trackDuration":10376,"codec":"PCMU","downloadUrl":"http://14.104.1.71:8081/mma/ExportRaw?recording=213d5b3cbe3c1-TRACK0","trackNumber":0,"trackMediaType":"AUDIO","participants":[{"participantStartDate":1363035340470,"deviceRef":"1004","isConference":false,"participantDuration":10376}]}],"sessionDuration":10376,"callControllerIP":"14.104.1.21","ccid":"0115028864-0000065536-0000000002-0352413710<https://csone.my.salesforce.com/apex/XRightPaneSearch?autoSearch=0352413710>C3<http://www-tac.cisco.com/Teams/ks/c3/casekwery.php?Case=0352413710><https://techzone.cisco.com/t5/Cisco-MediaSense/Media-Sense-Poster-Tool-Cheat-Sheet-for-API-calls-to-Media-Sense/ta-p/221428>"},{"sessionState":"CLOSED_NORMAL","callControllerType":"direct","sessionId":"113d5b23698f1","urls":{"rtspUrl":"rtsp://14.104.1.71/archive/113d5b23698f1"},"sessionStartDate":1363033680786,"tracks":[{"trackStartDate":1363033680786,"trackDuration":29712,"codec":"PCMU","downloadUrl":"http://14.104.1.71:8081/mma/ExportRaw?recording=113d5b23698f1-TRACK0","trackNumber":0,"trackMediaType":"AUDIO","participants":[{"participantStartDate":1363033680786,"deviceRef":"1004","isConference":false,"participantDuration":29712}]}],"sessionDuration":29712,"callControllerIP":"14.104.1.21","ccid":"0684898048-0000065536-0000000001-0352413710<https://csone.my.salesforce.com/apex/XRightPaneSearch?autoSearch=0352413710>C3<http://www-tac.cisco.com/Teams/ks/c3/casekwery.php?Case=0352413710><https://techzone.cisco.com/t5/Cisco-MediaSense/Media-Sense-Poster-Tool-Cheat-Sheet-for-API-calls-to-Media-Sense/ta-p/221428>"}]}}
--
To respond to this post, please click the following link: http://developer.cisco.com/web/mediasense/community/-/message_boards/view_message/20350803 or simply reply to this email.
0 Helpful
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:

Quick Links
Discussions
Customers Also Viewed These Support Documents