Application Notes for AnchorPoint Telecom Financial Management System with Avaya Communication Manager and Avaya Site Administration - Issue 1.

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for AnchorPoint Telecom Financial Management System with Avaya Communication Manager and Avaya Site Administration - Issue 1.0 Abstract These Application Notes describe the configuration steps required to integrate the AnchorPoint Telecom Financial Management System with Avaya Communication Manager and Avaya Site Administration to manage call accounting and switch inventory. AnchorPoint uses the Network Call Guard, an external data collection unit, to collect call records from Avaya Communication Manager over a Call Detail Recording (CDR) link running Avaya Reliable Session Protocol (RSP). AnchorPoint polls the Network Call Guard for call records to perform call costing and generate reports. In addition, AnchorPoint imports configuration files exported from Avaya Site Administration into its database to maintain the switch inventory. Information in these Application Notes has been obtained through compliance testing and additional technical discussions. Testing was conducted via the DeveloperConnection Program at the Avaya Solution and Interoperability Test Lab. 1 of 26

2 1. Introduction These Application Notes describe the configuration steps required to integrate the AnchorPoint Telecom Financial Management System with Avaya Communication Manager and Avaya Site Administration (ASA) to manage call accounting and switch inventory. AnchorPoint was compliance-tested with an Avaya S8700 Media Server with a G600 Media Gateway and an Avaya S8300 Media Server with a G700 Media Gateway. Avaya Communication Manager can generate Call Detail Records for trunk calls and intra-switch calls (i.e., local station calls) using various CDR formats to be sent over a CDR link running Avaya Reliable Session Protocol (RSP). Avaya Site Administration is used to export configuration files for AnchorPoint. The exported configuration files supported by AnchorPoint include switch hardware, coverage paths, hunt groups, stations, and agent login-ids. The AnchorPoint Telecom Financial Management System consists of two components: the AnchorPoint application server and the AnchorPoint Network Call Guard. The Network Call Guard, an external data collection unit running on a Windows NT PC, collects call records from Avaya Communication Manager over a CDR link running Avaya Reliable Session Protocol. The Network Call Guard is capable of pre-processing call records received from Avaya Communication Manager in the Expanded and Printer CDR formats for its Toll Fraud feature (not covered in these Application Notes). The Network Call Guard can also receive call records in the Int-Direct CDR format, but no pre-processing is performed. The raw or formatted call records are transferred to the AnchorPoint server for call accounting purposes. The AnchorPoint application server polls the Network Call Guard for call records on a scheduled or on-demand basis. AnchorPoint 1 processes call records, maintains switch inventory, and generates reports using the Call Accounting, Voice Inventory, and Interface for ASA modules. AnchorPoint retrieves call records from the Network Call Guard using FTP, converts the CDR data further, and stores the converted CDR data in an SQL database to generate reports and to perform call costing. As mentioned earlier, AnchorPoint supports the Expanded, Printer, and Int-Direct CDR record formats. The switch inventory is obtained from configuration files exported from Avaya Site Administration (ASA). AnchorPoint maintains the switch hardware configuration, coverage paths, hunt groups, stations, and agent login-ids in its database. The AnchorPoint application server software was installed on a PC running Windows XP Professional with MS SQL Server The configuration in Figure 1 illustrates an enterprise network with Avaya Media Servers and Gateways communicating with the AnchorPoint Network Call Guard over the IP network. The AnchorPoint server interfaces with the Network Call Guard over the IP network to retrieve call detail records. The Avaya S8700 Media Servers communicate with the Network Call Guard over a CDR link running RSP, established using a C-LAN board in the Avaya G600 Media Gateway. In this configuration, the S8300 Media Server was used to establish trunk calls to the S8700 Media Server. The S8300 Media Server was not configured to send call records to 1 In these Application Notes, the AnchorPoint application server may be referred to as AnchorPoint server or simply AnchorPoint. 2 of 26

