Avaya Solution & Interoperability Test Lab

Application Notes for Metropolis ProfitWatch Call Accounting

System with Avaya Aura Communication Manager Issue
1.0

Abstract
These Application Notes describe the steps required to integrate the Metropolis ProfitWatch
Call Accounting System with Avaya Aura Communication Manager.
Metropolis
ProfitWatch Call Accounting System captures call records from Avaya Aura Communication
Manager using a Call Detail Record (CDR) link with Avaya Reliable Session Protocol (RSP)
enabled for reliable transmission of call records. In turn, ProfitWatch processes the call
records and generates detailed reports.
Information in these Application Notes has been obtained through DevConnect compliance
testing and additional technical discussions. Testing was conducted via the DevConnect
Program at the Avaya Solution and Interoperability Test Lab.

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

1 of 21
Metro-PW-ACM

1. Introduction
These Application Notes describe the steps required to integrate the Metropolis ProfitWatch Call
Accounting System with Avaya Aura Communication Manager. Metropolis ProfitWatch Call
Accounting System captures call records from Avaya Aura Communication Manager using a Call
Detail Record (CDR) link with Avaya Reliable Session Protocol (RSP) enabled for reliable
transmission of call records. In turn, ProfitWatch processes the call records and generates detailed
reports.

2. General Test Approach and Test Results

DevConnect Compliance Testing is conducted jointly by Avaya and DevConnect members. The
jointly-defined test plan focuses on exercising APIs and/or standards-based interfaces pertinent to
the interoperability of the tested products and their functionalities. DevConnect Compliance Testing
is not intended to substitute full product performance or feature testing performed by DevConnect
members, nor is it to be construed as an endorsement by Avaya of the suitability or completeness of
a DevConnect members solution.
This section describes the compliance testing used to verify interoperability of Metropolis
ProfitWatch Call Accounting System with Avaya Aura Communication Manager. This section
covers the general test approach and the test results. The testing covered feature and serviceability
test cases. The feature testing covered the ability of ProfitWatch to capture and process call records.
The call records captured and displayed by ProfitWatch were compared for accuracy to the call
records received by an Avaya Definity Reliable Data Transport Tool, CDR test tool. Call records for
various call types were generated, including internal calls, inbound and outbound trunk calls,
including PSTN calls, transferred calls, and conference calls. Calls were established using H.323
and SIP telephones.
The serviceability testing focused on the ability of ProfitWatch to recover from adverse conditions
such as loss of network connectivity. With the use Avaya RSP, call records that were generated
while ProfitWatch was disconnected from the network were not lost.

2.1. Interoperability Compliance Testing

Interoperability compliance testing covered the following features and functionality:

Sending call records from Communication Manager to ProfitWatch for various call types,
including internal calls, inbound and outbound trunks, including PSTN calls, transferred
calls, and conference calls
Calls were established using H.323 and SIP telephones
Trunk calls traversed ISDN-PRI, H.323, and SIP trunks
Call records were captured and displayed on ProfitWatch
Call records were processed by ProfitWatch, which generated detailed reports
Proper system recovery after loss of network connectivity and power loss

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

2 of 21
Metro-PW-ACM

2.2. Test Results

ProfitWatch passed compliance testing with the following observation(s):

Avaya Aura Communication Manager generates additional call records for calls that
involve SIP telephones, because SIP calls are routed over a SIP trunk. The called and calling
parties of these call records are usually the same and contain the SIP extension.

2.3. Support
For technical support on Metropolis ProfitWatch Call Accounting System, contact Metropolis
Customer Service by phone, through their website, or email.
Phone:
Web:
Email:

(954) 414-2900 x32

http://www.metropolis.com/support.html
support2012@metropolis.com

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

3 of 21
Metro-PW-ACM

3. Reference Configuration
Figure 1 illustrates the configuration used for the compliance test. In the sample configuration, two
sites, Sites A and B, are connected via H.323 and SIP trunks. ProfitWatch only monitors the calls at
Site A. Site B is primarily used to generate inter-site traffic across the H.323 and SIP trunks.
Site A has Avaya S8800 Servers running Avaya Aura Communication Manager with an Avaya
G650 Media Gateway. Site A also includes Avaya Aura Session Manager and Avaya 9600 Series
H.323 and SIP Telephones. In addition, Site A has connectivity to the PSTN. The configuration at
Site B is similar to Site A and also uses the Session Manager at Site A. ProfitWatch connects via the
LAN and establishes a CDR link to Communication Manager at Site A.
Site A

