Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

call detail recording

Status
Not open for further replies.

ckhwi

Technical User
Apr 19, 2005
21
US
Switch is G3si R11
ECAS is version 2.4

Have x-port extension 1571 forwarded off-net to cell phone. When internal extension (7265) dials 1571, ECAS only shows one call record - when 1571 dials out to cell phone, not the incoming call from internal extension (7265). Both extensions are listed in intra-switch-cdr.

List trace shows complete call:

LIST TRACE

time data

12:47:09 Calling party station 7265 cid 0x12e
12:47:09 Calling Number & Name 7265
12:47:09 term station 1571 cid 0x12e
12:47:09 dial 91234567# route:HNPA|ARS
12:47:09 term trunk-group 5 cid 0x12e
12:47:09 call-forwarding 91234567#
12:47:09 route-pattern 3 preference 1 cid 0x12e
12:47:09 seize trunk-group 5 member 17 cid 0x12e
12:47:09 Calling Number & Name NO-CPNumber NO-CPName
12:47:10 Proceed trunk-group 5 member 17 cid 0x12e
12:47:16 Alert trunk-group 5 member 17 cid 0x12e
12:47:21 active trunk-group 5 member 17 cid 0x12e
12:48:52 idle station 7265 cid 0x12e

ECAS report: 06/22/2006 12:46:30 PM 0:01:30 1571 123-4567 MADISON, WI In-LATA1 86517 $0.10

When 1571 is dialed from outside the PBX, there are two call records shown - one incoming from outside number and the corresponding outbound call to the cell phone.

ECAS report: 06/21/2006 3:12:36 PM 0:00:24 1571 608-250-4665 MADISON, WI Incoming 83714 $0.00
06/21/2006 3:12:36 PM 0:00:24 1571 123-4567 MADISON, WI In-LATA1 86502 $0.05

Other internal to internal calls show up in report:

LIST TRACE

time data

12:59:31 tone receiver 01A0201 cid 0x219
12:59:31 active station 7265 cid 0x219
12:59:35 dial 7114
12:59:35 ring hunt-group 31 cid 0x219
12:59:36 active station 4111 cid 0x219
13:02:50 idle station 7265 cid 0x219

ECAS report: 06/22/2006 12:58:48 PM 0:03:12 7265 4111 Internal $0.00

Anyone else notice this or have an idea why the incoming portion isn't registering on the internal to internal call? Would really like to see who is calling internally.

Thanks.

 
Internal calls do not generate a cdr record by design.

-CL
 
This is what I found researching Avaya documentation for CDR and what is programmed in system parameters CDR:

Call Splitting
Call splitting keeps track of calls where more than two parties are involved. These can be calls that are transferred, conferenced, or where an attendant becomes involved. If you have call splitting activated and any of these situations arise, CDR produces a separate record for each new party on the call.

Incoming trunk call splitting (ITCS)
If incoming trunk call splitting is enabled, CDR starts a new record whenever an incoming trunk call is conferenced or transferred. If ITCS is enabled and an incoming trunk call is conferenced or transferred to a local extension that is optioned for Intraswitch CDR, the call produces an incoming trunk call record. It does not produce an Intraswitch record.

Intraswitch CDR
If a station is optioned for Intraswitch CDR, and ITCS is also enabled, ITCS overrides Intraswitch CDR. That is, incoming trunk calls involving the station produce trunk call records, not Intraswitch CDR records.

Some calls may seem to be intraswitch CDR calls, but actually result in trunk calls. For example, a station-to-station call to an extension that is forwarded to an outgoing trunk produces only a trunk CDR record, regardless of whether or not either station has intraswitch CDR assigned.

We have ITCS turned on so that is why we didn't get the intraswitch call record for the station-to-station call to the extension forwarded off-net.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top