3 AnchorPoint. However, using ASA, switch inventory information was exported from both the S8300 and S8700 Media Servers, and imported into AnchorPoint. Poll CDR AnchorPoint Network Call Guard ( ) CDR Data AnchorPoint Application Server with Avaya Site Administration ( ) Avaya P333T-PWR Switch IP Network Avaya S8700 Media Servers Avaya G600 Media Gateway (C-LAN IP: ) Avaya S8300 Media Server with G700 Media Gateway and Avaya P333T-PWR Switch Figure 1: AnchorPoint managing Avaya Media Servers and Gateways 2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment Software Avaya S8300 Media Server with Avaya G700 Media Communication Manager Gateway (R012x ) Avaya S8700 Media Server with Avaya G600 Media Communication Manager Gateway (R012x ) Avaya Site Administration (ASA) AnchorPoint Telecom Financial Management System with: Call Accounting Module Voice Inventory Module Interface for Avaya Site Administration (ASA) AnchorPoint was installed on a PC running Microsoft Windows XP Professional and Microsoft SQL Server 2000 AnchorPoint Network Call Guard installed on a PC running Microsoft Windows NT of 26

4 3. Configure Avaya Communication Manager This section provides the steps for configuring Call Detail Recording (CDR) on the Avaya S8700 Media Server. The steps are similar for the S8300 Media Server and are not shown in these Application Notes. It is assumed that the Avaya Media Servers have already been configured with an IP address Configure the Call Detail Recording (CDR) This section describes the procedure for configuring a CDR link on the S8700 Media Server. The S8700 Media Server is configured to generate CDR records for intra-switch calls and for incoming and outgoing trunk calls using the Expanded CDR format. AnchorPoint also supports the Printer and Int-Direct CDR formats. The CDR link is established between the C-LAN board in location 2A03 and the AnchorPoint Network Call Guard call collection unit (CCU). The Avaya Reliable Session Protocol (RSP) is enabled on the CDR link for reliable delivery of CDR records. The following configuration was done through the System Access Terminal (SAT) interface. In the node-names ip form shown below, assign node names to the IP addresses of the C-LAN board and the AnchorPoint CCU. These node names will be used in the ip-services form to specify the local and remote nodes of the CDR link. change node-names ip Page 1 of 1 IP NODE NAMES Name IP Address Name IP Address AnchorPoint-CCU clan-02a 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 Figure 2: IP Node Names Form The following screen provides the configuration for the C-LAN board in location 2a03. This C- LAN board will be the local node of the CDR link. change ip-interface 2a03 Page 1 of 1 IP INTERFACES Type: C-LAN Slot: 02A03 Code/Suffix: TN799 D Node Name: clan-02a03 IP Address: Subnet Mask: Gateway Address: Enable Ethernet Port? y Network Region: 1 VLAN: n ETHERNET OPTIONS Auto? y Number of CLAN Sockets Before Warning: 400 Figure 3: IP Interfaces Form for C-LAN Board 2a03 4 of 26

5 The ip-services form specifies the local and remote nodes of the CDR link. In the following configuration, the CDR link, referred to as CDR1, is established between a C-LAN board (local node) and the AnchorPoint CCU (remote node). Communication Manager sends the call records over the CDR links using port number Currently, the CCU only supports CDR links on port number The node names specified for the local and remote nodes map to the IP addresses specified in the node-names ip form. For the CDR service type, the Enabled and Local Port fields are display-only fields that default to blank and 0, respectively. These fields are not relevant for CDR links. change ip-services Page 1 of 3 IP SERVICES Service Enabled Local Local Remote Remote Type Node Port Node Port SAT y clan-01a any 0 CDR1 clan-02a03 0 AnchorPoint-CCU 9000 Figure 4: IP Services Form (Page 1) On Page 3 of the ip-services form, enable the Reliable Session Protocol (RSP) for the CDR link by setting the Reliable Protocol field to y. change ip-services Page 3 of 3 SESSION LAYER TIMERS Service Reliable Packet Resp Session Connect SPDU Connectivity Type Protocol Timer Message Cntr Cntr Timer CDR1 y Figure 5: IP Services Form (Page 3) 5 of 26

6 Use the system-parameters cdr form to set parameters for the types of calls to record and how to format the CDR data. For the configuration described herein, the system-parameters cdr form was configured as shown in Figure 6. AnchorPoint also supports the Printer and Int- Direct CDR formats. AnchorPoint requires that the CDR Date Format be set to month/day for the Expanded and Printer CDR formats, but supports any CDR Date Format for the Int-Direct CDR format. See reference [1] for a description of the parameters on this form. change system-parameters cdr Page 1 of 2 CDR SYSTEM PARAMETERS Node Number (Local PBX ID): CDR Date Format: month/day Primary Output Format: expanded Primary Output Endpoint: CDR1 Secondary Output Format: Secondary Output Endpoint: Use ISDN Layouts? n Use Enhanced Formats? n Condition Code 'T' For Redirected Calls? n Modified Circuit ID Display? n Remove # From Called Number? n Record Outgoing Calls Only? n Intra-switch CDR? y Suppress CDR for Ineffective Call Attempts? y Outg Trk Call Splitting? y Disconnect Information in Place of FRL? n Outg Attd Call Record? y 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 Inc Trk Call Splitting? 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: 15 Figure 6: System Parameters CDR Form To generate CDR records for trunk calls, set the CDR Reports field in the Trunk Group form to y. This applies to all trunk group types. change trunk-group 60 Page 1 of 22 TRUNK GROUP Group Number: 60 Group Type: isdn CDR Reports: y Group Name: H.323 Calls to S8300 COR: 1 TN: 1 TAC: 160 Direction: two-way Outgoing Display? n Carrier Medium: IP Dial Access? y Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n TestCall ITC: rest Far End Test Line No: TestCall BCC: 4 TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Max Message Size to Send: 260 Charge Advice: none Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc Trunk Hunt: ascend Digital Loss Group: 18 Calling Number - Delete: Insert: Numbering Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 Figure 7: Trunk Group Form 6 of 26

7 To generate CDR records for intra-switch calls (i.e., calls between stations on the same media server), enter the extensions to be tracked by intra-switch CDR in the following screen. change intra-switch-cdr Page 1 of 2 INTRA-SWITCH CDR Assigned Members: 4 of 5000 administered 1: : 37: 55: 73: 91: 2: : 38: 56: 74: 92: 3: : 39: 57: 75: 93: 4: : 40: 58: 76: 94: 5: 23: 41: 59: 77: 95: 6: 24: 42: 60: 78: 96: 7: 25: 43: 61: 79: 97: 8: 26: 44: 62: 80: 98: 9: 27: 45: 63: 81: 99: 10: 28: 46: 64: 82: 100: 11: 29: 47: 65: 83: 101: 12: 30: 48: 66: 84: 102: 13: 31: 49: 67: 85: 103: 14: 32: 50: 68: 86: 104: 15: 33: 51: 69: 87: 105: 16: 34: 52: 70: 88: 106: 17: 35: 53: 71: 89: 107: 18: 36: 54: 72: 90: 108: Figure 8: Intra-switch CDR Form 3.2. Configure Avaya Site Administration (ASA) Avaya Site Administration (ASA) can be used to extract configuration files from Avaya Communication Manager for AnchorPoint. The configuration files that were exported included the switch hardware configuration, coverage paths, hunt groups, stations, and agent login-ids. Start the ASA application by selecting Start Programs Avaya Site Administration. It is assumed that the voice systems (i.e., Avaya Media Servers and Gateways) have already been added to ASA. See reference [2] for instructions. Select the system from which configuration information will be extracted. In this example, the S8700 Media Server and G600 Media Gateway were selected as denoted by S8700 in the drop-down textbox in the Tool Bar as shown in Figure 9. 7 of 26

8 Figure 9: Avaya Site Administration Main Window with Hardware Manager To export the hardware configuration of the Avaya Media Gateway, select the Tasks tab on the left and click on the Fault & Performance bar. Click on Hardware Manager to display the hardware configuration in the window. Select the Export option from the File menu to display the Export Format window as shown in Figure 10. In the Export Format window, specify the filename, including the directory path, for the hardware export file. Accept the default values for the other fields and click the OK button. Figure 10: Export Format 8 of 26

9 The hardware configuration is successfully exported as indicated in the following status message. Figure 11: Export Status Message To export coverage paths, hunt groups, stations, and agent login-ids, select the Tasks tab on the left panel of the ASA Main Window and click on the Advanced bar. Click on Export Data to display the Export Data Filter window shown in Figure 12. Set the Select an object to export field to the desired object. In this example, the station configuration is exported. Click on the Next button. This procedure applies to the other object types as well. Figure 12: Avaya Site Administration Main Window and Export Data Filter Dialog Box 9 of 26

10 The Export Data Fields window is displayed as shown in Figure 13. Select the fields to be exported by moving them to the Selected section. The fields supported by AnchorPoint for each object type are listed in Table 1. These fields should be exported exactly as shown for each object type. After selecting the export fields, click the Next button. Figure 13: Export Data Fields Table 1 lists the fields that should be exported for each object type and the order in which the fields should be exported. Coverage Path Hunt Group Station Agent Login-ID Path Number Next Path Number Point1 Point2 Point3 Point4 Point5 Point6 Group Number Group Name Group Extension Group Type COR Extension Type Port Name Coverage Path 1 Coverage Path 2 Hunt-to Station COR COS Room Jack Cable Floor Building Dial Code Info1 Info2 Login ID Name COR Coverage Path Table 1: Export Fields per Object Type 10 of 26

11 The Export Data Format window is displayed as shown below. Set the Export file field to a filename, including the directory path where the export file should be stored. Accept the default values for the other fields and click the Next button. Figure 14: Export Data Format The Export Data Schedule dialog box is displayed as shown in Figure 15. Select the Run Now checkbox to export the file immediately. Click the Next button. The Export Data Summary window is displayed. Click on the Finish button to export the file to the specified directory path. Figure 15: Export Data - Schedule 11 of 26

12 4. Configure AnchorPoint This section covers the configuration of the AnchorPoint Telecom Financial Management System, including the AnchorPoint application server and the Network Call Guard Configure the Network Call Guard The Network Call Guard is a call collection unit (CCU) responsible for establishing the CDR link to Avaya Communication Manager and collecting call records. The CCU Configuration utility is used to configure the CDR link, CDR format, and the schedule for creating the poll file that contains the pre-processed CDR data. The CCU Configuration utility is located in C:\ccuv5\CCUCONFIG.EXE. The CCU is typically used to capture call records from a single site. It is assumed that the CCU has already been configured with the appropriate IP address (i.e., ). The Network Call Guard uses CDR port This port must match the configuration on Avaya Communication Manager as shown in Figure 4. This configuration is performed in the CCU PBX Communications configuration utility. The CCU PBX Communications application is configured to start automatically under Windows Services. To access the CCU configuration functions, double click the CCU Configuration icon on the Network Call Guard desktop. The CCU Configuration window displayed in Figure 16 appears. Configure the PBX Site Name field with the name of the site where the Network Call Guard is installed. Select the TCP RDT checkbox to enable the Avaya Reliable Session Protocol (RSP). Next, set the PBX Type field to one of the following values: 0 = PBX Raw (currently used with the Int-Direct CDR format) 2 = Avaya G3 Printer (non-expanded) or (84 byte variant) 6 = Avaya G3 Expanded Although the Network Call Guard uses the PBX Type field to pre-process call records for the Toll Fraud feature, the PBX Type field must be set correctly according to the CDR format being used by Avaya Communication Manager, even if the Toll Fraud feature is not being used. By selecting the Raw Output checkbox, the raw call records will be placed alongside the preprocessed call records in the poll file. The poll file contains the CDR record retrieved by AnchorPoint. Finally, the Poll Schedule field and the Time of Day and Interval checkboxes are used to schedule when the poll file is created. The poll file may be created on a daily basis or at specific time intervals. In this example, the poll file is created daily at midnight as indicated by the Poll Schedule field in Figure 16. AnchorPoint should be configured to poll for CDR data after the poll file has been created. After completing the CCU configuration, restart the CCU by clicking the Restart CCU button. 12 of 26

13 Figure 16: CCU Configuration 4.2. Configure the AnchorPoint Server In the solution described in these Application Notes, AnchorPoint is used to manage call accounting and switch inventory for a network containing Avaya Media Servers and Gateways. This section will cover the configuration of the AnchorPoint server to support these applications CDR Collection For CDR collection, the following configuration is required in AnchorPoint. Sites need to be defined in AnchorPoint. The CDR Import Program needs to be configured per site. The CDR Import Program specifies how CDR data should be interpreted (i.e., Expanded, Printer, or Int-Direct CDR format). The polling schedule for retrieving CDR data (i.e., poll file) from the Network Call Guard needs to be configured. 13 of 26

14 Note: Other configuration, such as trunk groups and access codes, need to be configured in AnchorPoint for call costing. This configuration is beyond the scope of these Application Notes and the reader should consult reference [3] for more details. Start the AnchorPoint application by selecting Start Programs AnchorPoint for Windows AnchorPoint for Windows. The AnchorPoint menu is displayed as shown below. Figure 17: AnchorPoint Menu From the AnchorPoint menu, select Maintenance Sites to display the Site Maintenance window in Figure 18, which can be used to add a site to the AnchorPoint database. In the Detail tab, set the Site and Description fields and specify the CDR Import Program. The CDR Import Program field should be set as follows: When using the Expanded or Printer CDR format, set the field to TIGCCU. When using the Int-Direct CDR format, set the field to TIGAVAYAINTDIRDM or TIGAVAYAINTDIR. The former option uses the day/month format, whereas the latter format uses the month/day format. Figure 18: Site Maintenance Detail Tab 14 of 26

15 In the Contact/Switch Info tab shown in Figure 19, set Port Map Formatting Options fields to None. This prevents delimiters, such as commas and dashes, from being used in slot and port numbers in the switch inventory information. Set the Nbr of Digits in Port Addr field to 2. Click the Add button to add the site entry into the database. Figure 19: Site Maintenance Contact / Switch Info Tab AnchorPoint polls the Network Call Guard for CDR data using FTP. From the AnchorPoint menu, select Tools Poller/Scheduler Poller Site Maintenance to specify the FTP parameters. The window in Figure 20 is displayed. Configure the Password field with the FTP password for the Network Call Guard and set the Phone Number field to ftp:<ccu IP Address>@<Username>. In this example, the Phone Number field was set to ftp: @administrator. In this configuration, the Modem Setup fields are ignored. Set the other fields as shown below. Click the Add button to add the site for polling. Note this is different from adding the site to the database as shown in Figure of 26

16 Figure 20: Site Maintenance Call Collector Setup The next step is to schedule AnchorPoint to poll the Network Call Guard for CDR data (i.e., the poll file). Select Tools Poller/Scheduler Scheduler Maintenance from the AnchorPoint menu. The Site & Schedule Maintenance window is displayed as shown in Figure 21. Click the Add button to schedule polling. AnchorPoint should poll for call records after the CCU has created the poll file. The Add Schedule Item window is displayed as shown in Figure 22. Figure 21: Site & Schedule Maintenance 16 of 26

17 In the Add Scheduled Item window, set the Site ID field appropriately and specify the Date and Time for the polling. Click the OK button when finished. This item will be added to scheduled maintenance in Figure 21. Figure 22: Add Scheduled Item To activate polling, the Scheduler must be running. From the AnchorPoint menu, select Tools Poller/Scheduler Scheduler to run the scheduled events. The scheduler window is displayed. The Scheduler must be kept running for AnchorPoint to poll the Network Call Guard. Figure 23: Scheduler Note: AnchorPoint can also poll the Network Call Guard on-demand. Select Tools Poller/Scheduler Poller from the AnchorPoint menu to poll the Network Call Guard manually. Refer to [3] for instructions. 17 of 26

18 Once the call records have been retrieved from the Network Call Guard, AnchorPoint can perform its call costing function. Select Tools Call Processing Cost Calls Records from the AnchorPoint menu to display the Cost Call Records window shown below. Select the Site and set the other fields as shown below. Click the OK button. Figure 24: Cost Call Records AnchorPoint provides the following response when the operation is completed successfully. Figure 25: AnchorPoint Reply To view the call records, select Reports Detail Inquiry Current Calls from the AnchorPoint menu and set the query fields appropriately, as shown in Figure 26. Click the Screen button to run the query and display the CDR report. The CDR report is displayed in Figure of 26