Site B

Avaya Aura Session Manager

Avaya Aura System Manager

LAN

Avaya S 8800 Server running

Avaya Aura Communication Manager

Avaya S 8300 Server running

Avaya Aura Communication
Manager with G 450 Media Gateway

PSTN
Avaya 9600 Series H.323
and SIP Telephones

Avaya G650 Media Gateway

Avaya 9600 Series SIP

and H.323 Telephones

Metropolis ProfitWatch
Call Accounting System

Figure 1: Metropolis ProfitWatch Call Accounting System with Avaya Aura Communication
Manager

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

4 of 21
Metro-PW-ACM

4. Equipment and Software Validated

The following equipment and software/firmware were used for the sample configuration provided:
Equipment

Software/Firmware

Avaya Aura Communication Manager running

on Avaya S8800 Server with Avaya G650
Media Gateway.

6.0.1 (R016x.00.1.510.1) with Service

Pack 5.01 (Patch 19303)

Avaya Aura Communication Manager running

on Avaya S8300D Server with Avaya G450
Media Gateway.

6.0.1 (R016x.00.1.510.1) with Service

Pack 5.01 (Patch 19303)

Avaya Aura Session Manager

6.1 (6.1.5.0.615006)

Avaya Aura System Manager

6.1.0 (6.1.0.07345-6.1.5.502)
with Software Update Revision
6.1.9.1.1634)

Avaya 9600 Series IP Telephones

3.1 SP 4 (H.323)
2.6.7 (SIP)

Metropolis ProfitWatch Call Accounting System 2012.07.20

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

5 of 21
Metro-PW-ACM

5. Configure Avaya Aura Communication Manager

This section describes the Communication Manager configuration at Site A that is required to
interoperate with ProfitWatch. In the test configuration, ProfitWatch did not monitor Site B so only
the configuration for Site A is shown. This section covers the configuration of the CDR link as well
as CDR collection for intra-switch and trunk calls. The procedure covers the following areas:

Administer IP Node Names

Configure CDR Link
Enable CDR for Intra-Switch Calls
Enable CDR for Trunks Calls

5.1. IP Node Names

This section describes the CDR configuration. It is performed using Communication Manager SAT
interface. Use the change node-names ip command to associate the IP address of ProfitWatch to a
node name. In the compliance test, the node name CDR-Metropolis was assigned to IP address
192.168.100.250. Also, highlighted in the example below is the node name clancrm, which
represents the IP address of the CLAN circuit pack used as the source of CDR data.
change node-names ip

Page

1 of

IP NODE NAMES
Name
CDR-Metropolis
RDTT
clancrm
default
devcon-asm
devcon14
medpro-1a13
medprocrm
procr
procr6
val-1a02

IP Address
192.168.100.250
192.168.100.250
10.32.24.20
0.0.0.0
10.32.24.235
192.168.100.10
10.32.24.26
10.32.24.21
10.32.24.10
::
10.32.24.15

( 11 of 11
administered node-names were displayed )
Use 'list node-names' command to see all the administered node-names
Use 'change node-names ip xxx' to change a node-name 'xxx' or add a node-name

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

6 of 21
Metro-PW-ACM

5.2. Configure CDR Link

Use the change ip-services command to define the CDR link between Communication Manager and
ProfitWatch. In the Service Type field, enter CDR1 for the primary CDR link. In the Local Node
field, enter the node name that will terminate the CDR link on Communication Manager. In the
compliance test, which used an Avaya G650 Media Gateway, the Local Node was the CLAN circuit
pack discussed in Section 5.1. The Remote Node field was set to the node name defined for
ProfitWatch, which was CDR-Metropolis. The Remote Port may be set to a value between 5000
and 64500 inclusive and must match the port configured on ProfitWatch (see Section 6.1). In this
example, remote port 9002 was used.
change ip-services
Service
Type
CDR1

Enabled

Page
Local
Node
clancrm

IP SERVICES
Local
Remote
Port
Node
0
CDR-Metropolis

1 of

Remote
Port
9002

On Page 3, set the Reliable Protocol field to y to enable the use of the Avaya Reliable Session
Protocol (RSP) for reliable CDR transmission.
change ip-services
Service
Type
CDR1

Reliable
Protocol
y

Page
SESSION LAYER TIMERS
Packet Resp
Session Connect
Timer
Message Cntr
30
3

SPDU
Cntr
3

3 of

Connectivity
Timer
60

Use the change system-parameters cdr command to set the parameters for the type of calls to track
and to specify the format of the CDR data. The settings for the compliance test are described below.
ProfitWatch used the unformatted CDR format.

CDR Date Format: month/day

Primary Output Format: unformatted
Primary Output Endpoint: CDR1

The remaining parameters define the type of calls that will be recorded and what data will be
included in the record. See reference [1, 2] for a full explanation of each field. The test
configuration used some of the more common fields described below.

Intra-switch CDR? y This allows call records for internal calls involving specific stations.
Record Outgoing Calls Only? n This allows incoming trunk calls to appear in the CDR
records along with the outgoing trunk calls.
Outg Trk Call Splitting? y This allows a separate call record for any portion of an
outgoing call that is transferred or conferenced.
Suppress CDR for Ineffective Call Attempts? y This prevents calls that are blocked from
appearing in the CDR record.
Inc Trk Call Splitting? y This allows a separate call record for any portion of an incoming
call that is transferred or conferenced.

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

7 of 21
Metro-PW-ACM

Default values may be used for all other fields.

change system-parameters cdr

Page

1 of

CDR SYSTEM PARAMETERS

Node Number (Local PBX ID): 1
CDR Date Format: month/day
Primary Output Format: unformatted
Primary Output Endpoint: CDR1
Secondary Output Format: unformatted Secondary Output Endpoint: CDR2
Use ISDN Layouts? n
Enable CDR Storage on Disk? n
Use Enhanced Formats? n
Condition Code 'T' For Redirected Calls? n
Use Legacy CDR Formats? n
Remove # From Called Number? n
Modified Circuit ID Display? n
Intra-switch CDR? y
Record Outgoing Calls Only? n
Outg Trk Call Splitting? y
Suppress CDR for Ineffective Call Attempts? y
Outg Attd Call Record? y
Disconnect Information in Place of FRL? n
Interworking Feat-flag? n
Force Entry of Acct Code for Calls Marked on Toll Analysis Form? n
Calls to Hunt Group - Record: member-ext
Record Called Vector Directory Number Instead of Group or Member? n
Record Agent ID on Incoming? n
Record Agent ID on Outgoing? y
Inc Trk Call Splitting? y
Inc Attd Call Record? n
Record Non-Call-Assoc TSC? n
Call Record Handling Option: warning
Record Call-Assoc TSC? n
Digits to Record for Outgoing Calls: dialed
Privacy - Digits to Hide: 0
CDR Account Code Length: 5

5.3. Enable CDR for Intra-Switch Calls

If the Intra-switch CDR field is set to y in the figure above, use the change intra-switch-cdr
command to define the extensions that will be subject to call detail records. In the Assigned
Members field, enter a specific extension whose usage will be tracked with a CDR record. Add an
entry for each additional extension of interest. Both H.323 and SIP extensions were added to this
table for the compliance testing.
change intra-switch-cdr

Page

1 of

INTRA-SWITCH CDR
Extension
77301
77303
77304
77308
78005
78006

Extension

Assigned Members:
Extension

of 5000
administered
Extension

Use 'list intra-switch-cdr' to see all members, 'add intra-switch-cdr' to add

new members and 'change intra-switch-cdr <ext>' to change/remove other members

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

8 of 21
Metro-PW-ACM

5.4. Enable CDR for Trunk Calls

For each trunk group for which CDR records are desired, verify that CDR reporting is enabled. To
do this, use the change trunk-group n command, where n is the trunk group number, to verify that
the CDR Reports field is set to y. This applies to all trunk group types.
The example below shows the ISDN-PRI trunk to the PSTN.
change trunk-group 1

