VCXTM Administration Guide V7210 IP Call Processor V7220 Accounting Suite 3Com Telephones and Attendant Console VCX Call Records Utility VCX Complementary Attendant VCX™ V7000 IP Telephony Solution System Release 5.2 Part Number 900-0234-01 Rev AA Published Decembver 2004 http://www.3com.
3Com Corporation 350 Campus Drive Marlborough, MA 01752-3064 Copyright © 2002, 2003, and 2004, 3Com Corporation. All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without written permission from 3Com Corporation.
CONTENTS ABOUT THIS GUIDE Related Documentation Your Comments 18 1 17 CONFIGURING THE AUTHENTICATION SERVER Direct Phone to Gateway Dialing 19 Accessing the Authentication Server Interface 19 Configuring End Users 21 Adding End Users 21 Viewing All End Users 23 Searching for End Users 24 Editing End User Profiles 25 Cloning End Users 25 Deleting End Users 26 Configuring User Phones 27 Adding Phones 27 Deleting Phones from a User 31 Adding Phone Features 32 Editing Phone Features 35 Deleting Phone Feature
Editing a MAC Address 50 Deleting a MAC Address 50 Configuring an Attendant Console 51 Supported Attendant Console Feature Buttons 51 Adding an Attendant Console 51 Editing Feature Mapping Buttons on an Attendant Console 53 Editing Extensions on an Attendant Console 54 Editing Attendant Console Basic Information 54 Deleting an Attendant Console 55 Attendant Console Busy Lamp Flash Descriptions 55 Configuring Patterns 55 Configuring URI Translation Patterns 57 Adding URI Translation Pattern 57 Deleting UR
Deleting Emergency Lines from an ERL 78 Configuring Dial Plans 79 Adding Dial Plans 79 Editing Dial Plan Names 82 Editing Dial Rules Associated with a Dial Plan Deleting Dial Plans 83 Configuring Dial Rules 83 Adding Dial Rules 84 Deleting Dialing Rules 85 Configuring Call Park 85 Configuring the Server 87 Enabling VPN Translation 87 2 83 CONFIGURING THE DIRECTORY SERVER Accessing the Directory Server Configurables 89 Configuring a Call Route through the Web Provisioning Server Managing Patterns 91 Ad
Adding Day Time Bands 102 Editing Day Time Bands 103 Deleting Day Time Bands 104 Managing Calendar Bands 105 Adding Calendar Bands 105 Editing Calendar Bands 106 Deleting Calendar Bands 107 Managing End Points 108 Adding End Points 108 Editing End Points 111 Deleting End Points 111 Adding or Editing Out Dial Patterns of End Points 112 Deleting Out Dial Patterns from Existing End Points 113 Managing End Point Black Lists 114 Adding End Point Black Lists 114 Deleting End Point Black Lists 116 Managing End
Adding Destination URI Translations 135 Globally Editing URI Translation Sourced Based Route Properties Server Configuration 138 Globally Configuring Routes 138 Resetting Globally Provisioned Routes 139 3 CONFIGURING THE ACCOUNTING SERVER Database Identification Configuration 141 Changing the Database Name 141 Changing the Database Server Name 141 Changing the Database User Name 142 Changing the Database User Password 142 Configuring the Database Keep Alive Timeout 143 Configuring the Client Activity I
Call Processor Advantages 151 Configuration Methods 152 Through EMS 152 Through CLI 152 Configuring Call Control 152 Through EMS 152 Configuring Trusted Endpoints 153 Adding Trusted Endpoints 153 Editing Trusted Endpoints 155 Deleting Trusted Endpoints 156 Verifying Call Processor Version 157 Configuring the Back-end Server Plugins 157 Adding Primary and Secondary Accounting Servers 157 Editing Accounting Server IP Addresses 159 Removing Accounting Servers 159 Adding Primary and Secondary Authentication
7 CALL REPORTING Call Detail Records Introduction 181 CDR Generating Components 181 Logging into the Call Report Utility 182 Updating the CDR Fields 182 Retrieving VCX CDRs Manually 182 Retrieving VCX CDRs Automatically 183 Changing the Servers Associated with the Call Report Utility Uninstalling the Call Report Utility 184 Supported VCX CDR Field Descriptions 185 8 183 CONFIGURING THE SIP PHONE DOWNLOADER Configuring the SIP Phone Downloader 187 Through the SipPhoneDL.
Stopping the Accounting, Authentication, and Directory Servers Backing Up and Restoring Databases 204 Exporting Table Data 207 Importing Saved Table Data 209 Clearing the Configurable Tables 209 Running Individual Tasks on the Accounting Server 210 Monitoring Accounting Server Activity on the Accounting Server Checking the Data on the Accounting Server 212 Manually Completing an Incomplete Call on the Billing Support Server 212 Enabling Message Tracing 213 Enabling Server Logging 214 SNMP Support 214 Re
Configuring erl_direct 232 Configuring erl_elin_map 233 Configuring erl_es_number_map 233 Configuring es_contact 233 Configuring es_defaults 234 Configuring es_number 234 Configuring feature_uri_info 235 Configuring patterns 236 Configuring persons 236 Configuring person_uri_map 245 Configuring selective_ringing 245 Configuring server_configuration 246 Configuring support_profiles 246 Configuring tos_feature_map 247 Configuring tos_name 248 Configuring trans_src_dest 248 Configuring trusted_clients 249
Configuring ep_outdial_map_data.txt 268 Configuring ep_wlist_map_data.txt 268 Configuring global_policy_data.txt 269 Configuring global_policy_map_data.txt 269 Configuring holidays_data.txt 270 Configuring outdial_patterns_data.txt 270 Configuring patterns_data.txt 272 Configuring patterns_testcall_map_data.txt 272 Configuring requestors_data.txt 273 Configuring route_data.txt 274 Configuring route_ep_map_data.txt 275 Configuring route_ep_outdial_map_data.txt 276 Configuring trusted_clients_data.
Manually Populating the User Call History 297 Manually Running the Super CDR Export 298 Manually Scheduling the Super CDRs Export 298 Manually Deleting CDRs 299 Manually Running the Super CDR Delete 300 Manually Scheduling the Super CDR Delete 300 Manually Dropping a Scheduled Job 301 Manually Acquiring a Job Number 301 Manually Dropping a Job 301 Manually Resuming a Broken Job 301 Manually Acquiring a Broken Job Number 301 Manually Resuming a Job 302 Viewing the Log Files 302 Manually Configuring the D
Flow Control Configuration Identification 323 State 323 322
ABOUT THIS GUIDE This chapter contains an overview of this guide, lists guide conventions, related documentation, and product compatibility, and describes how to contact Customer Service.
ABOUT THIS GUIDE Table 1 and Table 2 list conventions that are used throughout this guide.
Related Documentation Related Documentation 17 These 3Com documents contain additional information about the products in this release that are a part of or support the VCX V7000 IP Telephony Solution and the 3Com Convergence Application Suite.
ABOUT THIS GUIDE Your Comments ■ VCX V7111 VoIP SIP Gateways User Manual ■ VCX V7122 Gateway Fast Track Installation Guide ■ VCX V7122 VoIP SIP Gateways User Manual Your suggestions are important to us because we want to make our documentation more useful to you. Please send e-mail comments about this guide or any of the 3Com Voice Products documentation and Help systems to: VOICE_Techpubs_comments@3com.
1 CONFIGURING THE AUTHENTICATION SERVER This chapter provides information on how to configure the authentication server through the provisioning server. Use the web provisioning server to manage rate plans, patterns, and calls plans and to add and manage users in specific network domains. Also, use the web provisioning server to search users based on select criteria. View no more than 50,000 objects through the provisioning server at a time; otherwise, it could overload the provisioning server.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Figure 1 Authentication Server Main Page
Configuring End Users Configuring End Users Adding End Users 21 Use this feature to add and manage end users and end user phones. Make searches to manage the URI addresses, call plans, and call plan details associated with a specific end user. End user profiles can be added, deleted, or modified. To add a new end user profile: 1 Under the Users heading, click Add. See Figure 1. The Add User page appears.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Table 3 Adding Personal Information Field Description Example Required? Title The social title of the new user Miss, Mr., Mrs., Ms. No First Name The first name of the new user Jane, John Yes Middle Name The middle initial of the new A., B., C., D. user. No Last Name The last name of the new user.
Configuring End Users 23 Table 5 Adding Web Login Password Field Description Example Required? Login Name The unique web login name for the JOHN new user. YES Password The unique password for the new user. 123ABC Yes Confirm Password The unique password for the new user. Simply type the login password again for verification purposes. 123ABC Yes Note: If the password and confirmation do not match, an error appears. 6 When you are finished, click Save.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Table 6 Users Page—Columns of Information (continued) Column Description Sample Content Actions This column contains three actions you can perform for each end user: N/A ■ ■ ■ Add Phone—use this to add a phone to an existing end user Clone—use this option to clone an existing end user Delete—use this option to delete an existing end user 2 Use the Users page to manage phones and other end user-specific features.
Configuring End Users Editing End User Profiles 25 To edit an end user profile: 1 Click the Users heading. The Users page appears. 2 In the Login Name column, click the login name of the end user you want to edit. The Edit User page appears. 3 Make the necessary changes for this end user. 4 Click Save. The Users page reappears with the changes saved for this end user. Cloning End Users Clone an end user to save time.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Deleting End Users Use the administration provisioning server to delete one or more end user profiles. Deleting One End User To delete one end users: 1 Search for the particular end user you want to delete. See Searching for End Users on page 24. If a phone exits for the user, delete the phone before deleting the user. 2 From the Users page, click Delete in the Actions column. The Users page refreshes, showing the new list of end users.
Configuring User Phones Configuring User Phones Adding Phones 27 Use the provisioning server to add, delete, and modify phones profiles for an existing user. Also, use the provisioning server to customize calling features for an existing user. To add a new phone for an existing end user: 1 Search for a particular end user. See “Searching for End Users” on page 24. 2 From the Users page, click Phones in the Phones column. The User Phones page appears. See Figure 3.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Figure 4 Add Phone Window 4 Fill out the fields according to the descriptions in Table 7.
Configuring User Phones 29 The Add Phone field descriptions are as follows: Table 7 Add Phone Field Descriptions Field Description Name Indicates the unique name for the phone. For example: Home Office Status Indicates the status of the phone. End users can only make calls on a particular phone if it is enabled. Phone Address A unique phone address. Use the sip:@ format for this field. For example: sip:2222@192.1.1.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Table 7 Add Phone Field Descriptions (continued) Field Description Date Time Format Display Indicates the format of the phone’s LCD. An example of what each format would like is provided.
Configuring User Phones 31 Table 7 Add Phone Field Descriptions (continued) Field Description Type of Service Indicates what feature bundle is assigned to the phone. Type of Service bundles are configured in the “Configuring Type of Service” section on page 65. Dial Plan Dial plans are comprised of individual or bundled dial rules and are configured in the Configuring Dial Plans.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Adding Phone Features To add phone (calling) features for an existing phone: 1 Search for a particular end user. See “Searching for End Users” on page 24. 2 From the Users page, click Phones in the Phones column. The User Phones page appears. 3 In the Actions column, click Features. The Assigned Phone Features page appears. 4 From the Assigned Phone Features page, click Add Features. The Add New Phone Features page appears.
Configuring User Phones 33 Table 8 Calling Features for Phones (continued) Calling Feature Description Caller Identity This feature configures the following features: ■ ■ ■ ■ Calling Number Delivery—Use this feature if the phone supports the caller ID display feature. If so, the phone light emitting diode (LED) will display the number for incoming calls. Calling Name Delivery—Use this feature if the phone supports the caller ID display feature.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Table 8 Calling Features for Phones (continued) Calling Feature Description Speed Dial When making a call, use a speed dial to provide short-cut dial strings for frequently used phone numbers. The access codes are automatically assigned. Users are assigned 12 speed dials with access codes *11 through *22. Speed dial phone addresses should not use the sip:@ format.
Configuring User Phones 35 5 Select the checkbox in front of the features you want to add and click Add Selected. A confirmation dialog box appears. 6 If you are satisfied with your selection, click OK. If adding the Enable Call Identity Suppression feature, in order for this feature to immediately take affect, you need to log out of the phone and then log back in, otherwise; the feature will not take affect until the phone’s configured registry timer setting has elapsed.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Table 9 Edit Phone Features Field Descriptions Default Access Code Feature Format Caller Identity ■ Calling Number Delivery—N/A N/A ■ Calling Name Delivery—N/A N/A ■ Call Identity Suppression Universal—N/A *83 Enable Call Identity Suppression Per Call—N/A *82 Disable Call Identity Suppression Per Call—N/A *67 ■ ■ Call Forward Busy Use the sip:@ format for the Phone Address field.
Configuring User Phones 37 access code before dialing the actual phone number. The standard format for all access codes is *##, for example *77. 6 Click Update to save your settings. 7 Click Cancel to return to The Assigned Phone Features page. Deleting Phone Features To delete one calling features for an existing phone: 1 Search for a particular end user. See Searching for End Users on page 24. 2 From the Users page, click Phones in the Phones column. The User Phones page appears.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER The Restrictions page appears. 4 From the Restrictions page, click Add Phone Restriction. The Phone Restrictions page appears. See Figure 5. Figure 5 Phone Restrictions Window 5 Fill out the fields according to the descriptions in Table 10.
Configuring User Phones 39 Table 10 Phone Restrictions Field Descriptions (continued) Field Description Owner Configure the phone restriction owner using one of the following: ■ EndUser ■ Administrator Note: Phone restrictions owned by the Administrator will not be seen by the end user (from the Calling Features User Interface). Pattern Use the drop-down menu to select a previously used pattern or type in a new pattern. For more information, see Configuring Patterns. 6 Click Save.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Deleting Phone Restrictions To delete restrictions for an existing phone: 1 Search for a particular end user. See Searching for End Users on page 24. 2 From the Users page, click Phones in the Phones column. The User Phones page appears. 3 From the User Phones page, click Call Restrictions in the Actions column. The Restrictions page appears. 4 In the Actions column, click Delete next to the restriction you want to delete.
Configuring User Phones 41 Figure 6 Phone Registration Window 5 Fill out the fields according to the descriptions in Table 11. The Add Registration field descriptions are as follows: Table 11 Add Registration Field Descriptions Field Description URI Address This is the URI address of the home phone. This field is not editable. For example, sip:@. Priority If end users have multiple SIP contacts, use this field to prioritize them.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Table 11 Add Registration Field Descriptions (continued) Field Description Type Choose the type of SIP contact: ■ UnKnown ■ SIP ■ SIPS Note: SIPS is used for future implementations only. Contact URI This is an optional field to be used in the SIP Registration message. 6 Click Save. The Phone Registrations page appears showing the new phone registration. 7 Click Cancel to return to The User Phones page.
Configuring User Phones 43 Table 12 Phone Registrations Page (continued) Column Description URI Address This field contains the URI address for a particular phone registration. Priority This field contains the registration priority for a particular phone registration. End Time This field contains the expiration time for a particular phone registration. Deletable This field indicates whether the phone registration is a Provisioning (static) or Dynamic contact.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Figure 7 Populated Call History The Call History log contains 6 columns of information available for each phone. Table 13 lists each column and describes the type of information available in that column. Table 13 Call History Information for Phones Column Description Caller Address This field contains the address of the phone who initiated a specific call (the calling party).
Configuring User Phones 45 Table 13 Call History Information for Phones (continued) Column Description Duration (hh:mm:ss) This field contains the time duration for a specific call. Features Used This field contains a list of calling features used during a specific call. NOTE: If a speed dial is made using a mapped button, nothing for the call is listed in the Features Used column. If the same speed dial is made manually, the Features Used column lists Speed Dial.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Figure 8 Selective Call Ring Tones Window The Selective Call Ring Tones page contains two columns of information available for each phone registration. Table 14 lists each column and describes the type of information available in that column. Table 14 Ring Tones Page Descriptions Column Description Phone Number This field contains the phone number of an incoming call that you want to assign a specific ring tone to.
Viewing the LCD Directory Adding or Editing Ring Tones of Specific Phones 47 To add or edit ring tones of specific phones: 1 Search for a particular end user. See Searching for End Users on page 24. 2 From the Users page, click Phones in the Phones column. The User Phones page appears. 3 From the User Phones page, click Selective Ringing in the Actions column. The Selective Call Ring Tones page appears. See Figure 8. 4 Fill out the fields according to the descriptions provided in Table 14. 5 Click Save.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Figure 9 LCD Directory Window
Configuring Media Access Control Configuring Media Access Control Adding a MAC Address 49 The Media Access Control (MAC) address is used to physically identify each telephone within the network. Every telephone has a unique MAC address, which is located on the bottom of the telephone. In order to associate a MAC address with the correct phone number, you need to register them. To add a MAC address: 1 From the left-hand side of the main page, click the Media Access Control heading.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Table 15 MAC Address field descriptions Field Heading Description Locked Indicated whether or not the telephone is disabled from the end user. Checked - The end user cannot change their extension using their telephone. Unchecked - The end user can change their extension using their telephone. Location Physical location of the phone. For example, you could indicate what the building, room, or cube the telephone is in. 4 Click Save.
Configuring an Attendant Console 51 Configuring an Attendant Console The Attendant Console allows an attendant to manage call handling within the enterprise more productively and quickly for end users. Calls can be accepted and dispatched within the enterprise and allows an attendant to verify if a telephone is busy. Up to three attendant consoles can be configured for each VCX system.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER 2 Fill in the fields according to the Table 18. Table 18 lists the Attendant Console field descriptions. Table 16 Attendant Console Field Description Field Description MAC Address MAC address of the attendant console. Location Textual description of where Attendant Console is located such as a cube, office, or geographic area. Associated User Phone Address The address (sip:1234@10.67.10.
Configuring an Attendant Console 53 5 Map the phone extensions to the attendant console buttons. The attendant console allows up to 100 telephones to be configured. a From the Attendant Console page, under the Actions column, click Extension Mappings in the same row as the attendant console you want to edit. The Attendant Console page appears, which allows the attendant console buttons to be mapped to specific extensions. b There are 100 fields available to configure telephone extensions.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Editing Extensions on an Attendant Console To edit the extensions for a attendant console: 1 From the left-hand side of the main page, click Attendant Console. The Attendant Console page appears. 2 From the Actions column, in the same row as the attendant console you want to edit telephone extension mappings for, click Extension Mappings. The Attendant Console page appears that allows telephone extension mapping configuration.
Configuring Patterns Deleting an Attendant Console 55 To delete an attendant console: 1 From the left-hand side of the main page, click Attendant Console. The Attendant Console page appears. 2 Click the checkbox(es) preceding the MAC Address(es) for each attendant console(s) you want to delete. 3 Click Delete Selected. A pop-up window appears verifying you really want to delete the attendant console. 4 Click OK. 5 The Attendant Console page refreshes, verifying the attendant console was deleted.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Figure 11 Add Pattern Window 3 Fill in the fields according to the Table 18. Table 18 lists the Add Pattern field descriptions. Table 18 Add Pattern Field Description Field Description PATTERN NAME A unique name for the pattern. PATTERN This is the pattern value. It can contain a wild card (*), but only one or zero. If a * is present, it should be the last character in the pattern value. 4 Click Save.
Configuring URI Translation Patterns Configuring URI Translation Patterns 57 To successfully communicate with other voice networks, the authentication server translates numbers based on source and destination calling patterns. For example, if an end user dials number 456789 and the URI translation is configured so that the source pattern equals *and the destination pattern equals 456*, the result pattern is *@3com.com.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Figure 12 URI Translation Window 3 Use the drop-down menus according to Table 19. Patterns need to be pre-configured before you create any URI Translations. See “Configuring Patterns” on page 55 for more information. Table 19 URI Translation Menu Descriptions Field Description Group Name Assign the URI translation to a group: ■ Virtual Private Network Source Pattern The source pattern where the call is coming from.
Configuring URI Translation Patterns 59 If the caller’s telephone number is 847-555-2122, the 800 number for the caller’s company is 800-555-3433, the telephone number of the caller 508-555-4344, and the caller needs to dial a “9” to reach an outside line, you would set up an URI Translation in this manner: Source Pattern – sip:8* This signifies any telephone number that starts with an 8 (in this case 847-555-2122) within the company should follow the patterns set for the destination pattern.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Configuring Class of Service Class of Service indicates what phone numbers an end user is allowed to either place or receive. Class of Services are comprised of one or more elements. Elements are made of patterns, which are associated with a phone number type such as Local or Emergency (varies by country).
Configuring Class of Service 61 Figure 13 Class of Service Details For Window 5 Add elements to the Class of Service by selecting an element from the Select element to add it to the class drop-down menu. 6 Click Add. The Class Of Service Details For page refreshes. Continue to add as many elements as you want to the Class of Service.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Enabling or Disabling Inbound or Outbound Calls in a Class of Service To enable or disable inbound or outbound calls in a Class of Service: 1 From the left-hand side of the main page, click the Class of Service heading. The Class Of Service List page appears. 2 From the Name column, click the name of the Class of Service you want to edit. The Class Of Service Details For page appears.
Configuring Class of Service 63 element row, click under the Inbound calls and Outbound calls heading to either enable or disable these types of calls. ■ If Whitelist is listed — These types of elements (calls) are allowed to be placed or received. ■ If Blacklist is listed — These types of elements (calls) are not allowed to be placed or received. To delete elements from a Class of Service: a From the Action column, click Remove from class in the same row as the element that you want to delete.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Configuring Class of Service Elements Adding Class of Service Elements Elements are made of patterns, which are associated with a phone number type such as Local or Emergency. Elements are needed so Class of Service types can be created. Any element created is added to a drop-down menu for when you go to add or edit a Class of Service.
Configuring Type of Service 65 6 From the Type pattern value you want to add to element field, type a pattern for the element. 7 Click Add. The Patterns For page refreshes, showing the recently added pattern. Continue to add as many patterns as you want to associate with that element. Editing Class of Service Elements Editing a class of service element allows you to either delete or add a new pattern to an element.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Adding a Type of Service To add a Type of Service: 1 From the left-hand side of the main page, click the Type of Service heading. The Types Of Service List page appears. See Figure 15. Figure 15 Types of Service List Window 2 From the Type name of new type field, type in a unique name to describe the new Type of Service. 3 Click Add. The Types of Service List page refreshes showing the recently added Type of Service.
Configuring Type of Service 67 Figure 16 Type Of Service Details For Window 5 Add a feature to the Type of Service by selecting a feature from the Select feature to add it to the type drop-down menu. Features descriptions are provided in the Adding Phone Features section on page 32. 6 Click Add. The Type Of Service Details For page refreshes. Continue to add as many features as you want to the Type of Service.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Editing Type of Services To edit the features assigned to a Type of Service: 1 From the left-hand side of the main page, click the Type of Service heading. The Types Of Service List page appears. 2 From the Name column, click the name of the Type of Service you want to edit. The Type Of Service Details For page appears.
Configuring Emergency Services 69 To ensure that emergency calls always go through, a set of system-wide defaults are defined — the callback phone number and an emergency gateway, identified by its IP address. These system defaults are used for phones which are not part of any ELIN. The emergency dialable digits are controlled by the ERL screens. If the emergency digits are identified by an ERL then those emergency dialable digits will not be applied a Class of Service treatment.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER 2 Click Add New ERL. The Emergency Location page appears. 3 In the Location field, type a descriptive identifier for the location the ERL is for based on geographic or physical location. For example, building XYX, 1st floor. There is a 10 character limit. 4 In the Emergency Callback Phone field, type the phone number of the contact person responsible for emergency situations within an organization (for example, a security guard). 5 Click Save.
Configuring Emergency Services 71 The List of IP Ranges for page appears. b Click Add New. The IP Address Range page appears. c In the IP Address field, type the IP network address for phones you want to include in this ERL. d In the Subnet Mask field, type the subnet mask for this IP address range. e Click Save. The List of IP Ranges for page refreshes showing the new IP address range. 7 Configure the Emergency Digits for the ERL.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER a Click from the top of the Emergency Digits For page to return to the ERL configuration page. b Click Emergency Gateway IP within the same row as the ERL you want to configure. The Emergency Gateway IP Addresses For page appears. c Click Add New. The Gateway IP Address page appears.
Configuring Emergency Services 73 a new emergency caller and the association with an older emergency caller is overwritten with the association of the new emergency caller. f In the Usage Release Timer field, type in the maximum amount of time you want to allow the ELIN to remain in use. This number is entered as a string in hours and the range is 1 through 24.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Deleting ERLs To delete an ERL: 1 From the left-hand side of the Users main page, click the Emergency Services heading. The Emergency Response Locations page appears. 2 Click the checkbox(es) preceding the ERL(s) you want to delete. 3 Click Delete Selected. A pop-up window appears, verifying if you really want to delete the ERL(s). 4 Click OK. The Emergency Response Location page refreshes, verifying the ERL(s) were deleted.
Configuring Emergency Services Deleting IP Addresses from an ERL 75 To delete an IP address range from an ERL. 1 From the left-hand side of the Users main page, click the Emergency Services heading. The Emergency Response Locations page appears. 2 From the Location Settings heading, click IP Ranges within the same row as the ERL you want to delete IP address from. The List of IP Ranges for page appears. 3 Click the checkbox(es) preceding the IP address(es) you want to delete.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Deleting Emergency Digits from an ERL To delete an Emergency Digit from an ERL. 1 From the left-hand side of the Users main page, click the Emergency Services heading. The Emergency Response Locations page appears. 2 From the Location Settings heading, click Emergency Digits within the same row as the ERL you want to delete an Emergency Digit from. The Emergency Digits For page appears.
Configuring Emergency Services 77 5 Click Save. The Emergency Gateway IP Addresses For page refreshes, showing the Emergency Gateway. Deleting Emergency Gateway IP Addresses from an ERL To delete an Emergency Gateway IP Address from an ERL. 1 From the left-hand side of the Users main page, click the Emergency Services heading. The Emergency Response Locations page appears.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER 3 From the ELIN heading, click the ELIN you want to edit. The Emergency Line ID Number page appears. 4 From the ELIN field, type the Emergency Location Identification Number. 5 In the Association Release Timer field, type in the amount of time you want to leave the ELIN associated to the emergency caller. This number is entered as a string in hours and the range is 1 through 24. This association is used to callback the emergency caller.
Configuring Dial Plans 79 The Emergency Line ID Numbers page refreshes, verifying the ELIN(s) were deleted. Configuring Dial Plans Adding Dial Plans Dial plans are comprised of individual or bundled dial rules. By creating dial plans, it makes it easier for you to configure end user phones since the dial plan names are added to a drop-down menu when you configure an end user phone. Dial rules must be created before a dial plan is created.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Figure 19 Add Dial Plan Window 4 Type a unique name to assign to the dial plan in the Name field. 5 Click Update. The Dial Plans page appears, showing the new dial plan name. 6 Click Dial Rules in the same row as the new dial plan to associate dial rules with it. The Dial Rules For Dial Plan: page appears. See Figure 20.
Configuring Dial Plans 81 Figure 20 Dial Rules For Dial Plan: Window 7 Click Assign Dial Rules. The Assign New Dial Rules for Dial Plan: page appears. Figure 21.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Figure 21 Assign New Dial Rules for Dial Plan: Window 8 Click the checkbox of each dial rule you want to associated with the new dial plan. 9 Click Assign Selected. The Dial Rules For Dial Plan: page appears showing all of the dial rules associated with that dial plan. Editing Dial Plan Names To edit a dial plan name: 1 From the left-hand side of the main page, click Dial Plans. The Dial Plans page appears.
Configuring Dial Rules Editing Dial Rules Associated with a Dial Plan 83 To edit the dial rules associated with a dial plan: 1 From the left-hand side of the main page, click Dial Plans. The Dial Plans page appears. 2 Click Dial Rules in the same row as the dial plan you want to edit. The Dial Rules For Dial Plan: page appears. a To assign additional dial rules, click Assign Dial Rules.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER Adding Dial Rules To add a dial rule: 1 From the left-hand side of the main page, under the Dial Plans heading, click Dial Rules. The Dial Rules page appears. 2 Click Add Dial Rules. The Add Dial Rule page appears. See Figure 22. Figure 22 Add Dial Rules Window 3 Fill out the fields according to Table 20. Table 20 describes the Dial Rule Parameters fields.
Configuring Call Park 85 Table 20 Dial Rule Parameter Field Descriptions (continued) Field Description Timeout This indicates the number of seconds that the phone will wait for another digit to be dialed before it places the call. Note: The default timeout is 5 seconds. Pattern This represents a defined string of numbers.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER To configure the call park feature: 1 From the left-hand side of the main page, under the Server Configuration heading, click Call Park. The Call Park Configuration page appears. See Figure 23. Figure 23 Call Park Configuration Window 2 Fill out the fields according to Table 21. Table 21 describes the Call Park Configuration fields.
Configuring the Server Configuring the Server Enabling VPN Translation 87 The Server Configuration section enables or disables Virtual Private Network (VPN) translation for URI translation patterns. To enable VPN and speed dial translation: 1 From Server Setup heading, click Server. The Server Configuration page appears. 2 Click the VPN Translation checkbox to enable it. The description for the options are shown in Table 22.
CHAPTER 1: CONFIGURING THE AUTHENTICATION SERVER
2 CONFIGURING THE DIRECTORY SERVER This chapter provides information on how to configure the directory server through the provisioning server. Use the provisioning server to manage routes; bundles; end points; black and white lists; patterns; out dial patterns; requestors; holidays; calender, week day, and day time bands; URI route maps; and destination URI translation.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER Figure 24 Directory Server’s Main Page Configuring a Call Route through the Web Provisioning Server To add a call route using the web provisioning server: 1 Follow the steps according the “Accessing the Directory Server Configurables” section on page 89. 2 Add an end point. For instructions, go to the “Adding End Points” section on page 108. 3 Add a pattern for the end point. For instructions go to the “Adding Patterns” section on page 91.
Managing Patterns 91 8 Associate the route with the end point added. For instructions go to the “Assigning End Points and Bundles to Routes” section on page 122. 9 Associate the out dial pattern with the routes added. For instructions go to the “Assigning Out Dial Patterns for Routes” section on page 124. Managing Patterns Adding Patterns This section provides information on how to add, edit, and delete patterns. Patterns are regular expressions that are used in various tables in the pattern schema.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER ■ Individual — From the Action column, click Delete in the same row as the pattern. ■ Multiple — Check each box preceding the Name column and then click Delete Selected. A pattern cannot be deleted if it is associated with a route. You will get a DB Exception error if you try to delete a pattern that is associated with a route. The Patterns page refreshes, showing the deleted patterns.
Managing Out Dial Patterns 93 4 Fill in the fields according to the descriptions below: ■ Name — Enter a unique name for the out dial pattern. ■ Match Pattern — From the drop-down menu, click a pattern listed in the List of Patterns page. ■ Translation String — Type a translation string for the out dial pattern. This determines how the outbound destination URI will be translated. ■ E164 Description — If the destination URI is a E.164 number then this field lists the type of the resultant E.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER ■ Number Plan Description — Indicates the type of numbering plan used. The ISDN PRI is provisioned in the outdial pattern. The directory server sends the NPI value to the SIP Proxy. The SIP proxy adds the NPI value to the outgoing SIP INVITE and sends it to the chosen gateway to make the outgoing call. If an NPI value is provisioned it forces an NPI value to be added to the outgoing call parameters or override an existing NPI value.
Managing Requestors 95 Figure 26 List of Requestors Window 2 From the List of Requestors page, click Add Requestor. The Add Requestor page appears. 3 Fill in the fields with the following requestor information. ■ Name — Unique requestor name. ■ IP Address — IP address in binary. ■ IP Port — IP address port number. ■ DNS Name — Name of qualified domain name. ■ Time Zone Name — Name of time zone such as CST, EST, etc.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER Editing Requestors To edit a requestor: 1 From the directory provisioning page, click Requestors. The List of Requestors page appears. 2 From the List of Requestors page, edit a requestor by clicking on the requestor name under the Name column. The Edit Requestor page appears. 3 Edit the necessary fields according to these descriptions: ■ Id — This value is automatically generated and cannot be changed. ■ Requestor Name— Unique requestor name.
Managing Holidays Managing Holidays Adding Holidays This sections provides information on how to add, edit, and delete calendar holidays based on the month and day, and is used as input parameters for URI Translation and Routing. To add holidays: 1 From the directory provisioning page, click Holidays. The List of Holidays page appears. See Figure 27. Figure 27 List of Holidays Window 2 From the List of Holidays page, click Add Holiday. The Add Holiday page appear. See Figure 28.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER Figure 28 Add Holiday Window 3 Fill in the fields with the following holiday information. ■ Name — Type a unique holiday name. ■ Month — From drop-down menu, click month of year for holiday. ■ Day — From drop-down menu, click day of month for holiday. 4 Click Save. The List of Holidays page appears, showing the added holiday. Editing Holidays To edit holidays: 1 From the directory provisioning page, click Holidays. The List of Holidays page appears.
Managing Week Day Bands 99 4 Click Save. The List of Holidays page appears, showing the edited holiday. Deleting Holidays To delete a holiday: 1 From the directory provisioning page, click Holidays. The List of Holidays page appears. 2 From the List of Holidays page, either an individual or multiple holidays can be deleted. ■ Individual — From the Action column, click Delete in the same row as the holiday. ■ Multiple — Check each box preceding the Name column and then click Delete Selected.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER Figure 29 List of Week Day Bands Window 2 From the List of Week Day Bands page, click Add Week Day Band. The Add Week Day Bands page appears. See Figure 30. Figure 30 Add Week Day Bands Window 3 In the Name field, type a description. 4 Click the checkboxes for days to include in the week day band.
Managing Week Day Bands 101 5 Click Save. The List of Week Day Bands page appears, with the added week day band. Editing Week Day Bands To edit week day bands: 1 From the directory provisioning page, click Week Day Bands. The List of Week Day Bands page appears. 2 From the List of Week Day Bands page, edit a week day band by clicking a week day band from the Name field. The Edit Week Day Band page appears.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER Managing Day Time Bands Adding Day Time Bands This section provides information on how to add, edit, and delete day time bands. Day time bands are used as input parameters for URI Translation and Routing and are based on the hour, minute, and second for a single day. To add day time bands: 1 From the directory provisioning page, click Day Time Bands. The List of Day Time Bands page appears. See Figure 31.
Managing Day Time Bands 103 Figure 32 Add Day Time Band Window 3 Fill in the fields with the following day time band information. ■ Name — Type a unique calendar band name ■ Start Time — From the drop-down lists, select the correct Hour, Minute, and Second for the daytime band to start. The drop-down lists use military time, for example, 0 equals 12:00:00AM (midnight) and 23:00:00 equals 11:00:00PM.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER 3 Edit the necessary fields according to these descriptions: ■ Band Id — This value is automatically generated and cannot be changed. ■ Name — Type a unique calendar band name ■ Start Date — From the drop-down lists, select the correct Month, Date, Year, Hour, Minute, and Second for the calendar band to start. The time drop-down lists use military time, for example, 0 equals 12:00:00AM (midnight) and 23:00:00 equals 11:00:00PM.
Managing Calendar Bands Managing Calendar Bands Adding Calendar Bands 105 This section provides information on how to add, edit, and delete calendar bands. Calendar bands are used as input parameters for URI Translation and Routing and are based on a calendar time band table, which includes the year, month, day, hour, minute, and second. To add calendar bands: 1 From the directory provisioning page, click Calendar Bands. The List of Calendar Bands page appears. See Figure 33.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER The Add Calendar Band page appears. See Figure 34. Figure 34 Add Calendar Band Window 3 Fill in the fields with the following calendar band information. ■ Name — Type a unique calendar band name ■ Start Date — From the drop-down lists, select the correct Month, Date, Year, Hour, Minute, and Second for the calendar band to start. The time drop-down lists use military time, for example, 0 equals 12:00:00AM (midnight) and 23:00:00 equals 11:00:00PM.
Managing Calendar Bands 107 The Edit Calendar Band page appears. 3 Edit the necessary fields according to these descriptions: ■ Band Id — This value is automatically generated and cannot be changed. ■ Name — Type a unique calendar band name ■ Start Date — From the drop-down lists, select the correct Month, Date, Year, Hour, Minute, and Second for the calendar band to start. The time drop-down lists use military time, for example, 0 equals 12:00:00AM (midnight) and 23:00:00 equals 11:00:00PM.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER Managing End Points Adding End Points This section provides information on how to add, edit, and delete end points, and manage the out dial patterns associated with them. An end point is usually a Tier 1 component that is a destination element in a route. End points are assigned to routes and are returned to the signaling application in the route response. To add end points: 1 From the directory provisioning page, click End Points.
Managing End Points Figure 36 End Point Window 109
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER 3 From the drop-down menu, select a type of end point to add, see Table 23 for possible end point combinations: ■ Type — The device type that is associated with the end point. The supported devices are listed in Table 23. ■ Active — ■ Yes = active ■ No = inactive ■ Description — Unique description of the end point. ■ Click either the IP Address or DNS radio button and type an IP address or DNS in the field below.
Managing End Points Editing End Points 111 To edit end points: 1 From the directory provisioning page, click End Points. The List of End Points page appears. 2 From the List of End Points page, edit end points by clicking an end point from the Name column. 3 Edit the necessary fields according to the descriptions provided below: ■ ID — This value is automatically generated and cannot be changed. ■ Active — ■ Yes = active ■ No = inactive ■ Description — Unique description of the end point.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER An end point cannot be deleted if it is associated with a route. You will get a DB Exception error if you try to delete an end point that is associated with a route. The List of End Points page refreshes, showing the deleted end points. Adding or Editing Out Dial Patterns of End Points To add or edit out dial patterns of end points: 1 From the directory provisioning page, click End Points. The List of End Points page appears.
Managing End Points 113 Figure 38 New OutDial Patterns for EndPoint Window The out dial patterns must be set up according to the instructions provided in the “Managing Out Dial Patterns” section to have any out dial pattern options to choose from. 5 Add out dial patterns to end points by clicking the checkboxes preceding the OutDialPattern column. 6 Click Assign Selected OutDialPatterns. The EndPoints - OutDial Patterns page appears, showing the assigned out dial patterns.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER 4 From the EndPoints - OutDial Patterns page, either an individual or multiple out dial pattern can be deleted. ■ Individual — From the Action column, click Delete in the same row as the out dial pattern. ■ Multiple — Check each box preceding the Name column and then click Delete Selected. The EndPoints - OutDial Patterns page refreshes showing the deleted out dial patterns.
Managing End Point Black Lists 115 Figure 39 EndPoint Blacklist Window 2 Click Add Blacklist. The New EndPoint to Blacklist page appears. See Figure 40. Figure 40 New Endpoints To Blacklist Window 3 Click the radio button preceding the Name column for the end point to black list. 4 Click Select Patterns to BlackList. The List of Patterns page appears.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER 5 Click the checkboxes preceding the Pattern Name field for the patterns to associate with the black listed end point. 6 Click Add. The EndPoint Blacklist page appears, showing the black listed end points and the associated patterns. Deleting End Point Black Lists To delete end point black lists: 1 From the directory provisioning page, as shown in Figure 24, click End Point Black Lists. The EndPoint Blacklists page appears.
Managing End Point White Lists 117 Figure 41 EndPoint Whitelists Window 2 Click Add Whitelist. The New EndPoint to Whitelist page appears. See Figure 42. Figure 42 New Endpoint to Whitelist Window 3 Click the radio button preceding the Name column for the end point to white list. 4 Click Select Patterns to WhiteList.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER The List of Patterns page appears. 5 Click the checkboxes preceding the Pattern Name field for the patterns to associate with the white listed end point. 6 Click Add. The EndPoint Whitelist page appears, showing the white listed end points and the associated patterns. Deleting End Point White Lists To delete end point white lists: 1 From the directory provisioning page, as shown in Figure 24, click End Point White Lists.
Managing Routes Figure 43 List of Routes Window 119
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER Table 24 lists the fields for List of Routes.l Table 24 List of Routes Field Descriptions Name Description Use this checkbox to delete more than one route at a time. If a box is checked, and then the Delete Selection button is clicked, all of the checked routes are deleted. Name The name of the route you assign. Code Contact This is used by the SIP Proxy to determine how the end points in the route are activated.
Managing Routes 121 Figure 44 Route Information Window The following fields appear in the Add Routes page, which are described in Table 24: ■ Name ■ Contact Code ■ Sort Order 3 Fill in the information for the new route. 4 Click Save. The List of Routes page appears, showing the new route. Editing Routes To edit routes: 1 From the directory provisioning page, as shown in Figure 24, click Routes. The List of Routes page appears.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER Deleting Routes To delete routes: 1 From the directory provisioning page, as shown in Figure 24, click Routes. The List of Routes page appears. 2 From the List of Routes page, either an individual or multiple route can be deleted. ■ Individual — From the Action column, click Delete in the same row as the route. ■ Multiple — Check each box preceding the Name column and then click Delete Selected.
Managing Routes 123 The New EndPoints For Route page appears. See Figure 45. Figure 45 New EndPoints For Route Window 4 Assign an end point and/or bundle to a route by clicking the checkboxes preceding the Type column. 5 Click Assign Selected EndPoints. The Route - EndPoints page appears, showing the assigned end points and/or bundles.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER 5 Click Update. The Route - EndPoint page refreshes, showing the updated end points. Unassigning End Points or Bundles Assigned to Routes To unassign bundles and/or end points assigned to routes: 1 From the directory provisioning page, as shown in Figure 24, click Routes. The List of Routes page appears. 2 From the List of Routes page, click Manage EndPoints from the Action column for the route that needs to have an end point and/or bundle unassigned from.
Managing Routes 125 Figure 46 Route - EndPoint Window 3 From the Route - EndPoint page, in the Action column, click Manage OutDial Pattern for the bundle to modify. The Route - EndPoints - OutDial Patterns page appears, showing the out dial patterns associated with either bundle or end point of the route. 4 Click Assign OutDial Pattern. The New OutDial Patterns For Route - EndPoint page appears, showing the available out dial patterns available to assign.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER Figure 47 Route - EndPoints - OutDial Patterns Window Unassigning Out Dial Patterns of Routes To unassign out dial patterns from either an end point or bundle associated with a route: 1 From the directory provisioning page, as shown in Figure 24, click Routes. The List of Routes page appears. 2 From the List of Routes page, click Manage EndPoints from the Action column for the route that needs to have an out dial pattern unassigned from it.
Managing URI Route Maps 127 The Route - EndPoints - OutDial Patterns page refreshes, verifying the out dial pattern was unassigned. Managing URI Route Maps This section provides information on how to add and delete URI route maps. A URI route map maps destination URIs to route IDs using various routing policies and source based input parameters.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER Figure 48 List Routes Mapped To URI Patterns Window 2 From the List Routes Mapped To URI Patterns page, click Add URI Route Map.
Managing URI Route Maps 129 The URI Route Map page appears. See Figure 49. Figure 49 URI Route Map Window 3 Fill in the fields with the information you need to add your mapped route. This associates a pattern with a route. Descriptions for each field are below. There are 5 categories of source based input parameters. There is a specific ordering of how these categories are used to determine the resultant output. Database records are returned for the first categories that have a match.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER ■ Active — If checked it is active, if not checked it is inactive. ■ Blacklisted — If checked it is black listed, if not checked it is not black listed. ■ Name — Type a unique name for the URI Route Map. ■ Route — This is a defined route. To add a route to select from the drop-down menu, go to the “Managing End Point Black Lists” section. ■ Pattern — This is a defined pattern.
Managing URI Route Maps ■ ■ 131 Day Band — This is a defined day time band that represents a time band within one day (0800 - 1200 hours). The resolution is done to seconds. To add a day time band to select from the drop-down menu, go to the “Adding Day Time Bands” section. A day time band and a week day band must be used together, but cannot be used in combination with other source based inputs. Calendar Bands — This is a defined specific calendar band (calendar band) such as 1/1/01 to 6/1/01.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER ■ Click a link in any column other than the Map column — if one of these links is selected, any modifications to the specific link is globally applied to all things associated with that link. For example, if a pattern is modified, anything that uses that pattern is modified. 3 A new window appears, that is related to the type of link selected. Make the necessary changes and click Save.
Managing URI Route Black Lists 133 Figure 50 List of Blacklisted EndPoints For A URI Route Window 2 From the List of Blacklisted EndPoints For A URI Route page, click Add Blacklisted Endpoint. The Select A URI Route page appears. 3 From the Add Endpoint Blacklist column, click Add Endpoint Blacklist for the URI Route that needs to have end points black listed on. 4 The Available Route Endpoints page appears.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER 2 From the List of Blacklisted EndPoints For A URI Route page, either an individual or multiple end point can be unassociated with the URI route map. ■ Individual — From the Action column, click Delete in the same row as the end point. ■ Multiple — Check each box preceding the Uri Route Name column and then click Delete Selected.
Managing URI Translation Adding Destination URI Translations 135 To add destination URI translations: 1 From the directory provisioning page, as shown in Figure 24, click URI Translation. The List Outdial Patterns Mapped To URI Patterns page appears. 2 From the List of Available URI Translations page, click Add URI Translation. The URI Translation page appears. 3 Fill in the fields with the information you need to add your mapped route. This associates a pattern with a route.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER ■ Sourced Based — If checked, it will associate the defined inputs (Direct and Indirect Requestors, Day Band, and Date Band) to the URI route map. If not check, no source based inputs will be associated with the URI route map.
Managing URI Translation 137 to select from the drop-down menu, go to the “Adding Calendar Bands” section. This cannot be used in combination with other source based inputs. 4 Click Save. The List OutDial Patterns Mapped To URI Patterns page appears, showing the added URI translation.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER Server Configuration Globally Configuring Routes The Server Configuration option is used to globally configuring all routes in a directory server database. The Directory Server Configuration page represents a sequence of features that can be provisioned and applied globally. All of the features need to be provisioned first in order to be applied to the routes.
Server Configuration 139 section on page 94, and are usually Tier 1 components such as a Gateway. b To enable Direct Requestors, check the Direct Requestors box. Direct Requestors are provisioned in the “Managing Requestors” section on page 94, and are usually Tier 2 components such as a Gatekeeper or SIP Proxy. c To enable Holidays, check the Holiday box. Holidays are provisioned in the “Managing Holidays” section on page 97. d To enable Week Day Bands and/or Day Time Bands check the Week/Day Bands box.
CHAPTER 2: CONFIGURING THE DIRECTORY SERVER
3 CONFIGURING THE ACCOUNTING SERVER The accounting server sends call detail records (CDRs) to the billing support server (if a billing support server exists in the system), exports CDRs into flat files or directly info the RT_CDR table, and deletes individual CDRs after a configurable period. You can also schedule jobs to export and delete CDRs. Database Identification Configuration Changing the Database Name Use either the acctconfig.
CHAPTER 3: CONFIGURING THE ACCOUNTING SERVER Enterprise Management Suite To change the database server name for the accounting server using EMS: 1 From the Explorer tab, select the accounting server. 2 From the Properties tab, select the Database Configuration tab. 3 In the ServerName column, double-click the associated field and enter the new database server name. For example, cwbes. 4 Click Save all.
Configuring the Database Keep Alive Timeout Configuring the Database Keep Alive Timeout 143 Configure the database keep alive timeout setting for the accounting server using either the server configuration file (acctconfig.xml) or Enterprise Management Suite. Enterprise Management Suite To configure the database keep alive timeout setting for the accounting server using EMS: 1 From the Explorer tab, select the accounting server. 2 From the Properties tab, select the Database Configuration tab.
CHAPTER 3: CONFIGURING THE ACCOUNTING SERVER Enterprise Management Suite To configure the client activity interval for the accounting server using EMS: 1 From the Explorer tab, select the accounting server. 2 From the Properties tab, select the BES Common Configuration tab. 3 Double-click the ClientActivityInterval field and enter the client activity interval in milliseconds. The default setting is 200000. The range is 2000 through 200000. 4 Click Save all.
Configuring the Logging Level 145 3 Double-click the ClientReqThreads field and enter the client request threads. The range is 1 through 255. 4 Click Save all. Configuring the Logging Level Server Configuration File Configure the logging level for the accounting server using either the server configuration file (acctconfig.xml) or Enterprise Management Suite. To configure the logging level using the acctconfig.xml file: 1 Log in as root. 2 Stop the accounting server.
CHAPTER 3: CONFIGURING THE ACCOUNTING SERVER Enabling Packet Tracing Server Configuration File Enable packet tracing for the accounting server using either the server configuration file (acctconfig.xml) or Enterprise Management Suite. To enable packet tracing using the acctconfig.xml file: 1 Log in as root. 2 Stop the accounting server. 3 Go to the /opt/3com/VCX/acct/conf directory. 4 Edit the acctconfig.xml file for the accounting server.
Creating Backup Configuration Files Creating Backup Configuration Files 147 Enterprise Management Suite allows you to save the configurations for the accounting server and create CFM backup configuration files. Use configuration file manager (CFM) backup configuration files to restore the accounting server to a previous set of configurations. CFM files store data in a defined format that can be altered. Creating a CFM Backup File You can save the Linux Server configuration to a CFM file.
CHAPTER 3: CONFIGURING THE ACCOUNTING SERVER Restoring Backup Configuration Files You can restore the 3Com VCX IP Telephony Server configuration from the last backup (current), the baseline, or the planned CFM file. To restore the 3Com VCX IP Telephony Server configuration: 1 From the Explorer tab, right-click the 3Com VCX IP Telephony Server. 2 Select the configuration file you want to restore (baseline, current, or planned).
SNMP Support SNMP Support Enabling SNMP Support 149 The SNMP Common Agent needs to be enabled in order for the accounting server to be recognized by SNMP MIB browsers such as Enterprise Management Suite (EMS). To enable SNMP support on the accounting server: 1 Log in as root. 2 Stop the common agent. 3 Stop the accounting server. 4 Go to the /opt/3com/VCX/acct/conf directory. 5 Open the acctconfig.xml file. 6 Under the SNMP Configuration tag, edit the acctconfig.
CHAPTER 3: CONFIGURING THE ACCOUNTING SERVER 3 Double-click the 3Qenables field and select either enable or disable from the drop-down list. 4 If you enabled 3Q, double-click the ClientThread field and enter the number of threads to receive data. 5 Click Save all.
4 CONFIGURING THE CALL PROCESSOR The VCX V7210 Call Processor is an application that provides call routing as well as other call services for the VCX V7000 IP Telephony Solution. The Call Processor XML file (nmdb.xml) should not be modified manually since the Call Processor writes freely to the file at run-time and requires the Call Processor to be stopped in order to be edited. Use either CLI commands or the Enterprise Management Suite to configure the Call Processor instead.
CHAPTER 4: CONFIGURING THE CALL PROCESSOR Configuration Methods Through EMS Through CLI Configuring Call Control Through EMS There are two recommended means of configuring the Call Processor. This section provides a simple overview of each method, which are listed in order of usability (easiest listed first). ■ Through the Enterprise Management Suite (EMS) ■ Through the Command Line Interface EMS is an optional management tool that offers a simple method to configure the call processor.
Configuring Trusted Endpoints 153 Table 27 EMS Call Controller Call Control Configurable Descriptions Attribute Description Range Default AuthDomainString This configurable determines what value the Call Processor will send in the "domain" parameter of the authentication challenge to SIP Endpoints. any string 3Com AuthRealmString This configurable determines what value the Call any string Processor will send in the "realm" parameter of the authentication challenge to SIP Endpoints.
CHAPTER 4: CONFIGURING THE CALL PROCESSOR Through the CLI To add a trusted endpoint to a Call Processor using the CLI: 1 Log onto the server hosting the Call Processor. 2 Navigate to the /opt/3com/VCX/callprocessor/remoteCli/bin. 3 Start the Remote CLI application. .
Configuring Trusted Endpoints 155 5 To exit the Remote CLI application, enter: exit Through EMS To add a trusted endpoint to a Call Processor using EMS: 1 Log into EMS. 2 From the Explorer tab, navigate to the 3Com Sip Call Processor. 3 From the Properties tab, click Trusted Endpoints. 4 Click Add. The Add row to table window appears. 5 From the Index field, specify the index of the trusted endpoint. 6 From the IpAddress field, enter an IP address that you want to make a trusted endpoint.
CHAPTER 4: CONFIGURING THE CALL PROCESSOR Through EMS To edit a trusted endpoint to a Call Processor using EMS: 1 Log into EMS. 2 From the Explorer tab, navigate to the 3Com Sip Call Processor. 3 From the Properties tab, click Trusted Endpoints. 4 Double-click the field (s) you want to edit under the IpAddress column. 5 High-light what you want to edit. 6 Type in the new information. 7 Click in a different field to activate the Save all button. 8 Click Save all.
Verifying Call Processor Version 157 3 From the Properties tab, click Trusted Endpoints. 4 From the IpAddress column, click the IP Address field you want to delete. 5 Click Delete. The trusted endpoint is removed from the call processor. Verifying Call Processor Version To verify what the Call Processor version is. Through the Command Prompt To verify the Call Processor version from a command prompt: 1 Log onto the server hosting the Call Processor as root.
CHAPTER 4: CONFIGURING THE CALL PROCESSOR The Add row to table window appears. 5 Fill in the fields according to the descriptions in Table 29. Table 29 Accounting Server Tab Descriptions in EMS Attribute Description Values Priority Specifies the priority of the accounting server. Integer: 1 - 5 1 = primary) 2 = secondary AcctServerIpAddress Specifies the IP Address of the IP Address String accounting server. xxx.xxx.xxx.
Configuring the Back-end Server Plugins 159 config acctc use=false config accts pri=2 IpAddress= config accts pri=2 LocalIpAddress= config acctc use=true 5 The CLI lists the new IP address of the accounting server. 6 Exit the Remote CLI application. Editing Accounting Server IP Addresses To edit an accounting server IP address for the Call Processor using EMS: 1 Log into EMS.
CHAPTER 4: CONFIGURING THE CALL PROCESSOR Adding Primary and Secondary Authentication Servers Authentication servers can be added using either EMS or through the Remote CLI Application. Through EMS To add an authentication server through EMS: 1 Log into EMS. 2 From the Explorer tab, navigate to the 3Com Sip Call Processor. 3 From the Properties tab, click Authentication Servers. 4 Click Add. The Add row to table window appears. 5 Fill in the fields according to the descriptions in Table 29.
Configuring the Back-end Server Plugins 161 config authc use=true 5 The CLI lists the new IP address of the authentication server. 6 Exit the Remote CLI application. To add a secondary authentication server through the CLI: 1 Log onto the server hosting the Call Processor. 2 Navigate to the /opt/3com/VCX/callprocessor/remoteCli/bin. 3 Start the Remote CLI application.
CHAPTER 4: CONFIGURING THE CALL PROCESSOR Removing Authentication Servers To remove an authentication server from the call processor: Through EMS To remove an authentication server through EMS: 1 Log into EMS. 2 From the Explorer tab, navigate to the 3Com Sip Call Processor. 3 From the Properties tab, click Authentication Servers. 4 Put cursor in the row of the authentication server you want to delete. 5 Click Delete. The authentication server is removed from the VCX IP Telephony Server.
Configuring the Back-end Server Plugins 163 Through the CLI To add a primary directory server through the CLI: 1 Log onto the server hosting the Call Processor. 2 Navigate to the /opt/3com/VCX/callprocessor/remoteCli/bin. 3 Start the Remote CLI application.
CHAPTER 4: CONFIGURING THE CALL PROCESSOR 4 Double-click the IP Address under the DirServerIpAddress column you want to edit. 5 High-light what you want to edit. 6 Type in the new IP address. 7 Click in a different field to activate the Save all button. 8 Click Save all. The new IP Address is added to the nmdb.xml file and is listed in the DirServerIpAddress column of EMS.
Monitoring Call Statistics Enabling or Disabling Authentication Server 165 To enable or disable an authentication server: Through EMS 1 Log into EMS. 2 From the Explorer tab, navigate to the 3Com Sip Call Processor. 3 From the Properties tab, click Authentication Server Configuration. 4 From the UseAutheticationServerAdmin row, double-click the field in the same row under the 3COM Sip Call Processor column. ■ To enable, change to true. ■ To disable, change to false. 5 Click Save All.
CHAPTER 4: CONFIGURING THE CALL PROCESSOR Table 32 Call Statistics Field Attribute Descriptions Attribute Description CurrentActiveCalls This number defines the total number of calls that are in process of being connected, are already connected, or are in process of being disconnected. TotalAttemptCalls This number defines the total number of origination call attempts that were handled by the call processor.
5 Configuring 3Com Telephones CONFIGURING TELEPHONES There are multiple steps that need to be completed in order for a 3Com telephone to work within a VCX system. 1 Configure the telephone through the administration provisioning server. a Configure a new user. See “Adding End Users” on page 21. b Configure a phone extension to be associated with the new user. See “Adding Phones” on page 27. c Configure any phones restrictions that need to be added for the new user.
CHAPTER 5: CONFIGURING TELEPHONES Assessing the Telephone LUI Menus ■ Test the telephone buttons, display panel, and LEDs ■ Clear all device settings ■ Specify the MAC address of the NCP (test environment option) ■ View firmware information (technician option) ■ Test connectivity ■ Restart the telephone To access the LUI menu: 1 Cycle power to the telephone by disconnecting and then reconnecting its power connector, and then start the LUI utility (as described in step 2, next) before the
3Com Telephone Local User Interface Menus ■ 169 3Com 2101 Basic Telephone, see Figure 55 on page 172. Table 33 on page 173 describes each LUI utility menu item. Figure 52 Local User Interface Controls on the 3Com 3102 Business Telephone 6 1 5 3Com Test Menu Scroll-- Options 2 3 4 1 Display panel. 2 Soft buttons move the cursor left or right. The middle button is not used. 3 Key pad numeric keys select menu items or enter numeric characters in a menu item.
CHAPTER 5: CONFIGURING TELEPHONES Figure 53 Local User Interface Controls on 3Com 3101 and 3101SP Basic Telephones 1 3Com Test Menu NBX Test Menu Scroll-Options Scroll--Options 2 5 3 4 1 Display panel. 2 Soft buttons move the cursor left or right. The middle button is not used. 3 Key pad numeric keys select menu items or enter numeric characters in a menu item. Use the # key to save changes after you edit an item. 4 Access buttons AB1-AB4 (from left to right) select LUI menu items.
3Com Telephone Local User Interface Menus 171 Figure 54 Local User Interface Controls on the 3Com 2102 and 2102-IR Business Telephones 1 6 3Com Test Menu Scroll--Options 2 3 4 5 1 Display panel. 2 Soft buttons move the cursor left or right. The middle button is not used. 3 Program button starts and exits from the LUI utility or exits from a menu item and moves to the next higher menu.
CHAPTER 5: CONFIGURING TELEPHONES Figure 55 Local User Interface Controls on the 3Com 2101 Basic Telephone 1 3Com Test Menu Scroll--Options 2 7 6 3 5 4 1 Display panel. 2 Soft buttons move the cursor left or right. The middle button is not used. 3 Key pad numeric keys select menu items or enter numeric characters in a menu item. Use the # key to save changes after you edit an item. 4 Access buttons AB1-AB3 select LUI menu items. 5 Volume Down button selects LUI menu item AB4.
3Com Telephone Local User Interface Menus 173 Table 33 LUI Menu Items Menu Option Description 1 View Settings Press 1 on the number pad and scroll to view these options: MAC Address – MAC address of this telephone. NCP MAC Address – MAC address of call processor. All Fs, the normal value for this setting, indicates that the telephone responds to any NCP. SW Build Ident. – Software version running on this telephone. Serial # Rev – Telephone serial number and hardware version.
CHAPTER 5: CONFIGURING TELEPHONES Table 33 LUI Menu Items (continued) Menu Option Description 2 Set my IP Lets you specify the IP information for this telephone. 3 Set SubNMsk When entering an IP address: 4 Set Gatwy IP ■ ■ ■ ■ ■ 5 Set NCP IP Use the key pad to enter digits 0–9. Use the left and right soft keys or scroll keys to move the cursor left or right. If any of the fields within the IP address contain only one or two digits, add leading zeros. Example: Enter 10.234.1.125 as 010.
3Com Telephone Local User Interface Menus 175 Table 33 LUI Menu Items (continued) Menu Option Description 6 VCX Config Menu Alt Dnld Servr – The IP address of a secondary server that stores the telephone’s image. Set VLAN Config – Used to enable or disable VLAN configuration. ■ VLAN Enable – 1 You are prompted to enter the VLAN ID. A valid VLAN ID is in the range of 0 through 4095. Press the pound key (#) to store it in memory. ■ VLAN Disable - 0 7 Spare Reserved for future use.
CHAPTER 5: CONFIGURING TELEPHONES Table 33 LUI Menu Items (continued) Administration Telephone Feature Keys Menu Option Description AB1 Set NCP MAC This option is not used in VCX networks. AB2 Show EEProm Lets you scroll through the locations in the memory of the telephone. The information is presented in hexadecimal format and can be properly interpreted only by a 3Com service person. AB3 Ping H3/IP This option has no purpose in a VCX system and therefore is not used.
6 CONFIGURING THE COMPLEMENTARY ATTENDANT The Complementary Attendant Software (CAS) is an application that is installed on a computer with a Windows 2000 or Windows XP O/S, which is used to manage an enterprise’s telephone network. Attendants can monitor calls by seeing if they are busy, conference in callers, put calls on hold or park, dial callers, and transfer calls easily.
CHAPTER 6: CONFIGURING THE COMPLEMENTARY ATTENDANT Figure 56 Complementary Attendant GUI Updating Telephone Directory The telephone extension directory shows all of the end users within the VCX system. Any end users and their associated telephone extensions that are configured in the Administration Interface of the provisioning server (the server the complementary attendant is associated with) is automatically updated when the complementary attendant is started.
Changing the Telephone Associated with the CAS Changing the Telephone Associated with the CAS 179 In order to change a complementary attendant telephone, it must already be configured in the authentication server. To add the telephone and associated user, see “Adding End Users” on page 21 and “Adding Phones” on page 27. This makes the telephone available when you want to associate the complementary attendant with a different telephone.
CHAPTER 6: CONFIGURING THE COMPLEMENTARY ATTENDANT Table 35 CAS Server(s) Tab Descriptions (continued) Field Description Dialing Domain The IP address of the server where users are configured. In the administration provisioning server, users are created in two formats: 1 By using only the call processor’s IP address. For example, if the user is configured as sip:8475551234@, the dialing domain is . 2 By using a virtual IP address.
7 CALL REPORTING This chapter describes the Call Detail Records (CDRs), the fields contained in the CDRs, and how to configure the Call Report utility. Call Detail Records Introduction CDR Generating Components Call Detail Records (CDRs) contain a large amount of information about each call that is processed by the VCX V7000 IP Telephony Suite.
CHAPTER 7: CALL REPORTING Logging into the Call Report Utility To log into the Call Reports utility: 1 Login to the computer where the Call Report utility is installed and initially configured. 2 From the Start menu, click VCX Call Reports. The installation default location is Start | All Programs | 3Com VCX | VCX Call Reports. The Call Report utility appears. See Figure 57.
Changing the Servers Associated with the Call Report Utility 183 4 Any new files are downloaded from the server and displayed in the VCX tab fields. Retrieving VCX CDRs Automatically To update the CDR fields for a VCX system automatically: 1 From the VCX Call Reports utility, click the Preferences button. 2 Click the Retrieval tab. 3 Check the checkbox preceding the VCX: Automatically retrieve every hours field.
CHAPTER 7: CALL REPORTING Table 36 Call Report Server Preferences Descriptions (continued) Field Section Field Description VCX CDR Login User Name User name of the login for the VCX server hosting the billing support server. The default is root. Password Password of the login for the VCX server hosting the billing support server. The default is pvadmin. Remote Directory The location where the V7200 super CDR files are located. The default is /opt/3com/VCX/bss/db/export/.
Supported VCX CDR Field Descriptions 185 The program uninstalls. You should reboot your machine once the uninstallation occurs. Supported VCX CDR Field Descriptions This section contains information about each of the supported CDR fields from the call processor. These CDRs are captured by the Accounting Server and can either be sent to the Billing Support Server or made into a flat file. These fields can be viewed from the Call Records utility from the VCX tab.
CHAPTER 7: CALL REPORTING Table 37 Call Processor CDR Fields (continued) VCX Fields Description CODECTYPE Audio CODEC type used for the call, such as G.729, G.711, or G.723. CALLTERMINATION CAUSE 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.
8 CONFIGURING THE SIP PHONE DOWNLOADER This chapter describes how to configure the SIP phone downloader application through Enterprise Management Suite (EMS). The SIP downloader is initially configured through the installation scripts. Use this chapter to edit any SIP downloader information. The 3Com phone can be initially configured using the SipPhoneDL.xml file, too, which is located in the /opt/3com/VCX/devdnldsvr/bin directory.
CHAPTER 8: CONFIGURING THE SIP PHONE DOWNLOADER 3 Under Config, configure the following tags: ■ LocalDeviceName — This is your NIC device, such as //dev//dmfe0. Make sure the NIC device has read and write permissions for the cworks user; otherwise, change the permission on this device or run this application as the super user. ■ MaxSessions — A session is used to download a specific device. The max sessions determines how many devices can be downloaded all at once (parallel).
Configuring the SIP Phone Downloader 189 In super user mode, type the following to print a list of the various downloaders: ifconfig -a 1 Launch EMS and discover the server that the SIP Phone Downloader is installed on. The navigation tree looks similar to Figure 58. Figure 58 SIP Phone Downloader Configuration Tab in EMS 2 Click 3COM Application Downloader. 3 From the Properties tabs, click Configuration.
CHAPTER 8: CONFIGURING THE SIP PHONE DOWNLOADER 5 Click Save all. Device Mapping through EMS The SIP Phone Downloader application comes with two images: ndset_boot_19 and nbset_19, and the boot version is C.403. All images need to be stored in the $HOME/sipdl/images. To configure the device mapping: 1 Launch EMS and discover the server that the SIP Phone Downloader is installed on. The navigation tree looks similar to Figure 59.
Device Mapping through EMS ■ 191 ImageFilename — Application code and SIP Phone application. This value should be set to nbset_19. 5 Click Save all.
CHAPTER 8: CONFIGURING THE SIP PHONE DOWNLOADER
9 MAINTAINING THE V7000 IP TELEPHONY SUITE This chapter describes various V7000 IP Telephony Server maintenance tasks. Maintenance procedures are concerned with upgrading or uninstalling applications, exporting, importing, or clearing database tables, and any preventative tasks that maintain the health of a system. Overall System Maintenance Upgrading a VCX System This section provides maintenance tasks that involve the V7000 IP Telephony Server (not including the V7350 IP Messaging Application).
CHAPTER 9: MAINTAINING THE V7000 IP TELEPHONY SUITE 6 Go to the upgrade- directory created when the file was untarred. 7 Install the components by entering: ./upgrade-vcx This causes the VCX system to check which components need to be upgraded and then it procedes to install them. 8 If you have other servers to upgrade, continue to follow step 2 through step 7 for each server that needs to be upgraded; otherwise, continue with step 10.
Overall System Maintenance 195 Downgrade Assumptions This procedure makes the following assumptions: ■ The system being downgraded was, prior to the 5.2 upgrade, successfully running VCX 5.0.2c code. ■ Prior to the upgrade, database backups were taken using the steps outlined in the section Backing Up the Authentication and Directory Server on page 204.
CHAPTER 9: MAINTAINING THE V7000 IP TELEPHONY SUITE If the system is running back-end services and replication is in use, you must complete this step; otherwise, continue with step 4. a On the Master Definition server, login in as cworks. b Go to /opt/3com/VCX/auth/bin. c Enter the following command to stop replication: ./dropReplication 4 Restore the databases with the backups that were taken prior to the upgrade.
Overall System Maintenance 197 vcx-os-query This produces output resembling the following: OS Version Partition Label A 1.4.0 /dev/sda2 /A B 2.1.1 /dev/sda3 /B Status active The order of the O/S versions (A or B) may be reversed depending on the upgrade history of the system. The active version of the O/S reflects the version shipping with VCX 5.2. c Select the 1.4.0 O/S version for use at the next reboot by entering: vcx-os-switch 1.4.
CHAPTER 9: MAINTAINING THE V7000 IP TELEPHONY SUITE Verifying Software Versions This section describes how to verify the software versions of individual components and entire releases. Verifying Component Software Versions To verify what the component software versions are: 1 Log onto the VCX system as root. 2 Navigate to /opt/3com/VCX/scripts. 3 Enter this command: ./vcx-assemble --validate This lists all of the components and their software versions that comprise the current running assembly.
Overall System Maintenance 199 To clear cache from Tomcat: 1 Navigate to /opt/3com/3rdparty/tomcat./vcx-scripts/init.d. 2 Stop Tomcat. ./tomcat stop 3 Enter the following command to clear the cache: rm -rf ../../work/ 4 Restart Tomcat. ./tomcat start Stopping Tomcat To stop the tomcat application: 1 Login into the server hosting the VCX IP Telephony System. 2 Login as tomcat. (default password is tomcat). 3 Enter /opt/3com/VCX/tomcat/bin. 4 Enter ./shutdown.sh. 5 Enter exit.
CHAPTER 9: MAINTAINING THE V7000 IP TELEPHONY SUITE To save the 3Com VCX IP Telephony Server configuration in EMS: 1 From the Explorer tab, right-click 3Com VCX IP Telephony Server. 2 From the pop-up menu, select Configuration and then select Backup. The progress is shown in the Job Progress section of the EMS GUI. When the save is finished, the Working icon changes to a Finished icon. The default directory for .CFM files is: ...3Com\EMS\backups.
Overall System Maintenance 201 To modify the daylight savings and/or timezone configuration for your VCX system: 1 Login into the VCX server as root.
CHAPTER 9: MAINTAINING THE V7000 IP TELEPHONY SUITE Call Processor Maintenance Starting the Call Processor This section provides maintenance tasks that are specific to just the call processor. To start the Call Processor: 1 Log on to the machine hosting the Call Processor. 2 Navigate to the /opt/3com/VCX/callprocessor/bin directory. 3 Enter this command: ./callp start Restarting the Call Processor To restart the Call Processor: 1 Log on to the machine hosting the Call Processor.
Back-end Server Maintenance ■ green — it is running ■ red — it is down From a Command Prompt To verify the state of the Call Processor from a command prompt: 1 Log into a machine hosting the Call Processor as root. 2 Enter the following command: ps -ef | grep call Back-end Server Maintenance Starting the Accounting, Authentication, and Directory Servers ■ Running — the Call Processor Process ID is listed. ■ Not Running — nothing is listed except the root ID.
CHAPTER 9: MAINTAINING THE V7000 IP TELEPHONY SUITE authentication server — auth directory server — dir 3 Enter ./ stop Backing Up and Restoring Databases The back up and restore feature is available for the authentication and directory server databases. 3Com recommends backing up databases regularly and also before performing any upgrades. Once an upgrade has been performed you can use the restore feature to repopulate the databases.
Back-end Server Maintenance 205 A backup file named authbackup..tgz is generated and saved in the /opt/3com/VCX/auth/db/export directory. 5 Login as user cworks. 6 Change the directory to /opt/3com/VCX/dir/bin. 7 Enter the following command to start the directory server database back up. ./backupDir The script prompts you to verify if Tomcat and the directory server applications are stopped. A backup file named dirbackup..
CHAPTER 9: MAINTAINING THE V7000 IP TELEPHONY SUITE 3 Login as user cworks. If using replication, login as cworks on both the primary and secondary authentication server. 4 Verify that Tomcat, authentication server, and directory server applications are stopped. a To stop tomcat, log in as tomcat using the password tomcat. su - tomcat b Change the directory to $CATALINA_HOME/bin. c Enter ./shutdown.sh d Enter exit to log out as tomcat.
Back-end Server Maintenance 207 10 Login as user cworks. If using replication, login as cworks on both the primary and secondary directory server. 11 Change directory to /opt/3com/VCX/dir/bin. 12 Enter the following command to start the directory server database restoration. If you use replication, enter the command on both the primary and secondary directory server. ./restoreDir The script prompts you to verify if Tomcat and the directory server applications are stopped.
CHAPTER 9: MAINTAINING THE V7000 IP TELEPHONY SUITE ■ For all the tables under one schema (except the runtime tables). See Exporting Table Data for all Tables in a Schema. Exporting data saves the current configuration. Exporting Table Data for a Single Table Data for a single table can be exported to the export directory listed in the Oracle initialization folder. Runtime tables cannot be exported. To export data for a single table: 1 From a SQL Plus command line, login as the cwauth user.
Back-end Server Maintenance 209 For this procedure, change the following to match the system: ■ Change the value of p_dir to the export directory. ■ Make sure to enter the procedure name EXACTLY as shown. SET SERVEROUTPUT ON declare p_dir varchar2(255); begin p_dir:='/tmp/export'; CWDATA.
CHAPTER 9: MAINTAINING THE V7000 IP TELEPHONY SUITE To clear the configurable tables from the back-end server database: 1 Log on to the directory server as cworks. 2 Change to the /opt/3com/VCX//bin directory: cd /opt/3com/VCX//bin 3 Clear the data by entering the following command: ./besbulkload.
Back-end Server Maintenance 211 If this is the first time exporting CDRs, make sure the UTL_FILE_DIR entry in the oracle initialization file (init.ORA) is set correctly. Deleting CDRs This procedure is for deleting CDRs from the accounting server database.
CHAPTER 9: MAINTAINING THE V7000 IP TELEPHONY SUITE Rediscovering the Accounting Server After making configuration changes on the accounting server, rediscover the 3Com VCX IP Telephony Server to refresh the configuration MIB values. To rediscover to 3Com VCX IP Telephony Server: 1 In the explorer tree, right-click the 3Com VCX IP Telephony Server. 2 From the pop-up menu, click Rediscover. A dialog box appears and displays the progress of the command.
Back-end Server Maintenance 213 Enterprise Manager and change the code_complete_id from 0 (incomplete) to 3 (completed by operator) for the specific record.
CHAPTER 9: MAINTAINING THE V7000 IP TELEPHONY SUITE Enabling Server Logging The acctconfig.xml, authconfig.xml, or dirconfig.xml file has a setting to enable server logging. This is used to control the common logging function, which is shared with all Tier 2 and Tier 3 devices. This controls the logging of various status, warning, and error messages in the server.
Back-end Server Maintenance 215 4 Under the SNMP Configuration tag, verify that the SNMP Common Agent is enabled. It should look like this: ^M ^M 5 If SNMP support is disabled, continue with Enabling SNMP Support. Enabling SNMP Support To enable SNMP support: 1 Log in as root. 2 Stop the common agent. 3 Stop the back-end server you want to enable SNMP support on.
CHAPTER 9: MAINTAINING THE V7000 IP TELEPHONY SUITE Reserving and Unreserving the Back-end Server in EMS The Operator Reserve command reserves either the accounting, authentication, or directory server so that no one else can perform operations on the server using EMS. The Operator Unreserve command cancels the reservation. Reserving Using EMS To reserve the back-end server using EMS: 1 In the explorer tree, right-click the individual back-end server.
Back-end Server Maintenance 217 First, use Enterprise Management Suite to tell the 3Com VCX IP Telephony Server where to send traps. Then use Enterprise Management Suite to enable the traps. Finally, start the trap generation. Configuring Trap Destinations To configure a trap destination using EMS: 1 From the Enterprise Management Suite Explorer tab, select 3Com VCX IP Telephony Server to configure. 2 From the Properties tab, select Trap Destinations. 3 At the bottom of the right-hand pane, click Add.
CHAPTER 9: MAINTAINING THE V7000 IP TELEPHONY SUITE Figure 60 Enabling Back-end Server Traps 4 Enable and disable SNMP traps according to your customized needs. Table 38 lists SNMP traps for the authentication server. Table 38 Back-end Server SNMP Traps Trap MIB Description itbesGenericError Back-end Server generic error. itbesServiceInstallFailed Back-end Server service installation failed. itbesServiceUninstallFailed Back-end Server service uninstall failed.
Back-end Server Maintenance 219 Table 38 Back-end Server SNMP Traps (continued) Trap MIB Description itbesPrivateQueueOpenFailed Back-end Server failed to open the private queue. itbesPrivateQueueDeleteFailed Back-end Server failed to delete the private queue. itbesResponseQueueDeleteFailed Back-end Server failed to delete the response queue. itbesResponseQueueCreateFailed Back-end Server failed to create the response queue.
CHAPTER 9: MAINTAINING THE V7000 IP TELEPHONY SUITE
A CALL PROCESSOR COMMAND LINE INTERFACE COMMANDS This chapter contains a complete listing of command line interface (CLI) commands available for the call processor. Call Processor CLI Overview The call processor can be configured from the server where the call processor was installed by using the remoteCLI application. The remote CLI application is located in the /opt/3com/VCX/callprocessor/remoteCli/bin directory and uses the same editing style as the text editor vi.
APPENDIX A: CALL PROCESSOR COMMAND LINE INTERFACE COMMANDS CLI Command Descriptions The remote CLI application uses the following commands for administering the Call Processor: Table 39 Remote CLI Command Descriptions Command Description exit Quits the Remote CLI application. shutdown Shuts down the Call Processor gracefully. version Shows the software version of the Call Processor and the version of the Distributed Message Routing (DMR) 3Com proprietary protocol.
MANUALLY CONFIGURING THE AUTHENTICATION SERVER B 3Com recommends configuring the authentication server through the provisioning server. See “Configuring the Authentication Server” on page 19. This appendix describes the tables used when configuring users or other authentication functions in large quantities (in bulk). Information on how to bulkload data into the authentication server database is provided in “Common Commands” on page 315.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER Add one row for each mapping. For example: |PRIMARY_URI_ID|ALLOWED_BRIDGE_URI_ID|PHONE_LINE_NO 3|2|4| 3|4|4| Configuring bw_list The bw_list table provides call restrictions (black lists) and allowances (white lists) for existing phones. Table 41 bw_list_data.txt Fields Column Name Description Value BW_LIST_ID This refers to a unique identification number Integer for the record.
Configuring Authentication Server Database Tables Configuring code_feature_type 225 The code_feature_type table provides a list of all of the calling features available for a network. Table 42 code_feature_type_data.txt Fields Column Name Description Value CODE_FEATURE_TYPE_ID A unique identification number for the calling feature. Integer CODE_FEATURE_NAME The name for a specific calling feature.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER Configuring cos_elm The cos_elm table provides a list of all of the Class of Service elements available to configure Class of Services. The elements contain the patterns that determine what types of calls an end user is allowed to place and receive. Table 43 cos_elm_data.txt Fields Column Name Description Value COS_ELM_ID A unique identification number for the Class Integer of Service element.
Configuring Authentication Server Database Tables 227 Add one row for each Class of Service element to pattern mapping: |COS_ELM_PATTERN_MAP_ID|COS_ELM_ID|PATTERN_ID 1|1|100| 2|1|101| 3|1|102| Configuring cos_name The cos_name table provides a list of all of the Class of Service names and is used to configure trunk to trunk calling. Table 45 cos_name_data.txt Fields Column Name Description Value COS_NAME_ID A unique identification number for the Class Integer of Service.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER Configuring cos_name_elm_map The cos_name_elm_map table provides a list of all of the elements associated with each Class of Service and configures whether or not an end user is allowed to received and/or place certain types of calls. Table 46 cos_name_elm_map_data.txt Fields Column Name Description Value COS_NAME_ELM_MAP_ID A unique identification number for the Class Integer of Service to element mapping.
Configuring Authentication Server Database Tables Configuring dial_plan 229 The dial_plan table provides a list of all of the configured phone numbers (or groups of phone numbers) which makes it so an end user do not have to dial the OK button on their phone to place a call. Table 47 dial_plan_data.txt Fields Column Name Description Value DIAL_PLAN_ID A unique identification number for the Dial Plan. Integer DIAL_PLAN_NAME The name for a specific Dial Plan.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER Configuring dial_rule The dial_rule table provides a list of all of the dial rules, which are used to configure dial plans. Table 49 dial_rule_data.txt Fields Column Name Description Value DIAL_RULE_ID A unique identification number for the Dial Rule. Integer DIAL_RULE_NAME The name for a specific Dial Rule. String MIN_LENGTH The minimum number of digits in a phone number an end user must dial before a call is placed automatically.
Configuring Authentication Server Database Tables Configuring elin 231 The elin table provides a list of all Emergency Line ID Numbers. Table 50 elin_data.txt Fields Column Name Description ELIN_ID A unique identification number for the ELIN. Integer Value ELIN Emergency Location Identification Number ASSOC_RELEASE_TIMER the amount of time you want to leave the Integer ELIN associated to the emergency caller. This number is entered as a string in hours and the range is 1 through 24.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER Configuring erl The erl table provides a list of all Emergency Response Locations. Table 51 erl_data.txt Fields Column Name Description ERL_ID A unique identification number for the ERL. Integer Value ERL Geographic location or descriptive title for ERL. EMER_NOTIF_CALLBACK _PHONE The phone number of the contact person String responsible for emergency situations within an organization (for example, a security guard).
Configuring Authentication Server Database Tables Configuring erl_elin_map 233 The erl_elin_map table provides a mapping of each Emergency Response Location with all Emergency Line ID Numbers. Table 53 erl_elin_map_direct_data.txt Fields Column Name Description Value ERL_ELIN_MAP_ID A unique identification number for each mapping of an ELIN to a ERL. Integer ELIN_ID A unique identification number for the ELIN. Integer ERL_ID A unique identification number for the ERL.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER Configuring es_defaults The es_defaults table provides default values for the emergency services. Emergency defaults are used when there is no information in the emergency response database for an emergency caller (phone IP address). Typically, phone IP addresses are stored within ranges for a defined ERL. Table 55 es_defaults_data.
Configuring Authentication Server Database Tables Configuring feature_uri_info 235 The feature_uri table provides actual data for the feature for a particular URI address (for example, the actual address and timeout value). Table 57 feature_uri_info_data.txt Fields Column Name Description Value FEATURE_URI_INFO_ID A unique identification number for the calling feature URI. Integer URI_ACCESS_CODE_ID This refers to the actual address code for a particular feature.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER Configuring patterns The patterns table is a global repository for all patterns. Table 58 patterns_data.txt Fields Column Name Description Value PATTERN_ID A unique identification number for the pattern. Integer PATTERN This is the pattern value. It can contain a wild card (*), String but only one or zero. If a * is present, it should be the last character in the pattern value. Add one row for each pattern.
Configuring Authentication Server Database Tables Table 59 persons_data.txt Fields (continued) Column Name Description Value CODE_CTRY Indicates the country code.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER Table 59 persons_data.txt Fields (continued) Column Name Description Value CODE_CTRY (cont.
Configuring Authentication Server Database Tables Table 59 persons_data.txt Fields (continued) Column Name Description Value CODE_CTRY (cont.) 64 – Egypt Integer 65 – El Salvador 66 – Equatorial Guinea 67 – Eritrea 68 – Estonia 69 – Ethiopia 70 – F.Y.R.O.M.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER Table 59 persons_data.txt Fields (continued) Column Name Description Value CODE_CTRY (cont.) 94 – Guyana Integer 95 – Haiti 96 – Honduras 97 – Hong Kong S.A.R.
Configuring Authentication Server Database Tables Table 59 persons_data.txt Fields (continued) Column Name Description Value CODE_CTRY (cont.) 126 – Macau S.A.R.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER Table 59 persons_data.txt Fields (continued) Column Name Description Value CODE_CTRY (cont.
Configuring Authentication Server Database Tables Table 59 persons_data.txt Fields (continued) Column Name Description Value CODE_CTRY (cont.) 190 – Somalia Integer 191 – South Africa 192 – Spain 193 – Sri Lanka 194 – St. Helena 195 – St. Kitts and Nevis 196 – St. Pierre and Miquelon 197 – St.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER Table 59 persons_data.txt Fields (continued) Column Name Description Value CODE_CTRY (cont.
Configuring Authentication Server Database Tables Configuring person_uri_map The person_uri_maps table maps the URI with to the end user. Table 60 person_uri_map_data.txt Fields Column Name Description Value URI_ID A unique identification number of the URI. Integer PERSON_ID A unique identification number for the person (end user). Integer Add one row for each URI to end user mapping.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER Configuring server_configuration The server_configuration table contains the configuration for the call park feature. Table 62 server_configuration_data.txt Fields Column Name Description Value SERVER_CONFIGURATION_ID A unique identification number for the call park configuration. Integer CALL_PARK_START The number to begin call sessions for calls being parked. Integer Note: 3Com recommends the start number to be 800.
Configuring Authentication Server Database Tables Configuring tos_feature_map 247 The tos_feature_map table contains the configuration for assigning specific ringtones to specific URIs. Table 64 tos_feature_map_data.txt Fields Column Name Description TOS_ID A unique identification number for the Type Integer of Service. Value CODE_FEATURE_TYPE _ID A unique identification number for the phone feature.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER Configuring tos_name The tos_name table contains the configuration for assigning specific ringtones to specific URIs. Table 65 tos_name_data.txt Fields Column Name Description TOS_ID A unique identification number for the Type Integer of Service. Value TOS_NAME The name assigned to the Type of Service. String Modify the data row for each Type of Service.
Configuring Authentication Server Database Tables 249 Add one row for each translations source destination. For example: TRANS_SRC_DEST_ID|TRANS_GROUP_ID|SRC_PATTERN_ID| DEST_PATTERN_ID|RESULT_PATTERN_ID 1|1|53|3|53 2|1|4|5|6| Configuring trusted_clients The trusted_clients_profiles table holds all the trusted clients for the server. Any application using the BES client library that wishes to connect to the BES server must be listed in this table. Table 67 trusted_clients_data.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER Configuring uri_access_code The uri_access_code table defines access codes for particular features of specific URI addresses (for example, end users can set the access code for the call forwarding number for their home). Table 68 feature_uri_info_data.txt Fields Column Name Description URI_ACCESS_CODE_ID A unique identification number for the Integer access code.
Configuring Authentication Server Database Tables Configuring uri_bw_list_map The uri_bw_list_map table links a particular URI address to its black or white list (call restriction). Table 69 uri_bw_list_map_data.txt Fields Column Name Description Value URI_ID Not supported by 3Com. N/A BW_LIST_ID This refers back to the Configuring bw_list table. Integer LIST_ADDED_BY This field shows who added this black/white Integer list. Either the Administrator or the End User can add a phone restriction.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER Add one row for each calling features to URI translation mapping. For example: |URI_ID|CODE_FEATURE_TYPE_ID 4|8| 1|1| 1|2| Configuring uri_sip_phone_profile The uri_sip_phone_profile table contains the URI SIP phone configuration. Table 71 uri_sip_phone_profile_data.txt Fields Column Name Description Value URI_ID A unique identification number for Integer the URI.
Configuring Authentication Server Database Tables 253 Table 71 uri_sip_phone_profile_data.txt Fields (continued) Column Name Description Value MUSIC_ON_HOLD_SERVER Address of the Music on Hold server. String CODE_TIME_ZONE_ID Time zone of where the server is located. Integer VM_PILOT_ADDRESS Address of the voice mail server, where your phone connects to so you can hear your voice mail messages. For example, voicemail.3com.com.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER RINGTONE_OTHER_CALL_ID|MUSIC_ON_HOLD_SERVER| CODE_TIME_ZONE_ID|VM_PILOT_ADDRESS 1|3com.com|3600|1|172.16.243.100|proxy.3com.com|5060| sip phone 1|3|3|3|1|music.3com.com|1|vm.3com.com| 4|3com.com|||||5060|John Test|10|2|1|1|172.16.243.100|1|voicemail.3com.com| 102|domain.com|10|1|172.16.243.
Configuring Authentication Server Database Tables Add one row for each weekday.
APPENDIX B: MANUALLY CONFIGURING THE AUTHENTICATION SERVER
C MANUALLY CONFIGURING THE DIRECTORY SERVER 3Com recommends configuring the directory server through the provisioning server. See “Configuring the Directory Server” on page 89. This appendix describes the tables used when configuring call routes or other directory server functions in large quantities (in bulk). Information on how to bulkload data into the authentication server database is provided in “Common Commands” on page 315.
APPENDIX C: MANUALLY CONFIGURING THE DIRECTORY SERVER c If the end point needs an associated out dial pattern, then a record to the ep_outdial_map table. 3 Add a route to the route table. 4 Associate the end points by adding records to the route_ep_map table. a If the route to end point combination has an out dial pattern, then add the record to the route_ep_outdial_map table. 5 Associate the Destination URI to the route.
Directory Server Database Table Descriptions Directory Server Database Table Descriptions Configuring datetime_bands _data.txt 259 This section provides information on each directory server database table and their associated fields. The datetime_bands table is used as an input parameter for URI translation and destination URI routing. The start and end times are based on calendar times, which include the year, month, day, hour, minute, and second. Table 74 datetime_bands.
APPENDIX C: MANUALLY CONFIGURING THE DIRECTORY SERVER Add one row for each day time band. For example: |DAY_TIME_BAND_ID|DAY_TIME_BAND_NAME|START_TIME|END_TIME 1|0-12 hours|01-JAN-2001 00:00:00|01-JAN-2001 11:59:59| 2|8-5pm|01-JAN-2001 08:00:00|01-JAN-2001 17:00:00| Configuring week_day_bands _data.txt The week_day_bands table is used as an input parameter for URI translation and destination URI routing. Weekdays start on Sunday.
Directory Server Database Table Descriptions Configuring desturi_route_ep _blacklist_map _data.txt 261 The desturi_route_ep_blacklist_map table shows which end points are blacklisted so that those end points are excluded from routes. Table 77 desturi_route_ep_blacklist_map_data.txt Fields Column Name Description Value ID Number of consecutive black listed end points starting with 1.
APPENDIX C: MANUALLY CONFIGURING THE DIRECTORY SERVER Table 78 desturi_route_map_data.txt Fields (continued) Column Name Description Value WEEK_DAY_BAND_ID This is a unique identification number for the week day band, which is located in the week_day_bands_data table. Integer DAY_TIME_BAND_ID This is a unique identification number for the day time band, which is located in the day_bands_data table.
Directory Server Database Table Descriptions Configuring desturi_translation _data.txt 263 The desturi_translation table provides destination URI translation based on source input parameters and translation strings. Understanding Translation Algorithms This section is provided to help you understand how pattern matching and translation strings are used. The outbound destination URI is translated using the match pattern ID and translation string.
APPENDIX C: MANUALLY CONFIGURING THE DIRECTORY SERVER For example, if the source based inputs are Direct Requestor equals "Gatekeeper 2" and Holiday equals "New Years" and there are no combination records for "Gatekeeper 2" and "New Years" but there is a record for "New Years" only then that record is returned. Table 80 desturi_translation_data.txt Fields Column Name Description Value DESTURI_TRANS_ID This is a unique identification number for the unique destination URI translation.
Directory Server Database Table Descriptions 265 Table 80 desturi_translation_data.txt Fields (continued) Column Name Description Value DATETIME_BAND_ID This is a unique identification number for the date time band, which is located in the datetime_bands_data table. Integer PATTERN_ID This is the destination URI matching pattern. String TRANSLATION_STRING Determines how the destination URI will be translated. String Add one row for each destination URI translation.
APPENDIX C: MANUALLY CONFIGURING THE DIRECTORY SERVER Table 82 ep_data.txt Fields Column Name Description Value EP_ID This is a unique end point identification number for Integer each end point. ACTIVE Indicates whether or not the end point status is active. Integer 0 - Not Active 1 - Active CODE_EP_TYPE Defines the type of end point. Integer 2 - Gateway 6 - Terminal 9 - Call Processor EP_NAME A unique name of the end point. String EP_DESC A description of the end point.
Directory Server Database Table Descriptions 267 Table 82 ep_data.txt Fields (continued) Column Name Description Value PC_MEMBER Not Used. N/A CODE_BLWL_USAGE Determines the type of blacklist or whitelist to use.
APPENDIX C: MANUALLY CONFIGURING THE DIRECTORY SERVER 3|1|2|GWChicagoWest|Chicago West Suburbs||0.0.0.0||1413|2|2|||||||1| Configuring ep_outdial_map _data.txt The ep_outdial_map table contains the out dial pattern IDs for an end point. The out dial patterns are optional for an end point. When a route containing the end point is added to the run time tables then all out dial entries for this endpoint are included in the run time table (RT_RTEP_OUTDIAL_MAP).
Directory Server Database Table Descriptions Configuring global_policy _data.txt 269 The global_policy table determines which policies or configurables are available for the server and their status. The policies are listed in the CODE_POLICY table. Table 86 global_policy_data.txt Fields Column Name Description Value GLOBAL_POLICY_ID A unique identification number for the global policy. Integer ACTIVE Indicates whether or not the global policy is active.
APPENDIX C: MANUALLY CONFIGURING THE DIRECTORY SERVER Configuring holidays_data.txt The holidays table creates a holiday date based on the month and day. This is used for URI translation and destination URI routing. Table 88 holidays_data.txt Fields Column Name Description Value HOLIDAY_ID A unique identification number for the holiday. Integer HOLIDAY_NAME A name for the holiday. String HOLIDAY_MONTH The month the holiday takes place.
Directory Server Database Table Descriptions 271 Table 89 outdial_patterns_data.txt Fields (continued) Column Name Description Value CODE_E164_TYPE If the destination URI is a E.164 number then this field lists the type of the resultant E.164 number. Integer 1 - Unknown 2 - International 3 - National 4 -Network Specific 5 -Subscriber 6 -Abbreviated 7 -Reserved CODE_NUMPLAN_IND Indicates the type of numbering plan used. These are defined in the CODE_NUMPLAN_IND_DATA.txt table.
APPENDIX C: MANUALLY CONFIGURING THE DIRECTORY SERVER Configuring patterns_data.txt The patterns table is a supporting table that contains regular expression patterns used in various tables in the Directory schema. Table 90 patterns_data.txt Fields Column Name Description Value PATTERN_ID A unique identification number for the pattern. Integer PATTERN_NAME The name assigned to the pattern. String PATTERN String The actual pattern assigned. Add one row for each pattern.
Directory Server Database Table Descriptions Configuring requestors_data.txt 273 The editing_requestors table contains requestors that are used as source based input parameter for URI Translation and Destination URI Routing. Requestors are usually Tier 1 or Tier 2 components. Table 92 editing_requestors_data.txt Fields Column Name Description REQ_ID A unique identification number for the requestor. Integer REQ_NAME The name assigned to the requestor.
APPENDIX C: MANUALLY CONFIGURING THE DIRECTORY SERVER Configuring route_data.txt The route table contains routes for the server. A route is a collection of end points that are sorted depending on the CODE_ROUTE_SORT_POLICY. Table 93 route_data.txt Fields Column Name Description Value ROUTE_ID A unique identification number for the route. Integer ROUTE_NAME The name assigned to the route.
Directory Server Database Table Descriptions Configuring route_ep_map _data.txt 275 The route_ep_map table contains all the end points for the route. A bundle end point will not be expanded in this table. Table 94 route_ep_map_data.txt Fields Column Name Description Value ROUTE_ID This refers to a unique route identification number, which was assigned in the route_data table. Integer EP_ID This refers to a unique end point identification Integer number, which was assigned in the ep_data table.
APPENDIX C: MANUALLY CONFIGURING THE DIRECTORY SERVER Configuring route_ep_outdial _map_data.txt The route_ep_outdial_map table contains out dial patterns for the combination of the route and end point. The out dial patterns can be set at the route-endpoint level thus allowing a common set of out dial patterns to be applied to each end point in the route.
Directory Server Database Table Descriptions 277 Add one row for each trusted client. For example: |CLIENT_ID|CLIENT_NAME|IP_ADDRESS|IP_PORT|DNS_NAME|RADIUS_SE CRET 3|GK4|152.67.61.52|1025||| 2|Chicago PC|0.0.0.
APPENDIX C: MANUALLY CONFIGURING THE DIRECTORY SERVER
D MANUALLY CONFIGURING THE ACCOUNTING SERVER The accounting server is automatically configured through scripts during the installation. This appendix is provided as reference in case you want to manually reconfigure the accounting server or to troubleshoot configurations that may be broken. Configuring Accounting Server Database Tables The accounting server uses database tables to govern the processing of CDRs. Configure these tables according to your customized needs.
APPENDIX D: MANUALLY CONFIGURING THE ACCOUNTING SERVER *If no billing support servers are in the system, it is not necessary to edit the information in these tables. Configuring acct_server_config Use the acct_server_config table to assign the SERVER_ID_ACCT for this accounting server. If you also configured the Configuring acct_server_list and Configuring bss_acct_server_map tables, the data contained in those tables must be consistent with the data in the Configuring acct_server_config table.
Configuring Accounting Server Database Tables 281 To avoid connection errors in a system with multiple accounting and billing support servers, use the for the SERVER_CONNECTION column for all accounting and billing support server databases. Add the service name () to each TNS file on every node (accounting and billing support servers) in your network. Add this name by either editing the TNS file, setting up through Net8, or by adding a node through DBA Studio.
APPENDIX D: MANUALLY CONFIGURING THE ACCOUNTING SERVER Configuring bss_server_list The bss_server_list table lists all of the billing support servers in the system. This unique identifier is used to identify the billing support server in other database tables. Table 101 bss_server_list_data.txt Fields Column Name Description Value SERVER_ID_BSS A unique identifier for this billing support server.
Configuring Accounting Server Database Tables 283 Table 102 job_delete_cdrs_data.txt Fields (continued) Column Name Description Value JOB_INTERVAL A configurable interval at which the sysdate+Integer job is run. The minimum value is 5 minutes. A value of sysdate+1 would mean that the job would run once in 24 hours. A value of sysdate+1/24 would mean that the job would run every hour. ACTIVE_STATUS 0 = Not active, the job this record represents will not be submitted.
APPENDIX D: MANUALLY CONFIGURING THE ACCOUNTING SERVER Assign the JOB_TO_SUBMIT as CWDELETE.delcdr. To resubmit a job that is already in queue, you must delete the job, make changes to the record, change the ACTIVE_STATUS to 1, and then resubmit it. Configuring job_export_cdrs The Oracle built-in DBMS_JOB package will be used for extracting and exporting data to flat files. The JOB_NUMBER, JOB_TO_SUBMIT, JOB_NEXT_RUN, JOB_INTERVAL, and JOB_PARSING parameters are DBMS_JOB package parameters.
Configuring Accounting Server Database Tables 285 Table 103 job_export_cdrs_data.txt Fields (continued) Column Name Description Value COL_DELIMETER Column delimiter, such as a comma(,) or pipe (|). Character ACTIVE_STATUS 0 = Not active, the job this record represents will not be executed. 0,1,2 1= Active, the job this record represents will be executed. 2 = Already submitted. ROW_DELIMETER Row delimiter N/A FILE_TYPE Type of file N/A SET_COMPLETE_INTERVAL This is only used for SuperCDRs.
APPENDIX D: MANUALLY CONFIGURING THE ACCOUNTING SERVER Configuring job_export_fields_ map The job_export_fields_map table specifies which CDR fields are exportable and in what sequence the fields will be exported. For each CODE_SOURCE_ID, specify the exportable CDR fields and in what sequence to export those fields. For CDRs with different CODE_SOURCE_ID values (source identifiers), you may want to export only specific fields. Table 104 job_export_fields_map_data.
Configuring Accounting Server Database Tables Configuring job_ uploadruntimecdr 287 Is used for to transfer CDRs from RT_CDR1 and RT_CDR2 to RT_CDR on low performance servers for a system with both an accounting and billing support server. Table 105 job_uploadruntimecdr_list_data.txt Fields Column Name Description Value JOB_ID A unique identifier for a job. Integer JOB_NUMBER This value is assigned by Oracle, not by user assignment. N/A JOB_TO_SUBMIT The job name, which is CWHISTORY.
APPENDIX D: MANUALLY CONFIGURING THE ACCOUNTING SERVER Configuring upload_history The upload_history table lists each billing support server and the upload CDR range. The billing support server uses the upload_history table during an upload procedure. The accounting server uses the upload_history table during CDR deletions. Table 106 Upload_history Fields Field Description Value PREV_ENDING_CDR The ID of the final CDR in the last upload.
E MANUALLY CONFIGURING THE BILLING SUPPORT SERVER The billing support server is automatically configured through scripts during the installation. This appendix is provided as reference in case you want to manually reconfigure the billing support server or to troubleshoot configurations that may be broken. Manually Creating Database Links Database links must be configured from the billing support server to each accounting server or else the data direction will be incorrect.
APPENDIX E: MANUALLY CONFIGURING THE BILLING SUPPORT SERVER To create the database link: 1 Using a text editor, open the dblink.sql script (located in the /opt/3com/VCX/bss/db/cwbss/mod directory). The file is similar to the following: create database link cwbes.self connect to cwacct identified by besgroup using '’cwbes’’'; commit; exit; 2 Change cwbes.self to . where the accounting database is installed.
Manually Configuring Upload from Multiple Accounting Servers ■ 291 BSS_SERVER_CONFIG — See “Configuring bss_server_config” on page 303 for fields descriptions. 2 Verify there are database links from the billing support server to each accounting server. When creating database links, from the ACCT_SERVER_LIST table, the SERVER_CONNECTION field must be used as the remote service name. 3 Configure the JOB_COLLECT_CDR table to schedule the upload job.
APPENDIX E: MANUALLY CONFIGURING THE BILLING SUPPORT SERVER cwu.job_upload; end; Manually Configuring Oracle Jobs on an Accounting Server In this configuration the billing support server extracts data from the accounting server's RT_CDR1 and RT_CDR2 tables directly and inserts them into its RT_CDR table and then truncates the tables on the accounting server. There is additional configuration performed on the accounting server database side.
Manually Uploading CDRs 293 a From a SQL Plus command line, connect to the billing support server as cwbss user. b Execute the following commands: set serveroutput on begin CWU.UPLOADRUNTIMECDR; end; 5 Schedule the CDR merge job. Refer to the “Manually Scheduling the CDR Merge” on page 296. 6 Schedule the Super CDR export job. Refer to the “Manually Scheduling the Super CDRs Export” on page 298. 7 Schedule the Super CDR delete job. Refer to the “Manually Scheduling the Super CDR Delete” on page 300.
APPENDIX E: MANUALLY CONFIGURING THE BILLING SUPPORT SERVER schedules of the Oracle jobs and submit the Oracle jobs following the instructions in the dedicated sections of this guide. Manually Running the CDR Upload Use the CWU.UPLOAD procedure to manually upload CDRs from the accounting server(s) to the billing support server. To manually upload CDRs: 1 From a SQL Plus command line login as the cwbss user. 2 Enter the following script: set serveroutput on begin cwu.
Manually Merging CDRs into Super CDRs ■ 295 Verify that the job_interval is set correctly. 3 From a SQL Plus command line, login as the cwbss user. 4 Enter the following script: set serveroutput on begin CWU.JOB_UPLOAD; end; The CDR upload runs as scheduled. Once the CDR upload runs, the data from the accounting server database’s RT_CDR table is loaded into the billing support server’s RT_CDR table. To kill a scheduled job, refer to Manually Dropping a Scheduled Job.
APPENDIX E: MANUALLY CONFIGURING THE BILLING SUPPORT SERVER To manually merge CDRs into super CDRs: 1 From a SQL Plus command line, login as the cwbss user. 2 Enter the following script: set serveroutput on begin cwm.mergecdr; commit; end; The completed calls from the billing support server’s RT_CDR table are merged into the rt_super_cdr_status table. Manually Scheduling the CDR Merge Use the CWM.MERGECDR procedure to merge CDRs into super CDRs as scheduled in the job_merge_cdr table.
Manually Exporting Super CDRs 297 CWM.JOB_MERGE; end; The CDR merge runs as scheduled. Once the CDR merge runs, the completed calls from the billing support server’s RT_CDR table are merged into the RT_SUPER_CDR_STATUS table. To drop a scheduled job, refer to Manually Dropping a Scheduled Job. Manually Exporting Super CDRs The billing support server can export super CDRs into a text file (Super CDRs are stored in the rt_super_cdr_status table).
APPENDIX E: MANUALLY CONFIGURING THE BILLING SUPPORT SERVER The USER_CALL_HISTORY table should be populated from information in the call records for each URI_ID. The call history for a user can be viewed in the web provisioning server. Any call where the start time, end time, and duration equals zero (for example, when a call is forwarded or not answered), the date is translated to 1970-01-01 in the Start Time and End Time columns of the Call History.
Manually Deleting CDRs 299 ■ Only the record with ACTIVE_STATUS=1 is submitted. Verify that only one entry is set to ACTIVE_STATUS=1. ■ Verify that the job_to_submit is CWE.OUTPUT. ■ Verify that the job_interval, file_name, file_path, and col_delimiter entries are set correctly. 3 From a SQL Plus command line, login as the cwbss user. 4 Enter the following script: set serveroutput on begin CWE.JOB_EXPORT; end; The super CDRs are exported as scheduled.
APPENDIX E: MANUALLY CONFIGURING THE BILLING SUPPORT SERVER the supercdr_hold table to 0). Only disable holding parameters for testing purposes. Manually Running the Super CDR Delete Use the cwdelete.delsupercdr procedure to manually delete stored super CDRs. To manually delete super CDRs: 1 From a SQL Plus command line, login as the cwbss user. 2 Enter the following script: set serveroutput on begin cwdelete.
Manually Dropping a Scheduled Job Manually Dropping a Scheduled Job Manually Acquiring 301 To kill or drop a job, acquire the job number and then drop the job from using the SQL Plus command line. To acquire a submitted job number: a Job Number 1 From a SQL Plus command line, login as the cwbss user. 2 Enter one of the following scripts: ■ SELECT JOB FROM USER_JOBS; ■ SELECT JOB_NUMBER, JOB_TO_SUBMIT FROM JOB_DELETE_CDRS; The script returns the job number.
APPENDIX E: MANUALLY CONFIGURING THE BILLING SUPPORT SERVER Manually Resuming To resume a job (after fixing the problem of job broken): a Job 1 From a SQL Plus command line, login as the cwbss user. 2 Execute the SQL script: begin DBMS_JOB.RUN(job_number); end; The broken job is resumed. Viewing the Log Files The billing support server’s log files are located in the /opt/3com/VCX/bss/log directory.
Manually Configuring the Database Tables through Bulk Loading Manually Configuring the Database Tables through Bulk Loading 303 This section describes the database tables and fields: ■ Configuring bss_server_config ■ Configuring bss_server_list ■ Configuring acct_server_list ■ Configuring bss_acct_server_map ■ Configuring job_collect_cdr ■ Configuring job_delete_cdr ■ Configuring job_export_fields _map ■ Configuring job_export_supercdr ■ Configuring job_merge_cdr ■ Configuring supercdr
APPENDIX E: MANUALLY CONFIGURING THE BILLING SUPPORT SERVER To edit the table: 1 Using a text editor, open one of the following files: ■ To load data into an empty table, open the /opt/3com/VCX/bss/db/cwbss/bulkload/bss_server_config_data.txt file. ■ To append data, open the /opt/3com/VCX/bss/db/cwbss/bulkload/custom/bss_server_config_dat a.txt file. 2 Add one row for each billing support server.
Manually Configuring the Database Tables through Bulk Loading Configuring acct_server_list 305 The acct_server_list table creates a unique identifier for each accounting server in the system. The billing support server uses this identifier to identify the accounting server in related tables. Table 109 acct_server_list Fields Column Name Description Value SERVER_ID_ACCT A unique identifier for this accounting server.
APPENDIX E: MANUALLY CONFIGURING THE BILLING SUPPORT SERVER Table 110 bss_acct_server_map Fields Column Name Description Value SERVER_ID_ACCT A unique identifier for this accounting server. SERVER_ID_ACCT in this table must match a SERVER_ID_ACCT in the acct_server_list table. Integer FLG_COLLECT_REQ Not used. N/A To edit the table: 1 Using a text editor, open one of the following files: ■ To load data into an empty table, open the /opt/3com/VCX/bss/db/cwbss/bulkload/bss_acct_server_map_data.
Manually Configuring the Database Tables through Bulk Loading 307 Table 111 job_collect_cdr Fields Column Name Description JOB_INTERVAL A configurable interval at which the job is run. sysdate+Integer The minimum value is 5 minutes. A value of sysdate+1 would mean that the job would run once in 24 hours. A value of sysdate+1/24 would mean that the job would run every hour. CREATE_TIME The date this entry was created. ACTIVE_STATUS 0 = Not active, the job this record represents will not be submitted.
APPENDIX E: MANUALLY CONFIGURING THE BILLING SUPPORT SERVER Configuring job_delete_cdr The job_delete_cdr table schedules the job that deletes/removes data from the database. The supercdr_hold table (refer to Configuring supercdr_hold) overrides any data deletion. If the supercdr_hold table is configured to hold calls for a certain period of time, the CDRs are held until those conditions are met.
Manually Configuring the Database Tables through Bulk Loading 309 To edit the table: 1 Using a text editor, open one of the following files: 1 To load data into an empty table, open the /opt/3com/VCX/bss/db/cwbss/bulkload/job_delete_cdr_data.txt file. ■ To append data, open the /opt/3com/VCX/bss/db/cwbss/bulkload/custom/job_delete_cdr_data.tx t file. 2 Add one row for each scheduled job.
APPENDIX E: MANUALLY CONFIGURING THE BILLING SUPPORT SERVER Configuring job_export_fields _map The job_export_fields_map table establishes which CDR fields are exportable for each code source ID type. To export a specific CDR field for a specific code source ID, include an entry in this table. Table 113 job_export_fields_map Fields Column Name Description CODE_SOURCE_ID Source identifier code. Value Integer This field maps to the code_cdr_source_id table in the CWCOM database.
Manually Configuring the Database Tables through Bulk Loading Configuring job_export_supercdr 311 The job_export_supercdr table schedules the job that exports super CDRs. Table 114 job_export_supercdr Fields Column Name Description Value JOB_ID The unique identifier for the job. Integer JOB_NUMBER This value is assigned by Oracle, not by user N/A assignment. JOB_TO_SUBMIT The job name, usually a stored procedure name, such as CWE.OUTPUT.
APPENDIX E: MANUALLY CONFIGURING THE BILLING SUPPORT SERVER ■ To append data, open the /opt/3com/VCX/bss/db/cwbss/bulkload/custom/job_export_supercdr_d ata.txt file. 2 Add one row for each scheduled job. For example: |JOB_ID|JOB_NUMBER|JOB_TO_SUBMIT|JOB_NEXT_RUN|JOB_INTERVAL|F ILE_NAME|FILE_PATH|COL_DELIMITER|ROW_DELIMITER|ACTIVE_STATUS |SET_COMPLETE_INTERVAL|SELECT_WHERE_CLAUSE|DESCRIPTION 1||CWE.
Manually Configuring the Database Tables through Bulk Loading 313 Table 115 job_merge_cdr Fields (continued) Column Name Description Value ACTIVE_STATUS 0 = Not active, the job this record represents will not be submitted. 0,1 1= Active, the job this record represents will be submitted. SELECT_WHERE_CLAUSE A SQL clause that defines special conditions for merging cdrs. This field is not used at this time. String DESCRIPTION A description of this job.
APPENDIX E: MANUALLY CONFIGURING THE BILLING SUPPORT SERVER Configuring supercdr_hold The supercdr_hold table configures the rules for holding and purging super CDRs. The rules are set up on a per account type basis. Table 116 lists the supercdr_hold fields. Table 116 supercdr_hold Fields Column Name Description Value HOLDING_PERIOD The amount of time to hold the CDR before purging it. Integer NUM_LIMIT The maximum number of records to hold per user.
F COMMON COMMANDS This appendix contains information that is common to more than one component of the VCX V7000 IP Telephony Solution such as: Using the Database Bulk Load ■ Using the Database Bulk Load ■ Back-end Server Configuration Tab Descriptions This section provides information on how to bulkload data into the database tables. This section is common to the authentication and directory back-end servers (BES). Each back-end server has its own identifier such as cwauth or cwdir.
APPENDIX F: COMMON COMMANDS Editing the Text Files ■ Appending Data to the Database ■ Clearing the Database Use a text editor to edit the individual text files. The first line of the file contains the column names, each preceded by a | (pipe). Each line following the first line is a row of data, with each field followed by a |. Enter a | for every field, even if there is no data for that field.
Using the Database Bulk Load 317 ./besbulkload.pl -s -n -p ■ To load data for a single table, use the -tab option. Enter the following command: ./besbulkload.pl -s -n -p -tab To load files from a directory other than /opt/3com/VCX//db//bulkload, add the -dpath option to the command.
APPENDIX F: COMMON COMMANDS Several messages appear that list the name of each table as data is appended into each table. When the appending is complete, a command prompt appears. Clearing the Database Use this procedure to delete the data from all the tables in the database. Once data is deleted it must be reloaded from the text files. See Loading Data into the Database.
Using the Database Bulk Load 319 Table 118 besbulkload.pl Script Options (continued) Option Description -custom Allows APPEND loading of the files listed in the besbulkfiles_custom_schema_name.txt file. The files must be located in the /opt/3com/VCX//db//bulkload/cust om directory. -dpath The directory path containing the import data files. The defaults to /opt/3com/VCX//db//bulkload directory. -h Accesses the Help menu.
APPENDIX F: COMMON COMMANDS Back-end Server Configuration Tab Descriptions Tab Location Enterprise Management Suite (EMS) contains several common configuration tabs. Most of these configurables must be set to their initial, default configuration. These tabs are available for the accounting server, authentication server, and directory server. To access these tabs: 1 From the EMS GUI, navigate to the 3Com VCX IP Telephony Server within the Equipment folder.
Back-end Server Configuration Tab Descriptions BES Common Configuration 321 Use the BES Common Configuration tab to enable packet tracing for the accounting, authentication, or directory server. Table 120 BES Common Configuration Tab Attribute Description Settings ClientActivityInterval Keep alive interval in milliseconds.
APPENDIX F: COMMON COMMANDS Database Configuration Use the Database Configuration tab to configure the basic database configuration for the accounting, authentication, or directory server. Table 122 Database Configuration Tab Attribute Description caETblIndex Identifies the instance of a managed Read-only entity. The entry will be reserved for the same entity type for the time the agent has started, and attempts will be made to reserve consistency across reboots.
Back-end Server Configuration Tab Descriptions Identification Use the Identification tab to view basic statistics for the accounting, authentication, or directory server. Table 124 Identification Tab State 323 Attribute Description Settings Alias A management defined alias for the entity saved across reboots. String Class The internal schema className for this object. Read-only FQN The fully qualified name of this object. This is Read-only the complete path from the root of all objects.
Index Numerics 3Q refer to 3Queue 3Queue protocol configuration 320 A ACCESS_CODE 225, 247, 250 accessing directory server configurables 89 Accounting Server Activity, Monitoring 211 Rediscovering 212 Unique Identifier 305 acct_server_config 280 acct_server_list 280 active 261, 264, 266, 269, 275 ACTIVE_STATUS 307, 308, 311, 313 Activity, Monitoring Accounting Server 211 adding black lists 114 calendar bands 105 calling features 32 Class of Service 60 class of service 60 day time bands 102 dial plans 79
C bss_acct_server_map 281 bss_server_config, Editing 303 bulk load using the database 315 bulk loading appending data to the database 317 clearing the database 318 editing text files 316 loading data into database 316 provisioning call routes 257 Bulkloading Logs 302 bundles associating routes 122 Busy Lamp Flash 36 buttons, telephone testing 175 BW_LIST_ID 251 C cache clearing for Tomcat 198 Calendar 106 calendar bands adding 105 editing 106 managing 105 calendar bands deleting 107 calendar bands, deleti
adding 60 Trunk to Trunk 61 class of service adding 60 adding elements 62 configuring 60 editing 62 elements 64 managing 60 clearing database 318 client_id 249, 276 client_name 249, 276 cloning end users 25 CODE_ACCT_TYPE 314 code_blwl_usage 267 code_call_model 266 code_ctry 237 code_e164_type 271 code_ep_type 266, 275 CODE_FEATURE_NAME 225 CODE_FEATURE_STATUS_ID 250 CODE_FEATURE_TYPE_ID 225, 247, 250, 251 CODE_NUMPLAN_IND 271 CODE_RING_TONE_ID 245 code_route_contact 274 code_route_sort_policy 274 code
E importing saved table 209 loading into the database 316 Database Creation Log 302 Tables, Configuring 303 database appending data 317 clearing the 318 configuration 322 loading data into the 316 tables, configuring 279 database configuration 322 date_created 236 datetime_band_id 259, 262, 265 datetime_band_name 259 day time bands adding 102 deleting 104 editing 103 managing 102 day_time_band_id 259, 262, 264 day_time_band_name 259 day_time_bands_data.
out dial patterns 93 patterns 91 priorities of bundles assigned to a route 123 priorities of end points assigned to a route 123 priorities of routes 123 requestors 96 ring tones 47 routes 121 text files 316 week day bands 101 elements class of service 64 configuring 64 editing 65 EMS configuring trap destinations 217 reserving authentication server 216 unreserving authentication server 216 updating the server state 216 enabling back-end server traps 216, 217 message tracing 213 server logging 214 SNMP
J J Job Number, Checking 301 job_delete_cdrs 282 job_export_cdrs 284 job_export_fields_map 286 JOB_ID 306, 308, 311, 312 JOB_INTERVAL 307, 308, 311, 312 JOB_NEXT_RUN 306, 308, 311, 312 JOB_NUMBER 306, 308, 311, 312 JOB_TO_SUBMIT 306, 308, 311, 312 Jobs Dropping 301 Killing 301 K Killing, Jobs 301 L last_name 236 LEDs (status lights) telephone diagnostics 175 lights testing on the telephone 175 LIST_ADDED_BY 251 loading data database 316 LocalDeviceNameAdmin 189 LocalIPAddressAdmin 189 LocalIPPortAdmin 18
P pattern 236, 272 editing 91 PATTERN_ID 226 pattern_id 236, 262, 265, 268, 272 pattern_name 272 PATTERN_VALUE 230 patterns adding 91 deleting 91 managing 91 patterns_data.txt 236, 272 patterns_testcall_map_data.txt 272 pc_cluster 266 pc_member 267 pc_network 266 person_groups_data.txt 245 person_id 236 persons_data.
S RT_CDR table recreating 149 Running Individual Tasks 211 S saving, Solaris server configuration 147 Scheduling CDR Deletion 308 CDR Exporting 311 CDR Merge 312 CDR Upload 306 schema exporting 208 scripts besbulkload.
telephone viewing MAC address through 173 testing telephone buttons 175 telephone LEDs 175 text files editing 316 Text Files, Editing bss_server_config 303 time 95 TIME_OUT_HOUR 312 TIMEOUT 230, 235, 247 title 236 Tomcat clear cache 198 TOS_FATURE_MAP_ID 247 TOS_ID 247, 248 TOS_NAME 248 total_ep 274 trans_group_id 248 trans_src_dest_data.
W week_day_id 254 week_day_name 254 week_days_data.
