IP Telephony - VCX
1752353 Members
5394 Online
108787 Solutions
New Discussion

Re: VCX CDR App

 
Justin_Goldberg
Valued Contributor

VCX CDR App

A customer has a PRI and some hunt groups setup.

 

They want to see a report of all calls coming into this site. 

 

I figured out the cdr app reports, but do I have to do this for each line?

 

In other words, can this app do a boolean query, like 'show calls (from OR to *6141) OR (from OR to *1212)', or would I need to have a report for each number/extension?

 

The calls come in to six different phone numbers, they are not DIDs, they all ring to the hunt groups.

 

I know it's a free and basic app, and afaik the only documentation we have is the help file, so any help would be greatly appreciated.

2 REPLIES 2
Inge_Suzzy
Frequent Advisor

Re: VCX CDR App

Taking advantage of this post, i want to know if the CDR App can give information about  trunk groups, I am searching in  their fields of the app but i don't see nothing related.

____________________________________
Ing. Angélica Susana Hernández Vázquez
System and Field Engineer
Justin_Goldberg
Valued Contributor

Re: VCX CDR App

I'm not sure how. Perhaps someone else can chime in on how to create a trunk group.

 

 

Here's all the fields from the vcx admin guide

 

 

 

Table 26   CDR Field Descriptions and Values

Tag Variable Description and Values Example

a0 VERSIONID Indicates version ID of the CDR.

For internal use only.

N/A

a4 SERVICETYPE Indicates service type used.

For internal use only.

N/A

a6 SOURCEIDENTIFIER Identifies the Source of the CDR,

which can only be the call

processor.

16 – call processor

16

a7 SESSIONID Indicates the session identifier.

For internal use only.

N/A

a8 TOTALNUMBERCALLATTEMPTSPERSES The total number of call attempts

made per session.

8

a9 SESSIONSEQUENCENUM Indicates when a session sequence

starts.

For internal use only.

N/A

b0 SESSIONSEQUENCEEND Indicates when a session sequence

ends.

For internal use only.

N/A

b1 ACCTAUTHENTICATIONFAILURECNT Account Auth Failure Count 1

b3 CALLINGPARTYE164ADDRESS An E.164 number from which the

call is placed to the access gateway.

Only the phone extension is

displayed.

304001

b6 CALLINGPARTYIPADDRESS Calling Party IP Address 9843771d

(continued)188 CHAPTER 6: CONFIGURING ACCOUNTING AND BILLING SUPPORT SERVERS

b9 CALLEDPARTYE164ADDRESS An E.164 number of the called

destination. Only the phone

extension is displayed.

333333

c2 CALLEDPARTYIPADDRESS Called Party Phone Number f2794398

d8 INGRESSGATEKEEPERIPADDRESS Call Processor IP Address 10.10.10.10

e4 CALLIDENTIFIER This is a globally unique call ID.

For internal use only.

N/A

e5 CALLTYPE Indicates the type of call placed.

1 – Phone to phone

2 – PC to phone

3 – Phone to PC

4 – Fax to fax

1

e6 CALLSTARTTIMEINGRESSGWACCESS Date and time when the call

accessed the ingress gateway.

20050414 19:54:07

e8 CALLSTARTTIMEANSWERED Date and time when the call is

answered. For example, receipt of

answer supervision until call

disconnect.

20050407 20:37:31

f0 CALLENDTIME Date and time when the call

disconnects. This is typically the

time when the billing stops.

20050414 19:54:07

f2 CALLDURATIONCONNECTTODISCONN Call duration in seconds from

connect to disconnect.

2

f3 CODECTYPE Audio CODEC type used for the

call, such as G.729, G.711, or

G.723.

For internal use only.

N/A

f4 CALLTERMINATIONCAUSE Reason for call disconnect or not

completed. Note that a value of

zero indicates that the call has not

been disconnected, or that no

disconnect reason was given. Only

one value can be provided as the

disconnect reason.

The codes listed come directly from

the all processor and correspond to

SIP error codes. You can find a

detailed list under SIP RFC 3261.

404

(continued)

Table 26   CDR Field Descriptions and Values

Tag Variable Description and Values ExampleManaging CDRs and Super CDRs 189

h7 SIGNALINGPROTOCOL Type of Signaling Protocol

For internal use only.

N/A

h8 PROTOCOLTRANSPORT Type of Protocol Transport

For internal use only.

N/A

j5 CALLMODEL Call Model

For internal use only.

N/A

j8 TRANSLATEDCALLEDPARTYE164ADDR Translated Called Party E.164

address

304001

l1 TEXTCALLIDENTIFIER SIP Text Call Identifier 80990ea1-8cab-d911-9410-a

c771eb4454b

o0 FEATURESUSED Idicates the feature used during a

call.

1 – Speed dial

2 – Call forward unconditional

4 – Call forward ring no answer

8 – Call forward busy

16 – Calling identity supression

4

o1 URIID URI ID, which is used for call

history.

74000001

o2 CALLEEFORWARDNUMBER Call Forwarded Number by Called

Party.

sip:5555000@10.10.10.10

o4 INBOUNDENDPOINTTYPE Indicates the type of inbound end

point.

2 – Gateway

6 – Terminal

9 – Call processor

10 – Others

11 – Unknown

12 – Redirect call processor

13 – IP Messaging server

6

o5 OUTBOUNDENDPOINTTYPE Indicates the type of outbound end

point.

2 – Gateway

6 – Terminal

9 – Call processor

10 – Others

11 – Unknown

12 – Redirect call processor

13 – IP Messaging server

2

(continued)

Table 26   CDR Field Descriptions and Values

Tag Variable Description and Values Example190 CHAPTER 6: CONFIGURING ACCOUNTING AND BILLING SUPPORT SERVERS

Viewing CDRs CDRs are stored on the accounting server.

To v ie w a CDR:

1 Log on an accounting server as cworks.

2 The CDRs are kept in the /opt/3com/VCX/acctxml/db/export directory.

The newest CDR is listed last and would look similar to this:

cdr200504111533531_c.xml

The file naming convention uses this format:

cdr<Year Month Date Hour Minutes ThreeExtraNumbers>_c.xml

A CDR looks similar to this:

<cdr_collection><cdr><a0>1</a0><a4>2</a4><a6>16</a6><a7></a7

><a8>1</a8><a9>1</a9><b1>1</b1><b3>304010</b3><b6>98437911</

b6><b9>304002</b9><c2>98437f49</c2><e5>1</e5><e6>20050411

20:32:22</e6><e8>20050411 20:32:22</e8><f0>20050411

20:32:43</f0><f2>21</f2><f3>0</f3><h7>1</h7><h8>0</h8><j5>2<

/j5><l1>008fbe79-36a9-d911-89b3-b82da66107be</l1><o0>4</o0><

o1>114000001</o1><o2>sip:8475555000@10.10.10.10</o2><o4>6</o

4><o5>2</o5><j8>8475555000</j8></cdr></cdr_collection>

o6 TRANSFEREDTOURI URI that a call was transferred to. 74000002

o7 TRANSFERINGPARTYURI URI of the transferring Transferring

Party URI

74000003

o8 REFERENCECALLID This is the reference text call ID for

when silent monitor and barge in is

used.

Not supported in this release.

N/A

o9 FORWARDINGPARTYURI Forwarding party URI.

Not supported in this release.

N/A

p1 GROUPNAME The name of a hunt group that was

defined when it was created.

1stShift

p2 CALLQUEUEEXITTIME The call queue exit time in a hunt

group - the time stamp filed.

Not supported in this release.

N/A

p3 MEMBEREXTENSION The member extension used in a

hunt group.