19 Figure 26: Call Detail Inquiry Report Query Figure 27: Call Detail Inquiry Report 19 of 26

20 Switch Inventory To maintain the switch inventory, AnchorPoint imports configuration files extracted from Avaya Communication Manager through Avaya Site Administration (ASA). The ASA export files are then imported into AnchorPoint. AnchorPoint can import ASA export files for hardware, coverage paths, hunt groups, stations, and agent login-ids. To use the AnchorPoint Interface for ASA the following items must be defined in AnchorPoint: Site: The site was defined in Figures 18 and 19. Cabinet Code: Cabinet codes for the Avaya G600 and G700 Media Gateways are defined in Figure 28. Shelf (Carrier) Code: Shelf (carrier) codes for the Avaya G600 and G700 Media Gateway are defined in Figure 29. Phone Equipment Type Code: Phone equipment type codes are defined in Figure 30. Organization Code (not covered in these Application Notes) To define Cabinet Codes for the Avaya G600 and G700 Media Gateways, select Maintenance Validation Tables Voice Inventory Switch Equipment Cabinet Code from the AnchorPoint menu. The Cabinet Code Maintenance window is displayed in Figure 28. Configure the fields as shown below. Set the Number of Shelves field according to the number of shelves in the G600 and G700 Media Gateways. In this example, the G600 and G700 Media Gateways had two shelves and one shelf, respectively. Figure 28: Cabinet Code Maintenance 20 of 26

21 To define the Carrier Codes for the Avaya G600 and G700 Media Gateways, select Maintenance Validation Tables Voice Inventory Switch Equipment Carrier Code from the AnchorPoint menu. Set the fields as shown in Figure 29. The Number of Slots field was set to 11 for the G600 Media Gateway. Although the G600 Media Gateway has 10 physical slots, an additional slot was added to account for the fact that the IP Server Interface card appears twice in the hardware configuration. The Number of Slots for the G700 Media Gateway was set to 6 to cover slots V1-V4 and V8-V9. Figure 29: Carrier Code Maintenance The different station types that may be encountered in the station export file must be defined in AnchorPoint. To define the Phone Equipment Type Codes, select Maintenance Validation Tables Phone Equipment from the AnchorPoint menu. Add the station types in the Phone Equipment Maintenance window shown in Figure 30: Phone Equipment Maintenance 21 of 26

22 The procedure for updating the AnchorPoint database using export files from ASA is described below. To update the switch hardware information in the AnchorPoint database, select Interfaces ASA Build Port Map from the AnchorPoint menu. Specify the Site with which the data is associated, the Default Cabinet Code, and the Default Carrier Code as shown below. Specify the hardware export file from the ASA in the Hardware Manager Export Filename field. Click the Import button. As the hardware data is being imported into the database, the counters in the screen will increment. When the import is completed, the user will have the option to display the imported hardware in the subsequent screens. Figure 31: Build Port Map To update the coverage paths and hunt groups in the AnchorPoint database, select Interfaces ASA Update Coverage Path and Interfaces ASA Update Hunt Group, respectively, and follow the import procedure described above for the switch hardware. To update the stations and agent login-ids in the AnchorPoint database, select Interfaces ASA Update Database from the AnchorPoint menu. The Update Database window in Figure 32 is displayed. Set the fields as shown in Figure 32. In the Station Export Filename field, specify the location of the station export file from ASA. In the Agent-IDs Export Filename field, specify the location of the agent login-ids export file from ASA. Click the Import button. As the station and agent login-id data is being imported into the database, the counters in the screen will increment. When the import is completed, the user will have the option to display the imported hardware in the subsequent screens. 22 of 26

23 Figure 32: Update Database AnchorPoint provides standard reports that identify objects that exist in the AnchorPoint database but are not in the switch (i.e., ASA export files). These reports are accessible under Interfaces ASA Reports. The following reports are available: Groups Not Defined on Switch for Coverage Paths and Hunt Groups Switch Hardware Not Defined on Switch Extensions Not Defined on Switch AnchorPoint allows users to view the switch inventory that was imported into the database. To view the switch hardware, select Maintenance Sites and select the site. From this window, the user may drill down to view the cabinet, shelf/carrier, cards, and port information. To view the stations and agent login-ids, select Maintenance Database Phone from the AnchorPoint menu. To view the coverage paths and hunt groups, select Maintenance Validation Tables Voice Inventory Software Groups Coverage Path and Maintenance Validation Tables Voice Inventory Software Groups Hunt Group, respectively. 23 of 26

24 5. Interoperability Compliance Testing Interoperability compliance testing covered feature and performance testing. Feature testing focused on verifying that AnchorPoint can perform the following functions: Establish a CDR link running RSP to Avaya Communication Manager, Collect and process CDR records from Avaya Communication Manager, and Maintain switch inventory information using export files from Avaya Site Administration. Performance testing was performed with a bulk call generator to generate a call volume for an extended period of time. The ability of the Network Call Guard call collection unit to capture all of the generated call records was verified. In addition, system configuration information was imported to the AnchorPoint database using export configuration files from Avaya Site Administration General Test Approach All feature test cases were performed manually. The general test approach entailed verifying CDR collection on the Network Call Guard for different call types, such as trunk calls, intraswitch calls, conference calls, transferred calls, and forwarded calls, using the Expanded, Printer, and Int-Direct CDR formats. Furthermore, switch inventory was maintained in AnchorPoint using export files from Avaya Site Administration (ASA). Performance tests verified that the Network Call Guard could collect call records during a sustained, high volume of calls. To verify the end-to-end solution, CDR reports were created on AnchorPoint Test Results All feature and performance tests passed. The Network Call Guard successfully established a CDR link with RSP to Avaya Communication Manager, and captured and processed call records using the Expanded, Printer, and Int-Direct CDR formats. AnchorPoint successfully processed the CDR data, performed call costing, and produced call accounting reports. AnchorPoint also maintained switch inventory information related to switch hardware, coverage paths, hunt groups, stations, and agent login-ids. Modifications to the switch configuration resulted in the data being successfully updated in AnchorPoint. Note that when a configuration object is deleted on the switch, AnchorPoint does not automatically delete the item from its database. It allows a report to be run that identifies objects that exist in the AnchorPoint database but not in the switch. 6. Verification Steps To verify the AnchorPoint Telecom Financial Management System, including the Network Call Guard, perform the following steps: Use the ping command to verify IP communication between the C-LAN in the G600 Media Gateway, the Network Call Guard, and the AnchorPoint server. 24 of 26

25 Run the status cdr-link command on the SAT to verify the state of the CDR link on Avaya Communication Manager. Verify that the Network Call Guard is collecting raw CDR data. Perform a manual poll or schedule a poll to verify that AnchorPoint can retrieve CDR data from the Network Call Guard. Perform a call costing operation and display a CDR report on AnchorPoint to verify that AnchorPoint can process the CDR data. 7. Support Customers requiring technical support for the AnchorPoint Telecom Financial Management System may contact AnchorPoint Client Services at (770) (available 8am - 5pm EST, Monday thru Friday). 8. Conclusion These Application Notes illustrate the configuration steps required to enable the AnchorPoint Telecom Financial Management System to collect CDR records from Avaya Communication Manager and to maintain switch inventory information. AnchorPoint was successfully compliance-tested with an Avaya S8300 Media Server with a G700 Media Gateway and an Avaya S8700 Media Server with a G600 Media Gateway. 9. Additional References This section references the Avaya and AnchorPoint product documentation that are relevant to these Application Notes. The following Avaya product documentation can be found at [1] Administrator s Guide for Avaya Communication Manager, Release 2.0, Issue 7, December 2003; Document Number [2] Avaya Site Administration Online Help The following AnchorPoint product documentation is available from AnchorPoint. Visit their website at for company and product information. [3] AnchorPoint User Guide for Release 5.0 [4] AnchorPoint Network Call Guard Installation and User Guide for Release 5.0 [5] AnchorPoint Interface for Avaya Site Administration User Guide for Release of 26

26 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 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 DeveloperConnection Program at 26 of 26