cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
569
Views
0
Helpful
1
Replies

External call transfer not showing correct information about the originator in MediaSense, but showing in the CDR info

jesus.menendez
Level 1
Level 1

When we transfer a call from an external trunk and we get the list of sessions, we noticed that the last part of the transfer, when the external number is connected to the final destination, it is not showing the source xrefCi anymore

We can see that data using the CDR information from the Cisco switch, so we were wondering why MediaSense doesn't work it out correctly

This is the session data from that last transfer..

{

    "responseMessage": "Success: Your request was successfully completed.",

    "responseCode": 2000,

    "responseBody": {

        "sessions": [

            {

                "sessionState": "CLOSED_NORMAL",

                "callControllerType": "Cisco-CUCM",

                "sessionId": "12414daf6236051",

                "urls": {

                    "httpUrl": "https://192.168.46.17:8446/recordedMedia/oramedia/mp4/12414daf6236051.mp4",

                    "rtspUrl": "rtsp://192.168.46.17/archive/12414daf6236051",

                    "mp4Url": "https://192.168.46.17:8446/recordedMedia/oramedia/mp4/12414daf6236051.mp4",

                    "wavUrl": "https://192.168.46.17:8446/recordedMedia/oramedia/wav/12414daf6236051.wav"

                },

                "sessionStartDate": 1433166558957,

                "tracks": [

                    {

                        "trackStartDate": 1433166558957,

                        "trackDuration": 7021,

                        "codec": "PCMA",

                        "downloadUrl": "https://192.168.46.17:8446/mma/ExportRaw?recording=12414daf6236051-TRACK1",

                        "trackNumber": 1,

                        "trackMediaType": "AUDIO",

                        "participants": [

                            {

                                "participantStartDate": 1433166558957,

                                "deviceRef": "+442037727258",

                                "isConference": false,

                                "xRefCi": "23469024",

                                "participantDuration": 7021,

                                "deviceId": "SEPB83861x1669A3"

                            }

                        ]

                    },

                    {

                        "trackStartDate": 1433166558957,

                        "trackDuration": 7021,

                        "codec": "PCMA",

                        "downloadUrl": "https://192.168.46.17:8446/mma/ExportRaw?recording=12414daf6236051-TRACK0",

                        "trackNumber": 0,

                        "trackMediaType": "AUDIO",

                        "participants": [

                            {

                                "participantStartDate": 1433166558957,

                                "deviceRef": "+442037727258",

                                "isConference": false,

                                "xRefCi": "23469024",

                                "participantDuration": 7021,

                                "deviceId": "SEPB838611669A3"

                            }

                        ]

                    }

                ],

                "sessionDuration": 7021,

                "callControllerIP": "192.168.46.14"

            },

        

        ]

    }

}

And the CDR data we get from the xrefCI 23469024

1,1,58050,23469021,1433166539,1,0,808364224,"+442037727259","",0,393216,4,808364224,27120,4,20,0,0,0,0,0,0,"0","0",23469024,1,0,841918656,"+442037727258","+442037727258","rphone9",0,393216,4,841918656,17940,4,20,0,0,0,0,0,0,"0","0",1433166545,1433166558,"+442037727258","70c32c1b-051c-4745-abb1-65e5fa50e4a6","Line-PT","Line-PT","Line-PT","Line-PT",13,"SEPB8386116697F","SEPB838611669A3",10,10,0,0,0,0,0,"StandAloneCluster",0,"","",0,"",3,3,0,0,64,64,"","","","192.168.46.48","192.168.46.50",0,0,0,0,0,0,0,0,0,0,0,0,0,"",0,"",0,0,0,"","",2,"","","","","","","","",0,0,"","","","","","","","",0,0,0,"+442037727258","+442037727258","+442037727258",""

1,1,58047,23469011,1433166558,1,23469011,305047744,"+447930984085","",0,0,4,305047744,20512,2,20,0,0,0,0,0,0,"0","0",23469024,1,0,841918656,"+442037727258","+442037727258","rphone9",0,16,4,841918656,17940,2,20,0,0,0,0,0,0,"0","0",1433166558,1433166565,"+442037727259","7bd1d1f4-57b5-4bfc-b8be-31ba43dc1939","Line-PT","","Line-PT","Line-PT",7,"LON-SIPT-to-CUBE-01","SEPB838611669A3",10,12,0,10,0,4,0,"StandAloneCluster",10,"","",0,"",2,3,0,0,64,64,"","","","192.168.46.18","192.168.46.50",0,0,0,0,0,0,0,0,0,0,0,0,1,"C0711F21079B11E5B7839B1AB48EE091",0,"",0,0,0,"","",2,"","","","","","","","",0,0,"","","","","","","","",0,0,0,"+442037727258","+442037727258","+442037727259",""

Basically we create two entries and we were looking for a way to choose which one belongs to the session that we can see in MediaSense

1 Reply 1

nitinsi
Cisco Employee
Cisco Employee

Hi Jesus M,

As this case is of BiB forking and in case of BiB forking, MediaSense always creates new session after call transfer. Let’s take one example to explain the correlation between the xRefCI fields.

A – Calls -> B                            (xRefCI-A, xRefCI-B)

B – Consultive Call -> C        (xRefCI-B,  xRefCI-C)

A – B Transferred Call -> C (xRefCI-A’, xRefCI-C)

So xRefCI of originator changes from xRefCI-A to xRefCI-A’ because of a transfer in the final call. Which is represented in JSON as well.

Same thing is represented by CDR as well. For same XREFCI, you getting two entries in CDR.

Moreover, XRefCI are managed by CUCM, and MediaSense just receive them from SIP signaling.

You can make make a search combination of XRefCI and the right extension (other party) to get the exact recording you wish to get hold of. You can try this search from our Search & Play portal as well.


Let us know if you face any issue. If you do, we will check this again at out end after reproducing this scenario.



Thanks

Nitin Singh

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: