[cisco-voip] Conference call CDR analysis

[Ahmed Elnagar]

I am not so aware of CDRs but I remember that billing software developer
depends on the field of bridge ID "b00203202002 in your case" to
correlate conference CDRS.

 

 Best Regards;

  Ahmed Elnagar

  Senior Network PS Engineer

  Mob: +2019-0016211

  CCIE#24697 (Voice)

  

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of dev
Sent: Monday, October 11, 2010 7:13 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Conference call CDR analysis

 

Hi CDR experts out there..

 

I highly appreciate your input on this.

 

I am trying to understand the call scenario that took place here. Can
you help clarify it for me. My assumption is that ext 8024 being the
conference controller here sets up a conference call between the two
PSTN numbers then hung up out of the conference after 1 minute. Then
called the same PSTN mobile number again. Am I correct?

 

If yes, my understanding is that if a conference is left with two
parties only, they get joined together. Why isn't it happening here?

 

I have attached the CDR for reference.. Thanks for helping

 

 

 

globalcallid_callid

datetimeconnect 

callingpartynumber

finalcalledpartynumber

duration

Lastredirectdn

,origlegcallidentifier

,destlegidentifier,

joinonbehalfof

,origcallterminationonbehalfof

,destcallterminationonbehalfof

comment

241980

2010-09-05 13:33:12.000

8024

90101917777

1

90101917777

49364529

49364530

0

4

4

 

241983

2010-09-05 13:33:59.000

8024

900962779260050

0

900962779260050

49364559

49364560

0

4

4

 

241980

2010-09-05 13:34:40.000

8024

b00203202002

1

8024

49364529

49364572

4

12

0

ConfControllerDn=8024;ConfControllerDeviceName=SEP0004F2E66609;ConfReque
storDn=8024;ConfRequestorDeviceName=SEP0004F2E66609

241980

2010-09-05 13:34:40.000

90101917777

b00203202002

20

8024

49364530

49364573

4

12

4

ConfControllerDn=8024;ConfControllerDeviceName=SEP0004F2E66609;ConfReque
storDn=8024;ConfRequestorDeviceName=SEP0004F2E66609

241980

2010-09-05 13:34:40.000

900962779260050

b00203202002

20

8024

49364560

49364574

4

12

0

ConfControllerDn=8024;ConfControllerDeviceName=SEP0004F2E66609;ConfReque
storDn=8024;ConfRequestorDeviceName=SEP0004F2E66609

241989

2010-09-05 13:36:38.000

8024

90101917777

18

90101917777

49364596

49364597

0

12

0

 

 

Disclaimer: NOTICE The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Raya will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any malicious code or virus being passed on. Views expressed in this communication are not necessarily those of Raya.If you have received this message in error, please notify the sender immediately by email, facsimile or telephone and return and/or destroy the original message. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101011/fe26cbf4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1801 bytes
Desc: image001.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101011/fe26cbf4/attachment.jpg>