Page

1 of

21

TRUNK GROUP
Group Number:
Group Name:
Direction:
Dial Access?
Queue Length:
Service Type:

1
To PSTN
two-way
y
0
tie

Group Type: isdn

CDR Reports: y
COR: 1
TN: 1
TAC: 1001
Outgoing Display? n
Carrier Medium: PRI/BRI
Busy Threshold: 255 Night Service:
Auth Code? n
Far End Test Line No:

TestCall ITC: rest

TestCall BCC: 4

The example below shows the H.323 trunk between Sites A and B.
change trunk-group 3

Page

1 of

21

TRUNK GROUP
Group Number:
Group Name:
Direction:
Dial Access?
Queue Length:
Service Type:

3
To Site B
two-way
n
0
tie

Group Type: isdn

CDR Reports: y
COR: 1
TN: 1
TAC: 1003
Outgoing Display? n
Carrier Medium: H.323
Busy Threshold: 255 Night Service:
Auth Code? n
Member Assignment Method: auto
Signaling Group: 3
Number of Members: 10

The example below shows the SIP trunk between Sites A and B. This SIP trunk actually terminates
to Avaya Aura Session Manager, which then routes calls to Site B over another SIP trunk.
change trunk-group 50

Page

1 of

21

TRUNK GROUP
Group Number:
Group Name:
Direction:
Dial Access?
Queue Length:
Service Type:

JAO; Reviewed:
SPOC 9/4/2012

50
To devcon-asm
two-way
n
0
tie

Group Type: sip

COR: 1
Outgoing Display? n

TN: 1

CDR Reports: y
TAC: 1050

Night Service:
Auth Code? n
Member Assignment Method: auto
Signaling Group: 50
Number of Members: 10

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

9 of 21
Metro-PW-ACM

6. Configure Metropolis ProfitWatch Call Accounting System

This section provides the procedures for configuring Metropolis ProfitWatch Call Accounting
System. The procedures include the following areas:
Administer PBX
Administer Customize
Administer Grace Periods

6.1. Administer PBX

From the Metropolis ProfitWatch Call Accounting System server, launch ProfitWatch to display
the ProfitWatch Call Accounting 2012 screen as shown below. Select Setup PBX from the top
menu.

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

10 of 21
Metro-PW-ACM

The Password Security screen is displayed. Enter the appropriate credentials.

The Select PBX screen is displayed next. Enter the following values for the specified fields, and
retain the default values for the remaining fields.

PBX Model:
Receive data using:
Listen Port:
Optional protocol:

Select an applicable type, in this case Avaya S8700.

I.P. Port (PBX sends data to IP port)
The remote port number from Section 5.2.
Avaya RSP

Click Modify PBX Settings in the left pane.

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

11 of 21
Metro-PW-ACM

The Modify PBX screen is displayed. Note that in a live customer environment, CDR data may
start appearing in the top portion of the screen. Select the Outgoing Calls tab.
For Extension Length, enter the maximum number of digits used for internal extensions on Avaya
Aura Communication Manager. As the calling number field in the CDR record is right-justified
and ends at position 42, adjust the Extension Pos value accordingly. In the compliance testing,
calling numbers with 5-digit extensions appear in position 38-42 in the CDR records.
For Digits, enter 18 for Pos and 15 for Length as shown below. This will match to any number in
the dialed number field in position 18-32 of the CDR record.
Retain the default values in the remaining fields.

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

12 of 21
Metro-PW-ACM

Select the Incoming Calls tab. For Extension Length, enter the maximum number of digits used
for the internal extensions on Avaya Aura Communication Manager. The dialed number field in
the CDR record is right-justified and ends at position 32, adjust the Extension Pos value
accordingly. In the compliance testing, dialed numbers with 5-digit extensions appear in position
28-32 in the CDR records.
For Digits, enter 33 for Pos and 10 for Length as shown below. This will match to any number in
the calling number field in position 33-42 of the CDR record.
Retain the default values in the remaining fields.

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

13 of 21
Metro-PW-ACM

6.2. Administer Customize

From the ProfitWatch Call Accounting 2012 screen shown in Section 6.1 select Setup
Customize from the top menu to display the Customize screen.
Check Process Incoming calls and Process extension-to-extension (internal) calls, if desired. Set
the appropriate value for Maximum Internal Extension Length, and retain the default values in the
remaining fields. The screenshot below shows the settings used for the compliance testing.

6.3. Administer Grace Periods

From the ProfitWatch Call Accounting 2012 screen shown in Section 6.1 select Charges
Grace Periods from the top menu to display the Grace Periods screen. Modify the grace period
value for each type of call if desired. Note that calls with duration shorter than the grace period will
not be logged. The screenshot below shows the settings used for the compliance testing.

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

14 of 21
Metro-PW-ACM

7. Verification Steps
This section provides the tests that can be performed to verify the configuration of Avaya Aura
Communication Manager and Metropolis ProfitWatch Call Accounting System.

7.1. Verify Avaya Aura Communication Manager

From the SAT of Avaya Aura Communication Manager, use the status cdr-link command to
verify that the CDR link to ProfitWatch is up.
status cdr-link
CDR LINK STATUS
Link State:
Date & Time:
Forward Seq. No:
Backward Seq. No:
CDR Buffer % Full:
Reason Code:

JAO; Reviewed:
SPOC 9/4/2012

Primary

Secondary

up
2011/11/30 10:35:6
0
0
0.00
OK

CDR not administered

0
/0 /0 0 :0 :0
0
0
0.00

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

15 of 21
Metro-PW-ACM

7.2. Verify Metropolis ProfitWatch Call Accounting System

Make and complete a few phone calls, including internal, inbound from the PSTN, and outbound to
the PSTN.
From the Metropolis ProfitWatch Call Accounting System server, launch ProfitWatch. Verify that
an entry is displayed for each completed call. Note that the Cost data shown below is estimated by
ProfitWatch based on call destination and duration.

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

16 of 21
Metro-PW-ACM

Follow the navigation in Section 6.1 to display the Modify PBX screen. In the top portion of the
screen, verify that an entry is displayed for each completed call with proper values.

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

17 of 21
Metro-PW-ACM

From the ProfitWatch Call Accounting 2012 screen (not shown below), select Reports Report
Generator from the top menu. The Reports Generator screen is displayed. Select Extension
Extension Details Report from the top menu, and click Report.

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

18 of 21
Metro-PW-ACM

The Extension Details Report automatically pops up in a browser window.

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

19 of 21
Metro-PW-ACM

8. Conclusion
These Application Notes describe the steps required to configure Metropolis ProfitWatch Call
Accounting System to interoperate with Avaya Aura Communication Manager, including
establishing a CDR link with Avaya Reliable Session Protocol (RSP) enabled and
capturing/processing call records. All tests passed as noted in Section 2.2.

9. Additional References
This section references the product documentation relevant to these Application Notes.
[1] Administering Avaya AuraTM Communication Manager, June 2010, Release 6.0, Issue 6.0,
Document Number 03-300509, available at http://support.avaya.com.
[2] Avaya AuraTM Communication Manager Feature Description and Implementation, June 2010,
Release 6.0, Issue 8.0, Document Number 555-245-205, available at http://support.avaya.com.
[3] Metropolis ProfitWatch Call Accounting User Guide, available at http://www.metropolis.com.

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

20 of 21
Metro-PW-ACM

2012

Avaya Inc. All Rights Reserved.

Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and
are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the
property of their respective owners. The information provided in these Application Notes is
subject to change without notice. The configurations, technical data, and recommendations
provided in these Application Notes are believed to be accurate and dependable, but are
presented without express or implied warranty. Users are responsible for their application of any
products specified in these Application Notes.
Please e-mail any questions or comments pertaining to these Application Notes along with the
full title name and filename, located in the lower right corner, directly to the Avaya DevConnect
Program at devconnect@avaya.com.

JAO; Reviewed:
SPOC 9/4/2012

Solution & Interoperability Test Lab Application Notes

2012 Avaya Inc. All Rights Reserved.

21 of 21
Metro-PW-ACM