Administering Avaya Aura SIP Enablement Services on the Avaya S8300 Server

Transcription

1 Administering Avaya Aura SIP Enablement Services on the Avaya S8300 Server Issue 2.0 May 2009

2 Copyright 2009, Avaya Inc. All Rights Reserved Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases. For full legal page information, please see the complete document, Avaya Legal Page for Software Documentation, Document number To locate this document on the web site, simply go to and search for the document number in the search box. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the following Web site: Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Certain Software programs or portions thereof included in the Product may contain software distributed under third party agreements ( Third Party Components ), which may contain terms that expand or limit rights to use certain portions of the Product ( Third Party Terms ). Information identifying Third Party Components and the Third Party Terms that apply to them is available on Avaya s web site at The disclaimers of warranties and limitations of liability set forth in the Third Party Terms do not affect any express warranty or limitation of liability that may be provided to you by Avaya pursuant to the license terms covering the Product contained in a separate written agreement between you and Avaya. To the extent there is a conflict between the General License Terms or your customer sales agreement and any Third Party Terms, the Third Party Terms shall prevail solely for such Third Party Components. Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Web site:

3 Contents Chapter 1: Administering Communication Manager for SIP Enablement Services Administering Communication Manager for SIP Prepare Communication Manager Administer call routing Administer SIP signaling and trunks Administer stations Redirect calls off the network Chapter 2: Communication Manager screen details for SIP SIP administrative screens ARS/AAR Digit Analysis Table screen ANI Reqd Call Type (for AAR only) Call Type (for ARS only) Dialed String Location (for the ARS Digit Analysis Table) Max Min Node Num Percent Full Route Pattern Configuration Set screen Configuration Set Description Dial Plan Analysis screen Call Type Dialed String Percent Full Total Length Feature Access Codes screen page Auto Alternate Routing (AAR) Access Code Auto Route Selection (ARS) Access Code Feature Related System Parameters screen, page EMU Inactivity Interval for Deactivation Incoming Call Handling Treatment screen Called Len Called Number Del Insert Service/Feature Issue 2.0 May

4 Contents IP Codec Set screen IP Network Map screen Region Emergency Location Extension IP Network Region screen Region Authoritative Domain Intra-region IP-IP Direct Audio Inter-region IP-IP Direct Audio Use Default Server Parameters Server IP Address Server Port IP Node Names screen Name IP Address Proxy Selection Route Pattern Media Gateway screen Network Region Numbering Public/Unknown screen Off-PBX Station Mapping screen page Command parameters Station Extension Application Dial Prefix Phone Number Trunk Selection Configuration Set Dial Prefix Off-PBX Station Mapping screen page Station Extension Call Limit Mapping Mode Calls Allowed Bridged Calls Configuration considerations for SIP phones Route Pattern screen Secure SIP Signaling Group Page 1 screen Group Number Group Type Transport Method Administering SES on the Avaya S8300 Server

5 Contents Co-resident SES Near-end Node Name Far-end Node Name Near-end Listen Port Far-end Listen Port Far-end Network Region Far-end Domain Bypass If IP Threshold Exceeded DTMF over IP Session Establishment Timer Direct IP-IP Audio Connections IP Audio Hairpinning Enable Layer 3 Test Station screen, page Type System Capacity screen SIP Trunks System-Parameters screens DID/Tie/ISDN/SIP Intercept Treatment Disable call classifier for CCRON over SIP trunks System-Parameters Customer-Options screen, page Maximum Off-PBX Telephones - EC Maximum Off-PBX Telephones - OPS Used System Parameters Customer Options screen, page Maximum Administered SIP Trunks System Parameters Customer Options screen, page ISDN PRI Enhanced EC IP Trunks System Parameters Customer Options screen, page Private Networking Trunk Group screens Group Number Group Type CDR Reports Group Name COR TN TAC Direction Issue 2.0 May

6 Contents Outgoing Display Dial Access Busy Threshold Night Service Queue Length Service Type Auth Code Signaling Group Number of Members Trunk Group screen, Page UNICODE Name Redirect on OPTIM failure Digital Loss Group Preferred Minimum Session Refresh Interval (sec) Trunk Group screen, Page ACA Assignment Measured Maintenance Tests Numbering Format Prepend '+' to Calling Number? Replace Unavailable Numbers Show ANSWERED BY on Display field Trunk Group screen, page Mark Users as Phone Important: SIP device as an OPS extension Chapter 3: Administering web interface Top Screens Logon ID Password SIP Enablement Services Server (Maintenance) Setup screens Setup SIP Domain Setup Hosts Setup Default User Profile and Media Servers Setup Default User Profile Setup Media Servers Edit System Properties screen SES Version Administering SES on the Avaya S8300 Server

7 Contents System Configuration Host Type SIP Domain SIP License Host Management System Access Login Management System Access Password DiffServ/TOS Parameters Parameters DB Log Level Network Properties Redundant Properties Add Host screen Host IP Address Profile Service Password Host Type Parent Listen Protocols Link Protocols Access Control Policy Emergency Contacts Policy Minimum Registration (seconds) Registration Expiration Timer (seconds) Line Reservation Timer Outbound Routing Allowed From Outbound Proxy Outbound Port Outbound Direct Domains Default Ringer Volume Default Ringer Cadence Default Receiver Volume Default Speaker Volume VMM VMM Server Address VMM Server Port VMM Report Period Edit Default User Profile screen Host Address 1, Address City State Country Issue 2.0 May

8 Contents ZIP Update Add Media Server screen Media Server Interface Name Host SIP Trunk Link Type SIP Trunk IP Address SIP Trunk Port Media Server Admin Address Media Server Admin Login Media Server Admin Password/ Password Confirm SMS Connection Type Core Router screens Branch Prefix Branch Address Core Router Total Length List Handle Maps screen Branch Prefix IM Handle User screens User ID Host Name Add User task Contact List task Devices task Delete All Displayed Users task Delete Selected Users task Extensions task Handles task Memos task Move User Permissions Profile Watchers for User Submit Add User screen Primary Handle User ID Administering SES on the Avaya S8300 Server

9 Contents Password, Confirm Password Host First Name, Last Name Address 1, Address Office City State Country ZIP Survivable Call Processor Add Media Server Extension Add My Contact List task screen Handle Name Alias Telephone #1 / Telephone # Handle (link) Group (link) View Delete Add Contact Add Group Speed Dial Reload Configuration Contact Details screen Update Contact screen Add Contact screen Address Name Alias Group Name Notes Track Availability Contact Phones Add Add Group screen Group Name Submit Speed Dial List screen Issue 2.0 May

10 Contents Handle Name Alias Prefix Telephone # Delete Contact screen Group Details screen Handle Name Alias Telephone #1 and Telephone # Back to My Contact List Add Contact Delete Group Update Group View Delete Delete Group screen Delete all contacts Move all contacts Back to My Contact List Yes No Update Group screen Old Group Name Group Name Back to My Contact List Submit Update Devices Screen menu One Touch Dial List screen Button Address Label Save Ringer Settings screen Button Bridged Appearance Ringer ON/OFF Save Tone and Volume Settings screen Ringer Cadence Administering SES on the Avaya S8300 Server

11 Contents Ringer Volume Receiver Volume Speaker Volume Delete All Displayed Users task Delete Selected Users task Extensions tasks Extension User Media Server Host Free Edit User Delete List Media Server Extensions when user has none Add Another Media Server Extension Assign Free Media Server Extension Add Media Server Extension screen Add Media Server Extension screen field descriptions Extension Media Server Add Select Free Extension screen Extension Select Handles task User ID Handle Contact Edit (Handle) Delete (Handle) Add Another Handle Edit (Contact) Delete (Contact) Add Another Contact Add Handle in New Group Delete Group Edit Handle detail screen User ID Domain Handle Update Issue 2.0 May

12 Contents Edit Host Contact screen User ID Contact Contact Type Media Server option User option Update Add Handle screen User ID Handle Add Add Host Contact screen User ID Handle Contact and Contact Type Media Server option User option Add Add Handle in a New Group screen User ID Handle Add Group screen commands Add User Memos screen User ID List of memos Add Memo box Delete Add Memo button Move User Task Moving a user to another home server Permissions screen Current Permissions Type Change Permissions Type Handle Change Permissions Type Allow List/Block List Add Entry Edit User Profile screen User ID Password, Confirm Password Administering SES on the Avaya S8300 Server

13 Contents Host First Name, Last Name Address 1, Address Office City State Country ZIP Watchers Task Current Permissions Type Contact List Members Unknown (SIP Users) Go to Permissions Go to Contact List Search User screen Host User ID First Name, Last Name Address 1, Address Office City State Country ZIP Search Select User screen User ID Update Password screen User ID Password, Admin_Password_Confirm Update Default Profile Moving a user to another home server from Edit Profile screen Confirm Delete User screen Confirm Delete Delete Extensions Also OK Cancel Issue 2.0 May

14 Contents Chapter 4: System Management Interface Alarms screens Current Alarms screen Product ID ID Source EvtID Lvl Ack Date Description Server Alarms Agent Status 8300 Server Master Agent Status Sub Agent Status SNMP Agents 8300 Server Master Agent Status View G3-AVAYA-MIB Data IP Addresses for SNMP Access SNMP Users/Communities Enable SNMP Version Enable SNMP Version 2c Enable SNMP Version User (read-only) User (read-write) Troubleshooting SNMP Traps screen Status IP Address Notification SNMP Version Community or User Name V3 Security Model Authentication Password (v3 only) Privacy Password (v3 only) Problems displaying trap information Functions Add Change Delete Administering SES on the Avaya S8300 Server

15 Contents Change Trap Destination screen new Add or change a trap destination Problems adding or changing traps SNMP version-dependent information SNMP v2c and v3 inform operation SNMP v3 user-based security model Delete Trap Destination screen new Filters screen 8300 Server Filters Configure Filters Customer Alarm Reporting Options SNMP Test screen Restarts screen 8300 Server Cause Action Escalated Time System Logs screen Select Log Types (multiple log output will be merged) Select a View Select Event Range Match Pattern Display Format Temperature/Voltage screen Feature Value Crit_Low Warn_Low Warn_High Crit_High Status Ping screen Ping screen field descriptions Host Name Or IP address Options Execute Ping Successful ping results Unsuccessful ping results Traceroute screen Host Name or IP Address Options Issue 2.0 May

16 Contents Successful traceroute results Unsuccessful traceroute results Netstat screen Output type Output format Show only the following output families Active Internet connections (w/o servers) Active UNIX domain sockets (w/o servers) Modem Test screen Test Options Troubleshooting modem problems Network Time Synch screen Server screens Mode SIP Role Major Alarms Minor Alarms Control Network Server Hardware Processes Refresh page Process Status screen Content Frequency Interchange Servers screen Force Interchange Busy-Out Server screen Release Server screen Shutdown Server screen Options to Shut down Server Date/Time screen General Notes on Timeserving Date Select Time Time Zone Software Version screen Operating System SES Release String Software Load Server BIOS Build ID Administering SES on the Avaya S8300 Server

17 Contents SAMP Version ID Server Configuration Restore Defaults screen The following interfaces will be removed The following files will be altered Set Static Routes IP Address Subnet Mask Gateway Interface Network Time Server screen Time of Day Synchronization Use Local Clock Use these Network Time Servers Providing The Keys.install File Set Modem Interface screen IP Address Change Modem Settings RMB Network Configuration screen Services Laptop Reserved (Services Future Use) (Optional) Eject CD-ROM screen Eject Server Upgrades screens Moving around within the Manage Software wizard Running the Manage Software wizard after a session time-out Using progress indicators Working with the Manage Software wizard window Choose task Install New Software Wizard Steps/Pages Choose Software Choose License Source Review Notices Using progress indicators Working with the wizard window Begin Installation Install in Progress Reboot Server Service Impacts Reboot in Progress Issue 2.0 May

18 Contents Install License Files Installation Complete Make Upgrade Permanent screen Partition Status Partition status states Manage Updates screen BIOS Upgrade screen 8300 Server Backup Now screen Data Sets Backup Method Encryption Schedule Backup screen Data set Day Time Status Destination Add a backup schedule Data Set File Size Date Time Status Destination Network Device Local directory Local PC card Restore History screen Format PC Card /Compact Flash screen Administrator Accounts screen 8300 Server Types of logins REMOTE logins CDR logins ADMINISTRATIVE logins Types of Linux Groups User Profiles Creating an administrator account (login) Deleting login groups File synchronization Login Reports screen 8300 Server List local host logins Administering SES on the Avaya S8300 Server

19 Contents Display login information Locked logins Modem screen Modem Administration Solving modem problems Server Access screen 8300 Server Syslog Server screen 8300 Server License File screen 8300 Server Install the license file I previously downloaded Install the license file specified below Solve license file installation problems Authentication File screen File Path URL Proxy Server Install the Authentication file I previously downloaded Install the Authentication file I specify below Install Firewall screen Input to server Output from server Service Port/Protocol Tripwire Status Audit Frequency Install Root Certificate screen 8300 Server Internet Explorer SSH Keys screen Current SSH public keys Generate New SSH Keys Web Access Mask screen Access Masks and Names Commands Name Device Manager Computer Configuration and Device Manger File Synchronization screen 8300 Server IP Phones screen 8300 Server Download Files screen Prerequisites Issue 2.0 May

20 Contents File(s) to download from the machine I'm using to connect to the server File(s) to download from the LAN using URL Install this file on the local server CM Phone Message File screen 8300 Server Tftpboot Directory screen 8300 Server To check the version of installed firmware: Serial Numbers screen 8300 Server SES Software screen 8300 Server Messaging Software screen 8300 Server Scheduled Backup Appendix A: Feature requirement specifications Call processing software RFC 3325 compliance Compliance with RFC FNU requirements Send All Calls of the endpoint s own (1111) extension FNU structure Send All Calls of another endpoint s (2222) extension FNU structure Appendix B: Terminal requirements for SIP Terminals Glossary Index Administering SES on the Avaya S8300 Server

21 Chapter 1: Administering Communication Manager for SIP Enablement Services This chapter describes the screens to visit and the fields to change so that your SES and Communication Manager system can run concurrently on a new Avaya S8300 server. For detailed information and rationale about these steps, see these sections: SIP administrative screens on page 29 Important: SIP device as an OPS extension on page 102 Administering Communication Manager for SIP This section describes how to administer and configure SIP on a Communication Manager 5.0 system so that Communication Manager (and SES, running on the same server) support SIP endpoints. You administer and configure SIP trunking on the system with Communication Manager screens and fields, some of which are specific to SIP. You may have been directed to this point from the section in the SES installation procedures, from the section, Administering Communication Manager and endpoints. All installation work discussed prior to this point should be correctly completed. Communication Manager must be functioning properly before you start SIP administration and SES implementation. If your Communication Manager installation uses the Enhanced Meet Me conferencing feature, install that feature before you start the following administration steps. Administer SIP endpoints on Communication Manager using OPS. OPS supports advanced SIP telephony. To administer SIP trunks in Communication Manager 5.0, complete the procedures in this section. Each step includes a link to an example screen, should you need to review it. Prepare Communication Manager on page 20 Administer call routing on page 22 Administer SIP signaling and trunks on page 24 Administer stations on page 27 Redirect calls off the network on page 28 Administration for visiting users on page 28. Issue 2.0 May

22 Administering Communication Manager for SIP Enablement Services Prepare Communication Manager Complete these steps to prepare Communication Manager for SES. 1. Verify that your system supports and is correctly configured for IP connectivity. See Administering Network Connectivity on Avaya Aura Communication Manager, doc ID Go to the System Capacity screen. Figure 19: System Capacity screen on page 76. Check the values for the field SIP Trunks (included in "Trunk ports"). If no values are displayed here, it means that SIP has not been licensed properly. You cannot proceed. Correct SIP licensing problems and begin here after completing that. 3. Go to the System-Parameters Customer-Options screen page 4. Figure 24: System Parameters Customer Options screen, page 4 on page 83. Check the following values: a. Verify or set the field ISDN PRI to y. b. Verify that the IP Trunks field is set to y. c. Verify or set the field Enhanced EC500 to y. You must log off and log back in to effect changes to System Parameters Customer-Options screens. 4. Go to the System Parameters Customer-Options screen page 2. Figure 23: System Parameters Customer Options screen, page 2 on page 82 Verify that the Maximum Administered SIP Trunks field has a value within these ranges: 0 through 400 for S8300C servers (on which you are administering co-resident SES) 0 through 500 for S8400 servers (standalone servers running CM software only) 0 through 800 for S8500-series servers (standalone servers running CM or SES Edge) 0 through 5000 for S8700/S8710/S8720/S8730 servers (running CM only) You must log off and log back in to effect changes to System Parameters Customer-Options screens. 20 Administering SES on S8300

23 Administering Communication Manager for SIP 5. Go to the System Parameters Customer Options screen, page. 1 Figure 22: System Parameters Customer Options screen, page 1 on page 80. Use these fields at the bottom of the page: Maximum Off-PBX Telephones - EC500, for cell phones Maximum Off-PBX Telephones - OPS, for advanced SIP telephony phones In each field, verify that the number of stations that you want to set up for each type of OPS telephone is correct. If not, there may be a problem with your Avaya license files or server. You must log off and log back in to effect changes to System Parameters Customer-Options screens. 6. Go to the IP Node Names screen. Figure 10: IP Node Names screen on page 55. Check all fields to ensure that they are correct for your network. Entries are required for all other home or edge servers running SES and any others running Communication Manager. 7. Go to the IP Address Mapping screen. Figure 8: IP Network Map screen on page 49. Enter the IP address and the host name for the administered SIP proxy server (SES Edge 5.0 in multiple server SES configurations) on your network in the corresponding fields. 8. Go to the IP Network Region screen to assign an IP network region for the SIP trunk. Figure 9: IP Network Region screen on page 51. a. In the Authoritative Domain field, enter the SIP domain name for which this network region applies. This same SIP domain name is used in the SES interface. b. Set the field Intra-region IP-IP Direct Audio to y. c. Set the field Inter-region IP-IP Direct Audio to y d. Set the field Server IP Address and the field Server Port to the IP address and port number of the RTCP Monitor server, if applicable in your system. 9. Go to the Media Gateway screen on page 58. Make sure that the Network Region is the same as the network region for the SIP authoritative domain. 10. Go to the IP Codec Set screen on page 47. Check that you have the right media compression for your SIP endpoint types and other constraints. Issue 2.0 May

24 Administering Communication Manager for SIP Enablement Services Administer call routing Before you can make SIP calls from endpoints that are connected to Communication Manager, administer call routing properly in Communication Manager. 1. Go to the Feature Access Code screen. Feature Access Codes screen page 1 on page 43. You may set either the ARS Access code fields, or the AAR Access code fields or both. To enable these fields, make sure that on the System Parameters Customer Options screen page 5, the Private Networking field is set to y. See Figure 25: System Parameters Customer Options screen, page 5 on page Go to the ARS Digit Analysis Table screen. Figure 1: ARS Digit Analysis Table screen on page 31. Administer this screen to make sure that dialed strings of digits are interpreted correctly and the resulting calls are routed appropriately using the SIP trunks that you administered in Step 3 through Step 6 in the section Administer SIP signaling and trunks on page 24. Note: Note: You may not access a SIP trunk with a dialed TAC. If you use Avaya Distributed Office, you must administer this screen to use AAR. Avaya Distributed Office does not use ARS. 3. Go to the Dial Plan Analysis screen to translating the digits dialed by users. Figure 3: Dial Plan Analysis screen on page 39. You must have the summary of your dial plan available for reference. 4. Go to the Route Pattern screen. Figure 16: Route Pattern screen on page 67. Verify that the Secure SIP field is set to the default value of n for routing through a public network. You can set secure sip to y only if you have a secure connection between the public SIP network and the SES home server you are routing to. Choose a route pattern. Fill in the correct trunk, FRL, and number of digits to insert and delete. This task can be performed using either AAR or ARS. The most frequent case would be for ARS. 22 Administering SES on S8300

25 Administering Communication Manager for SIP 5. Go to the Numbering - Public/Unknown Numbering Table screen and assign public unknown numbering data. If your SES installation is part of an Avaya Distributed Office network, this screen should match extensions, trunks, and prefixes in Avaya Distributed Office Central Manager. Make an entry here for the trunk that you use in your route pattern. For Avaya Distributed Office, confirm that the value for Ext Len matches what is specified in the field SES Edge 5.0. See the Figure 13: Numbering Public/Unknown screen on page Go to the Locations screen. Figure 11: Locations screen on page 56. Type the appropriate Proxy Selection Route Pattern in the field corresponding to each location employing a SIP proxy server. Issue 2.0 May

26 Administering Communication Manager for SIP Enablement Services Administer SIP signaling and trunks Use these steps to set up SIP trunking facilities in Communication Manager on the server. 1. Go to the Signaling Group screen page 1. Figure 17: Signaling Group screen, Page 1 on page 69. a. Type sip in the field Group Type. The system displays a screen for SIP groups. b. Verify that the Transport Method field contains the default value of tls. c. Verify that the ETSI CCBS Support field contains the default value of n. d. In the Co-Resident SES field, set the value to y, as this signaling group is used to communicate with the SES application. e. Verify that the Near-end Node Name field contains the default value of procr. For CM running co-resident with SES on the S8300, the value of this entry is typically procr. This also is the value for the S8400 or S8500-series servers running only CM, For an Avaya S8700-series standalone server running Communication Manager 5.0, the entry is the node name for the selected CLAN or procr interface, as applicable. f. In the Far-end Node Name field, keep the value as procr. enter the name of the node that you administered as the SIP proxy server (that is, an SES Edge 5.2 server) in Step 7. g. In the Near-End Listen Port field, verify that the value is set to default h. Verify that the Far-end Listen Port field contains the default value of 6001, as the SES application expects this port number to be set. i. For the Far-end Network Region field, if you want the SIP proxy server that you administered in Step 7 to use the codec set and/or parameters specified for an IP network region that is different from that of the LAN IP interface, then enter the network region of the SIP proxy server. j. For the Far-end Domain field, enter the IP address that represents your SIP Domain. For example, to route SIP calls within your enterprise, enter the domain assigned to your SIP proxy (SES Edge 5.0) server. For external SIP calling, this domain name could be that of the proxy assigned to you by your SIP service provider. k. In the field DTMF over IP, make sure that the value is rtp-payload. l. The recommended value for the field SIP Session Establishment Timer is 3 minutes, but it must be less than or equal to the SES value named TimerC. This timer works in conjunction with the SES variable, TimerC, usually set in the ccs.conf file. For proper ringing no answer times, the SES TimerC should be a value greater than or equal to the Session Establishment Timer on this page. If you cannot access ccs.conf, make sure the value of Session Establishment Timer is set less than the value of TimerC. 24 Administering SES on S8300

27 Administering Communication Manager for SIP m. Setting the field Enable Layer 3 Test is optional. The default is n. The value n uses the ping test and does not use the OPTIONS test. Enter a y to use the OPTIONS test instead of a ping. 2. Go to the System Parameters Features screen page 1. Figure 20: System Parameters Feature screen Page 1 on page 78. a. Set the DID/Tie/ISDN/SIP Intercept Treatment field to attd. b. Verify that the Trunk-to-Trunk Transfer field is set to restricted. 3. Go to the Trunk Group screen page 1. Figure 26: Trunk Group screen, page 1 on page 86: a. Type sip in the Group Type field. The screen displays fields that pertain to SIP groups. An entry of sip also affects the fields that are presented on other administrative screens discussed later. b. Depending on your need for Call Detail Recording (CDR), type y for yes or n for no in the CDR Reports field. Note that very large numbers of CDR reports may be generated by SIP calls. c. Type the number of the SIP signaling group that you previously administered in the Signaling Group field. d. Type a value in the range of 0 through 255 in the Number of Members field for the number of SIP trunks that belong to this group. Group Member Assignments are automatically completed and populated on the Trunk Group screens on page 86, and on any subsequent pages of the screen that are necessary, based on the values that you entered on the Trunk Group screens. Group members cannot be administered individually. All members of each administered group share the same characteristics. Note: Note: The total number of all SIP trunks that are specified for all groups must be less than or equal to the value in the Maximum Administered SIP Trunks field on the System-Parameters Customer Options screen (step 4 on page 20). For more information, see Figure 19: System Capacity screen on page 76. e. Repeat the preceding Steps a. through d. for each SIP trunk group you want to assign, up to the trunk-number limit for your server. 4. Go to the Trunk Group screen, Page 2 on page 94. Set the field Group type to sip. Administer the other fields on this screen as necessary for your Avaya system. Issue 2.0 May

28 Administering Communication Manager for SIP Enablement Services 5. Go to the Trunk Group screen page 3. Trunk Group screen, page 3 on page 97. Verify that the value in the Numbering Format field is what you want, Public, Private, unk-pvt (Unknown-Private), or Unknown. Administer the other fields on this screen as necessary for your Avaya system. 6. Go to the Trunk Group screen page 4. Trunk Group screen, page 4 on page 101. Set the field Mark Users as Phone? to y for a particular trunk only if a device or a network that is connected to that SIP trunk requires the User as Phone parameter. Set to y if a public network trunks through a SIP service provider. 7. Go to the Numbering - Public/Unknown Numbering screen and assign public unknown numbering data, as applicable. If your SES installation is part of an Avaya Distributed Office network, this screen should match extensions, trunks, and prefixes in Avaya Distributed Office Central Manager 1.x. See the Numbering Public/Unknown screen on page Administering SES on S8300

29 Administering Communication Manager for SIP Administer stations Use these steps to set up stations in Communication Manager. 1. Go to the Station screen page 1. See Figure 18: Station screen page 1 on page 75. Set the field Type either to 46xx or 96xx, where xx are the ending digits of your station type. If you use 46xx as the Type for a SIP endpoint, then the system may generate minor alarms for these stations. In this case, you may ignore these alarms. If you set Type to any of the DCP phone types, such as a 6400 or 8400, then undesirable interactions with the TTI and other features may occur. Depending on your system softweare, you may need to use a 46xx station type, such has 4620SIP or 4620SIPCC, even if you have a station with a different name or model number. Refer to the user documentation on administering your particular SIP endpoint in Avaya Communication Manager 5.0 for more details. 2. Go to the Configuration Set screen page 1. Figure 2: Configuration Set screen on page 37. Set the field Configuration Set Description to SIP phone. 3. Go to the Off-pbx Station Mapping screen page 1. Figure 14: Off-pbx station mapping screen page 1 on page 59. Add station mapping data for SIP endpoints on this screen. 4. Go to the Off-pbx Station Mapping screen page 2. Figure 15: Off-pbx station mapping screen page 2 on page 64. Add more station-mapping data for SIP endpoints on page 2 of this screen. Issue 2.0 May

30 Administering Communication Manager for SIP Enablement Services Redirect calls off the network One option in Communication Manager is to do additional administration to direct the coverage of calls that are redirected off the network (CCRON). Communication Manger monitors the progress of calls from inception to conclusion. If calls go off net, Communication Manager will never recognize the call as completed. Because of the virtual nature of SIP trunks, set this field to n to enable call classification over interworked trunks. Go to the System Parameters Call Coverage/Call Forwarding screen. Figure 21: System Parameters Call Coverage/Call Forwarding screen on page 79. Set the field Disable Call Classifier for CCRON over SIP trunks to y or n, depending on your system. For Avaya SIP solutions, as well as Avaya Distributed Office 1.x, this field is usually set to n. Administration for visiting users Another option in Communication manager is to administer SIP Visiting User; go to the Feature Related System Parameters screen, page 3 on page 44. Be sure that the EMU field is set to a number, not left blank. Set this to 1 for a one-hour session of visiting user, or up to a maximum of 24 hours for the session. The EMU Inactivity timer field determines how long the visiting user feature waits before the visiting status of a SIP phone is dropped due to inactivity. A blank in this field means that there is no automatic shut off of the visiting-user session. For phones designated a visiting, an inactivity timer notifies the user before a visiting session expires, even if the timer is set to null (that is, left blank in administration). Recall that Visiting user is supported only by the Avaya one-x Deskphone SIP on the 96xx series SIP IP telephones. 28 Administering SES on S8300

31 Chapter 2: Communication Manager screen details for SIP This section contains examples of properly populated screens that you might need to verify as you administer Communication Manager for SIP trunking. Best Practices When you add a SIP station in Communication Manager, use DCP set types that can be X-ported. This prevents excessive alarming caused by using 46xx set types. If you use 46xx station types, you receive minor alarms for these stations. You may ignore these alarms. Do not use DCP station types, as undesirable interactions occur with TTI and other features. Some trunk types do not allow X-ported stations that are TTI, for example SBS trunks, to call over them. When you add the SIP station in Communication Manager, do not use 4602 or 2402 set types. Even an Avaya 4602 SIP telephone needs at least three call appearances to handle conference and transfer operations. Similarly, on the change off-pbx-telephone station-mapping x screen page 2, the Call Limit should be at least 3, but also should match what the telephone has if the telephone has a number of call appearances that is greater than 3. (The Avaya default number is 2.) SIP administrative screens This section explains how to administer the following Communication Manager screens to support SIP trunking: ARS/AAR Digit Analysis Table screen on page 31 Configuration Set screen on page 37 Dial Plan Analysis screen on page 38 Feature Access Codes screen page 1 on page 43 Feature Related System Parameters screen, page 3 on page 44 Incoming Call Handling Treatment screen on page 46 IP Codec Set screen on page 48 Issue 2.0 May

32 Communication Manager screen details for SIP IP Network Map screen on page 49 IP Network Region screen on page 51 IP Node Names screen on page 55 Locations screen on page 56 Media Gateway screen on page 57 Numbering Public/Unknown screen on page 58 Off-PBX Station Mapping screen page 1 on page 59 Off-PBX Station Mapping screen page 2 on page 64 Route Pattern screen on page 67 Signaling Group Page 1 screen on page 69 Station screen, page 1 on page 75 System Capacity screen on page 76 System-Parameters screens on page 77 Important: SIP device as an OPS extension on page 102 Trunk Group screens on page 86 These screens deal with SIP administration. Every effort, when possible, has been made to put correct field values in the screen examples. Look at them carefully. Only SIP-related screens are described in this document. Since a properly configured and working Communication Manager is a prerequisite before enabling and administering SES, see the Administering Network Connectivity on Avaya Aura Communication Manager and the Administering Avaya Aura Communication Manager, , for more details about all the Communication Manager screens and fields, including the SIP-related ones presented here. Other screens that might require your attention cited in the section titled Important: SIP device as an OPS extension on page 102. The features and the configuration of your SES SIP network determine what you administer on these screens. See Important: SIP device as an OPS extension on page Administering SES on S8300

33 SIP administrative screens ARS/AAR Digit Analysis Table screen Communication Manager compares dialed numbers with the dialed strings in this table and determines the route pattern for the number. If you alter data in this table, resynchronize data as described in the document Installing and Administering SES, the section titled Data Synchronization between Communication Manager and PPM. If your SIP installation is part of Avaya Distributed Office, complete this screen with AAR as the value in the Call Type field. Avaya Distributed Office does not use ARS. Figure 1: ARS Digit Analysis Table screen change ars analysis ARS DIGIT ANALYSIS TABLE Location: Page 1 of X Percent Full: Dialed Total Route Call Node ANI Reqd String Min Max Pattern Type Num n n n n n n n n ANI Reqd Valid entries y/n r Usage Enter y if ANI is required on incoming R2-MFC or Russian MF ANI calls. This field applies only if the Request Incoming ANI (non-aar/ars) field on the Multifrequency-Signaling-Related System Parameters screen is n. Allowed only if the Allow ANI Restriction on AAR/ARS field on the Feature Related System Parameters screen is y. Use to drop a call on a Russian Shuttle trunk or Russian Rotary trunk if the ANI request fails. Other types of trunks treat r as y. Issue 2.0 May

34 Communication Manager screen details for SIP Call Type (for AAR only) In this field in Figure 1, enter the call type that is associated with each dialed string. Call types indicate numbering requirements on different trunk networks. ISDN protocols are listed in the table below. Valid entries aar intl pubu lev0 to lev2 Usage Regular AAR calls. The Route Index contains public network ISDN trunks that require international type of number encodings. The Route Index contains public network ISDN trunks that require international type of number encodings. Specify ISDN Private Numbering Plan (PNP) number formats. ISDN Protocol Call Type Numbering Plan Identifier Type of Numbering aar E.164(1) national(2) intl E.164(1) international(1) pubu E.164(1) unknown(0) lev0 PNP(9) local(4) lev1 PNP(9) Regional Level 1 (2) lev2 PNP(9) Regional Level 2 (1) 32 Administering SES on S8300

35 SIP administrative screens Call Type (for ARS only) Valid entries Usage Usage in China #1 alrt Alerts attendant consoles or other digital telephones when an emergency call is placed normal emer emergency call normal fnpa 10-digit North American Numbering Plan (NANP) call (11 digits with Prefix Digit "1") attendant hnpa 7-digit NANP call normal intl public-network international number toll-auto iop international operator attendant locl public-network local number normal lpvt local private normal natl non-nanp normal npvt national private normal nsvc national service normal op operator attendant pubu public-network number (E.164)-unknown normal svcl national(2) toll-auto svct national(2) normal svft service call, first party control local svfl service call, first party control toll Dialed String In Figure 1, user-dialed numbers are matched to the dialed string entry that most closely matches the dialed number. For example, if a user dials and the AAR or ARS Digit Analysis Table has dialed string entries of and , the match is on the entry. Issue 2.0 May

36 Communication Manager screen details for SIP An exact match is made on a user-dialed number and dialed string entries with wildcard characters and an equal number of digits. For example, if a user dials 424, and there is a 424 entry and an X24 entry, the match is on the 424 entry. Valid entries Usage 0 to 9 Enter up to 18 digits that the call-processing server analyzes. *, x, X Wildcard characters Location (for the ARS Digit Analysis Table) This is a display-only field on the ARS Digit Analysis Table screen shown in Figure 1. Valid entries Usage 1 to 64 Defines the location of the server running Communication Manager that uses this ARS Digit Analysis Table. On the System-Parameters Customer-Options screen, the ARS field and the Multiple Locations field must be set to y for values other than all to appear. all Indicates that this ARS Digit Analysis Table is the default for all port network (cabinet) locations. Appears only if the Multiple Locations field is set to n on the System-Parameters Customer-Options screen. Max In Figure 1 this is appears as the Total Max field. Valid entries Between Min and 28 Usage Enter the maximum number of user-dialed digits the system collects to match to the dialed string. 34 Administering SES on S8300

37 SIP administrative screens Min In Figure 1 this appears as the Total Min field. Valid entries Usage 1 to Max Enter the minimum number of user-dialed digits that the system collects to match to the dialed string. Node Num In Figure 1, enter the number of the node. Valid entries 1 to 999 or blank Usage Enter the number of the destination node in a private network if you use node number routing or FCS. If you complete this field, leave the Route Index field blank. Percent Full This field in Figure 1 displays the percentage (0 to 100) of system memory resources that have been used by AAR/ARS. If the figure is close to 100%, you can free memory resources. Route Pattern In this field in Figure 1, enter the route number that you want the server running Communication Manager to use for this dialed string. Valid entries p1 to p2000 Usage Specifies the route index number established on the Partition Routing Table. 1 to 640 Specifies the route patterns used route the call. 1 to 999 Specifies the route pattern used to route the call. For the S8300 server only. r1 to r32 Specifies the remote home numbering plan area (RHPNA) table. Complete this field if RHNPA translations are required for the corresponding dialed string. Issue 2.0 May

38 Communication Manager screen details for SIP Valid entries node deny Usage Designates node number routing. Block the call. 36 Administering SES on S8300

39 SIP administrative screens Configuration Set screen This screen defines a several call treatment options for EC500 cell phone calls. The EC500 allows the use of up to 10 Configuration Sets, which are already defined in the system with default values. For SIP, set the field Configuration Set Description to SIP Phone. Complete the other fields to meet the needs of your SIP endpoints. Figure 2: Configuration Set screen change off-pbx-telephone configuration-set 1 Page 1 of 1 CONFIGURATION SET: 1 C onfiguration SetDescription: Calling Number Style: network CDR for Origination: phone-number CDR for Calls to EC500 Destination? y Fast Connect on Origination? n Post Connect Dialing Options: dtmf Cellular Voice Mail Detection: none Barge-in Tone? n Calling Number Verification? y Identity when Bridging: principal Configuration Set Description Describes the purpose of the configuration set. Valid entries Up to 20 alphanumeric characters or blank Usage For example, EC500 handsets. For SIP, enter SIP Phone. Issue 2.0 May

40 Communication Manager screen details for SIP Dial Plan Analysis screen The Dial Plan Analysis Table is the system s guide to translating the digits dialed by users. This screen enables you to determine the beginning digits and total length for each type of call that Communication Manager needs to interpret. The Dial Plan Analysis Table and the Dial Plan Parameters screen work together to define your system s dial plan. Figure 3: Dial Plan Analysis screen display dialplan analysis Page 1 of x DIAL PLAN ANALYSIS TABLE PercentFu l: 7 Dialed Total C a l Dialed Total Call Dialed Total Call String Length Type String Length Type String Length Type 00 2 attd 1 3 dac 2 4 ext 3 4 ext 3 1 aar 4 1 ars 4 5 ext 5 5 ext 5 7 ext Call Type Valid entries aar Usage Automatic Alternate Routing Used to route calls within your company over your own private network. In order to use this code in your dial plan, the ARS/ AAR Dialing without FAC feature must be enabled on the System Parameters Customer-Options (Optional Features) screen. (Contact your Avaya technical support representative to discuss the ARS/AAR Dialing Without FAC feature before enabling it.) When dialing digits of Call Type aar, as soon as the dialed digits have reached the administered length, the digits are treated as if an AAR feature access code (FAC) was dialed. Control is transferred and the digits are routed according to the AAR Analysis and Digit Conversion forms. 38 Administering SES on S8300

41 SIP administrative screens Valid entries Usage In the example shown, extensions of 3xxx cannot be dialed directly. Whenever a user dials the first digit of 3, the system immediately interprets the dialed string as an AAR string and transfers control to AAR. Extensions of 3xxx can only be accessed using AAR Digit Conversion. That is, you must dial a longer AAR number from which AAR Digit Conversion deletes leading digits to form a number of the form 3xxx. ars Automatic Route Selection Used to route calls that go outside your company over public networks. SES solutions that include Communication Manager Branch Edition use only ARS. ARS is also used to route calls to remote company locations if you do not have a private network. In order to use this code in your dial plan, the ARS/AAR Dialing without FAC feature must be enabled on the System Parameters Customer-Options (Optional Features) screen. (Contact your Avaya technical support representative to discuss the ARS/AAR Dialing Without FAC feature before enabling it.) When dialing digits of Call Type ars, as soon as the dialed digits have reached the administered length, the digits are treated as if an ARS feature access code (FAC) was dialed. Control is transferred and the digits are routed according to the ARS Analysis and Digit Conversion forms. In the example shown, extensions of 4xxxx cannot be dialed directly. Whenever a user dials the first digit of 4, the system immediately interprets the dialed string as an ARS string and transfers control to ARS. Extensions of 4xxxx can only be accessed using ARS Digit Conversion. That is, you must dial a longer ARS number from which ARS Digit Conversion deletes leading digits to form a number of the form 4xxxx. attd Attendant Defines how users call an attendant. Attendant access numbers can start with any number from 0 to 9 and contain 1 or 2 digits. If a telephone s COR restricts the user from originating calls, this user cannot access the attendant using this code. Beginning with the November 2003 release of Communication Manager (2.0), you can also administer the attendant access code by entering an appropriate fac or dac entry on the Dial Plan Analysis screen, and then entering the actual access code on the Feature Access Code (FAC) screen. Location-specific attendant access codes can be administered on the Locations screen. Issue 2.0 May

42 Communication Manager screen details for SIP Valid entries dac Usage Dial access code Allows you to use trunk access codes (TAC) and feature access codes (FAC) in the same range. Dial access codes can start with any number from 0 to 9, * or # and can contain up to 4 digits. ext If an extension entry and a DAC entry have the same Dialed String, the extension entry can be longer than the DAC entry only if all of the trunk groups covered by that DAC entry have Dial Access on the Trunk Group screen set to n. You can use the DAC to activate or deactivate a Communication Manager feature or to seize a trunk from a trunk group, or both. In the first case, the DAC functions as a FAC, in the second as a TAC. For example, you can define the group 300 to 399 for dial access codes, and allow both FAC and TAC in that range. You can use 4-digit DACs for ordinary trunk access, but they do not work for attendant control of trunk groups, trunk-id buttons, or DCS, and only the last 3 digits of the codes can be recorded in CDR records. See also the description below for fac. Primary extension Defines extension ranges that can be used on your system. Extension can have a first digit of 0 through 9 and can be 1 to 7 digits in length. Extension cannot have the same first digit as a 1-digit ARS or AAR feature access code (FAC). When a dial plan has mixed station numbering, extensions of various lengths (all with the same first digit) are mapped on the Dial Plan Analysis table. The system then employs an inter-digit time-out to ensure that all dialed digits are collected. fac Feature access code only ó A FAC can be any number from 1 to 9 and contain up to 4 digits. You can use * or #, but only as a first digit. Avaya recommends that a FAC have the longest total length for a given dialed string when using mixed numbering. Otherwise, problems might occur when, for example, 3-digit FACs and 4-digit extensions begin with the same first digit and the FAC is an abbreviated dialing list access code. However, if the entry in the dial plan that defines the FAC is used to define the AAR or ARS access code, then it must have the longest total length in the dial plan. 40 Administering SES on S8300

43 SIP administrative screens Valid entries pext Usage Prefixed extension Is made up of a prefix (first digit) that can be a 0 to 9 (* and # not allowed) and an extension number of up to 5 digits in length. The maximum length of a prefix and extension combination is 6 digits. You cannot administer a dial access code with the same first digit as a prefixed extension. The purpose of the prefix is to identify the call type as an extension. After digit collection, the prefix digit is removed from the string of dialed digits. The remaining digits (extension number) are then processed. A prefixed extension allows the use of extensions numbers with any dialed string (the extension length must be specified on the table). The "prefixed extension" cannot have the same dialed string as the ARS or AAR facility access code (FAC). udp Works identically to ext, with this exception: If dialed digits match the Call Type udp, Communication Manager automatically checks the UDP Table first to see if there is a match, regardless of the value in the UDP Extension Search Order field on the Dial Plan Parameters screen. If there is no match, Communication Manager then checks the local server. If dialed digits match the Call Type of ext, Communication Manager checks the value in the UDP Extension Search Order field on the Dial Plan Parameters screen. - If the value in the UDP Extension Search Order field on the Dial Plan Parameters screen is udp-table-first, Communication Manager checks the UDP Table first to see if there is a match. If there is no match, Communication Manager then checks the local server. - If the value in the UDP Extension Search Order field on the Dial Plan Parameters screen is local-extensions-first, Communication Manager checks the local server first to see if there is a match. If there is no match, Communication Manager then checks the UDP Table. Note: The udp Call Type allows Communication Manager to recognize strings of 14 and 15 digits, which are longer than the maximum extension length of 13 digits. However, udp can be used with any length. Issue 2.0 May

44 Communication Manager screen details for SIP Dialed String The dialed string in the Dial Plan Analysis screen contains the digits that Communication Manager will analyze to determine how to process the call. This field allows you to enter up to four digits, so you can allocate blocks of 1000 numbers even when using a 7-digit dial plan. Valid entries Usage 0 to 9, * and # Enter any combination of 1 to 4 digits. the following restrictions apply: The digits * and # can only be used as first digits, and only for the Call Types fac and dac. For Call Type attd, if the Total Length is 2, the Dialed String must be 2 digits long. Two Dial Plan entries can use the same Dialed String only if the Dialed String is 1 digit long. Longer Dialed Strings must all be unique. A new entry cannot be administered if it causes an existing extension, feature access code, or trunk access code to become inaccessible. Percent Full This field in the Dial Plan Analysis screen displays the percentage (0 to 100) of the system s memory resources that have been allocated for the dial plan that are currently being used. Total Length This field in the Dial Plan Analysis screen concerns the number of digits for the call type. Valid entries 1 to 2 for attd 1 to 4 for dac 1 to 4 for fac 1 to 7 for ext 2 to 6 for pext Usage Enter the number of digits for this call type. The allowed length varies by call type. This must be greater than or equal to the number of digits in the Dialed String. 42 Administering SES on S8300

45 SIP administrative screens Feature Access Codes screen page 1 This screen assigns feature access codes (FACs) that, when dialed, activate or cancel the system features. Each field on this screen has the same valid values, which must conform to feature access codes or dial access codes as defined by your dial plan. The SIP-related fields are in bold. change feature-access-codes Page 1 of x FEATURE ACCESS CODE (FAC) Abbreviated Dialing List1 Access Code: Abbreviated Dialing List2 Access Code: Abbreviated Dialing List3 Access Code: Abbreviated Dial - rgm Group List Access Code: Announcement Access Code: Answer Back Access Code: Attendant Access Code: Auto Alternate Routing (AAR)Access Code: Auto Route Selection (ARS)Access C ode1: Access Code 2: Automatic Callback Activation: Deactivation: Call Forwarding Activation Busy/DA: All: Deactivation: Call Park Access Code: Call Pickup Access Code: CAS Remote Hold/Answer Hold-Unhold Access Code: CDR Account Code Access Code: Change COR Access Code: Change Coverage Access Code: Contact Closure Open Code: Close Code: Contact Closure Pulse Code: Auto Alternate Routing (AAR) Access Code Use this field to access AAR. Auto Route Selection (ARS) Access Code1 Use this field to access ARS. You can have one ARS access code for local and one code for long distance, and route accordingly. Issue 2.0 May

46 Communication Manager screen details for SIP Feature Related System Parameters screen, page 3 For SIP, the EMU Inactivity timer field determines how long the visiting user feature waits before the visiting phone is becomes unregistered due to inactivity. Figure 4: Feature Related System Parameters screen, page 3 display system-parameters feature Page 3 of 17 FEATURE-RELATED SYSTEM PARAMETERS TTI/PSA PARAMETERS WARNING! SEE USER DOCUMENTATION BEFORE CHANGING TTI STATE Terminal Translation Initialization (TTI) Enabled? n Customer Telephone Activation (CTA) Enabled? n Don t Answer Criteria For Logged Off IP/PSA?TTI Stations? n EMU PARAMETERS EM U Inactivity IntervalforDeactivation (hours): 1 CALLPROCESSING OVERLOAD MITIGATION Restrict Calls: stations-first EMU Inactivity Interval for Deactivation Use this field to administer a system-wide administrable interval for EMU (Enterprise Mobile User) de-registration and as an inactivity timer for an SIP visiting user. Valid entries are either digits 1 through 24, or blank. The default is blank. Leaving this field blank means that there is no session timing set. An entry of 1 means that after 1 hour of inactivity, the SIP phone will be dropped (unregistered) from the visited SES Home server. Note that this field is used both by Communication Manager (for Enterprise Mobile Users) as well as by SES 5.0 (for SIP Visiting Users). See Table 1 for a comparison of the differences. For phones designated as visiting, an inactivity timer notifies the user before a visiting session expires, even if the timer is left blank. 44 Administering SES on S8300

47 SIP administrative screens Table 1: Compare SIP Visiting User timer with EMU timer Phone types E911 call routed locally/ CPN sent from visited phone * Login Designating active phone Three states: Active, inactive, unregistered Phone features dependencies SES s SIP Visiting User Timer SIP phones, incl. Avaya one-x Deskphone SIP Supported Same login from any phone Most-recently registered phone is the active phone OR The active phone is set in the SIP PIM web interface. Supports all three states Depends on home phone functionality/user profile Communication Manager EMU Timer H.323 or DCP type phones Supported Requires FAC/PIN for login at visited phone Most recent registration is "active" Supports only two states: active and unregistered states Depends on visited phone functionality Inactivity timer Supported Supported *. The calling party number is not always sent from the visited phone. The CPN may be a derivation based on the IP address and the Communication Manager IP address, for example, in the case of emergency location extension mapping. Issue 2.0 May

48 Communication Manager screen details for SIP Incoming Call Handling Treatment screen For SIP Enablement Services (SES) trunk groups, the Per Call CPN/BN and Night Serv fields do not appear because these fields do on a screen for ISDN trunks. Figure 5: Incoming Call Handling Treatment screen (SIP and Avaya Distributed Office) change inc-call-handling-trmt trunk-group1 Page 1 of X INCOMING CALL HANDLING TREATMENT Service/ Called Called Del Insert Feature Len Number Called Len The Called Len field in Figure 5 specifies the number of digits received for an incoming call. A blank entry may be used only for the situation in which the Called Number field has been set to blank. When used with the blank entry, this means that any length of digits associated with the Called Party IE of the Incoming SETUP message will match this field. The use of the 0 entry is encouraged for the situation in which the PSTN provider does not provide any 'Number Digits' within the received Called Party IE (such as in Japan). Valid entries are 0 to 21, or leave blank. Called Number The Called Number field in Figure 5 specifies the leading digits received for an incoming call. A blank entry is used as a "wild card" entry and, when used, means that any number associated 46 Administering SES on S8300

49 SIP administrative screens with the specified Service/Feature can match in this field. Valid entries are up to 16 digits, or leave blank. Del Insert The Del field in Figure 5 specifies the number of leading digits to be deleted from the incoming Called Party Number. Calls of a particular type can be administered to be routed to a single destination by deleting all incoming digits and then administering the Insert field with the desired extension. Valid entries are 1 to 21, all, or leave blank. The Insert field in Figure 5 specifies the digits to be prepended to the front of the remaining digits after any (optional) digit deletion has been performed. The resultant number formed from digit deletion/insertion is used to route the call, provided night service is not in effect. Valid entries are up to 16 characters consisting of a combination from the following: 0 to 9, *, #, or leave blank. Service/Feature This field in Figure 5 is display-only. It is auto-populated with the value entered in the Service Type field on the Trunk Group screen. Issue 2.0 May

50 Communication Manager screen details for SIP IP Codec Set screen What you set in the IP codec screens depends on the type of phone you are using and the bandwidth. You should certainly have G.711mu-law or a-law. If the SIP endpoint is registering across a WAN with limited bandwidth or via a VPN tunnel, then use G.729. What you select is based on system constraints and their SIP endpoint types. Figure 6: IP Codec Set screen page 1 change ip-codec-set n Codec Set: 1 IP Codec Set Page 1 of x Audio Silence Frames Packet Codec Suppression Per Pkt Size (ms) 1: G.711MU y : 3: 4: 5: 6: 7: Media Encryption: 1: aes 2: aea 3: srtp-aescm128-hmac80 Figure 7: IP Codec Set screen page 2 change ip-codec-set n IP Codec Set Page 2 of x Allow Direct-IP Multimedia? y Maximum Bandwidth Per Call for Direct-IP Multimedia: 256:Kbits Mode Redundancy FAX relay 0 Modem off 0 TDD/TTY us 0 Clear-channel n 0 48 Administering SES on S8300

51 SIP administrative screens IP Network Map screen The IP Address Mapping screen in Figure 8 shows the SIP-related information in bold. You must administer this screen only if you use Emergency Contacts as part of your SES system. If you alter data in this table, resynchronize data as described in Installing and Administering SES, the section titled Data Synchronization between Communication Manager and PPM. Figure 8: IP Network Map screen change ip-network-map Page 1 of x IP ADDRESS MAPPING Em ergency Subnet Location From IP Address (To IP Address) or Mask) Region VLAN Extension _ _ Note: Note: In release 5.0 of Communication Manager, use this screen to allocate resources for both H.323 and SIP endpoints. The IP Address Mapping screen for 911 calls allows you to have a range of IP addresses in a location. You can then assign a 911 number that will be sent to the Public Safety Answering Point (PSAP) if any of the phones within that range of 911 IP addresses makes an emergency call. You can also have another range of addresses for another location with an assigned 911 number. If a user in one location moves to the second location, and makes an emergency call, the user s endpoint sends the correct CPN to the PSAP. Without using the ip-network-map, each SIP station sends out it own number if it makes an emergency call. This step is important in distributed Communication Manager environments in which network bandwidth may be consumed unnecessarily for calls among SIP and other endpoints. Issue 2.0 May

52 Communication Manager screen details for SIP Region This field in Figure 8 identifies the network region for the IP address range. Make sure the Region value you set here reflects the Authoritative Region on screen IP Network Region screen on page 51. If this screen does not correlate with the IP Network Region screen correctly, calls will not be processed successfully. Communication Manager may not assume its authoritative role for the call and routes back out to the proxy. The proxy then redirects back to Communication Manager. In the Locations form shown on page 56, the proxy sel. rte. pat. field causes the call to route out to the proxy. But if this were not configured, the call would be rejected with a 403 Screening Failure. For SIP, the setting for Region must be the same as the Region field in theip Network Region screen on page 51. Valid entries Usage Emergency Location Extension This field in Figure 8 allows the system to properly identify the location of a caller who dials a 911 emergency call from this station. An entry in this field must be of an extension type included in the dial plan, but does not have to be an extension on the local system. It can be a UDP extension. The entry defaults to blank. A blank entry typically would be used for an IP softphone dialing in through PPP from somewhere outside your network. If you populate the IP Address Mapping screen with emergency numbers, the feature functions as follows: 1 to 250 The network region number for this interface. This field must contain a non-blank value if the From IP Address field on the same row contains a non-blank value. If the Emergency Location Extension field in the Station screen is the same as the Emergency Location Extension field in the IP Address Mapping screen, the feature sends the extension to the Public Safety Answering Point (PSAP). If the Emergency Location Extension field in the Station screen is different from the Emergency Location Extension field in the IP Address Mapping screen, the feature sends the extension in the IP Address Mapping screen to the Public Safety Answering Point (PSAP). Valid entries Usage 0 to 9 (up to 7 digits) Enter the emergency location extension for this station. Default is blank. Note: Note: On the ARS Digit Analysis Table screen, you must administer 911 to be call type emer or alrt in order for the E911 Emergency feature to work properly. 50 Administering SES on S8300

53 SIP administrative screens IP Network Region screen The SIP-related fields are in bold in Figure 9. Figure 9: IP Network Region screen change ip-network-region 1 Page 1 of 19 IP NETWORK REGION R egion: 1 Location: 1 Authoritative Domain: Name: Intra-region IP-IP DirectAudio:y MEDIA PARAMETERS Inter-region IP-IP DirectAudio:y Codec Set: 1 IP Audio Hairpinning? y UDP Port Min: 2048 UDP Port Max: 3028 RTCP Reporting Enabled? y RTCP MONITOR SERVER PARAMETERS DIFFSERV/TOS PARAMETERS Use DefaultServerParam eters? n Call Control PHB Value: ServerIP Address:... Audio PHB Value: ServerPort:5005 Video PHB Value: 802.1P/Q PARAMETERS RTCP Report Period(secs): 5 Call Control 802.1p Priority: 7 Audio 802.1p Priority: 6 AUDIO RESOURCE RESERVATION PARAMETERS H.323 IP ENDPOINTS RSVP Enabled? y H.323 Link Bounce Recovery? y RSVP Refresh Rate(secs): 15 Idle Traffice Interval (sec): 20 Retry upon RSVP Failure Enabled? y Keep-Alive Interval (sec): 6 RSVP Profile: guaranteed-service Keep-Alive Count: 5 RSVP unreserved (BBE) PHB Value: 40 Region You can change the properties of each region administered in the IP Network Map screen on page 49 using this screen. Authoritative Domain The Authoritative Domain field in Figure 9 must be set to the same value as the SIP domain administered, the home domain, or a third-party proxy for the signaling group associated with this network region. Issue 2.0 May

54 Communication Manager screen details for SIP This field designates the name or IP address of the domain for which this network region is responsible or authoritative. Valid entries Up to 20 characters or blank. Usage Enter the name or IP address of the domain for which this network region is responsible. Note that this will appear in the From header of any SIP messages. A valid entry in this field is required for SIP endpoints on Communication Manager to call the public network. Note that the value for this Authoritative Domain field must match the content of the Domain field on the Edit screen in SES, which is set with the Master Administration web interface in the SES system. In a single-server configuration, a home authoritative server combined on an Edge server, exactly one authoritative domain is set, for example, company.com. In a duplex configuration, each home is subject to the domain to which it is connected. Each Edge can have a separate domain, and a single CM can support multiple domains. Subdomain structures are not supported. You may use domain structures such as eastcompany.com or westcompany.com. Intra-region IP-IP Direct Audio Set this field in Figure 9 to n to prevent direct audio connections between IP endpoints within a network region. Usually a SIP installation sets this to y. Valid entries y/n Usage Enter y to save on bandwidth resources and improve sound quality of voice over IP transmissions. An n entry might be used if, for example, the IP phones within the region are behind two or more fire walls. 52 Administering SES on S8300

55 SIP administrative screens Valid entries native(nat) translated(nat) Usage Enter native(nat) if the IP address from which audio is to be received for direct IP-to-IP connections within the region is that of the telephone/softphone itself (without being translated by NAT). IP phones must be configured behind a NAT device before this entry is enabled. Enter translated(nat) if the IP address from which audio is to be received for direct IP-to-IP connections within the region is to be the one with which a NAT device replaces the native address. IP phones must be configured behind a NAT device before this entry is enabled. Inter-region IP-IP Direct Audio This field in Figure 9 allows direct audio connections between IP endpoints within a network region. For SIP, set this to n. In SIP, band width is virtual. See SIP trunk engineering notes on page 24. Valid entries y/n native(nat) trnslated(nat) Usage Enter y to save on bandwidth resources and improve sound quality of voice over IP transmissions. An n entry might be used if, for example, the IP telephones within the region are behind two or more fire walls. Enter native(nat) if the IP address from which audio is to be received for direct IP-to-IP connections within the region is that of the telephone/softphone itself (without being translated by NAT). IP phones must be configured behind a NAT device before this entry is enabled. Enter translated(nat) if the IP address from which audio is to be received for direct IP-to-IP connections within the region is to be the one with which a NAT device replaces the native address. IP phones must be configured behind a NAT device before this entry is enabled. Issue 2.0 May

56 Communication Manager screen details for SIP Use Default Server Parameters Set this field in Figure 9 to n so that the screen displays the fields Server IP address and Server Port. Server IP Address The system displays this field, as shown in Figure 9, only when the Use Default Server Parameters field is set to n and the and the RTCP Enabled field is set to y. For SIP, set this field to the IP address of the RTCP Monitor server. Valid entries 0 to 255 in a series of four octets. Usage Enter the IP address for the RTCP Monitor server Server Port The system displays this field, as shown in Figure 9, only when the Use Default Server Parameters field is set to n and the RTCP Enabled field is set to y. Valid entries Usage 1 to Enter the port number for the RTCP Monitor server. 54 Administering SES on S8300

57 SIP administrative screens IP Node Names screen Enter the friendly names and the IP addresses for SES home servers and CLAN or procr on this screen. Figure 10: IP Node Names screen change node-names ip Page 1 of X IP NODE NAMES Name IP Address Name IP Address Note: Note: If you are using an SES system for SIP, enter the IP address for the SIP Proxy Server, a home or home/edge, for your network in the corresponding fields. Name The Name column in Figure 10 identifies the name of an adjunct or server, or switch node. Valid entries 1 to 15 alphanumeric characters Usage Used as a label for the associated IP address. The node names must be unique for each server and switch. Issue 2.0 May

58 Communication Manager screen details for SIP IP Address The IP Address column in Figure 10 identifies for the node named in the previous field by it s dotted octet address. Valid entries 32-bit address (4 decimal numbers, each in the range 0 to 255) Usage A unique IP address is assigned to each port on any IP device that is used for a connection. See the Administering Network Connectivity on Avaya Aura Communication Manager, doc ID for more information. Locations screen This screen allows for each location to point to the route pattern that is routing to its outbound SIP proxy server. This correlation is required by features and services such as Transfer and URI Dialing. You may use any route pattern for any SIP trunk. The SIP-related fields are in bold. Figure 11: Locations screen change locations Page 1 of 1 LOCATIONS ARS Prefix 1 Required For 10-Digit NANP Calls? y Loc. Name Timezone Rule NPA ARS Attd Loc. Pre- Proxy Sel. No Offset FAC FAC Parms. fix Rte.Pat. 1. Main + 00: Denver-01-01: Lincroft : xxx : xxx : 56 Administering SES on S8300

59 SIP administrative screens Proxy Selection Route Pattern The Proxy Selection Route Pattern field identifies the routing pattern that leads to the proxy server. This is the route pattern assigned on the Route Pattern screen. Valid entries Usage 1 to 999 or blank Type the number of the routing pattern to be used to get to the proxy server. Media Gateway screen Figure 12: Media Gateway screen add media-gateway x Page 1 of 1 MEDIA-GATEWAY Number: IP Address: Type: FW Version/HW Vintage: Name: MAC Address: Serial No: Encrypt LInk? Network Region: Location: Registered? Controller IP Address: Recovery Rule: Site Data: Name: Slot Module Type Name V1: # ICC MM V2: ANA MM V3: DCP MM V4: DS1 MM V8: V9: gateway-announcements Max Survivable IP Ext: Announcement board must also be enabled; use enable announcement-board Network Region For SES, the Network region field must have the same value as the network region of the SIP authoritative domain. Network Region indicates what is assigned to the media gateway. It is used by the primary server to allocate resources from the nearest Media Gateway. The number of characters is dependent upon the type of primary server. Issue 2.0 May

60 Communication Manager screen details for SIP Numbering Public/Unknown screen Access the Numbering Public/Unknown screen with the command change public-unknow n-num bering n, where n is the length of a value between 0 and 7 appearing in the Ext Code column. The screen consists of two pages: page 1 displays up to 30 Ext Code entries matching the requested Ext Code length entered on the command line, and page 2 provides 30 blank entries for new user input. If there is sufficient room on the screen, Ext Code entries that are longer than the specified length are also displayed. Enter a length of 0 to designate the attendant. If there are more entries of length n than can be displayed, modify your command to use the ext-digits x command line modifier. For Avaya Distributed Office, confirm that the value for Ext Len matches what is specified in the field SES Edge 5.0. Figure 13: Numbering Public/Unknown screen change public-unknown-numbering 5 NUMBERING - PUBLIC/UNKNOWN FORMAT Page 1 of X Total Ext Extension Trk CPN CPN Len Code Grp(s) Prefix Len Administering SES on S8300

61 SIP administrative screens Off-PBX Station Mapping screen page 1 Use the Stations with Off-PBX Telephone Integration screen to map an office phone to a cell phone through the Extension to Cellular feature. The office phone can be a standard office number or an administration without hardware (AWOH) station. For more information on Extension to Cellular, see Avaya Aura Communication Manager Feature Description and Implementation, This screen relates to the System-Parameters Customer-Options screen, page 1 on page 80. Figure 14: Off-pbx station mapping screen page 1 change off-pbx-telephone station-mapping Page 1 of 2 STATIONS WITH OFF-PBX TELEPHONE INTEGRATION Station Application D ial Phone N um ber Trunk C onfiguration Extension Prefix Selection Set OPS aar 1 Command parameters Action Object Qualifier add off-pbx-telephone station-mapping change off-pbx-telephone station-mapping <station extension> display off-pbx-telephone station-mapping <station extension> list off-pbx-telephone station-mapping <variable> The add off-pbx-telephone station-mapping command displays the blank Stations with Off-PBX Integration screens. You can add up to sixteen associations between an office telephone and an external telephone. The change off-pbx-telephone station-mapping <station extension> command displays the Stations with Off-PBX Integration screens. You can change the associations between office telephones and external telephones. The first line on the screen Issue 2.0 May

62 Communication Manager screen details for SIP contains the information for the station extension that you entered as the command variable. You can also add additional associations in this screen. The display off-pbx-telephone station-mapping <station extension> command displays the Stations with Off-PBX Integration screens. The <station extension> variable is optional. These screens list up to sixteen entries, starting with the station extension you entered as the command variable. If this extension is not administered for an off-pbx, the display starts with the next administered off-pbx extension in numerical order. The list off-pbx-telephone station-mapping <variable> command information about the association between an office phone and an off-pbx phone. The command variable specifies the office phone number or numbers of interest. The <variable> can be: A complete phone number A partial phone number followed by an asterisk, which is a wildcard character Blank Station Extension The Station Extension field is an administered extension in your dial plan. This number is the extension of the office telephone. Valid entries A valid number in your dial plan Usage Type an extension number of the office phone up to eight digits. Default is blank. Application Indicate the type of off-pbx application that is associated with the office phone. You can assign more than one application to an office phone. Valid entries blank EC500 OPS CSP Usage Default is blank. Cell phone with Extension to Cellular SIP-enabled phone Cell phone with Extension to Cellular provided by the cellular service provider 60 Administering SES on S8300

63 SIP administrative screens Dial Prefix The system prepends the Dial Prefix to the off-pbx phone number before dialing the off-pbx phone. The system deletes the dial prefix when a user enters their cell phone number using the Self Administration Feature (SAFE) access code. You must set the routing tables properly so that the dial prefix "1" is not necessary for correct routing. Valid entries blank 0 through 9, *, # Usage Type up to four digits, including * or #. If included, * or # must be in the first digit position. Enter a "1" if the phone number is long-distance. Enter "011" if the phone number is international. Default is blank. Phone Number Enter the phone number of the off-pbx phone. Valid entries Usage 0 through 9 Type up to fifteen digits. Enter the complete 10-digit number. Default is blank. Trunk Selection Defines which trunk group you will use for outgoing calls. Valid entries ars aar trunk group number Usage Indicate which trunk group to use for outgoing calls. Issue 2.0 May

64 Communication Manager screen details for SIP Configuration Set Use the Configuration Set field to administer the Configuration Set number. This number contains the desired call treatment options for the station. Ninety-nine Configuration Sets exist. Valid entries 1 through 99 blank Usage Type the number of the Configuration set or sets. Default is blank 62 Administering SES on S8300

65 SIP administrative screens Dial Prefix The system prepends the Dial Prefix to the off-pbx phone number before dialing the off-pbx phone. The system deletes the dial prefix when a user enters their cell phone number using the Self Administration Feature (SAFE) access code. You must set the routing tables properly so that the dial prefix "1" is not necessary for correct routing. See Figure 14. Valid entries blank 0 through 9, *, # Usage Type up to four digits, including * or #. If included, * or # must be in the first digit position. Enter a "1" if the phone number is long-distance. Enter "011" if the phone number is international. Default is blank. Issue 2.0 May

66 Communication Manager screen details for SIP Off-PBX Station Mapping screen page 2 Finish the administration steps to map an office phone to an off-pbx phone on the second page of the Stations with Off-PBX Telephone Integration screen. The information you entered in the first page appears as read-only information on the second page. Figure 15: Off-pbx station mapping screen page 2 add off-pbx-telephone station-mapping Page 2 of 2 STATIONS WITH OFF-PBX TELEPHONE INTEGRATION Station C a l M apping C a ls Bridged Extension Limit M ode A low ed C a ls both all none Station Extension The Station Extension field is an administered extension in your dial plan. This number is the extension of the office phone. See Figure 15. Valid entries a valid number in your dial plan Usage Type an extension number of the office phone up to eight digits. Default is blank. Call Limit See Figure 15. Valid entries blank 1 through 10 Usage Set the maximum number of calls that can be active simultaneously. Default is Administering SES on S8300

67 SIP administrative screens Mapping Mode Enter the mode of operation for the Extension to Cellular cell phone. Use these modes to control the degree of integration between the cell phone and the office phone. The modes are valid for calls only. For each office phone, you can only assign one cell phone as the origination mode. You cannot assign a cell phone as either the origination or both mode more than once. See Figure 15. Valid entries both termination origination none Usage Default is both when the Phone Number field was previously administered for another extension with a Mapping Mode of termination or none. Default = termination when the Phone Number field was previously administered with a Mapping Mode of origination or both. In the both mode, users can originate and receive calls from the office phone with the cell phone. In termination mode, users can only use their cell phone to receive calls from the associated office phone. Users cannot use the cell phone to originate calls from the associated office phone. Calls originating from the cell phone independent of the office phone are independent of Extension to Cellular and behave exactly as before enabling Extension to Cellular. In origination mode, users can only originate cell phone calls from the associated office phone. Users cannot use the cell phone to receive calls from the associated office phone. In the none mode, users cannot originate or receive calls from the office phone with the cell phone. Calls Allowed Identifies the call filter type for a station. The Calls Allowed values filter the type of calls to the office phone that a user can receive on a cell phone. See Figure 15. Valid entries all internal external none Usage Default is all. The cell phone receives both internal and external calls. The cell phone receives only internal calls. The cell phone receives only external calls. The cell phone does not receive any calls made to the associated office phone. Issue 2.0 May

68 Communication Manager screen details for SIP Bridged Calls Use the Bridged Calls field to determine if bridged call appearances extend to the cell phone. The valid entry definitions are the same as the Mapping Mode field entries. See Figure 15. Valid entries both termination origination none Usage Default is both. For OPS, which SIP often is, you must use none. This enables bridged appearances on OPS phones to work correctly. Configuration considerations for SIP phones The Bridged Calls field should be set to none unless the SIP station supports the Avaya extensions for bridged appearances. If this field has a value other than none, a call to your SIP station goes immediately to coverage without ringing if another SIP phone that is not registered has a bridged appearance on your phone. Avaya 4600-series SIP Telephones will not be able to register in an SES system unless they can obtain the correct SIPDOMAIN setting from the 46XXsettings.txt file. Always configure the SIPDOMAIN setting for the phones in the file named 46XXsettings.txt file and then ensure that the phones transfer settings from the file (via tftp or http) during boot up. The line in the file for this setting is: SET SIPDOM AIN = yoursipdomainname.com When you make a call from a Cisco 7940/7960 phone with the local Caller ID Block feature enabled, the called endpoint still displays your number. To work around this issue, use the Calling Number Block FNE in Communication Manager instead of the local feature in the phone. 66 Administering SES on S8300

69 SIP administrative screens Route Pattern screen The Route Pattern screen defines the route patterns used by Communication Manager. Each route pattern contains a list of trunk groups that can be used to route the call. The maximum number of route patterns and trunk groups depends on the configuration and memory available in your system. AAR analysis and ARS analysis determine which trunks calls use. You can convert an AAR number into an international number, and insert an area code in an AAR number to convert an on-network number to a public network number. Also, when a call directly accesses a local central office (CO), if the long-distance carrier provided by your CO is not available, then Communication Manager can insert the dial access code for an alternative carrier into the digit string. The SIP-related fields are in bold on the screen shown in Figure 16. Administering this screen is not required to make SIP work properly. Figure 16: Route Pattern screen change route-pattern 1 Page 1 of 2 Pattern Number: 1_ Secure SIP? n No. DCS/ Grp. FRL NPA Pfx Hop Toll Del Inserted QSIG IXC No. Mrk Lmt List Dgts Digits Intw 1: n user 2: n user 3: n user 4: n user 5: n user 6: n user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature BAND No. Numbering LAR W Request Dgts Format Subaddress 1: y y y y y n y none both ept outwats-bnd none 2: y y y y y n y rest next 3: y y y y y n y rest rehu 4: y y y y y n y rest none 5: y y y y y n y rest none 6: y y y y y n y rest none Secure SIP You will need to evaluate the setting of the Secure SIP? field in Figure 16 when the end-to-end solution supports the SIPS protocol. The only instance for a y in this field is when the source provider requires a secure SIP protocol. Issue 2.0 May

70 Communication Manager screen details for SIP In most instances, leave this field set to n. Valid entries y/n Usage Specify whether the SIP: or SIPS: prefix will be used, if the call is routed to a SIP trunk preference. If SIP trunks are not specified as SIP: or SIPS:, the call will be routed over whatever trunk is specified. Therefore, to ensure a SIP TLS connection when such a route-pattern is invoked, only SIP trunks should be specified. Default is n. To administer the Secure SIP field, choose the behavior you want from the following table. Original Request-URI Secure SIP? Final Request-URI SIP Y SIPS SIPS N SIPS SIP N SIP SIPS Y SIPS NA non-sip trunk or endpoint Y SIPS NA non-sip trunk or endpoint N SIP 68 Administering SES on S8300

71 SIP administrative screens Signaling Group Page 1 screen The system displays the Signaling Group screen shown in Figure 17 when sip is the Group Type field on this page. Verify and administer all fields on this screen. Figure 17: Signaling Group screen, Page 1 add signaling-group next Page 1 of 1 SIGNALING GROUP Group Number: 4 ETSI CCBS Support: n Group Type: sip Transport Method: tls Co-Resident SES? y Near-end Node Name: procr Far-end Node Name: procr Near-end Listen Port: 6001 Far-end Listen Port: 5061 Far-end Network Region: Far-end Domain: Bypass If IP Threshold Exceeded? n DTMF over IP: rtp-payload Direct IP-IP Audio Connections? y IP Audio Hairpinning? n IMS Enabled? n Session Establishment Timer(min): 3 Group Number This is a display-only field showing the signaling group, as shown in Figure 17. Issue 2.0 May

72 Communication Manager screen details for SIP Group Type This field describes the type of protocol to be used with the signaling group. Select SIP in this field and the screen changes to show only SIP-applicable fields, as shown in Figure 17. Valid entries sip Usage Use for SIP on the Avaya S8300, S8500 series, and S8700 series servers only. Transport Method The screen in Figure 17 displays this field only when the value of the entry in the Group Type field is sip. Make sure that the default tls is selected in this field. No other value is supported. Valid entries tls Usage Default (secure) transport method is TLS. This is the only method supported. Co-resident SES The screen in Figure 17 displays this field only for a SIP signaling group and only if Communication Manager and SES are configured to be Co-Resident. Set the value to y.. Valid entries y/n Usage Default value is n. Set the value to y if this SIP signaling group is used to communicate with SES. When set to y, it automatically populates the Near-end Listen Port field with 6001 which is the same port number that the Co-Resident SES is using to communicate with Communication Manager. Near-end Node Name The screen shown in Figure 17 displays this field when the value of the entry in the Group Type field is either h.323 or sip. 70 Administering SES on S8300

73 SIP administrative screens Additionally, the node name must be administered on the IP Node Names screen and the IP Interfaces screen. Valid entries procr Usage When the Co-resident SES field is set to y, it defaults to procr so that it can communicate with the SES application. Far-end Node Name The screen displays this field when the value of the entry in the Group Type field is either h.323 or sip. The node name must be administered on the IP Node Names screen. See Figure 17. Verify that the value for this field is set to default procr for the Co-Resident SES signaling group. Valid entries procr Usage Describes the far-end node. Near-end Listen Port The screen displays this field when the Group Type field is either h.323 or sip. The Near-end Listen Port field defaults to 6001 when the Co-resident field is set to y. See Figure 17. Valid entries Usage 6001 When the Co-resident SES field is set to y, it automatically populates the Near-end Listen Port field with 6001 which is the same port number that the Co-Resident SES is using to communicate with Communication Manager. Far-end Listen Port The screen displays this field when the Group Type field is either h.323 or sip. See Figure 17. Issue 2.0 May

74 Communication Manager screen details for SIP For SIP, set this to Valid entries Usage 6001 Type the same number as entered in the Near-end Listen Port field, that is, port entry 6001 for SIP over TLS. Far-end Network Region The screen displays this field when the Group Type field is either h.323 or sip. This field shows the number of the network region that is assigned to the far-end of the trunk group. See Figure 17. Valid entries or blank Usage Type the network region number that is assigned to the far end of the trunk group. The region number is used to obtain the codec set used for negotiation of trunk bearer capability. Leave blank to select the region of the near-end node by default. Far-end Domain The screen displays this field only when the value of the entry in the Group Type field is sip. See Figure 17. Valid entries Maximum of 40-character string, or blank Usage Enter the fully qualified domain name or IP address for the destination proxy server. For example, to route SIP calls within your enterprise, enter the domain assigned to your proxy server. For external SIP calling, the domain name could be that of your SIP service provider. If blank, the far-end IP address is used. 72 Administering SES on S8300

75 SIP administrative screens Bypass If IP Threshold Exceeded The screen displays this field when the Group Type field is either h.323 or sip. See Figure 17. Valid entries y/n Usage Type y to automatically remove from service the trunks assigned to this signaling group when IP transport performance falls below limits. These limits are set on the Maintenance-Related System Parameters screen. DTMF over IP The screen displays this field when the value of the entry in the Group Type field is either h.323 or sip. See Figure 17. For SIP, this must be set at the default value of rtp-payload. Valid entries rtp-payload Usage SIP trunks require rtp-payload. Session Establishment Timer This field determines how long the system waits before tearing down a ring no answer call. The default is 3 minutes. See Figure 17. For SIP, the recommendation is to set this to 3 minutes. Valid entries Usage 3 through 120 The time in minutes Communication Manager waits before tearing down a ring no answer call. Direct IP-IP Audio Connections The screen displays this field when the value of the entry in the Group Type field is either h.323 or sip. For SIP trunk groups, this is the value that allows direct audio connections between SIP endpoints. See Figure 17. Issue 2.0 May

76 Communication Manager screen details for SIP For SIP, leave this at the default of y. This value must match the setting for the IP Audio Hairpinning field. Valid entries y/n Usage Type y to save bandwidth resources and improve sound quality of VoIP transmissions for H.323 or SIP trunk groups. IP Audio Hairpinning The screen displays this field when the Group Type field is either h.323 or sip. The IP Audio Hairpinning field entry allows the option for H.323 and SIP-enabled endpoints to be connected through the IP circuit pack in the server or switch, without going through the time division multiplexing (TDM) bus. See Figure 17. For SIP, leave this at the default of y. This value must match the setting for the Direct IP-IP Audio Connections field. Valid entries y/n Usage Type y to enable hairpinning for H.323 or SIP trunk groups. Default is y. Enable Layer 3 Test Set this field to y for SIP. When the signaling group Enable Layer 3 Test field is set to y for a SIP signaling group, the maintenance test invokes a "transmitting the OPTIONS" request. The ping test becomes disabled. Note that if the field is set to n the test shall invoke the existing ping test, and the OPTIONS test shall be disabled. When the signaling group "Enable Layer 3 Test" field is set to "y" for a SIP signaling group and the test fails, the status trunk/trunk-group command for SIP trunks using that signaling group is reported as being in bypass mode. This way, SIP trunk status reports show trunks that are out of service. See Figure Administering SES on S8300

77 SIP administrative screens Station screen, page 1 This screen is not SIP-specific, it must be administered for all installations and so is part of SIP administration. Please verify the fields in bold. Figure 18: Station screen page 1 change station 1014 Page 1 of X STATION Extension: 1014 Lock Messages? n BCC: 0 Type: 46xx Security Code: TN: 1 Port: Coverage Path 1: COR: 1 Name: Coverage Path 2: COS: 1 Hunt-to Station: STATION OPTIONS Loss Group: 2 Personalized Ringing Pattern: 3 Data Module? n Message Lamp Ext: 1014 Speakerphone: 2-way Mute button enabled? y Display Language? English Authentication Required? Model: Expansion Module? Survivable GK Node Name: Survivable COR: Survivable Trunk Dest? Media Complex Ext: IP Softphone? y Remote Office Phone? y IP Video Softphone? IP Video? Type Set the type of station to DCP for 6424 endpoints or IP for 4600 series endpoints. If using 46xx as the Type, you will have minor alarm for these stations. You may ignore these alarms. If you set the Type to DCP, there are some undesirable interactions with the TTI as well as other features. Issue 2.0 May

78 Communication Manager screen details for SIP System Capacity screen The SIP-related fields are in bold on this screen, as shown in Figure 19: Figure 19: System Capacity screen display capacity Page 7 of 12 SYSTEM CAPACITY System Used Available Limit TRUNKS DS1 Circuit Packs: DS1 With Echo Cancellation: ICHT For ISDN Trunks: ISDN CBC Service Selection Trunks: Trunk Groups: Trunk Ports: H.323 Trunks (included in Trunk ports ): Remote Office Trunks (included in Trunk ports ): SBS Trunks (included in Trunk ports ): SIP Trunks(included in Trunk ports ): Note that system trunking capacity varies, based on the server running Communication Manager. See the document Capacities Table for more information. The capacities table document is for Avaya use only and not available to customers. Customers should consult their Avaya representative. SIP Trunks This field shows the number of administered, in use, and available SIP trunks. 76 Administering SES on S8300

79 SIP administrative screens System-Parameters screens This section describes each page of the various System Parameters screens. Valid data entry for each screen follows the screen example. System Parameters Features screen, page 1 on page 77 System Parameters Call Coverage/Call Forwarding screen, page 2 on page 79 System-Parameters Customer-Options screen, page 1 on page 80 System Parameters Customer Options screen, page 2 on page 82 System Parameters Customer Options screen, page 4 on page 83 System Parameters Customer Options screen, page 5 on page 85 System Parameters Features screen, page 1 The Feature-Related System Parameters screen in Figure 20 shows the SIP-related information in bold. Administer other fields as necessary for your system. Issue 2.0 May

80 Communication Manager screen details for SIP Figure 20: System Parameters Feature screen Page 1 change system-parameters features page 1 1-FEATURE-RELATED SYSTEM PARAMETERS Self Station Display Enabled? n Trunk-to-Trunk Transfer? restricted Automatic Callback - No Answer Timeout Interval (rings): 4_ Call Park Timeout Interval (minutes): 10 Off-Premises Tone Detect Timeout Interval (seconds): 20_ AAR/ARS Dial Tone Required? y Music/Tone On Hold: music Port: Music (or Silence) On Transferred Trunk Calls: all DID/Tie/ISDN/SIP InterceptTreatm ent: attd Internal Auto-Answer of Attd-Extended/Transferred Calls? y Automatic Circuit Assurance (ACA) Enabled? n ACA Referral Calls: local ACA Referral Destination: ACA Short Holding Time Originating Extension: ACA Long Holding Time Originating Extension: Abbreviated Dial Programming by Assigned Lists: Auto Abbreviated/Delayed Transition Interval(rings): Protocol for Caller ID Analog Terminals: Bellcore Display Calling Number for Room to Room Caller ID Calls? DID/Tie/ISDN/SIP Intercept Treatment There is only one field in Figure 20 that must be administered for SIP. Set this field to attd. Valid entries Usage Extension of a recorded announcement attd Toll charges do not apply to DID and private network calls routed to an announcement. NOTE: If entering a Multi-Location Dial Plan shortened extension, note the following: When entering a Multi-Location Dial Plan shortened extension in a field designed for announcement extensions, certain administration end validations that are normally performed on announcement extensions are not done, and resultant warnings or submittal denials do not occur. The shortened extensions also do not appear in any display or list that shows announcement extensions. Extra care should be taken to administer the correct type of announcement for the application when assigning shortened extensions. For system security, Avaya recommends entering attd in this field. This routes intercept calls to the attendant and, if the attendant receives several of these, indicates a problem. 78 Administering SES on S8300

81 SIP administrative screens System Parameters Call Coverage/Call Forwarding screen, page 2 The SIP-related fields are in bold on Figure 21. Figure 21: System Parameters Call Coverage/Call Forwarding screen change system-parameters coverage-forwarding page 2 SYSTEM PARAMETERS -- CALL COVERAGE / CALL FORWARDING COVERAGE OF CALLS REDIRECTED OFF-NET (CCRON) Coverage Of Calls Redirected Off-Net Enabled? y Activate Answer Detection (Preserves SBA) On Final CCRON Cvg Point? y Ignore Network Answer Supervision? y Disable call classifier for CCRON over ISDN trunks? n Disable ca lclassifierforccron oversip trunks? n For more details on the other fields on this screen, see the Administering Avaya Aura Communication Manager, Disable call classifier for CCRON over SIP trunks This field Figure 21 directs Communication Manager to dispense with the call classifier on interworked calls and rely on the SIP trunk signalling messages. For SIP, set this field to n. Valid entries y n Usage Use y to disable the call classifier for CCRON calls over interworked trunk facilities. Use n to enable the call classifier for CCRON calls over interworked trunk facilities. Issue 2.0 May

82 Communication Manager screen details for SIP System-Parameters Customer-Options screen, page 1 Administer or verify all fields on the screen shown in Figure 22: to meet the needs of your system. Figure 22: System Parameters Customer Options screen, page 1 display system-parameters customer-options page 1 of 10 OPTIONAL FEATURES Used G3 Version: V12 Location: 1 RFA System ID (SID): 1 Platform: 2 RFA Module ID (MID): 1 Used Platform Maximum Ports: Maximum Stations: Maximum XMOBILE Stations: Maximum Off-PBX Telephones -EC500: 0 0 Maximum Off-PBX Telephones -OPS: (NOTE: You must logoff & login to effect the permission changes.) The Avaya license file controls the fields on this screen. The web-based RFA process generates these license files for customers. The customer views this screen to see how many and what type of off-pbx phones the license supports. Normally, this screen is read only. However, an administrator with init login privileges can type in values that represent a portion of the licensed values. Depending on your login privileges, you can view or edit the fields shown. Maximum Off-PBX Telephones - EC500 Licensing obtained for this feature applies to EC500 and CSP phones. See Figure 22. Maximum Off-PBX Telephones - OPS Licensing for this feature applies to OPS phones, which are SIP phones supporting advanced SIP telephony. See Figure Administering SES on S8300

83 SIP administrative screens Used This column in Figure 22 shows the actual current usage as compared to the system maximum for each field. The Used column is always display only, and indicates the number of the applications that are administered on the Off-PBX Station Mapping screen page 1 on page 59. Issue 2.0 May

84 Communication Manager screen details for SIP System Parameters Customer Options screen, page 2 Figure 23: System Parameters Customer Options screen, page 2 display system-parameters customer-options page 2 of 10 OPTIONAL FEATURES IP PORT CAPACTIES USED Maximum Administrered H.323 Trunks: Maximum Concurrently Registered IP Stations: 50 0 Maximum Administered Remote Office Trunks: 0 0 Maximum Concurrently Registered Remote Office Stations: 0 0 Maximum Concurrently Registered IP econs: 0 0 Maximum Video Capable H.323 Stations: 0 0 Maximum Video Capable IP Softphones: 0 0 Maximum Adm inistered SIP Trunks: Maximum Number of DS1 Boards with Echo Cancellation: 0 0 Maximum TN2501 VAL Boards: 10 0 Maximum G250/G350/G700 CAL Sources: 10 0 Maximum TN2602 VoIP Channels: Maximum Number of Expanded Meet-me Conference Ports: 0 0 (NOTE: You must logoff & login to effect the permission changes.) Maximum Administered SIP Trunks This field in Figure 23 limits the number of SIP trunks administered. 82 Administering SES on S8300

85 SIP administrative screens System Parameters Customer Options screen, page 4 The SIP-related fields on this screen are in bold. Figure 24: System Parameters Customer Options screen, page 4 display system-parameters customer-options Page 4 of 10 OPTIONAL FEATURES Emergency Access to Attendant? y IP Stations? y Enable dadmin Login? y Internet Protocol (IP) PNC? y Enhanced Conferencing? y ISDN Feature Plus? y Enhanced EC500? y ISDN Network Call Redirection? y Enterprise Survivable Server? n Enterprise Wide Licensing? y ISDN-BRI Trunks? y ESS Administration? n Extended Cvg/Fwd Admin? y ISDN PRI? y External Device Alarm Admin? y Local Survivable Processor? y y Malicious Call Trace? y Media Encryption Over IP? y External Device Alarm Admin? y Mode Code for Centralized Voice Mail? y Five Port Networks Max per MCC? y Flexible Billing? y Multifrequency Signaling? y Forced Entry of Account Codes? y Multimedia Appl.Server Interface (MASI)? y Global Call Classification? y Multimedia Call Handling (Basic)? y Hospitality (Basic)? y Multimedia Call Handling (Enhanced)? y Hospitality (G3V3 Enhancements)? y IP Trunks? y IP Attendant Consoles? y (NOTE: You must logoff & login to effect the permission changes.) ISDN PRI Provides Integrated Services Digital Network (ISDN-PRI) software for either a switching-hardware platform migration only or a switching-hardware platform migration in combination with a software release upgrade. Also provides signaling support for H.323 signaling. Set to y for SIP. See Figure 24 above. Enhanced EC500 As shown in Figure 24, set this to y. This setting provides mobile call services including "Anytime Anywhere" accessibility with One Number availability and Origination mapping. Issue 2.0 May

86 Communication Manager screen details for SIP IP Trunks Controls permission to administer H.323 trunks. Must be y for IP trunks. See Figure Administering SES on S8300

87 SIP administrative screens System Parameters Customer Options screen, page 5 The SIP-related fields on this screen are in bold. Figure 25: System Parameters Customer Options screen, page 5 display system-parameters customer-options OPTIONAL FEATURES page 5 of x Multinational Locations? Multiple Level Precedence and Preemption? Multiple Locations? Station and Trunk MSP? n Station as Virtual Extension? n System Management Data Transfer? n Personal Station Access (PSA)? y Posted Messages? n Tenant Partitioning? n PNC Duplication? n Terminal Trans. Init. (TTI)? y Port Network Support? y Time of Day Routing? y Processor and System MSP? n Uniform Dialing Plan? y Private Networking? y Usage Allocation Enhancements? y Processor Ethernet? y TN2501 VAL Maximum Capacity? y Remote Office? n Restrict Call Forward Off Net? y Secondary Data Module? y Wideband Switching? y Wireless? n Private Networking Upgrades PNA or ETN software RTU purchased with earlier systems. Set this to y if you want to enable AAR access codes or ARS access codes 1 and 2 on the Feature Access Codes screen. Issue 2.0 May

88 Communication Manager screen details for SIP Trunk Group screens This section describes each page of the Trunk Group screens. Valid data entry for each screen follows the screen example. Trunk Group screen, Page 1 on page 86 Trunk Group screen, Page 2 on page 94 Trunk Group screen, Page 3 on page 97 Trunk Group screen, Page 1 The system displays the Trunk Group screen shown in Figure 26, when sip is the Group Type on page 1. Verify or administer all the values on this screen. SIP-specific fields are in bold. Figure 26: Trunk Group screen, page 1 change trunk-group 7 Page 1 of 20 TRUNK GROUP Group Number: 7 Group Type: sip CDR Reports: y Group Name: to sip-proxy1 COR: 1 TN: 1 TAC: 999 Direction: two-way Outgoing Display? y Dial Access? n Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n Signaling Group: 1 N um berofm em bers: 10 Group Number In the Trunk Group screen, page 1, this field contains the group number assigned to this group when the trunk group was added. 86 Administering SES on S8300

89 SIP administrative screens Group Type In the Trunk Group screen, page 1, type sip to specify the trunk group as SIP. Tip: Tip: Busy-out the trunk group before you change the group type. Release the trunk group after you make the change. For more information about busying out and releasing trunk groups, see your system s maintenance documentation. Valid entries sip Usage Use SIP trunks to connect a server running Communication Manager to a "home" SIP proxy server. CDR Reports In the Trunk Group screen, page 1, set this field according to the kind of call detail records (CDR) you want to generate. Valid entries y n r (ring-intvl) Usage All outgoing calls on this trunk group generate call detail records. To generate CDRs on incoming trunks, type n in the Record Outgoing Calls Only field on the CDR System Parameters screen. Calls over this trunk group will not generate call detail records. Generate CDR records for both incoming and outgoing calls. In addition, the following ringing interval CDR records are generated: Abandoned calls: The system creates a record with a condition code of H, indicating the time until the call was abandoned. Answered calls: The system creates a record with a condition code of G, indicating the interval from start of ring to answer. Calls to busy stations: The system creates a record with a condition code of I indicating a recorded interval of 0. Issue 2.0 May

90 Communication Manager screen details for SIP Group Name On Trunk Group screen, page 1, set this field to uniquely identify a trunk group. Valid entries 1 to 27 characters Usage Enter a unique name that provides information about the trunk group. Do not use the default entry or the group type (DID, WATS) here. For example, you might use names that identify the vendor and function of the trunk group: USWest Local, Sprint Toll, Level(3) SIP. COR In Trunk Group screen, page 1, the setting for this field depends on your system. Decisions regarding the use of Class of Restriction (COR) and Facility Restriction Levels (FRLs) should be made with an understanding of their implications for allowing or denying calls when AAR/ARS/WCR route patterns are accessed. See Chapter 5 of the Avaya Toll Fraud and Security Handbook, doc ID , for details on using COR and FRLs. Valid entries Usage 0 to 95 Enter a class of restriction (COR). Classes of restriction control access to trunk groups, including trunk-to-trunk transfers. Tip: Tip: Remember that facility restriction levels are assigned to classes of restriction. Even if two trunk groups have classes of restriction that allow a connection, different facility restriction levels may prevent operations such as off-net call forwarding or outgoing calls by remote access users. 88 Administering SES on S8300

91 SIP administrative screens TN On Trunk Group screen, page 1, set this field to assign a trunk to a partition. In the Customer Options screen, if Tenant Partitioning is set to n, this field is present on the Trunk Screen but does not function. Go the Customer Options screen if you suspect incorrect operation. Valid entries Usage 1 to 100 Type a tenant partition number to assign this trunk group to the partition. Enter the digit 1 in this field to assign the trunk to the universal group which can be called by any other TN group. Tip: Tip: Double-check your entry. If you accidentally type an unassigned tenant partition number, the system accepts the entry but no calls go to the trunk group. TAC Type the trunk access code (TAC) for each trunk group. Assign a different TAC to each trunk group. CDR reports use the TAC to identify each trunk group. Each trunk must have a different TAC. This field is on Trunk Group screen, page 1. Valid entries 1- to 4-digit number asterisk (*) and pound sign (#) Usage Type any number that fits the format for trunk access codes or dial access codes defined in your dial plan. NOTE: Although this field is required, trunk groups of type SIP cannot be dialed by using TAC. The TAC you type here only identifies them on CDR reports. * and # may be used as the first character in a TAC. Issue 2.0 May

92 Communication Manager screen details for SIP Direction On Trunk Group screen, page 1, enter the direction of the traffic on this trunk group. The entry in this field affects which timers appear on the Administrable Timers page. The system displays this field for all trunk groups except DID and CPE. Valid entries Usage incoming outgoing two-way Enter two-way for Network Call Redirection. Outgoing Display In Trunk Group screen, page 1, this field allows display telephones to show the name and number of the trunk group used for an outgoing call before the call is connected. This information may be useful to you when you are trying to diagnose trunking problems. Valid entries y n Usage Displays the trunk group name and number. Displays the digits the caller dials. Dial Access In Trunk Group screen, page 1, this field controls whether users can route outgoing calls through an outgoing or two-way trunk group by dialing its trunk access code. Allowing dial access does not interfere with the operation of AAR/ARS. Dial access to SIP trunks is not allowed. Valid entries n Usage The entry n is used for SIP trunks, no others. Prevents users from accessing the trunk group by dialing its access code. Attendants can still select this trunk group with a Trunk Group Select button. This is the default entry. 90 Administering SES on S8300

93 SIP administrative screens Busy Threshold In Trunk Group screen, page 1, this field specifies the threshold limit for the number of trunks that could be simultaneously active. Once the threshold is reached, any additional calls that would result in accessing that trunk group get redirected to the attendant. The attendant takes control of that trunk group and the access to the trunk members. Use this field if you want attendants to control access to outgoing and two-way trunk groups during periods of high use. When the threshold is reached and the warning lamp for that trunk group lights, the attendant can activate trunk group control: internal callers who dial out using a trunk access code will be connected to the attendant, and the attendant can prioritize outgoing calls for the last remaining trunks. Calls handled by AAR and ARS route patterns go out normally. Valid entries The S8700/S8710 supports a maximum of busy hour call completions (BHCC). The S8300 remains at a maximum of 3600 BHCC. Night Service Usage 0 to 255 Type the number of trunks that must be busy in order to light the warning lamp on the Attendant Console. For example, if there are 30 trunks in the group and you want to alert the attendant whenever 25 or more are in use, type 25. In Trunk Group screen, page 1, this field sets the destination for incoming calls when Night Service is in operation. If a Night field on the Group Member Assignments page is administered with a different destination, that entry overrides the group destination for that trunk. CPE, DID, and DIOD trunk groups do not support night service. Tip: Tip: Whenever possible, use a night service destination on your switch to prevent incorrect behavior of some features, even on a DCS network. Valid entries blank An extension number (can be a VDN) attd Usage Leave this field blank if the Trunk Type (in/out) field is not auto. Type the extension of your night service destination. Calls go to the attendant and are recorded as Listed Directory Number (LDN) calls on call detail records. Issue 2.0 May

94 Communication Manager screen details for SIP Queue Length In Trunk Group screen, page 1, outgoing calls can wait in a queue, in the order in which they were made, when all trunks in a trunk group are busy. If you type 0 in this field, callers receive a busy signal when no trunks are available. If you type a higher number, a caller hears a confirmation tone when no trunk is available for the outgoing call. The caller can then hang up and wait. When a trunk becomes available, Communication Manager calls the extension that placed the original call. The caller hears three short, quick rings. The caller does not need to do anything but pick up the handset and wait. Communication Manager remembers the number the caller dialed and automatically completes the call. The screen displays this field when the Direction field on the screen is set to outgoing or two-way. Valid entries Usage 0 Type 0 for DCS trunks. 1 through 100 Type the number of outgoing calls that you want to be held waiting when all trunks are busy. Service Type In Trunk Group screen, page 1, the Service Type field indicates the service to which this trunk group is dedicated. A listing of predefined entries is shown below. In addition to the Services/ Features listed in this table, any user-defined Facility Type of 0 (feature) or 1 (service) on the Network Facilities screen is allowed. For SIP trunks, only public-ntwrk and tie are valid. Valid entries public-ntwrk tie Usage Public network calls. It is the equivalent of CO (outgoing), DID, or DIOD trunk groups. If Service Type is public-ntwrk and the trunk is not a SIP trunk, then Dial Access can be set to y. Tie trunks. General purpose. This setting is used for systems inside the Avaya network, not for customers. 92 Administering SES on S8300

95 SIP administrative screens Auth Code In Trunk Group screen, page 1, this field affects the level of security for incoming and outgoing calls on the Communication Manager server. The system displays this field if the Direction field is incoming or two-way. The Auth Code field can only be y if the Authorization Codes field is y on the System Parameters Feature screen Page 1 on page 78. Valid entries y or n Usage Type y to require callers to enter an authorization code in order to tandem a call through an AAR or ARS route pattern. The code will be required even if the facility restriction level of the incoming trunk group is normally sufficient to send the call out over the route pattern. Signaling Group In Trunk Group screen, page 1, the screen displays this field only when the value of the entry in the Group Type field is sip. The value here must be set as in the previous signaling group screen, in this example, 1. Valid entries 1 through 650 Usage Type the number of the SIP signaling group associated with this trunk group on the Signaling Group Page 1 screen on page 69, Group Number field. This field restricts calling, and requires a code for users below the FRL level for incoming and outgoing calls. Number of Members In Trunk Group screen, page 1, the value here must be less than or equal to the maximum administered number for SIP trunks on the System Parameters Custom Options screen. The screen displays this field only when the value of the entry in the Group Type field is sip. Valid entries 1 through 255 Usage Type the number of SIP trunks that are members of the trunk group. All members of a SIP trunk group will have the same characteristics. NOTE: Member pages for SIP trunk groups are completed automatically based on this entry and are not individually administrable. Issue 2.0 May

96 Communication Manager screen details for SIP Trunk Group screen, Page 2 Figure 27: Trunk Group screen, page 2 change trunk-group 7 Page 2 of 20 TRUNK PARAMETERS UNICODE Name? y TRUNK GROUP Redirect on OPTIM failure: 5000 Digital Loss Group: 18 Preferred Minimum Session Refresh Interval (sec): 1800 UNICODE Name This in Trunk Group screen, page 2 field determines which table of names to use to display the name, the legacy or the UTF-8 character table. Valid entries y or n Usage Type n to use the table with legacy names. Type y to use the table with UTF-8 format if your system might contain Asian language names. Note that fifteen UTF-8 characters can take up to 45 bytes. Also, legacy names support Roman, Cyrillic, Ukrainian, and Katakana characters. Redirect on OPTIM failure In Trunk Group screen, page 2, this field is a timer that determines how long to wait for OPTIM to intercede before the call is redirected. Redirect on OPTIM failure is sometimes known as ROOF. Valid entries 250 to milliseconds Usage See EC500 documents for the SIP-related uses of OPTIM, that is, OPS. 94 Administering SES on S8300

97 SIP administrative screens Digital Loss Group In Trunk Group screen, page 2, this field determines which administered 2-party row in the loss plan applies to this trunk group if the call is carried over a digital signaling port in the trunk group. Valid entries Usage 1 to 19 Shows the index into the loss plan and tone plan. Issue 2.0 May

98 Communication Manager screen details for SIP Preferred Minimum Session Refresh Interval (sec) This field sets the session refresh timer value of a SIP session. The timer starts when a SIP session is established. Communication Manager then sends a session refresh request as a Re-INVITE or UPDATE after every timer interval. In this way, an ongoing session is maintained. For SIP, set this to Valid entries Usage 90 to 1800 Default 120 seconds. Recommendation for SIP is 1800 seconds. The interval for the session refresh requests is determined through a negotiation mechanism. If a session refresh request is not received before the interval passes, the session terminates. Both endpoints send a BYE, and call state aware proxies can remove any state for the call. 96 Administering SES on S8300

99 SIP administrative screens Trunk Group screen, Page 3 The system displays this screen of the Trunk Group screen, the Trunk Features screen, shown in Figure 28 when sip is the Group Type on Trunk Group screen page 1. Verify or administer all of the values on this screen for SIP. Figure 28: Trunk Group screen, page 3 change trunk-group 7 Page 3 of 20 TRUNK FEATURES ACA Assignment? n Measured: none Maintenance Tests? y N um bering Form at: public Prepend '+' to Calling Number? n Replace Unavailable Numbers? n Show ANSW ERED BY on Display field? y ACA Assignment In Trunk Group screen, page 3, this field may have a y or n entry. Valid entries y/n Usage Type y if you want Automatic Circuit Assurance (ACA) measurements to be taken for this trunk group. If you set this field to y, complete the Service Type field.the default entry for SIP is n. Issue 2.0 May

100 Communication Manager screen details for SIP Measured In Trunk Group screen, page 3, this field determines if the system will transmit data for this trunk group to the Call Management System (CMS). You cannot use internal and both unless either the BCMS (Basic Call Management System) or the Service Type field is y on the System-Parameters Customer-Options screen. If the ATM field is set to y on the System-Parameters Customer-Options screen, this field accepts only internal or none as values. If this field contains a value other than internal or none when ATM is y, the screen displays none for the field value. Valid entries internal external both none Usage Type internal if the data can be sent to the BCMS, the VuStats data display, or both. Type external to send the data to the CMS. Type both to collect data internally and to send it to the Communication Manager. Type none if trunk group measurement reports are not required. NOTE: This is the default for SIP trunk groups. Maintenance Tests In Trunk Group screen, page 3, the screen displays this field only when the value of the Group Type field is aplt, isdn, sip, or tie. Valid entries y/n Usage Type y (the default) to run maintenance tests hourly on this trunk group. One or more trunk members must be administered as SIP for this entry to be saved. 98 Administering SES on S8300

101 SIP administrative screens Numbering Format In Trunk Group screen, page 3, the Numbering Format field specifies the encoding of Numbering Plan Indicator for identification purposes in the Calling Number, the Connected Number IEs or both, and in the QSIG Party Number. Valid entries are public, unknown, private, and unk-pvt. Valid entries Public Usage Indicates that the number plan according to CCITT Recommendation E.164 is used and that the Type of Number is national. This is the default entry for SIP trunks. Unknown Private unk-pvt Indicates that the Numbering Plan Indicator is unknown and that the Type of Number is unknown. Indicates the Numbering Plan Indicator is PNP and the Type of Number is determined from the Private-Numbering screen. Also determines the Type of Number from the Private-Numbering screen, but the Numbering Plan Indicator is unknown. Prepend '+' to Calling Number? In the Trunk Group screen, page 3, set this field to y if you want to add a plus sign (+) to the beginning of a number to accommodate international calls. Replace Unavailable Numbers The system displays this field in the Trunk Group screen, page 3 only when the Group Type field is isdn or sip. This field dictates whether to replace unavailable numbers with administrable strings for incoming and outgoing calls assigned to the specified trunk group. Administrable strings are located in the System Parameters Features screen, page 1 screen. This field applies to BRI/PRI and SIP trunks. Valid entries y/n Usage Type y to replace the display of an unavailable number with a phrase, for example, Private Caller. The system replaces unavailable numbers regardless of the service type of the trunk. The default for SIP trunks is n. Issue 2.0 May

102 Communication Manager screen details for SIP Show ANSWERED BY on Display field If the outgoing call is over a trunk that might be redirected, some customers would prefer not to see the display message Answered by, but still want to see the connected party number. See Trunk Group screen, page 3. Valid entries y/n Usage Type y to show ANSWERED BY string in the proper language on originator s display when the connected party name is not available. The default for SIP trunks is y. 100 Administering SES on S8300

103 SIP administrative screens Trunk Group screen, page 4 When the Group Type is sip, the system displays the Protocol Variations screen. The system displays this screen for SIP trunks only. For SIP, set this field to y for a particular trunk only if a device or network connected to that SIP trunk requires the user as phone parameter. Consider the situation of a public network trunking connection to an outside or third party. Set this to y for a customer taking the trunk out to a third party. Figure 29: Protocol Variations screen display trunk-group 7 Page 4 of 20 PROTOCOL VARIATIONS Mark Users as Phone? n Mark Users as Phone Valid entries n y Usage Default. URIs in call control signaling messages originated at the gateway are encoded with the "user=phone" parameter. Note no subscription messages are encoded with the "user=phone" parameter, even when the field is set to y. Issue 2.0 May

104 Communication Manager screen details for SIP Important: SIP device as an OPS extension Note: Note: SES may use the 46xxsettings.txt file for stations other than 46xx phones, even if you have 9620 SIP or 9630 SIP, or the 16cc (Call Center) series, phones. If a 46xx or 96xx SIP IP telephone is configured as an OPS extension, then the number of call appearances must be configured in all of these following areas: 1. In the 46xxsettings.txt (or 96xxsettings.txt, if applicable) text file, or for the DHCP scope option: PHNNUMOFSA must be set to the number of call appearances. 2. Station screen page 2: Set restrict last appearance = n (default = y). 3. Station screen, page 3: You must add whatever number of additional button assignments as 'call appearances' to match the value of PHNNUMOFSA. 4. Off-PBX Station Mapping screen page 2: the call limit must equal the number of call appearances set in PHNNUMOFSA. 102 Administering SES on S8300

105 Chapter 3: Administering web interface This section describes in detail the use and meaning of the screens in the Master Administration web interface. This topic is divided into groups, based on the main headings in the menu at the left of the main window, starting with the screens you encounter at your first login. Top Screens on page 104 Setup screens on page 105 Core Router screens on page 122 User screens on page 125 Extensions tasks on page 156 Add Host screen on page 111 (if co-resident CM/SES 5.0 is to be used as a home server, you must add the standalone SES Edge 5.0 server for your enterprise as another host). Add Media Server screen on page 119 Trusted Certificate screens on page 268 System Logs screen on page 214 Publication Note Most of the screen examples in this document were taken from a distributed SES configuration featuring a simplex Edge 5.2 server and two simplex Home servers. If your installation is any other type of configuration, the screens may differ slightly from those shown in the examples. Figures may also be taken from other hardware configurations, as noted in the discussion. Issue 2.0 May

106 Administering web interface Top Screens These screens are the first ones you use when you log on. Logon screen on page 104 Logon screen field descriptions on page 104 System Management Interface on page 105 Logon screen To display the Logon screen to administer a co-resident system running Avaya Communication Manager and SIP Enablement Services, enter this URL: address of CM server_/ And for SIP Personal Information Manager (PIM), the application that an end user views, enter: address of CM server_/user To display the Logon screen for a standalone system, enter this URL: address of SES server_/admin The URL for the SIP PIM application that an end user views on a standalone SES server is: address of SES server_/user Logon screen field descriptions Logon ID Enter the user name for your administrative account. After you enter this and press the Enter key or select Logon, the screen refreshes to display the Password field. Originally, the craft account should be used for the initial administrative setup and after remastering the system. If you are logging in to a co-resident system, use the ID/Password combination for administering Avaya Communication Manager software. Password Enter your administrative account s password, 6 to 12 characters in length, at least 1 of which is alphabetic and at least 1 numeric. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 104 Administering SES on the Avaya S8300 Server

107 Setup screens After completing both fields, select Logon or press Enter. System Management Interface The system displays the System Management Interface after a successful login. Do one of the following: To access SIP Enablement Services: On the System Management Interface, select Administration > SIP Enablement Services. To access the Server (Maintenance): On the System Management Interface, select Administration > Server (Maintenance). System Management Interface menu description SIP Enablement Services The SIP Enablement Services interfaces provide screens for initial server setup, user contact database changes, and other activities related to servers running Avaya Communication Manager and/or SIP Enablement Services. Server (Maintenance) Maintenance activities include server status and diagnostics, alarms and traps, and remote access security. Note that many Maintenance web pages for a new Avaya S8300C server running Communication Manager 5.2 and SES 5.2 concurrently are shared by the software. Setup screens When installing or updating, the setup screens provide the needed interface. Once the system is set up, these screens are available individually, but not displayed by the system as a setup task. The setup screens consist of these: Setup screen on page 106 Edit System Properties screen on page 108 Add Host screen on page 111 Edit Default User Profile screen on page 117 Add Media Server screen on page 119 Issue 2.0 May

108 Administering web interface Setup Master Admin screen This screen lets you specify if the machine you are setting up is an SES edge server or and SES home server. Select the top radio button for an edge server, primary or backup. Select the second radio button if you are setting up a home server, either primary or backup. The IP address you type here is the IP address of the edge server that acts as parent to this home server. If you have a duplexed edge server, use the logical IP address. Setup screen The Setup screens contain links to the screens necessary to initially configure servers. These screens provide different choices, depending on which required tasks have been completed. Setup SIP Domain screen Before filling in the Setup screens, you need to know IP addresses, machine names, and the answers given to the prompts by the install script. Setup screen field descriptions Setup SIP Domain Select this link to go to the Edit System Properties screen. You must use this screen to specify the domain to assign to this SES configuration before you may proceed with any other setup options. After specifying the SIP domain, you must restart the proxy service on each SIP proxy host computer in your enterprise (for example, using the Maintenance web interface) before any newly specified domains are recognized system-wide. The next Setup screen lets you set up your host. Setup Hosts After setting up the domain, select this link to create a host computer entry for the first edge or home/edge server in your enterprise. Recall that a host is either a home, an edge, or a combined home/edge. The link on this screen directs you to the Add Host screen. Note: Note: You will not be able to continue with administration and configuration until the Set Up Host and Setup SIP Domain options both have been completed. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 106 Administering SES on the Avaya S8300 Server

109 Setup screens Setup Default User Profile and Media Servers The next Setup screen typically provide two other choices. Completing these screens is optional but recommended before continuing with administering SIP endpoints or associated telephone numbers (extensions in Avaya Communication Manager). Be aware that you may not add user information or extensions in SES until the next two setup options are completed. Setup Default User Profile The system displays this link after you have added one edge or home/edge server with Setup Hosts. Now, you may select this link to go to the Edit Default User Profile screen, or first you may choose to set up your system s servers running Communication Manager. Information for user profiles now accepts UTF-8 encodings to accommodate multibyte languages. You may input Shift_JIS (SJIS) as well. Whether the user s browser sends UTF-8 or SJIS is dependent upon the web browser s language setting. Setup Media Servers This system makes this link available after you have added any type of host using the Setup Hosts link. Select this link to go to the Add Media Server screen where you create one or more entries for your network s media servers running Avaya Communication Manager. Media gateways must also be up-to-date. Tip: Tip: You may not add user information such as end user contacts, or media server extensions, for example, telephone numbers or handles, to the database until these setup options have been completed. Issue 2.0 May

110 Administering web interface Edit System Properties screen The Edit System Properties screen defines the server s type and domain. Edit System Properties screen field descriptions SES Version This field displays the major and minor release number, R5.0-00, and the current load and build number,.819.2, of the Avaya software that is running on this SES server. System Configuration Identifies this SES server as being a simplex, standalone machines, or as duplex, redundant machines. This read-only field does not indicate the server s role of primary or backup. Host Type Identifies this SES server as a home, edge, or home/edge type. This read-only field does not indicate the server s role of primary or backup. SIP Domain Enter a domain name to assign to this SIP Enablement Services configuration. Name your domain with lowercase alphanumeric characters and dashes. Do not use any upper case or special characters with the exception of the dash. Note: Note: Updates to system-wide properties like the SIP Domain field require you to restart the proxy service on each SES host computer in the system. Otherwise, the domain name updates are not recognized. SIP License Host Enter the host name, the fully qualified domain name, or IP address of the SES server that is running the WebLM application and has the associated license file installed. This entry shows the IP address of the licence host in this field. Note that, for duplex-server configurations, this is the physical, fully qualified domain name or IP address of the SES system running WebLM, not the virtual address of the duplex pair. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 108 Administering SES on the Avaya S8300 Server

111 Setup screens Management System Access Login This is the login for the server that performs core-routing functions for an Communication Manager Branch Edition 1.x network. You must first specify the login for Communication Manager Branch Edition Central Manager in Communication Manager Branch Edition on the SES Edge server, then specify it here. The logins must match exactly. Management System Access Password This is the password for the server that performs core-routing functions for an Communication Manager Branch Edition 1.x network. You must first specify the password for Communication Manager Branch Edition Central Manager in Communication Manager Branch Edition on the SES Edge server, then specify it here. The passwords must match exactly. DiffServ/TOS Parameters The Call Control PHB Value defines the PHB (per hop behavior) value for signaling used by the intermediary routers in the network order. These values are used to expedite the message flow through the network. Improved flow reduces unnecessary delays and time outs. The default value for this field is '46' which is the 'expedite forwarding' value, normally used for real-time RTP traffic. The range is Parameters The Priority Value is associated with the priority tag in the ethernet header and is used to prioritize ethernet layer messages. Avaya default is 6. Range is 0-7 DB Log Level Setting the DB Log Level lets the administrator set a preference for database access logging. The information will be provided in /var/log/ecs/commandhistory. Logging levels will be added to the System Properties form. Logging levels will be a pull down menu with the following choices: Choice Stored in data base What is logged Disabled off No logging of database access. This is the default. Issue 2.0 May

112 Administering web interface Log Both Before And After Values both Log both the original values in the database and new or changed values. (continued on next page) Log After Values Only new Log the new or changed values only. Log No Values none Log the database access but, no values. Network Properties Lists the Local IP address and Local Name for this physical server, as well as the Logical IP and Logical Name for the node. In a simplex configuration, Local and Logical properties are the same. On a server that is one of a duplex pair, its Local properties differ from its Logical ones. However, the Logical properties are the same for both of the servers of a duplex pair. The information displayed was provided at install time. The Gateway IP Address field shows the IP address of the gateway that supports this domain. Redundant Properties The Management Device field reflects the SAMP that provides access to a standalone machine. In this screen, the term redundant properties has nothing to do with redundant, backup, duplex, high availability, or failover meanings for other Avaya servers. The remote maintenance board is a SAMP, for S8500B and S8500C server hardware. Select Update to submit the updated information on this host. Then, all the hosts should be updated. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 110 Administering SES on the Avaya S8300 Server

113 Setup screens Add Host screen A host is an SES home or edge server, or a combined home/edge server. If your system architecture is a home/edge, use this screen to add the home/edge server. If your system architecture uses a simplex home/edge architecture, you cannot add a host of any kind in addition to the home/edge server, and are denied access to this screen. If your system architecture is a single edge server with one or more home servers, use this screen to add the edge server at install time, and then add each home server. Specify the type, edge or home, in the Host Type field. Add Host screen field descriptions Host IP Address Enter the IP address for this host server, either home, edge, or combined home/edge. Use the dotted decimal notation to enter IP addresses (for example, ). Profile Service Password This password is for permissions between SES hosts, that is, home server(s) and edge. Note that the Profile Service Password is not used by users or administrators. Rather, it is a password that is used by internal software components for secure communication between SES servers and the master administration system. The Profile Service Password must be unique for each administered host. Host Type If the server is an S8300C running SES co-resident with Avaya Communication Manager software, then the Host Type drop-down list contains the following choices: CM combined home-edge this server functions as both your enterprise s SES Edge 5.0 and Home proxies as well as the Communication Manager server. Note that no additional SIP proxy servers or Communication Manager servers may exist within this architecture. CM home This option appears only after a standalone SES Edge 5.0 server has been added. Select this option if the server you are adding now is a co-resident SES Home and Communication Manager server. Issue 2.0 May

114 Administering web interface Parent Select one of the following from the drop-down list to indicate the server this host uses: Listen Protocols Select NONE if you selected home/edge for the server s Host Type above. Any edge or combination home/edge server has no parent, as this is a single-server configuration. Select HOST NAME or IP if you selected CM home for the server s Host Type above. The names of the edge servers for all your enterprise s domains are listed. Select the correct Edge 5.0 server as Parent of this SIP (home) proxy server. At a minimum, select TLS for the Listen Protocol. You may select UDP or TCP for other uses, but Avaya Communication Manager supports only the TLS link protocol for SIP trunking. Note that the protocol you select for linking must also be selected here for listening. At a minimum, you must select the protocol you selected as the Link Protocol, below, although you may want to select additional protocols only for listening but not for linking. When you add a host, all three protocols are selected for listening. There is little reason to change this default. Link Protocols This field refers to the trunk signaling between SES and Avaya Communication Manager. Typically, the selection here matches the Signal Group value on Communication Manager. The only link protocol that is supported for SIP trunking with Avaya Communication Manager is TLS. For third-party proxy servers, you may select to link to SES with TLS, TCP, or UDP, although UDP is untested at this time. You must also select the Link Protocol as a Listen Protocol, above. You may want to select additional listen protocols. There is no special reason to change the default. Access Control Policy This setting correlates to the Watcher feature on the end user s SIP PIM web interface. Accept the default policy of Deny All, or select Allow All to change this default policy and show the presence of SIP users on this server. The system displays the presence of SIP users on the Watchers screen in the SIP PIM web interface to Personal Profile Manager in SES. The administrator may set a system policy to specify that all users on the system default to a blocked state, where users must authorize each other to view each other s presence. The end SIP user may override this setting. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 112 Administering SES on the Avaya S8300 Server

115 Setup screens This administration policy is on a per-node basis and may be administered for each home node in the network. Emergency Contacts Policy Enable this field to allow unauthenticated calls for the emergency contact named for this host. If you allow emergency contacts, emergency calls can come to this host. If you disable this field, unauthenticated calls to the emergency URI will be dropped. Set up emergency URIs for the end user with the Add Emergency Contact screen. This feature is supported on single-server co-resident configurations with a home/edge SES. Minimum Registration (seconds) Enter a whole number of seconds, 900 through 59,940, that the SIP server should consider as the minimum acceptable duration when a SIP client registers. If no value is entered, the default of 900 seconds will be used. Registration Expiration Timer (seconds) The value for Registration Expiration Timer determines how long a SIP endpoint should register for and renew its registration. This value is not enforced by the registrar, but downloaded by an endpoint through PPM if they support it. The value for Minimum Registration (seconds) is enforced by the SIP registrar and it will not allow new registrations prior to that minimum registration time.the minimum registration timer is a SIP protocol feature that prevents endpoints from registering too quickly. Such a registration may be in error. The default is 3,600 seconds, or 60 minutes. This field affects all the users on this host. Line Reservation Timer This value configures the maximum amount of time that an end user is allotted to dial a number after going off-hook. The default for this field is 30 seconds. The range is 30 to 240 seconds. Outbound Routing Allowed From Select Internal or External or both to specify whether SIP traffic can be routed only from endpoints internal to this server s domain, or also from those external to it. Issue 2.0 May

116 Administering web interface Outbound Proxy Enter the host name of the server within your enterprise that should manage SIP traffic bound for domains external to this server s enterprise domain. For example, on a co-resident home server, this would be the host name of the SES Edge 5.0 server named as Parent of that home. On a combined home/edge (or a standalone edge proxy), this entry might be a remote host, a service provider, ar an alternate edge server. For a home server, define an outbound proxy only if a host other than the enterprise SES Edge will route outbound calls. Outbound Port Enter the number of the port ( ) on the outbound proxy server specified above that should manage SIP traffic bound for domains external to this server s domain. Use port 5060 if the entry for Outbound Transport is UDP or TCP, and port number 5061 if it is TLS. On a server that is running SES concurrently with Communication Manager, verify that the port number you choose here for SES 5.0 is not assigned to other processes in Communication Manager 5.0. Select the transport protocol of the outbound proxy server that should manage SIP traffic bound for domains external to this server s domain. The use of TLS is a best practice. Outbound Direct Domains Users do not need to be under the same edge server to take advantage of hairpinning/shuffling and the absence of map addresses. For example, a user in New York can call another user in Paris, and the call is directly routed to the trusted domain in Paris. Set those trusted domains for the host, home, edge, or home/edge, here. Use this area to list those domains for which traffic may completely bypass the Outbound Proxy server specified above. Separate entries in the list with commas, or with a white space followed by a new line, after each domain. Select the Add button to add a host with the properties you ve entered. If you have added an edge proxy, then selecting Continue at the next screen returns you to the Add Host screen on page 111 until you add at least one home proxy server as well. If you add a combined home/ edge proxy, then you return to the Setup screen on page 106 if you are initially installing hosts. Default Ringer Volume This field sets the ringer setting for the stations bridged appearance buttons. The values in this field are not related to the ringer setting configuration in Communications Manager, nor does it reflect the Communication Manager s settings. The default is 5. The range is 1 to 10. This field affects supported SIP endpoint users on this host, such as the Toshiba Business Phone SP-1020A and Avaya one-x Deskphone SIP R2. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 114 Administering SES on the Avaya S8300 Server

117 Setup screens Default Ringer Cadence The value in this field sets the speed of the default ring tone for supported SIP endpoints, such as the SP-1020A. The default is 2, and the range is 1 (slowest cadence) to 3 (fastest cadence). Default Receiver Volume This field sets the volume in the handset, rather than the speaker, for supported SIP endpoints, such as the Toshiba SP-1020A. The default is 5, and the range is 1 (lowest) to 10 (highest). Default Speaker Volume This field sets the volume on the speaker, rather than the handset, for supported SIP endpoints, such as the Toshiba SP-1020A. The default is 5, and the range is 1 (lowest) to 10 (highest). Issue 2.0 May

118 Administering web interface VMM Voice Over IP Monitoring Manager (VMM) is a voice over IP (VoIP) quality of service (QoS) monitoring tool. This feature is available only on supported SIP endpoints, such as the Toshiba SP-1020A. VMM information is taken from the VMM server. SES requires the server name, port address, and how frequently an end point should report back to the VMM Server. See the VMM document titled Voice Over IP Monitoring Manager User Guide, This field is specific to the Toshiba solution and only work with supported phone types. VMM Server Address Address of the VMM server. This field is specific to the Toshiba solution and only work with supported phone types. VMM Server Port Port number for the VMM server s address.the range is 1 through 65,535, and the default is This field is specific to the Toshiba solution and only work with supported phone types. VMM Report Period The report period is in seconds, and reflects how often an endpoint should report back to the VMM server. Reports show jitter, round trip time, and packet loss. This may help in solving troubles on the IP network. The default value is 5 seconds, and the range is 5-30 seconds. This field is specific to the Toshiba solution and only work with supported phone types. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 116 Administering SES on the Avaya S8300 Server

119 Setup screens Edit Default User Profile screen This screen lets you enter a common address for all user profiles on a SIP system. You will not have to type it in repeatedly for each user later. The system displays the data you enter here on an individual user s profile. You can add to or change it there to be more specific. There is exactly one default user profile on the entire system. The default user profile data resides on the edge server. A specific user's profile is then pushed to their specific home. Information for user profiles now accepts UTF-8 encodings to accommodate multibyte languages such as Japanese. You may input Shift_JIS (SJIS) as well. Whether the browser sends UTF-8 or SJIS is dependent upon the web browser s language setting. Edit Default User Profile screen field descriptions Host From the alphabetized drop-down list of names, select the home server for whose users this location information will become the default entries. The host name selected by default in the list is either the first home server alphabetically or the single home/edge server. Address 1, Address 2 This is the first line and second line of the default address for users. You may input Shift_JIS (SJIS) characters as well. Whether the browser sends UTF-8 or SJIS depends upon the browser s language setting. The name will be assigned to the speed dial button for this contact. In Japanese, this name string uses Kanji characters. (Contrast this with Alias.) City State Enter the name of the city or town of the default address for users. You may use alphanumeric characters. Enter the name of the state or province of the default address for. You may use alphanumeric characters. Issue 2.0 May

120 Administering web interface Country ZIP Enter the name of the country of the default address for users. You may use alphanumeric characters. Enter the ZIP or postal code of the default address for users. You may use only numeric characters. Edit Default User Profile screen commands Update Select Update to submit the information on this screen to the server s database. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 118 Administering SES on the Avaya S8300 Server

121 Setup screens Add Media Server screen This screen assigns a home server to each interface for Avaya Communication Manager. Depending on your configuration and features used, SES may employ two server links: SIP trunk this is a SIP signaling link between SES and Communication Manager. Administration interface If an SES Edge 5.0 server needs to obtain configuration information from co-resident Communication Manager 5.0 running with an SES home, it will use the link to the specified Media Server Admin Address. These two links may be to the same IP address. If so, Avaya server software services the two different protocols on different ports. Select Add to submit the Communication Manager server interface with the properties entered to the database for this SES home server. Add Media Server screen field descriptions Media Server Interface Name Host Enter the network node name in alphanumeric characters for the Communication Manager server s CLAN or processor CLAN IP interface. You may want to use the same name you used for this server on the IP Node Names screen in Avaya Communication Manager. Each server interface s name must be unique within the SIP domain. Refer to Administering Network Connectivity on Avaya Aura Communication Manager, If the server has more than one CLAN interface used for SIP trunking to this SES, then, you must add each CLAN interface as a unique server. In this screen, The Host field displays the name of the home server for whose users the server specified above is the default. SIP Trunk Link Type Select TLS for the SIP link between the server interface and this host. This is the default protocol selected for all servers. Issue 2.0 May

122 Administering web interface SIP Trunk IP Address This field holds the IP address for the media server s CLAN or processor ethernet interface that terminates the SIP link from SES. The IP address must be specified as dotted IP notation, that is, a 32-bit address comprising four 8-bit octets in the form xxx.xxx.xxx.xxx where xxx is a value in the range of If DNS is available within the SIP domain, enter the fully qualified domain name of the media server s CLAN or processor CLAN. SIP Trunk Port The SIP Trunk Port field is for SES/Communication Manager 5.0 co-resident installations only and allows you to configure SES 5.0 with the same port number configured in the Avaya Communication Manager signaling group field. When you configure the signaling group in Communication Manager 5.0, there is a co-resident check box, the selection of which will default the port to This value must match in SES 5.0. It is not critical that the matching ports are the default of 6001, but that they do match. The signaling group that Communication Manager software uses to talk with co-resident SES software cannot have a near-end port of 5061 because SES owns that port. Media Server Admin Address This field holds the fully qualified domain name or IP address (in dotted notation) for access to the administration service on the server running Avaya Communication Manager 5.0; this administration service is the System Access Terminal (SAT), so this address would be the address of procr or that of a CLAN interface that allows SAT administration service. If a CLAN in Communication Manager is used, then SAT service on port 5023 must be enabled on that CLAN. If any SES users have associated extensions in Communication Manager, SES obtains certain configuration information from Communication Manager over this interface. Media Server Admin Login Enter the login used to access the Avaya Communication Manager server s administration service, for example, Communication Manager s SAT. Your login on Communication Manager should be of type customer and service level superuser, at a minimum. If you have any configuration other than a single, combined home/edge SES co-resident server, then phones will not work correctly unless you provision an Avaya Communication Manager login and password for the server at the above address. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 120 Administering SES on the Avaya S8300 Server

123 Setup screens Media Server Admin Password/ Password Confirm This is the password for the Media Server Admin Login described above, that is the SAT password. If you have any configuration other than a single combined home/edge co-resident server, then phones will not work correctly unless you provision an Avaya Communication Manager login and password. SMS Connection Type This field defines the type of connection used administratively to obtain provisioned data from PPM on a standalone SES Edge 5.0 server and any server running Communication Manager. Choose SSH for a secure connection. Choose Not Available if you do not want SES 5.0 to communicate with Avaya Communication Manager, perhaps for troubleshooting purposes. Issue 2.0 May

124 Administering web interface Core Router screens The Core Router screens menu option appears depending on your SES configuration. It is a component of a Communication Manager Branch Edition solution, but is not used with co-resident SES 5.0 servers. The core router feature in SES 5.0 enables a branch office to call another branch by going through the SES Edge server. In order to use the core router feature of SES, the Management System Access Login field and Management System Access password field on the Edit System Properties page must be administered to match those administered for the Edge server of the Avaya Distributed Office. In SES, the screens used to set up the core router feature are these: List Prefix Maps screen List Handle Maps screen Prefix maps are used with Avaya Distributed Office, and correlate branch office prefixes with server IP addresses. Handle maps are used with Avaya Distributed Office, and show the IM handles of branch employees. List Prefix Maps screen The Prefix Maps screen shows, for Avaya Distributed Office, the correlation between branch office prefixes and the IP addresses of the servers at the branch office. The information here is a reflection administration performed in the Avaya Distributed Office. The List Prefix Maps screen is read only in SES.. List Prefix Maps screen field descriptions Branch Prefix Branch Prefix is the prefix used to uniquely identify each Communication Manager Branch Edition platform, including each optional SIP Server in the main or headquarters location. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 122 Administering SES on the Avaya S8300 Server

125 Core Router screens Branch Address Branch Address is the IP address of the Communication Manager Branch Edition platform at each location. Core Router Core Router is the IP address of the SES edge server performing branch to core routing. Total Length Total Length is the digit length of the assigned branch prefix plus extension. Issue 2.0 May

126 Administering web interface List Handle Maps screen This screen is a read-only summary page listing the current alphanumeric handles associated with users at Communication Manager Branch Edition branch locations. This screen is provided to SES by Avaya Distributed Office Central Manager. Fields on this list screen are read-only; they may be edited using the appropriate screen(s) in Communication Manager Branch Edition Central Manager. List Handle Maps screen field descriptions Branch Prefix Branch Prefix is the string of digits uniquely identifying each Communication Manager Branch Edition platform, including each optional SIP Server (home) in the main or headquarters location) IM Handle IM Handle is the alphanumeric IM handle for each branch user. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 124 Administering SES on the Avaya S8300 Server

127 User screens User screens The User screens permit customizing aspects of the system for each user. List Users screen To use this screen, check a box next to a user ID, select an action from the task drop-down menu, select Submit. You can view the screen only from the edge server s Master Administrator interface. List Users screen field descriptions User ID Host Name Lists the IDs of administered users in the SES database. This is the name of the home server for this user. A user s host is a home server or a combined home/edge server. either of which may be a co-resident CM/SES 5.0 server. This is the name of as many as 64 UTF-8 characters associated with this User ID and Handle in the user database. You may input Shift_JIS (SJIS) as well. Whether the browser sends UTF-8 or SJIS is dependent upon the browser s language setting. The name will be assigned to the speed dial button for this contact. In Japanese, this name string uses Kanji characters. (Contrast this with Alias.) List Users screen commands All of the tasks in this drop-down menu reflect data that the user sees on the SIP PIM interface. You may select any of the tasks in the Task field. Issue 2.0 May

128 Administering web interface Add User task Use the Add User screen to add a new user to this home server. This command is the same as selecting Users > Add from the menu. Contact List task This series of screens relates to the sites and friends the end users want to contact. Create and edit the personal contact with whom this user may want to communicate with the My Contact List task screen. Devices task Manage the tones, volume, and cadence of certain SIP-enabled devices with the Devices scree. For you to view this screen, the end user must have a compatible device. If you select a user that does not have a device that is compatible with this feature, the system displays a No Compatible devices found message. This message indicates that the end user s telephone does not support the Devices feature. Delete All Displayed Users task This task lets you delete all the users currently displayed without having to check the boxes to the left of the name. This is useful after a search has properly returned a group of users. Delete Selected Users task Delete more than one user at a time by checking several check boxes. You can check up to 68 check boxes to delete up to 68 users at one time. Select this and confirm your decision to delete one or more users. Extensions task Add, delete, and make available the extensions assigned to a user with the Extensions tasks on page 156. Handles task The Handles task concerns how the end user wants to be contacted. Administer a user s personal points of contact, and user groups with the screen in Handles task on page 161. A user may have more than one handle. For instance, one handle may be based on the user s (numeric phone) extension. Another handle may be an (alphabetic) team designation such as Head_Of_Payroll. Even though the number of contacts to a handle is limited to two, the number Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 126 Administering SES on the Avaya S8300 Server

129 User screens of handles for a user is not limited. A user must always log in to his or her SIP device using his or her primary handle as the user ID. The primary handle matches the User ID. Memos task Write short notes about the user for other administrators to read using the User Memos screen. Maximum size of the notes is 256 characters. Move User Move User occupies the screen only when there is more than one home server. Move User changes a user from one home server to another. You can also move a user from one home server to another using the Edit Profile screen. Permissions Profile Use this task to specify if other SIP users can detect a user s presence on the system. This is the Watchers feature of PPM. Note that presence cannot be matched properly if the handle of the watched user does not match exactly, including its case. Edit the full profile of a user and customize it with the Edit User Profile screen. Watchers for User Submit This task choice lets you select for the user who on the system may observe the user s presence. Selecting this task displays the Watchers Task screen. Note that presence cannot be matched properly if the handle of the watched user does not match exactly, including its case. Check mark a user, or in limited instances, several users, select a task from the drop-down menu, then select Submit to proceed to the next screen. Issue 2.0 May

130 Administering web interface Add User screen Add users one at a time with this screen. The contents setup in the default user profile initially populate the fields Host, Address 1, Address 2, City, Country, and ZIP. You may change those entries here for this single user. Check the Add Media Server Extension box to immediately assign an extension, and a SIP address based on that extension, to the new user. The fields for user profiles accept UTF-8 character encodings to accommodate multibyte character languages such as Japanese. You may input Shift_JIS (SJIS) characters as well. Whether the browser sends UTF-8 or SJIS is dependent upon the browser s language setting. The name will be assigned to the speed dial button for this contact. Used with the SP-1020A, this alias string is in Kana characters, and is designed to help with contact sorting. (Contrast this with Name.) Add User screen field descriptions Primary Handle A handle identifies the user on the SES system. Users primary handles must be the same as their user IDs. Selecting this link displays the detailed user contact information for the SIP user. User handles must be unique within the SES system domain. Users may have multiple handles to accommodate more than one personal point of contact. Note: Note: The SES system automatically appends portion of the handle. Do not type this portion of the handle when adding or updating this end user on other screens. Do not use the handles listed below for any user. They are reserved for system and administrative use: event-server cm-resubscribe confsvr handle_list presenceserver In addition: All handles must be between 3 and 16 ASCII characters in length. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 128 Administering SES on the Avaya S8300 Server

131 User screens If any of the preceding transformations produce handles already present, then they are dropped. No user handle may start with an underscore. All handles must be entered in lower case. All handles must be unique. All handles must be alphanumeric with no special characters other than dash (-). User ID (Optional) This is an identifier of at least three alphanumeric characters in length. Each administered user has one unique User ID and it is used as their display name within SES adminstration. For example, the User ID is the name listed for the user on the List Users, Search User, Edit User and List Media Server Extensions screens. It is recommended that the User ID be the same as the Primary handle administered for the user. If the User ID is left blank when the user is added, it is defaulted to the Primary handle. A User ID is administered as an alphanumeric string between 3-16 characters in length. A user's User ID may be changed from their Edit User Profile screen. A user's Primary handle may only be changed from the Edit Handle screen (List Users -> Select A user -> Select Handles task). Password, Confirm Password Host Enter a password of at 6 to 12 alphanumeric characters. Both field entries must match exactly. From the drop-down list of names, select the home server for this user. The host name of the current server is selected by default. This is the name of the SES host serving the domain for this user. An SES host is a home server or a combined home/edge server, either of which can be a co-resident CM/SES server. First Name, Last Name This is the name of as many as 64 UTF-8 characters associated with this User ID and Handle in the user database. You may input Shift_JIS (SJIS) as well. Whether the browser sends UTF-8 or SJIS is dependent upon the browser s language setting. The name will be assigned to the speed dial button for this contact. In Japanese, this name string uses Kanji characters. (Contrast this with Alias.) Issue 2.0 May

132 Administering web interface Address 1, Address 2 (Optional) This is the first line and second line of the default address for users. You may input Shift_JIS (SJIS) characters as well. Whether the browser sends UTF-8 or SJIS depends upon the browser s language setting. The name will be assigned to the speed dial button for this contact. In Japanese, this name string uses Kanji characters. (Contrast this with Alias.) Office City State Country ZIP Enter a designation for the user s office suite or perhaps floor, in alphanumeric characters. Enter the name of the city or town of the user s address in alphanumeric characters. Enter the name of the state or province of the user s address in alphanumeric characters. Enter the name of the country of the user s address in alphanumeric characters. Enter the number of the ZIP or postal code of the user in numeric characters. Survivable Call Processor The Survivable Call Processor field points to auxiliary call processor hardware if service from SES is lost. The list of SCPs on the drop-down list is empty until you add one or more SCPs. Ideally, administer your SCPs before you add or edit a user. Add Media Server Extension You may select this box to assign an extension now, or leave it unchecked to assign one later. If you check this box, the system displays the Add Media Server screen, after this user s profile has been added. If you do not check this box, you can wait and associate extensions with the user later. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 130 Administering SES on the Avaya S8300 Server

133 User screens Add User screen command Add After entering or updating entries, select Add to submit the user s profile to the database on this host. In SES 5.0, the data service will propogate the information automatically to any other SES hosts. Issue 2.0 May

134 Administering web interface My Contact List task screen This series of screens displays the sites and friends an end user wants to contact. The contact address can be IP addresses, address, or web pages with which an end user would like to communicate. If a SIP softphone user adds a contact for a non-sip user, then when the SIP user logs into SPIM, they will see a 'dummy' handle for the non-sip contact that looks like: "[email protected]", where "xxxxx" is a unique string. This screen is also available on the web page viewed by the end user of PPM, the SIP Personal Information Manager pages, but there it is rendered differently. The maximum number of contacts an end user may have on this page depends on the device they have. If the device is a Toshiba Business Phone, model SP-1020A, the maximum number of contacts is 100. For other devices, the maximum number of contacts is 250. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 132 Administering SES on the Avaya S8300 Server

135 User screens My Contact List screen field descriptions Handle This is a valid name or User ID for the contact. Selecting this link displays the detailed user contact information for the contact. Handles must be unique contact URIs within the SES system domain, but contacts may have multiple valid handles. Note: Note: The SES system automatically appends the sip_domain.com portion of the handle. This portion of the handle should not be entered as part of the handle field when adding or updating a handle. If you select a user s option button, or select a group name by clicking on it, the system displays a Contact Details screen or Group Details screen. These two screens let you edit details about the contact or group, respectively. Name Alias This is the name of as many as 64 UTF-8 characters associated with this User ID and Handle in the user database. You may input Shift_JIS (SJIS) as well. Whether the browser sends UTF-8 or SJIS is dependent upon the browser s language setting. The name will be assigned to the speed dial button for this contact. In Japanese, this name string uses Kanji characters. (Contrast this with Alias.) This field displays the optional alias name of as many as 32 UTF-8 characters associated with this contact in the user database. You may input Shift_JIS (SJIS) characters as well. Whether the browser sends UTF-8 or SJIS is dependent upon the browser s language setting. In Japanese, this alias string is in Kana characters, and it is designed to help with contact sorting. (Contrast this with Name.) Telephone #1 / Telephone #2 Lists a telephone number or valid SIP user address. A valid SIP user address may be any Uniform Resource Identifiers (URIs) beginning with sip: or sips:. The SIP user address is associated with this handle in the contact database. This field may contain a maximum of 256 ASCII characters. Issue 2.0 May

136 Administering web interface My Contact List screen commands Handle (link) If you click directly on an underlined handle, the system displays Contact Details for that handle as a view only screen. Group (link) View Delete If you click directly on an underlined group name, the system displays the Group Details screen for that group. At this time, only one level of hierarchy for groups are supported. View details about the contact or group. Select a contact, then select Delete to remove that contact from the user s list. This does not delete the contact from the system. Add Contact Add another individual contact or group. At this time, only one level of hierarchy for groups are supported. Add Group Add a group name to which this contact belongs. At this time, only one level of hierarchy for groups are supported. Speed Dial Select this to view the speed dial telephone numbers and speed dial digit assignments for contacts this user may want to communicate with. Reload Configuration If you have made changes on this end user s list of contacts, select Reload Configuration to refresh the list. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 134 Administering SES on the Avaya S8300 Server

137 User screens For SIP users, you may wish to reload the configuration data for your telephone, like its Ringer Settings, its Speed Dial List entries (from My Contact List), and its One Touch Dial List entries. Select this link and then submit the reload request. For system administrators, a variety of data affects the device: Changes to network node information Data regarding station aliasing Associated Dial Plan assignments Data may have been updated and submitted on the server running Avaya Communication Manager. Submitting this request reloads this updated device configuration data. Note: Note: Provisioned users who have been administered may not have logged on to their device, registering it with the SIP proxy server. Submitting the Reload Device Configuration (or executing the Reload Complete task) will take effect the next time they log on successfully to their SIP device. When you are ready to reload your configuration for this device, including any station-affecting changes you may have made in Avaya Communication Manager running co-resident on the SES 5.0 server, then select the Submit button on this screen. Otherwise, select the Cancel button to ignore this request. After you click Continue, the screen displays the My Contacts list. Issue 2.0 May

138 Administering web interface Contact Details screen This system displays this screen when you select an item and then the View button on the My Contacts screen. This screen is read only. To make changes, select Update Contact to obtain an editable view. With this information, SIP users can access each other at a variety of contact points. All fields on this screen are view only. Select Update Contact to make changes. Select Delete Contact to remove this contact s information from access by the user. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 136 Administering SES on the Avaya S8300 Server

139 User screens Update Contact screen Change the contact information for the end user s contact with this screen. With this information SIP users can access each other at a variety of contact points. SIP User dlaser, who wants to contact user Digi Minky, must put in all the contact information for DMinky via the PIM or Softphone. That way dlaser can choose to reach DMinky at a work telephone, cell telephone, web page, fax number, and so on. Issue 2.0 May

140 Administering web interface Add Contact screen From the SIP PIM interface an end user builds a list of friends, addresses, web pages and so on, with whom to communicate. As an administrator, with this screen, you may add a contact for the end user, with a group affiliation, and speed dial numbers. With this information, that SIP users can access each other at a variety of contact points. SIP User Dani Laser, who wants to contact user Digi Minky, must put in all the contact information for dminky via the PIM or Softphone. That way dlaser can choose to reach dminky at a work telephone, cell telephone, web page, fax number, and so on. If a SIP softphone user adds a contact for a non-sip user, then when the SIP user logs into SPIM, they will see a 'dummy' handle for the non-sip contact that looks like: "[email protected]", where "xxxxx" is a unique string. Add Contact and Update Contact screen field descriptions Address Name Alias On this screen, the Address field must contain the SIP address of the contact in this field, that is, the user s handle on the SIP domain. This is the name of as many as 64 UTF-8 characters associated with this User ID and Handle in the user database. You may input Shift_JIS (SJIS) as well. Whether the browser sends UTF-8 or SJIS is dependent upon the browser s language setting. The name will be assigned to the speed dial button for this contact. In Japanese, this name string uses Kanji characters. (Contrast this with Alias.) (Optional) This field displays the optional alias name of as many as 32 UTF-8 characters associated with this contact in the user database. You may input Shift_JIS (SJIS) characters as well. Whether the browser sends UTF-8 or SJIS is dependent upon the browser s language setting. In Japanese, this alias string is in Kana characters, and it is designed to help with contact sorting. (Contrast this with Name.) Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 138 Administering SES on the Avaya S8300 Server

141 User screens Group Name A valid name for the group with which the contact has been associated, as a selectable link. This field may contain a maximum of 32 UTF-8 characters. Select the link to view the details screen showing the contacts for this Group. Tip: Tip: If the contact list is lengthy, use your web browser s "Find in This Page" function to search the page for a particular entry. You may select a contact to View or Delete using the radio button to the left of the name and/or handle. After you choose a contact, select the "View" button to display the Contact Details screen, or select the "Delete" button to display a warning message for you to confirm the deletion from the contact list. Note: Note: Deleting a user contact from the contact list does not affect the associated provisioned user s information in the user database. Notes Enter a string in this field as the address associated with this contact. It may contain as many as 256 ASCII characters. When displayed in the read-only fields on the Contact Details screen, this becomes a clickable mailto: link on the web page. Enter any informational notation to be associated with this contact in this field. It is free-form text, and may contain as many as 1,024 UTF-8 characters. You can input Shift_JIS (SJIS) as well. Whether the user s browser sends UTF-8 or SJIS is dependent upon your browser s language setting. Track Availability Check the box if the user named at the very top of the screen, for example dlaser, wants to track the presence of the person named in the Address field, for example [email protected]. The user dminky has the option of not allowing herself to be tracked. Note that presence cannot be matched properly if the handle of the watched user does not match exactly, including its case. Contact Phones This group of fields lists up to six ways for a user to reach a contact. Issue 2.0 May

142 Administering web interface Phone Type The drop-down menu for this field provides identification for the rest of the information in the row. Phone Number SIP handle, , fax, or telephone number for this contact. Label / Label a short description of the contact, perhaps a server or type of contact. Speed Dial check this box to let the end user reach the contact with speed dial. The first contact is speed dial number 1, the second is number 2, and so on. Speed dial is a soft button on a SIP telephone Prefix any outward dialing prefix, comma, or other sequence the end user may need to dial before they dial the telephone number. Add Contact screen command Add Record this contact s information and it s association with a user in the database. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 140 Administering SES on the Avaya S8300 Server

143 User screens Add Group screen Part of the information captured about a contact is their membership in a group, for example, Test, Development, Management, or Documentation. Define groups here. Setting up a group provides a way of labeling and organizing many contacts.group names cannot be used for contacting all users in a group. Add Group screen field descriptions Group Name Enter a name of as many as 32 UTF-8 characters in length for a new group for user contacts that you would like to create. You can input Shift_JIS (that is, SJIS) as well. Whether the browser sends UTF-8 or SJIS is dependent upon your language setting. This is a logical name for organizational purposes, not a list name for addressing purposes via SIP contact Uniform Resource Identifiers (URIs). Add Group screen command Submit Record the new group in the database. Issue 2.0 May

144 Administering web interface Speed Dial List screen Handle This screen is view only. It reflects the settings made in Contact Details screen. You can quickly see what is assigned to speed dial 1, speed dial 2, and so on. To make changes to the speed dial information of a contact, use the Update Contact screen. Entries on this list typically appear as soft button labels on the SIP user s device. This is a valid name or User ID for the contact. Selecting this link displays the detailed user contact information for the contact. Handles must be unique contact URIs within the SES system domain, but contacts may have multiple valid handles. Note: Note: The SES system automatically appends the sip_domain.com portion of the handle. This portion of the handle should not be entered as part of the handle field when adding or updating a handle. Name Alias Prefix On this screen, the Name field is the label you assigned to the phone number for this contact. This field displays the optional alias name of as many as 32 UTF-8 characters associated with this contact in the user database. You may input Shift_JIS (SJIS) characters as well. Whether the browser sends UTF-8 or SJIS is dependent upon the web browser s language setting. In Japanese, this alias string is in Kana characters, and it is designed to help with contact sorting. (Contrast this with Name.) Lists the optional prefix digits associated with this user s extension (Telephone #) in the user database. An example of a prefix would be an AAR or ARS dial access code of 0-4 digits. This field blank may be blank if no such prefix code applies to this user contact. Telephone # Lists a telephone number or valid SIP user address. A valid SIP user address may be any Uniform Resource Identifiers (URIs) beginning with sip: or sips:. The SIP user address is associated with this handle in the contact database. This field may contain a maximum of 256 ASCII characters. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 142 Administering SES on the Avaya S8300 Server

145 User screens Select Handle to view the associated user s detailed contact information. Issue 2.0 May

146 Administering web interface Delete Contact screen As administrator, you may want to delete infrequently used contacts for a user. Deleting a contact will adjust the speed dial order. Deleting a contact does not delete the group of which the contact may be a member, nor does it delete the user contact from the entire system. Select OK to remove both the association from the end user and the contact from the database. Select Cancel if you change your mind about the delete. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 144 Administering SES on the Avaya S8300 Server

147 User screens Group Details screen If a contact can be classified with a certain group, view and delete group members here. At this time, only one level of hierarchy for groups are supported. Group Details screen field descriptions Handle This is a valid name or User ID for the contact. Selecting this link displays the detailed user contact information for the contact. Handles must be unique contact URIs within the SES system domain, but contacts may have multiple valid handles. Note: Note: The SES system automatically appends the sip_domain.com portion of the handle. This portion of the handle should not be entered as part of the handle field when adding or updating a handle. Name Alias After viewing the details of this group, select the Add Contact link to go to the Add Host screen and associate a contact with this group in your list of user contacts. Select the Delete Group link to go the Delete Group screen and delete this group name from your contact list. Select the Update Group link to go to the Update group screen and change the name of this group in your user contact list. This is the name of as many as 64 UTF-8 characters associated with this User ID and Handle in the user database. You may input Shift_JIS (SJIS) as well. Whether the browser sends UTF-8 or SJIS is dependent upon the browser s language setting. The name will be assigned to the speed dial button for this contact. In Japanese, this name string uses Kanji characters. (Contrast this with Alias.) This field displays the optional alias name of as many as 32 UTF-8 characters associated with this contact in the user database. You may input Shift_JIS (SJIS) characters as well. Whether the browser sends UTF-8 or SJIS is dependent upon the browser s language setting. In Japanese, this alias string is in Kana characters, and it is designed to help with contact sorting. (Contrast this with Name.) Issue 2.0 May

148 Administering web interface Telephone #1 and Telephone #2 Lists a telephone number or valid SIP user address. A valid SIP user address may be any Uniform Resource Identifiers (URIs) beginning with sip: or sips:. The SIP user address is associated with this handle in the contact database. This field may contain a maximum of 256 ASCII characters. Group Details screen commands Back to My Contact List Select this link to return to the My Contact List task screen. Add Contact Select this to display the Add Contact screen to add another contact to the group selected. Delete Group Select OK to delete the group from the database. Select Cancel if you change your mind about deleting the group. Deleting a group does not remove the contacts in the group from use. The contacts automatically become members of the default group. Update Group View Delete Select this to display the Update Group screen to change the group s name. Select a contact for the user and click View to show a view-only screen of the contact s details. Delete this contact from this particular group. This command does not delete this contact from any other groups to which it belongs. If a group is empty, View and Delete operate on the group, not members of the group. If a group is not empty, it has members, and View and Delete operate on the members, showing them in the group or deleting them from the group, respectively. Delete does not delete a contact group member from the entire user contact database. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 146 Administering SES on the Avaya S8300 Server

149 User screens Delete Group screen Deleting a group generates the following results: Delete the group and all its members. Move the members to another group and then remove the original group. Delete Group screen field descriptions Delete all contacts Select this radio button to remove the members from the group but keep the group itself. The contacts that are members of this group are not deleted from the database. Move all contacts Select this to move all the group s members to another group. The original group is deleted. Delete Group screen commands Back to My Contact List Yes No Select this link to return to the My Contact List task scren. Go ahead and submit your selections. Cancel the selections on the screen and do nothing. The system displays the My Contact List task screen. Issue 2.0 May

150 Administering web interface Update Group screen Modify the group name here. All contacts associated with the original group name now are associated with the new group name. Update Group screen field descriptions Old Group Name Displays the name of the existing group that you are about to change. Group Name Enter a new name for the existing group, of as many as 32 UTF-8 characters in length. You may input Shift_JIS (SJIS) characters as well. Whether the browser sends UTF-8 or SJIS is dependent upon the browser s language setting. Used with SP-1020A, this alias string is in Kana characters, and it is designed to help with contact sorting. (Contrast this with Name.) When finished entering data, select Submit to rename the group in your contact list. Update Group screen commands Back to My Contact List Select this link to return to the Contact List Submit Update Select this to submit the group name change to the database. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 148 Administering SES on the Avaya S8300 Server

151 User screens Devices Screen menu The Devices screen allows the users of certain supported SIP devices to view, change, and reload certain configuration settings. Note that the example screens shown in this section only apply to certain supported endpoints, such as the Toshiba Business Phone (SP-1020A). Issue 2.0 May

152 Administering web interface One Touch Dial List screen This screen is also available on the web page viewed by the user, the SIP Personal Information Manager pages. For you to view this screen, the end user must have a compatible device. One Touch Dial List screen field descriptions Button Address Label The number designating the button which is assigned to this auto-dial list entry in Avaya Communication Manager running on the server. The maximum button number is 66. May be blank, in which case SIP contact Uniform Resource Identifiers (URIs) for the auto-dial list entry may be entered here, or it may display the non-blank auto-dial list entry or entries made in Avaya Communication Manager running on the server for the associated button. In the latter case, if the entry is edited in this SIP PIM web interface, any changes made to these entries here in SES 5.0 will not be reflected in Avaya Communication Manager on the server. The maximum length of any Address field entry is 256 ASCII characters. May be blank, in which case a label for the auto-dial entry may be entered here, or it may display (read-only) the non-blank, auto-dial-entry label made in Avaya Communication Manager for the associated button. In the latter case, the entry may not be edited here. The maximum length of any Label field entry is 20 UTF-8 characters. Note that UTF-8 characters can include ASCII, Kanji and Kana characters. You may input Shift_JIS (SJIS) characters as well. Whether the browser sends UTF-8 or SJIS is dependent upon the web browser s language setting. Used with a supported endpoint, such as the SP-1020A, this alias string is in Kana characters, and it is designed to help with contact sorting. (Contrast this with Name.) Note: Note: The Toshiba Business Phone (SP-1020A) does not display half-width, Han Kaku Kana characters. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 150 Administering SES on the Avaya S8300 Server

153 User screens One Touch Dial List screen commands Save Submit the one touch dial information to the database. Issue 2.0 May

154 Administering web interface Ringer Settings screen This screen lets you turn the ringer on and off for the user, and shows information about the telephone s bridged appearance. This screen is also available on the web page viewed by the user, the SIP Personal Information Manager pages. For you to view this screen, the end user must have a compatible device. Ringer Settings screen field description Button This field shows one or more numbers designating the bridged appearance buttons on a telephone for which you may turn the ringer on or off (and independent of and not reflecting the OPS settings for the station in Avaya Communication Manager running on the server). Setting the ringer settings is for the station s bridge appearance buttons. This is not related to ringer settings configured in Communications Manager. Bridged Appearance Lists the administered extension associated with this telephone button in the user database. This field may contain a maximum of 256 alphanumeric characters. Ringer ON/OFF If the ringer of any available button is set to off, you may select the radio button under On to enable its ringer. Likewise, if it is set to On, you may select the button under Off to disable it. Ringer Settings screen command Save Submit the ringer settings or changes to the database. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 152 Administering SES on the Avaya S8300 Server

155 User screens Tone and Volume Settings screen This is a view-only screen for the administrator, and provides a list of how the tones, volumes and speed of the user s telephone device were set by the user. This screen is also available on the web page viewed by the user, the SIP Personal Information Manager pages. For you to view this screen, the end user must have a compatible device. Ringer Cadence Displays the default Ringer Cadence (default is 2) for the device administered for end users in the database. This number represents the speed of the telephone s ringing (1 through 3). Ringer Volume Displays the default Ringer Volume (default is 5) for a device administered by end users in the database. This number represents how loudly the telephone will ring. The range is 1 through 10. Receiver Volume Displays the default Receiver Volume (default is 5) for a device administered by end users in the database. This number represents handset loudness (1 through 10). Speaker Volume Displays the default Speaker Volume (default is 5) for a device administered by end users in the database. This number represents speakerphone loudness (1 through 10). Issue 2.0 May

156 Administering web interface Delete All Displayed Users task This task lets you delete all the users currently displayed without having to check the boxes to the left of the name. This is useful after a search has properly returned a group of users. After carefully checking the list of names on the List User s screen, select either OK or Cancel. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 154 Administering SES on the Avaya S8300 Server

157 User screens Delete Selected Users task Delete more than one user at a time by checking several check boxes. You can mark many check boxes and delete up to 68 users at one time. Select and confirm your decision to delete a user. When asked to delete the extensions also, check that box if you want to prevent that extension from being reused later by a different user. Issue 2.0 May

158 Administering web interface Extensions tasks This section describes administering a specific user s extension. With the screen described here, you can associate an extension with a user, remove an extension from a user, or free an extension for use by any other user with this screen series. If a user does not have any extension assigned, the system displays the List Media Server Extensions screen. List Media Server Extensions screen field descriptions Extension User The numeric telephone extension in the database. This is the extension for the user named at the top of the screen. This is the User ID assigned when the user was added to the SES system. See User ID on page 129. Media Server Host The name of the server running Avaya Communication Manager (in a distributed SES 5.0 system) to which the extension was assigned. This is the name of the SES home server for this user. For co-resident CM/SES 5.0 systems, this host name may be the same as the name of that of the Media Server, above. List Media Server Extensions screen commands Free This command removes an extension from the user named at the top of the screen, but keeps it available for reassignment. Select this to show an OK or Cancel screen. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 156 Administering SES on the Avaya S8300 Server

159 User screens Edit User Delete For the convenience of the administrator, this selection lets you display this user as the only user in the list. Usage is described in the List Users screen on page 125. Pick a task from the drop-down list. This command deletes an extension from the user in the database. The user remains, but no longer has this extension associated with him or her. Select this to show an OK or Cancel screen. See the example for the Confirm Delete User screen on page 192. Issue 2.0 May

160 Administering web interface List Media Server Extensions when user has none Sometimes, after requestng to view the administered extension for a user, none is shown. That is, a user may not have been assigned an extension yet, or may have had their assigned extension removed from the database for some reason. If a user has no assigned extension, the system displays the List Media Server Extensions screen. Tip: Tip: If you want to look up information about extensions in Communication Manager 5.2, perhaps to make more extensions available for SES users, then see the Extensions tasks on page 156. Add Another Media Server Extension This link takes you to the Add Media Server screen so that you may create an extension and assign to the user. Assign Free Media Server Extension This link takes you to the Select Free Extension screen. There, select an extension from the pull-down list that is already created and administered in Avaya Communication Manager on a server associated with this user's SES 5.0 home server. That extension is assigned to the user who is displayed here. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 158 Administering SES on the Avaya S8300 Server

161 User screens Add Media Server Extension screen Create an extension for a user who does not have one assigned. This screen only sets up the extension in SES. Also administer that extension in Avaya Communication Manager software. Tip: Tip: If you want to look up information about extensions in Avaya Communication Manager 5.0, perhaps to make more extensions available, see the Extensions tasks on page 156. Add Media Server Extension screen field descriptions Extension The numeric telephone extension in the database. Enter the numeric telephone number that you want to create as an extension in SES 5.0 also. The entered extension must be administered on the server running Avaya Communication Manager before the extension becomes functional. Media Server Select the network name for the extension s server interface from the drop-down list. The node name, in alphanumeric characters, associated with the CLAN (or processor CLAN) IP interface of a server running Communication Manager. For more information on IP node names, see Administering Network Connectivity on Avaya Aura Communication Manager, Add Media Server Extension command Add Select Add to create a new entry for this server extension in this SIP proxy server s database. Note: Note: This will not create any extensions or change any existing administration performed directly in Avaya Communication Manager. You must do that manually using the Administration web interface to Avaya Communication Manager. Issue 2.0 May

162 Administering web interface Select Free Extension screen You may want to verify in Avaya Communication Manager to make sure that the user s extension is administered there. This screen is accessed from the List Media Server Extensions when user has none on page 158, and you select Assign a Free Media Server Extension. This screen lets you choose an unused extension from the available extensions for the server running Avaya Communication Manager. When you first add a user, you are not required to assign a media extension for that user. To provide one later, you may use this screen. Extension Select Select this drop-down list to see what extensions are currently available for assignment. Select a free extension from this list. Make your list selection permanent. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 160 Administering SES on the Avaya S8300 Server

163 User screens Handles task The Handles task concerns the contact points at which the end user can be contacted. One way to get to this screen is to select List Users, find the user you want, and click the check box. From the drop-down list of Tasks, select Handles. Then click Submit. Handles may be: Totally numeric, as in a telephone number Totally alphabetic characters, as in a name A mix of alphanumeric characters, but no special characters other than the dash. Handles must be unique across the SIP domain. If a person wants to contact dlaser, they may try the extension That message first goes to the SIP Uniform Resource Indicator (URI) of If the message is not put through, the URI for the next contact point is tried, in this example sips:2222. If a person wants to connect with Dani Laser s web page, they would input dlaser_webpage. If rendering web pages is supported by the device they use, it will show Dani s web page. Do not use the handles listed below for any users. They are reserved for system and administrative use: event-server cm-resubscribe confsvr handle_list presenceserver In addition: All handles must be between 3 and 16 ASCII characters in length. If any of the preceding transformations produce handles already present, then they are dropped. No user handle may start with an underscore. All handles must be entered in lower case. All handles must be unique. All handles must be alphanumeric with no special characters other than dash (-). Issue 2.0 May

164 Administering web interface Edit User Handles screen field descriptions User ID This is an identifier of at least three and no more than 16 alphanumeric characters in length. Each administered user has one unique User ID and it is used as their display name within SES adminstration. For example, the User ID is the name listed for the user on the List Users, Search User, Edit User and List Media Server Extensions screens. It is recommended that the User ID be the same as the Primary handle administered for the user. If the User ID is left blank when the user is added, it is defaulted to the Primary handle. A User ID is administered as an alphanumeric string between 3-16 characters in length. A user's User ID may be changed from their Edit User Profile screen. A user's Primary handle may only be changed from the Edit Handle screen (List Users -> Select a user -> Select Handles task). Handle A handle identifies the user on the SES system. Users primary handles must be the same as their user IDs. Selecting this link displays the detailed user contact information for the SIP user. User handles must be unique within the SES system domain. Users may have multiple handles to accommodate more than one personal point of contact. Note: Note: The SES system automatically appends portion of the handle. Do not type this portion of the handle when adding or updating this end user on other screens. Contact In this screen, the information in the Contact column is the SIP address of the user, which is created based on the user s administered telephone extension and the IP address of the IP server interface for the Communication Manager server to which this user is assigned. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 162 Administering SES on the Avaya S8300 Server

165 User screens Edit User Handles screen commands Edit (Handle) Go to the Edit Handle detail screen for that user s handle for the associated user Contact. Delete (Handle) Display the Confirm Delete Handle screen for that user s handle. The handle that has no Delete command next to it is the primary handle for the user and cannot be deleted. Add Another Handle You may select Add Another Handle to provide another handle for the user ID named at the top of the screen. Users may have several handles, but each must be unique within the SIP domain to which they belong. Edit (Contact) Select Edit next to the contact information to change the information about this user s personal point of contact. Delete (Contact) Display the Confirm Delete Contact screen to delete a personal point of contact for the user named at the top of this screen. Add Another Contact Select this link to add another point of contact for the SIP user named at the top of the screen. Add Handle in New Group A group is a set of handles that resolves to a set of contacts. At this time, the SES system supports only one level of hierarchy for groups. Select Add Handle In New Group to go to the Add Handle in a New Group screen. There, you can create a new group to add a handle to. Issue 2.0 May

166 Administering web interface Delete Group Select Delete Group to display the Confirm Delete Group screen. When viewing the confirmation screen, you may choose to delete the group and all of its members, or to delete only the group association of the members, and leave the member user contacts available. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 164 Administering SES on the Avaya S8300 Server

167 User screens Edit Handle detail screen Change the users handle details with this screen. Edit Handle detail screen field description User ID Domain Handle This is an identifier of at least three and no more than 16 alphanumeric characters in length. Each administered user has one unique User ID and it is used as their display name within SES adminstration. For example, the User ID is the name listed for the user on the List Users, Search User, Edit User and List Media Server Extensions screens. It is recommended that the User ID be the same as the Primary handle administered for the user. If the User ID is left blank when the user is added, it is defaulted to the Primary handle. A User ID is administered as an alphanumeric string between 3-16 characters in length. A user's User ID may be changed from their Edit User Profile screen. A user's Primary handle may only be changed from the Edit Handle screen (List Users -> Select a user -> Select Handles task). With this screen, you can change the handle for this User ID. The domain name of the home server to which this user is assigned. A handle identifies the user on the SES system. Users primary handles must be the same as their user IDs. Selecting this link displays the detailed user contact information for the SIP user. User handles must be unique within the SES system domain. Users may have multiple handles to accommodate more than one personal point of contact. Note: Note: The SES system automatically appends portion of the handle. Do not type this portion of the handle when adding or updating this end user on other screens. Do not use the handles listed below for any user. They are reserved for system and administrative use: event-server Issue 2.0 May

168 Administering web interface cm-resubscribe confsvr handle_list presenceserver In addition: All handles must be between 3 and 16 ASCII characters in length. If any of the preceding transformations produce handles already present, then they are dropped. No user handle may start with an underscore. All handles must be entered in lower case. All handles must be unique. All handles must be alphanumeric with no special characters other than dash (-). Edit Handle detail screen command Update Select Update to submit the modified information to the database. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 166 Administering SES on the Avaya S8300 Server

169 User screens Edit Host Contact screen This screen lets you change the contact associated with a specific handle. Do not use this screen to change contacts assigned to the user by the SES system. Use this screen to edit the Avaya Communication Manager server contacts associated with a user's extension. Edit Host Contact screen field descriptions User ID Contact The user ID for whom you want to name a new host contact to redirect calls to. Enter a point of contact for the selectd user s handle. This contact is usually a fixed destination. The Media Server contact type is for all handles that should be resolved to contacts that are routed directly to a media server. This only includes handles that are also extensions, because media servers only recognize extensions, not alphanumeric handles. If you select the Media Server contact type, the entered Contact pattern should be a contact that includes an IP address of a server running Avaya Communication Manager. If you select the Media Server contact radio button, the system is expecting that the corresponding contact is a Communication Manager server contact. If you select the Media Server contact type, and the corresponding contact is not a pattern recognized by the server running Avaya Communication Manager, then calls may not be routed properly. The User contact type is used for all handles that should be resolved to contacts that are directly routed to addresses that are not Communication Manager servers. This includes other standalone SES home servers, or devices that are not connected to a CM or co-resident server. If you select the User contact type, the entered Contact on the page should be a contact that is not an IP address of a server running Avaya Communication Manager. If you select User contact type, and the corresponding contact is a server running Avaya Communication Manager, then calls may be routed to that server but not completed on it. Contact Type Media Server (that is, one running Avaya Communication Manager), or User Issue 2.0 May

170 Administering web interface Edit Host Contact screen commands Media Server option Specify that the information in the Contact field is a user s primary SIP contact address that is recognizable by a server running Avaya Communication Manager in your system. The call is to be routed successfully through that server to its destination. User option Update Indicate that the information in the Contact field is not a user s primary SIP contact address, and should not be routed through the server running Avaya Communication Manager in your system. Submit your additions or changes to the database. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 168 Administering SES on the Avaya S8300 Server

171 User screens Add Handle screen This displays when you select Add Another Handle command on the Edit User Handles screen. Use this screen to provide a SIP user with an additional handle that routes calls differently. Add Another Handle screen field descriptions User ID Handle An identifier of at least three alphanumeric characters in length, used to authenticate a user. A handle identifies the user on the SES system. Users primary handles must be the same as their user IDs. Selecting this link displays the detailed user contact information for the SIP user. User handles must be unique within the SES system domain. Users may have multiple handles to accommodate more than one personal point of contact. Note: Note: The SES system automatically appends portion of the handle. Do not type this portion of the handle when adding or updating this end user on other screens. This is never the Primary handle, which is defined on the Add User screen. Do not use the handles listed below for any user. They are reserved for system and administrative use: event-server cm-resubscribe confsvr handle_list presenceserver In addition: All handles must be between 3 and 16 ASCII characters in length. If any of the preceding transformations produce handles already present, then they are dropped. Issue 2.0 May

172 Administering web interface No user handle may start with an underscore. All handles must be entered in lower case. All handles must be unique. All handles must be alphanumeric with no special characters other than dash (-). Add Another Handle screen command Add Submit this additional information to the user database. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 170 Administering SES on the Avaya S8300 Server

173 User screens Add Host Contact screen The Add Host Contact screen allows an additional point of contact to be added for the selected handle. For user contacts that are not extensions, the Contact Type should be User. Add Host Contact screen field descriptions User ID Handle An identifier of at least three alphanumeric characters in length, used to authenticate a user. A handle identifies the user on the SES system. Users primary handles must be the same as their user IDs. Selecting this link displays the detailed user contact information for the SIP user. User handles must be unique within the SES system domain. Users may have multiple handles to accommodate more than one personal point of contact. Note: Note: The SES system automatically appends portion of the handle. Do not type this portion of the handle when adding or updating this end user on other screens. Contact and Contact Type Enter a point of contact for the selectd user s handle. This contact is usually a fixed destination. The Media Server contact type is for all handles that should be resolved to contacts that are routed directly to a media server. This only includes handles that are also extensions, because media servers only recognize extensions, not alphanumeric handles. If you select the Media Server contact type, the entered Contact pattern should be a contact that includes an IP address of a server running Avaya Communication Manager. If you select the Media Server contact radio button, the system is expecting that the corresponding contact is a Communication Manager server contact. If you select the Media Server contact type, and the corresponding contact is not a pattern recognized by the server running Avaya Communication Manager, then calls may not be routed properly. The User contact type is used for all handles that should be resolved to contacts that are directly routed to addresses that are not Communication Manager servers. This includes other standalone SES home servers, or devices that are not connected to a CM or co-resident server. If you select the User contact type, the entered Contact on the page should be a contact that is not an IP address of a server running Avaya Communication Manager. Issue 2.0 May

174 Administering web interface If you select User contact type, and the corresponding contact is a server running Avaya Communication Manager, then calls may be routed to that server but not completed on it. Add Host Contact screen commands Media Server option Specify that the information in the Contact field is a user s primary SIP contact address that is recognizable by a server running Communication Manager in your system. The call will route successfully through that server. User option Add Indicate that the information in the Contact field is not a user s primary SIP contact address, and should not be routed through the associated server running Avaya Communication Manager. Confirm to add into the database the new host contact you have set up. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 172 Administering SES on the Avaya S8300 Server

175 User screens Add Handle in a New Group screen Add Handle in New Group displays an Add Group screen that is specifically for groups of handles that resolve to the same User Contact in the database. Stated another way, use this screen to start a new group and add a new line for handles and contacts to resolve to. A group is a set of handles that resolves to a set of contacts. At this time, only one level of hierarchy for groups is supported. Even though the screen title says Add Group, you are adding the handle in the required field to the group you selected previously. Add Group screen field descriptions User ID Handle An identifier of at least three alphanumeric characters in length, used to authenticate. In this screen, enter a handle of any end user to include them in this group. Do not use the handles listed below for any user. They are reserved for system and administrative use: event-server cm-resubscribe confsvr handle_list presenceserver In addition: All handles must be between 3 and 16 ASCII characters in length. If any of the preceding transformations produce handles already present, then they are dropped. No user handle may start with an underscore. All handles must be entered in lower case. All handles must be unique. Issue 2.0 May

176 Administering web interface All handles must be alphanumeric with no special characters other than dash (-). Add Group screen commands Add Add the handle to the user database in the new group of handles that you specified. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 174 Administering SES on the Avaya S8300 Server

177 User screens User Memos screen This screen lets administrators write memos about a user. The memos are available only to another administrator looking at this screen. End users do not see this information. Issue 2.0 May

178 Administering web interface User Memo field descriptions User ID An identifier of at least three alphanumeric characters in length, used to authenticate a user. List of memos The available memos display in chronological order, most recent at the top. Add Memo box Delete Write a new memo about the user inside this text box. Remove the memo to the left. Add Memo button Select this button to store the memo in the area above. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 176 Administering SES on the Avaya S8300 Server

179 User screens Move User Task The Move User task lets you easily select and move one user to a second home server if one is available in your architecture. Select the user to move with the check box, select Move User in the Task pull-down list, and click submit. The system displays the Mover User screen. The drop-down list for the New Host field lets you see what SES home servers are available to move to. Select the new home and click OK. After moving a user, you may have to go to the server running Communication Manager and log in there. Then, using the off-pbx-telephone station-mapping screen, verify the moved user s SIP trunk. Make any changes on this screen that are necessary. The system displays a confirmation screen in order to allow you to cancel the move. Issue 2.0 May

180 Administering web interface Moving a user to another home server In this procedure, the destination SES home server must be enabled and fully functional. If you are moving a user to a different home server, and the destination (standalone) SES home server is associated with two or more IP interfaces on server(s) runnning Avaya Communication Manager, you will be prompted to select one of those IP interfaces. If the user has an administered extension and the destination home SES does not have any server(s) running Communication Manager administered, then the Move User operation cannot be completed. The move may only be completed after a server running Avaya Communication Manager is added to the destination SES home or the user's extension is removed or freed. 1. From the Administrator interface, go to the List Users screen. 2. Select the check box next to the user you want to move. 3. Click the Move User task in the pull down menu. The system displays a Move User page. Select the new home server using the New Host drop-down list box. Only those homes that the user can be moved to are displayed in this box. All home servers that exist are not shown. The New Host drop-down box does not contain the user's current home. If a home server connects to a server running Communication Manager that contains more than one server IP interface, the drop-down list displays the IP interfaces from which you may choose. 4. Press OK or Cancel. The update procedure is performed by the system. 5. On Communication Manager, change the SIP trunk for the extension of the user with the form off-pbx-telephone station-mapping form. 6. On the Toshiba Business Phone (SP-1020A), log out and log in again. Other telephones in your particular system may require different or additional procedures. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 178 Administering SES on the Avaya S8300 Server

181 User screens Permissions screen The Permissions page manages a user s control over presence, who they permit to see them on the system. This page has four versions, depending on the current setting, and every page allows the setting to be changed to the other type. Unblocked watchers are not updated until after the telephone user logs off and logs back in again. Presence cannot be matched properly if the handle of the watched user does not match exactly, including its case. Permissions screen field descriptions Current Permissions Type Note the type of Permissions that now are set for the user. The types of Permissions are Allow All, Block All, and Contact List Only. Block All is the default permission type for any user unless you specify a different type of permissions or modify the user s permissions. To modify the current Permissions type that is displayed for this user, you may use Permissions screen. Issue 2.0 May

182 Administering web interface Change Permissions Type Handle The drop-down list provides three levels of permissions: Allow All Select Allow All if you want all administered SIP users to be able to watch this user s presence and availability in the system using any presence-enabled SIP endpoint, such as Avaya IP Softphone with the IM client. Block All Select Block All if you want no administered SIP users to be able to watch this user s presence and availability in the system. Contact List Only Select Contact List Only if you want only those administered SIP users that you have added to your contact list to be able to watch this user s presence and availability in the system. After selecting the appropriate permissions type, select the Change button to commit the entry to the user contact database. Note that unblocked watchers are not updated until after the telephone user logs off and logs back in again. This is a selectable link, a valid handle for the blocked or allowed caller. Selecting the link displays the detailed user contact information for the associated user. Handles must be unique contact Uniform Resource Identifiers (URIs) within the SIP domain, but users may have several. Note: Note: If entering or changing the Handle, only provide characters for the portion in front of sign. The system automatically appends portion of the handle. Permissions screen commands Change Permissions Type Choose from the drop-down list of user-contact permissions: Allow All permits all administered SIP users to note your presence in the system. Block All permits no administered SIP users to note your presence in the system. Contact List Only lets only those administered SIP users on the user s contact list to be able to observe your presence in the system. Note that unblocked watchers are not updated until after the telephone user logs off and logs back in again. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 180 Administering SES on the Avaya S8300 Server

183 User screens Allow List/Block List Lists any users for whom there are discrete entries to Allow permission or Block permission to watch this user s presence and availability on the system. If the Current Permissions Type is set to Contact List Only, then the Allow List/Block List does not display. Instead, you may select the link to view the members who are allowed to watch this user s presence and availability in the system. If you wish to delete the Block (or Allow) permission type entry for a specific person on the list, then select the Remove link. Note: Note: If you didn t specify a domain for a user on either list, then the SIP system domain.com will be appended automatically to the user contact entry. Add Entry Use this area to add a valid user handle to one of the two permissions lists, Allow or Block. To remove a permission entry, select from the Allow List/Block List field. Note that unblocked watchers are not updated until after the telephone user logs off and logs back in again. Issue 2.0 May

184 Administering web interface Edit User Profile screen The User Profile screen contains specific demographic information about this user. This screen is originally populated by the default user profile data. This screen now supports UTF-8 encoding. You may input Shift_JIS (SJIS) characters as well. Whether the browser sends UTF-8 or SJIS is dependent upon the web browser s language setting. Edit User Profile screen field descriptions User ID This is an identifier of at least three alphanumeric characters in length. Each administered user has one unique User ID and it is used as their display name within SES adminstration. For example, the User ID is the name listed for the user on the List Users, Search User, Edit User and List Media Server Extensions screens. It is recommended that the User ID be the same as the Primary handle administered for the user. If the User ID is left blank when the user is added, it is defaulted to the Primary handle. A User ID is administered as an alphanumeric string between 3-16 characters in length. A user's User ID may be changed from their Edit User Profile screen. A user's Primary handle may only be changed from the Edit Handle screen (List Users -> Select A user -> Select Handles task). Password, Confirm Password Enter a password of at least 6 and at most 12 alphanumeric characters. Both field entries must match exactly. Host This is the name of the home server serving the domain for this user. An administrator can move a user to a different home server. In the drop-down list, select a new host for this user. The user is deleted from the original database and moved to the other home server s database. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 182 Administering SES on the Avaya S8300 Server

185 User screens First Name, Last Name This is the name of as many as 64 UTF-8 characters associated with this User ID and Handle in the user database. You may input Shift_JIS (SJIS) as well. Whether the browser sends UTF-8 or SJIS is dependent upon the browser s language setting. The name will be assigned to the speed dial button for this contact. In Japanese, this name string uses Kanji characters. (Contrast this with Alias.) Address 1, Address 2 This is the first line and second line of the default address for users. You may input Shift_JIS (SJIS) characters as well. Whether the browser sends UTF-8 or SJIS depends upon the browser s language setting. The name will be assigned to the speed dial button for this contact. In Japanese, this name string uses Kanji characters. (Contrast this with Alias.) Office City State Country Enter the designation for the user s office/floor, and so on, in alphanumeric characters. Originally populated by the information in the Default User Profile screen, you can customize it here. Enter the name of the city or town of the user s address in alphanumeric characters. Originally populated by the information in the Default User Profile screen, you can customize it here. Enter the name of the state or province of the user s address in alphanumeric characters. Originally populated by the information in the Default User Profile screen, you can customize it here. Enter the name of the country of the user s address in alphanumeric characters. Originally populated by the information in the Default User Profile screen, you can customize it here. Issue 2.0 May

186 Administering web interface ZIP Enter the number of the ZIP or postal code of the user in numeric characters. Originally populated by the information in the Default User Profile screen, you can customize it here. After entering or changing entries, select Update to submit the user s profile to the user database on this host. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 184 Administering SES on the Avaya S8300 Server

187 User screens Watchers Task The Watchers screen quickly relays the level of watch permissions this user has set. Then, with the command buttons, you can adjust that level using either the Permissions screen or the Contacts list. Note that unblocked watchers are not updated until after the telephone user logs off and logs back in. Watchers screen field descriptions Current Permissions Type Note the type of Permissions that now are set for the current user. The types of Permissions are Allow All, Block All, and Contact List Only. Block All is the default permission type for any user unless you or the user specify a different type of permission, or modify the user s permissions. To modify the current Permissions type displayed for this user, you may use Change Permissions Type field on the Permissions screen. Tip: Tip: Changing the Current Permissions Type does not interactively add or delete existing exception entries made on the Allow List/Block List. That is, if you change from Block All to Allow All, then any exceptions on the Block List remain in effect. Likewise, if you change from Allow All to Block All, then any exceptions on the Allow List remain in effect. Contact List Members This area of the screen lists members of the end user s contact list who are aware of the end user s presence, that is, who have subscribed to be updated on your presence and availability in the system. If no such users exist and are subscribed, then this field does not appear on this page. Note that presence cannot be matched properly if the handle of the watched user does not match exactly, including its case. Select the associated link to the right to Block a Contact List Member from being able to watch your presence and availability in this system. Unknown (SIP Users) Lists any SIP users not on the contact list, but provisioned in this system, and for whom you have added discrete entries to Allow permission to watch your presence. If no such entries Issue 2.0 May

188 Administering web interface have been made, this field does not appear on this page. If you wish to Block permission for a specific unknown SIP user from being able to watch your presence and availability in this system, then select the link to the right of the list entry. To change the default permissions for all SIP users, then select the Go To Permissions link and use the Change Permissions Type field on the Permissions screen. If you want to add any of the SIP users who are unknown to this system to your list of (known) user contacts, for example to watch their presence and availability, then you may select the Add to Contact List link to the right of any Unknown list member. Note that presence cannot be matched properly if the handle of the watched user does not match exactly, including the case of its alphabetic characters. Watchers screen commands Go to Permissions Select this to change the current level of permissions for the user. The system displays the Permissions screen. Go to Contact List Select this to add more contacts to the users contact list. Doing so makes the permission type of Contact List Only more inclusive. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 186 Administering SES on the Avaya S8300 Server

189 User screens Search User screen Locate any user on the system by searching on any of the fields in this screen. On the left, open up the Users menu and select Search from the sub-menus to display the Search User screen. Choose a home server on which to search. Fill in any of the fields to try and match. If any matches are found, the List Users screen that displays next shows only the matches. Search Users screen field descriptions Host User ID This is the name of the home server for this user. You must know what home server the user has assigned. By default, any is selected, which searches all the SES hosts you have administered for your enterprise. If you wish to search by ID, enter a valid User ID of at least 3 alphanumeric characters. This field allows for partial matches; enter a few characters to filter the results. A User ID is an identifier of at least three alphanumeric characters in length, used to authenticate a user to the system. Each user has one unique user ID, and the User ID is the same as the user s primary handle. A User ID may be a name or an ID number. First Name, Last Name If you wish to search by name, enter the given name or surname of the user in alphanumeric characters. (No punctuation is allowed.) This field allows for partial matches; enter a few characters to filter the results. This is the name of as many as 64 UTF-8 characters associated with this User ID and Handle in the user database. You may input Shift_JIS (SJIS) as well. Whether the browser sends UTF-8 or SJIS is dependent upon the browser s language setting. The name will be assigned to the speed dial button for this contact. In Japanese, this name string uses Kanji characters. (Contrast this with Alias.) Issue 2.0 May

190 Administering web interface Address 1, Address 2 Office City State Country ZIP If you wish to search by address, enter the first and/or second lines, respectively of the user s address in alphanumeric characters. This field allows for partial matches; enter a few characters to filter the results. This is the first line and second line of the default address for users. You may input Shift_JIS (SJIS) characters as well. Whether the browser sends UTF-8 or SJIS depends upon the browser s language setting. The name will be assigned to the speed dial button for this contact. In Japanese, this name string uses Kanji characters. (Contrast this with Alias.) Enter a designation for the user s office suite or floor, for example, in alphanumeric characters Enter the name of the city or town of the user s address in alphanumeric characters. Enter the name of the state or province of the user s address in alphanumeric characters. Enter the name of the country of the user s address in alphanumeric characters. Enter the ZIP or postal code of the user in numeric characters. Search Users screen field command Search After you ve entered the information on which you want to match in the database, select Search. The system displays the List Users screen. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 188 Administering SES on the Avaya S8300 Server

191 User screens Select User screen The Select User screen is available from the Users menu and three of its submenus: Users>Edit Users>Delete Users>Password This click path provides a quick way to select a user for the tasks above when you are certain of the user s ID. Select User screen field description User ID This is an identifier of at least three alphanumeric characters in length. Each administered user has one unique User ID and it is used as their display name within SES adminstration. For example, the User ID is the name listed for the user on the List Users, Search User, Edit User and List Media Server Extensions screens. It is recommended that the User ID be the same as the Primary handle administered for the user. If the User ID is left blank when the user is added, it is defaulted to the Primary handle. A User ID is administered as an alphanumeric string between 3-16 characters in length. A user's User ID may be changed from their Edit User Profile screen. A user's Primary handle may only be changed from the Edit Handle screen (List Users -> Select A user -> Select Handles task). Select the Edit User button to edit the profile of the user with the chosen User ID. Issue 2.0 May

192 Administering web interface Update Password screen This is the screen with which you change a user s password for them. This screen is preceded by the Select User screen that requires you to know the User ID. Update Password screen field descriptions User ID An identifier of at least three alphanumeric characters in length, used to authenticate a user to the system. Password, Admin_Password_Confirm Enter a password of at least 6 and at most 12 alphanumeric characters. Both field entries must match exactly. Update Password screen command Update After entering and confirming the new password, select Update to submit it to the database. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 190 Administering SES on the Avaya S8300 Server

193 User screens Default Profile Use of this screen usually occurs when the system is first installed and configured. Moving a user to another home server from Edit Profile screen In this procedure, first verify that the home server that is the destination for the move is fully functional. If the user has an assigned extension and the destination SES home does not have a server running Avaya Communication Manager administered, then the Move User operation cannot be completed. The move may only be completed after a server running Communication Manager is added to the destination SES home server or the user's extension is removed or freed. If your are moving a user to a home that links to a Communication Manager server with more than one CLAN IP interface, then you will be prompted to select one of the IP interfaces. Move user can also be done from the List Users screen. 1. From the Master Administration interface go to the Edit User Profile screen. 2. Select the Host field to display a drop-down menu of all home servers. The drop-down defaults to highlight the user's current home server. 3. Select another home server from the drop-down. If a home server connects to a server running Communication Manager that contains more than one server IP interface, the drop-down menu displays the interfaces from which to choose. 4. Select Update. 5. The system displays a Move User confirmation screen. 6. Press OK to accept the Move or Cancel to decline it. 7. The system performs an update and displays the Continue screen. 8. In Avaya Communication Manager on the administered server, change the SIP trunk for the extension of this user using the off-pbx-telephone station-mapping screen. 9. On the Toshiba Business Phone (SP-1020A), log out and log in again. Other telephones in your particular system may require different or additional procedures. Issue 2.0 May

194 Administering web interface Confirm Delete User screen This screen is preceded by a Select User screen that requires the user ID of the user you want to delete. Confirm Delete User screen field descriptions Confirm Delete Informs you of which user you have selected for deletion from the database. Delete Extensions Also Check this box to delete the extensions associated with this user. This user s extensions will be deleted from the user database, as well. Leave the box unchecked, which is the the default, in order to leave the unassociated extensions free for future use. Confirm Delete User screen commands OK Select OK to delete the user (and associated extensions, if applicable). Cancel Select Cancel to ignore the deletion, keeping the user and associated extension(s) unchanged. Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy. 192 Administering SES on the Avaya S8300 Server

195 Chapter 4: System Management Interface SES and Communication Manager share the System Management Interface. The System Management Interface comes with a help system embedded. For information about any System Management Interface screen not provided in this chapter, click the Help button on the screen.the screens in this chapter are SES screens that are additional to the Communication Manager screens. This section describes in detail the use and meaning of the screens in the System Management Interface. Alarms screens Diagnostics screens Server screens Server Configuration Server Upgrades screens Data Backup/Restore screens Security screens Media Gateways screen (8300) Miscellaneous screen Alarms screens Alarm screens are these: Current Alarms screen SNMP Traps screen On the S8300C, you will find these screens as well: Agent Status 8300 Server SNMP Agents 8300 Server Filters screen 8300 Server Issue 2.0 May

196 System Management Interface Current Alarms screen Current Alarms screen field descriptions Use the Current Alarms page to view a list of outstanding alarms. This page shows either a summary of alarms, if present, or a message stating that no alarms are present. Product ID ID Source Use these steps to view current alarms against the server identified by this Product ID: 1. Check if any alarms are present. If no alarms appear, continue with your web-administration activities. If yes, continue. 2. If alarms are present, the bottom part of the page shows a detailed list of outstanding alarms: This is a unique identification number assigned to the alarm. This is the abbreviated name of the software process that generated a platform alarm, as follows: ENV for environment attributes on the motherboard such as temperature, voltage, fan FSY for file synchronization GAM for global alarm manager GMM for global maintenance manager KRN for kernel LIC for license server logon for logon attempts NIC for Ethernet network interface SME for server maintenance engine TLG for trace log UPS for uninterruptible power supply USB for universal serial bus 194 Administering SES on the Avaya S8300 Server

197 Alarms screens _WD for watchdog EvtID The event identification number for each alarm is used to identify a particular event from a given source that generated the alarm. Lvl The level of the alarm is minor, major, or warning. Ack Displays a Y (yes) or N (no) to indicate whether the alarm has been acknowledged by the Initialization and Administration System (INADS). Date This is the timestamp assigned to the alarm when it occurred. Description The Description field provides a brief explanation of the alarm. Server Alarms The Current Alarms page allows you to clear (remove) some or all of the displayed alarms.! CAUTION: CAUTION: Clearing alarms only removes the alarm notifications from the active alarm list. It does not remove the conditions that caused the alarms. 1. Select one or more alarm entries. select Clear. All checked items disappear from the active alarm list. You will not receive a response if an entry is not selected before clicking Clear. 2. To remove all alarm entries from the list, select Clear All. Issue 2.0 May

198 System Management Interface Agent Status 8300 Server This screen is available on an S8300 coresident configuration. This screen is used in conjunction with a call center. The Agent Status web page shows the current state of the Master Agent and all of the sub agents. It also allows for the ability to start or stop the Master Agent. Agent Status screen field descriptions Master Agent Status The page shows the current status of the master agent: Up or Down. The Master Agent status is typically Up. You can stop the master agent to disable the capability to monitor the server using SNMP. To stop the Master Agent, click Stop Agent. The Agent Status page refreshes with a new status of Down, and the Start Agent button appears. To start the master agent click Start Agent. The Agent Status page refreshes with a new status of Up, and the Stop Agent button appears. Sub Agent Status The page shows the current status of the sub agents: FP Agent, MVSubAgent, Load Agent, and MIB2Agent. Note: The sub agents may show a status of Up however if the Master Agent's status is not Up the subagents are not connected. 196 Administering SES on the Avaya S8300 Server

199 Alarms screens SNMP Agents 8300 Server Configure the SNMP manager to interface with the telephony application from the SNMP Agents page. The SNMP Agent provides a means for a corporate network management system (NMS) to monitor the server. CAUTION: Note:! CAUTION: Caution: For the server to respond to SNMP queries, the following conditions must be present. 1) Master Agent must be running. 2) SNMP ports must be enabled through the firewall. Note: Note: Prior to making any configuration changes the Master Agent should be put in a Down state. The Master Agent status is shown below for your convenience. Once the configuration has been completed, then the Master Agent should be placed in an Up state. Changes to both the configuration on the SNMP Agents and/or SNMP Traps pages should be completed before starting the Master Agent. Please use the Agent Status page to start or stop the Master Agent. SNMP Agents screen field descriptions Master Agent Status The page shows the current status of the master agent: Up or Down. The Master Agent status is typically Up. You can stop the master agent to disable the capability to monitor the server using SNMP. To change the status of the Master Agent, use the Agent Status page. View G3-AVAYA-MIB Data Click the link, View G3-Avaya-MIB data to understand SNMP communications with the server's SNMP entities. IP Addresses for SNMP Access The SNMP agents can be programmed to accept incoming SNMP messages from a restricted list of SNMP managers. You have three selections: 1. No Access (IP addresses can not talk to agent) 2. Any IP address (includes any or all addresses) Issue 2.0 May

200 System Management Interface 3. Following IP addresses (choose up to 5 addresses) IP address1 IP address2 IP address3 IP address4 IP address5 To confirm all your options to change administration settings, click Submit. SNMP Users/Communities Under SMNP users/communities, select a SNMP Version: Enable SNMP Version 1 Enable SNMP Version 1 communicates with the SNMP agents on the server. Version 1 can be enabled and disabled independently of Versions 2c and 3. Community Name (read-only) community or user can only query for information Community Name (read-write) community or user can query agents for information (SNMPGETs) and send commands to an agent (SNMPSETs). Enable SNMP Version 2c Enable SNMP Version 2c ó communicates with the SNMP agents on the server. Version 2c can be enabled and disabled independently of Versions 1 and 3. Community Name (read-only) community or user can only query for information. If this option is activated, it displays. Community Name (read-write) community or user can query agents for information (SNMPGETs) and send commands to an agent (SNMPSETs). If this option is activated, it displays. Enable SNMP Version 3 Enable SNMP Version 3 communicates with the SNMP agents on the server. Version 3 can be enabled and disabled independently of Versions 1 and 2c. User (read-only) User Name authorizing a user to send traps to a destination is a security feature of SMNP Version 3. The user name can be a maximum of any 50 characters except (") quotation marks. 198 Administering SES on the Avaya S8300 Server

201 Alarms screens Authentication Password (for authentication and privacy) to become authenticated the user must create a password that is a minimum of 8 characters and a maximum of any 50 characters except (") quotation marks. Authentication Protocol specifies the authentication protocol in use. Privacy Password the user that is specified in "user name" must provide a password for privacy that is a minimum of 8 characters and a maximum of any 50 characters except (") quotation marks. Privacy Protocol specifies the privacy protocol in use. User (read-write) The option User read-write has the same fields as read-only. The information above also applies to (User) read-write. To confirm your options to change administration settings, click Submit. Or, continue to select more options. Troubleshooting Errors you may encounter at the Administer SNMP Agents page: Unable to Restart Master Agent. To resolve: 1. Click Process Status and verify the Master Agent is running. The Agent should be listed as UP. If so, proceed to Step 2. If the Master Agent is DOWN, a major failure occurred and requires fault isolation. 2. Go to the Agent Status page to ensure the master agent is not stopped. If it is stopped, restart it. Issue 2.0 May

202 System Management Interface SNMP Traps screen Use this Web page to configure destinations for SNMP traps or informs (alarms and notable events) on the corporate network. Some form of corporate network management system (NMS) must be in place to collect the SNMP messages. In addition, the SNMP ports must be enabled on the Ethernet interface to the corporate LAN. Note: Note: Note: Prior to making any configuration changes the Master Agent should be put in a Down state. The Master Agent status is shown below for your convenience. Once the configuration has been completed, then the Master Agent should be placed in an Up state. Changes to both the configuration on the SNMP Agents and/or SNMP Traps pages should be completed before starting the Master Agent. Please use the Agent Status to start or stop the Master Agent. Status Shows if the configured destination is enabled or disabled. IP Address Traps or inform requests (informs) are only sent to a destination if enabled. Disabling a destination keeps the configuration data in the file, but stops traps and informs from being sent. Every computer that communicates over the Internet is assigned an IP address that uniquely identifies the device and distinguishes it from other computers on the Internet. An IP address consists of 32 bits, often shown as 4 octets of numbers from represented in decimal form instead of binary form. Notification Refers to traps or inform requests as described above. SNMP Version The three final fields on this page are blank if SNMP Version 1 or Version 2c are used. Community or User Name The authentication mechanism used by the different SNMP versions. 200 Administering SES on the Avaya S8300 Server

203 Alarms screens Community Name Authentication is a plain text string used for SNMP v1 and v2c. User Name is part of the user-based security model for SNMP v3. This character string indicates the user who is authorized to send traps to the destination. V3 Security Model The level of security to use when sending v3 traps. Options are None, Authentication, and Privacy. See Add or change trap destination for details. Authentication Password (v3 only) Pass phrase for the user specified in the User Name field, used to digitally "sign" v3 traps. Privacy Password (v3 only) Pass phrase for the user specified in the User Name field, used to encrypt v3 traps. Problems displaying trap information The SNMP Trap page may display the following error: Unable to contact alarm agent: The Configure Trap Destinations page was unable to notify the server's alarm agent that the configuration file was changed. This error could occur following any add, change, or delete operation. Functions Note: Note: If changes are made on the SNMP Traps page it is recommended that a test alarm be generated to ensure that SNMP Traps are operating properly. To generate a test alarm, please go to the SNMP Test page. Add Change Select this button if you want to add a new SNMP trap. The Add Trap Destination screen is displayed. Select a trap and then click Change to modify the trap information. The Change Trap Destination screen is displayed. Issue 2.0 May

204 System Management Interface Delete Select a trap and then click Delete to remove the trap destination. The Delete Trap Destination page is displayed. 202 Administering SES on the Avaya S8300 Server

205 Alarms screens Change Trap Destination screen new When you click Add or Change on the SNMP Traps page, the Add Trap Destination or Change Trap Destination page appears. These screens are similar, except that: On the Add Trap Destination page, the data-entry fields are initially blank. On the Change Trap Destination page, the fields are populated with information for the trap you selected on the SNMP Traps page. Add or change a trap destination To add a new trap destination, or to change information regarding an existing trap: 1. On the main menu under the SNMP section, click SNMP Traps. 2. Choose the action that you want to do next: To add a new trap destination, Click Add. The Add Trap Destination page appears. All the fields are blank. To change a trap destination, select the trap destination you want to modify. Click Change. The Change Trap Destination page appears, prepopulated with trap information. When the appropriate page appears, enter or modify the information as described below. 3. To send traps or informs (acknowledged traps) click Check to Enable this Destination. 4. IP address: Enter the IP address for the workstation that has the network management software (NMS) that is to receive the trap notifications. This field is required for all versions of SNMP. 5. SNMP version: Select the radio button for the version of SNMP that the corporate NMS is running. Fill out the required information for each version: SNMP version 1: Enter a text string to provide security for SNMP messages. You can use any characters except: ` \ &, ' " (single back-quote, backslash, ampersand, comma, single quote, double quote). SNMP version 2c: Enter a notification type and community name as follows: Notification type: Select either trap or inform (acknowledged trap). See SNMP v2c and v3 inform operation for details. Community name: Enter a text string to provide security for SNMP messages. You can use any characters except: ` \ &, ' " (for example: company-snmp). SNMP version 3: Enter a notification type, user name, and a security model, plus any pass phrases required by the security model. Notification type: Select either trap or inform (acknowledged trap). See SNMP v2c and v3 inform operation for details. Issue 2.0 May

206 System Management Interface User name: Enter a text string that indicates the user that is authorized to send traps to the destination. The name can contain any characters except: ` \ &, ' " (for example: Jane Doe). Security model: Select one of the three levels of security (None, Authentication, Privacy) to use when sending v3 traps. None: no additional information is needed. Traps are sent in plain text without a digital signature. Authentication: an authentication password must be given. SNMP v3 uses this pass phrase to digitally "sign" v3 traps using MD5 protocol (associate them with the user). Privacy: both an authentication password and a privacy password must be given in order to provide user-specific authentication and encryption. Traps are signed as above and also encrypted using Data Encryption Standard (DES) protocol. Authentication password: Enter a text string at least 8 characters long to provide user-specific authentication by means of a digital signature. The pass phrase can contain any characters except: ` \ &, ' " (for example: hon3yb38r).privacy password: Enter a text string at least 8 characters long to provide user-specific authentication and trap encryption. The pass phrase can contain any characters except: ` \ &, ' " (for example: k33p58f3). Privacy password: Pass phrase for the user specified in the User Name field, used to encrypt v3 traps. 6. When you finish, click Add or Change. 7. If all information was entered and processed correctly, the SNMP Traps page appears, showing the new or modified entry. 8. If information was incomplete, an error message appears. See Problems adding or changing traps for resolution procedures. Problems adding or changing traps The Add or Change Trap Destinations screens display an error message if insufficient information is entered. To solve this: 1. Review the error message to determine the missing information. 2. Click Back on your browser to return to the previous page. 3. Enter the required information, then click Add or Change again. SNMP version-dependent information The Avaya server supports SNMP Version 1 (v1), Version 2c (v2c), and Version 3 (v3). Version-specific operation is covered in the following sections. 204 Administering SES on the Avaya S8300 Server

207 Alarms screens SNMP v2c and v3 inform operation In SNMP v2c and v3, the server can be configured to send informs. Informs are acknowledged traps, which means that the receiver of the trap is expected to respond with an SNMP message acknowledging receipt. The destination port for an incoming inform/trap on the media corporate Ethernet interface of the server is 162. The source port for this transaction is a random UDP port on this interface. If a firewall exists between the server and the inform destination, then the firewall must be configured either to allow traffic on all user-based UDP ports, or to allow sessions in which a temporary hole is punched through the firewall (the recipient of the trap needs to get the acknowledgement back through the firewall). For the acknowledgement, the source port on the server is 162 and the destination port is a random UDP port (the inverse of the what the inform had since the direction the packet is going is reversed). For each destination, the server's G3 alarm agent buffers alarms to be sent as informs; it does not send the next one until the current inform has been acknowledged. If a request is not acknowledged, the G3 alarm agent attempts the request again. This design may affect the timeliness in which alarms are reported. Also, alarms will be lost if the buffer fills up. To manage this, you can: Use traps instead of informs. Ensure that there is appropriate connectivity for the informs and their acknowledgements. SNMP v3 user-based security model SNMP v3 uses a user-based security model. If traps are sent using SNMP v3 with authentication and encryption, the trap receiver must be configured with the same user name and passwords to authenticate and to decrypt the message. If the user and the password information do not match, authentication or decryption fails and the trap is discarded. Also, in the authentication and privacy security models, SNMP v3 traps are sent using the v3 inform mechanism, but without retries the server makes only one attempt to send the trap). The v3 inform mechanism first obtains the necessary synchronization information by sending a query packet to the trap receiver. This query packet requires a response that has firewall implications. If a firewall exists between the server and the trap destination, it must be configured to let the response through. If the firewall blocks the response, the inform will not succeed and an error message will be written to the Linux syslog. Issue 2.0 May

208 System Management Interface Delete Trap Destination screen new Use this page to confirm the removal of the selected destination from the configuration file. When you click Delete on the SNMP Traps page, the Delete Trap Destination or Change Trap Destination page appears. Click on either Delete or Do Not Delete. 206 Administering SES on the Avaya S8300 Server

209 Alarms screens Filters screen 8300 Server Filters The Filters web page provides a list of available filters created using the Maintenance web pages. Filters created by other applications, for example, Fault and Performance Manager, will not be displayed. This page allows you to add, change or delete filters. These filters are applicable only for the Communication Manager Alarms and allow you to select which alarms should be sent as traps to the Trap Receiver(s) configured on the SNMP Traps page. Note: Note: If you have Fault and Performance Manager (FPM) then create the filters using that application. The FPM application provides additional capabilities that are not available from this page. The Customer Alarm Reporting Options can also be configured from this page. Note: Note: The Master should be in an Up state prior to configuring the Filters page. Master Agent Status is shown below for your convenience. Please use the Agent Status page to start or stop the Master Agent. The following information will be displayed for each filter. Severity shows one of the following seven severity options: Major Minor Warning Major/Minor Major/Warning Minor/Warning All Category and associated MO-Type are shown below: Category adm-conn announce atm MO-Type ADM-CONN ANN-PT, ANN-BD, ANNOUNCE ATM-BCH, ATM-DCH, ATM-EI, ATM-INTF, ATM-NTWK, ATM PNC-DUP, ATM-SGRP, ATM-SYNC, ATM-TRK ATM-WSP Issue 2.0 May

210 System Management Interface bri/asai cdr data-mod detector di environ esm exp-intf ext-dev generatr inads-link infc ip lic-file maint misc mmi mnt-test modem pkt pms/jrnl pnc pncmaint pnc-peer procr ASAI-ADJ, ASAI-BD, ASAI-PT, ASAI-RES, ABRI-PORT, BRI-BD, BRI-PORT, BRI-SET, LGATE-AJ, LGATE-BD, LGATE-PT CDR-LINK BRI-DAT, DAT-LINE, DT-LN-BD, PDMODULE, TDMOD- ULE DTMR-PT, DETR-BD, GPTD-PT, TONE-BD DI-BD, DI-PT AC-POWER, CABINET, CARR-POW, DC-POWER, EMG-XFER, EXT-DEV, POWER, RING-GEN ESM AC-POWER, CARR-POWER, DC-POWER, EPN-SNTY, EXP-INTF, MAINT, SYNC, TDM-CLK, TONE-BD CUST-ALM START-3, SYNC, TDM-CLK, TONE-PT, TONE-BD INADS EXP-INTF MEDPRO, IPMEDPRO, MEDPROPT, H323-SGRP, H323-BCH, H323-STN, DIG-IP-STN, RDIG-STA, RANL-STA, NR-CONN, REM-FF, ASAI-IP, ADJLK-IP, SIP-SGRP NO-LIC, LIC-ERR MAINT CONFIG, ERR-LOG, MIS, PROC-SAN, SYSTEM, TIME-DAY MMI-BD, MMI-LEV, MMI-PT, MMI-SYNC M/T-ANL, M/T-BD, M/T-DIG, M/T-PT MODEM-BD, MODEM-PT M/T-PKT, PKT-BUS JNL-PRNT, PMS-LINK DS1C-BD, DS1-FAC, EXP-INTF, FIBER-LK, PNC-DUP, SN-CONF, SNC-BD, SNC-LINK, SNC-REF, SNI-BD, SNI-PEER DS1C-BD, DS1-FAC, EXP-INTF, FIBER-LK, PNC-DUP, SN-CONF, SNC-BD, SNC-LINK, SNC-REF, SNI-BD SNI-PEER PROCR 208 Administering SES on the Avaya S8300 Server

211 Alarms screens quick-st sch-adj s-syn stabd stacrk stations sys-link sys-prnt tdm tone trkbd trkcrk trunks vc ABRI-PT, ADXDP-PT, ANL-16-LINE, ANL-LINE, ANL-NE-LINE, ANN-PT, ANNOUNCE, ASAI-ADJ, AU- DIX-PT, AUX-TRK, BRI-PT, BRI-SET, CDR-LINK, CLS- FY-PT, CO-DS1, CO-TRK, CONFIG, DAT-LINE, DID-DS1, DID-TRK, DIG-LINE, DIOD-TRK, DS1-FAC, DS1C-BD, DTMR-PT, EPN-SANITY, EXP-INTF, EXP-PN, FI- BER-LNK, GPTD-PT, HYB-LINE, ISDN-LNK, ISDN-TRK, JNL-PRNT, MAINT, MET-LINE, MODEM-PT, OPS-LINE, PDATA-PT, PDMODULE, PKT-BUS, PKT-INT, PMS-LINK, PMS-PRNT, PNC-DUP, PRI-CDR, S-SYN-PT, SN-CONF, SNC-BD, SNC-LNK, SNC-REF, SNI-BD, SNI-PEER, SYS-PRNT, SYSLINK, SYSTEM, TDM-BUS, TDM-CLK, TDMODULE, TIE-DS1, TIE-TRK, TONE-BD, TTR-LEV SCH-ADJ S-SYN-BD, S-SYN-PT ABRI-PORT, ADXDP-BD, ADXDP-PT, ANL-16-LINE, ANL-BD, ANL-LINE, ANL-NE-LINE, ASAI-ADJ, AU- DIX-BD, AUDIX-PT, BRI-BD, BRI-PORT, BRI-SET, DIG-BD, DIG-LINE, HYB-BD, HYB-LINE, MET-BD, MET-LINE ADXDP-PT, ANL-LINE, ANL-16-LINE, ANL-NE-LINE, AUDIX-PT, DIG-LINE, HYB-LINE, MET-LINE, OPS-LINE ABRI-PORT, ADXDP-PT, ANL-16-LINE, ANL-LINE, ANL-NE-LINE, ASAI-ADJ, AUDIX-PT, BRI-PORT, BRI-SET, DIG-LINE, HYB-LINE, MET-LINE, OPS-LINE SYS-LINK SYS-PRNT TDM-BUS CLSFY-BD, CLSFY-PT, DETR-BD, DTMR-PT, GPTD-PT, START-E, SYNC, TDM-CLK, TONE-BD, TONE-PT, TTR-LEV AUX-BD, AUX-TRK, CO-BD, CO-DS1, CO-TRK, DID-BD, DID-DS1, DID-TRK, DIOD-BD, DIOD-TRK, DS1-BD, IS- DN-TRK, PE-BCHL, TIE-BD, TIE-DS1, TIE-TRK, UDS1-BD, WAE-PT AUX-TRK, CO-DS1, C9-TRK, DID-DS1, DID-TRK, DI- OD-TRK, ISDN-LNK, ISDN-TRK, TIE-DS1, TIE-TRK CO-TRK, SUX-TRK, CO-DS1, DID-DS1, DID-TRK, DI- OD-TRK, ISDN-LNK, ISDN-TRK, PE-BCHL, TIE-DS1, TIE-TRK, WAE-PORT VC-BD, VC-DSPPT, VC-LEV, VC-SUMPT Issue 2.0 May

212 System Management Interface vsp wide-band wireless The MO-Type field will display the appropriate options based on the category selected. The options available in MO-Location are Media Gateway, Cabinet, Board, Port, Extension, and Trunk Group/Member. The Filter Type, which is not displayed, is always set to "Traps" in the SNMP set for filters. Configure Filters MMI-BD, MMI-PT, MMI-LEV, MMI-SYNC, VC-LEV, VC-BD, VC-SUMPT, VC-DSPPT, VP-BD, VP-PT, VPP-BD, VPP-PT, DI-BD, DI-PT, MEDPRO, IPMEDPRO, MED- PROPT PE-BCHL, WAE-PORT RC-BD, RFP-SYNC, WFB, CAU, WT-STA To add a filter, click Add. The Add Filters web page is displayed. To change a filter, select the filter you would like to change then click Change. The Change Filters web page is displayed. The fields on the Change Filters page will display the existing details for the filter selected. To delete a filter, select the filter or multiple filters you would like to delete then click Delete. A confirmation message will appear. To delete all filters, click Delete All. A confirmation message will appear. Note: Note: The Delete All option does not require any filters to be selected. All filters displayed on this page will be deleted. Customer Alarm Reporting Options This section displays the existing configuration for alarm reporting. If needed you can change the alarm reporting options Report Major and Minor Communication Manager alarms only. This option shows only the Major and Minor level alarms. Report All Communication Manager alarms. This option shows the Major, Minor and warning level alarms. 210 Administering SES on the Avaya S8300 Server

213 Alarms screens SNMP Test screen. The SNMP Test web page allows for the ability to send a test trap to the configured SNMP trap receiver(s). Note: Note: When a test trap is requested, please ensure that the configured SNMP Trap receiver(s) have received the test trap. Click the Generate Test Trap button to send a test trap. Issue 2.0 May

214 System Management Interface Restarts screen 8300 Server The Restarts page shows when the Communication Manager software was restarted and what level of restart was performed. Restart Causes is a good place to start troubleshooting. You can then track the server problem further, accessing other pages to obtain detailed information. For example, if the restart cause was a software request, it indicates a software error occurred and a software program automatically restarted the server. You can then go to the System Logs page to get more information about the error. Note: Note: The data in the Restart page comes from the restart cause history file. If the file does not exist or is corrupt, you will see a message that there has been a system failure and the system could not retrieve the necessary information. Cause Action Cause indicates why you need to restart. Restart level Initialized. The restart occurred when the system was initialized. Craft request. A user logged in as craft requested the restart through an administration session on the server. In this case, the user selected the level of restart. Internal request. The software requested the restart, usually in response to a server interchange. Internal request restarts are not initiated in direct response to an error and therefore are non-escalating. Software request. The software requested the restart. This type of restart, which happens automatically, typically occurs when the software detects an error. Restarts requested by the software may escalate to a higher level. The watchdog program is an example of a program that would send a request to restart the server. Action shows the restart level as categorized by three levels. Description 1 Warm restart. Only the Communication Manager software is restarted, and active calls remain up. Calls that were in progress during a level 1 restart are dropped. 2 Cold restart. The Communication Manager software is restarted and the translations are reloaded. During a level 2 restart, all calls are dropped. 4 Reload. The Communication Manager software is completely reloaded. All calls are dropped, the translations are reloaded, and the hardware is reinitialized. 212 Administering SES on the Avaya S8300 Server

215 Alarms screens Escalated Time Escalated indicates whether the current restart has been escalated (increased in level) from a previous level. Restarts can be automatically or manually escalated to a higher level. For example, if the software detected an error and could not resolve the error by doing a level 1 restart, it would automatically initiate a level 2 restart. In this case, the Restart Causes page would show a 2 in the Action column and a yes in the Escalated column. Shows the date and time the restart occurred. The restarts display according to when they occur, with the most recent restart appearing at the end of the list. Issue 2.0 May

216 System Management Interface System Logs screen This page enables you to select and view system log entries for the period of time you specify. You can use this page to view detailed information about network problems, security issues, system reboots, mail, and so on. Select Log Types (multiple log output will be merged) Select one log type at a time. If you select more than one, the log files merge. Log Type lm lxboot lxcron lxsys lxsec lxwtmp lxxfer wd cmds Description Log Manager Debug Trace (default): Provides information about SES hosts and High Availability Platform software such as restarts, initializations, and shutdowns, duplication status, process errors, system alarms, and communication with external gateways and port networks. The log rolls over when it reaches its size limit. Linux boot messages. Linux Scheduled Task log (CRON). Shows information from the Linux scheduling daemon. Linux Syslog. Collects all the system messages produced by the various subsystems (processes) running on Linux. Linux Access Security log. Information pertaining to logon connections to the Linux system. Actions logged in this file include opening or closing a remote session and modem messages. Linux login/logout/reboot log. Information about Linux logon and logout procedures, as well as system reboots. Linux File Transfer log. Contains information about files copied to or retrieved from the system. It indicates, among other things, the time, user, and files that were copied to or retrieved from the system. Watchdog Logs. Only the watchdog process writes to this log. It contains information about application starts, restarts, failures, shutdowns, heart beating, and Linux reboots. It also contains information about processes that use excessive CPU cycles. Platform Command History Log. High Availability Platform commands are logged to this file. These are the commands that modify the server administration or status. For all the shell commands executed on the system see the lxsys log or the bashhist view. 214 Administering SES on the Avaya S8300 Server

217 Alarms screens Log Type Description httperr httpssl HTTP/web server error log. These are errors and events generated by the platform web server and include items like web server restart, abnormal CGI script file terminations, and certificate mismatches. HTTP/web secure sockets layer (SSL) request log. These are all the requests made of the web servers SSL module. All pages requested or placed in secure mode are indicated. ccsadmin SES server Web Administration log. The last 16 administrative functions performed are in this log. Select a View Selecting multiple views may give odd results. Select one view only. If you select more than one, the Views may merge. You can define views in the log view* files, however, the following are included: View bashhist hwerr swerr Description Platform bash command history log. The list of commands run by interactive bash shells are these fields: PPID: process ID of the parent shell. PID: process ID of the shell. UID: user ID under which the shell is executing. Zero (0) means root or super user. Hardware error and alarm events. The events that go into the SES hardware error and alarm logs. Software events. The events that go into the SES server s software error log. Select Event Range Select one of the following event ranges: 1. Event ranges: Today Yesterday View entries for this date and time. Complete the year, month, day, hour, and minute text boxes as desired to focus your search. 2. Enter a 4-digit year, and 2-digit entries for the other fields as indicated. Issue 2.0 May

218 System Management Interface 3. You cannot skip fields (such as specifying a year and day but not month). Note: Note: The more information you enter, the more specific your search becomes. For example, to view all events for March 2002, enter 2002 for the year and 03 for the month. To view only the events for March 27, 2007, also enter 27 for the day, and so on. Match Pattern (Optional) To further limit your search, enter a keyword in the Match pattern field (such as a name or message type). The log will display only those entries that contain this keyword. You must check the box to the left of this field to search for entries with this keyword. Display Format Type the number of lines you want to view at one time. Select View Log to submit the requested information on this host. 216 Administering SES on the Avaya S8300 Server

219 Alarms screens Temperature/Voltage screen If your SES is on an S8300C and so co-resident with Communications Manager, check the temperature and voltage on the gateway, not the S8300. Temperature/Voltage screen field descriptions Use this page to view temperature, fan speeds, and voltage information about the server. You can quickly assess whether or not the hardware components are performing within normal ranges. If alarm conditions exist, you can take corrective action. Feature The Feature column lists the elements being measured. PCI card voltages EXT A card voltage Sample failure and alarm Motherboard (MB) voltages of power supply Fan speeds as measured by tachometer Temperatures of various areas on the motherboard.! CAUTION: CAUTION: If the temperature exceeds 50 degrees Celsius, you must adjust the room air conditioning or power off the server until the condition is corrected. To distinguish the particular condition caused an alarm, go to the and view the Linux system log (syslog) file to see the message that corresponds with the condition. The row SAMP Temp shows the temperatures used to determine if the actual temperature reading is high or low. Value The current reading of the component being measured. Crit_Low The excessively low value at which at which a major alarm is generated. Issue 2.0 May

220 System Management Interface Warn_Low The somewhat low value at which a warning alarm is generated. Warn_High Crit_High Status The moderately high value at which at which a major alarm is generated. The excessively high value at which at which a major alarm is generated. A generalization stating that the reading is either within normal limits or not. 218 Administering SES on the Avaya S8300 Server

221 Alarms screens Ping screen Ping screen field descriptions Use the Ping page to execute the ping command for information about your network. Typically, use the ping command to: Test whether or not a specified address in your network is working. Obtain information about how quickly and efficiently your network is processing data packets. Use the diagnostic information available through the command to manage your network. Host Name Or IP address Options Enter or select the host name or IP address you want to ping. Do not look up symbolic names for host addresses. Select this option to ping by IP address. If you do not select this option, the system looks up symbolic names for the host addresses. To do so, the system uses the domain name server, which translates the IP address to a symbolic name. If the domain name server is unavailable, the ping will not be successful. Bypass normal routing tables and send directly to a host. Select this option to ping a local host on an attached network. That is, select this option to bypass the routing table and ping a local host through an interface that has no route through it. If the host is not on a network that is directly attached, the ping will be unsuccessful and you will receive an error message. Execute Ping Start your ping command. If the ping is successful, the Execute Ping results page displays a brief summary that shows the number of packets sent and received. The summary also shows the minimum, average, and maximum of the round-trip times. Ping results screen When you run the ping command, a results page shows whether the command was successful or not. The following sections describe successful and unsuccessful ping results. Issue 2.0 May

222 System Management Interface Successful ping results If the ping command runs successfully, the Execute Ping results page displays a brief summary that looks something like this: PING ( ) from : 56 (84) bytes of data. 64 bytes from ( ): icmp_seq=0 ttl=245 time=6.3 ms 64 bytes from ( ): icmp_seq-1 ttl=245 time=6.3 ms ping statistics packets transmitted, 2 packets received, 0% loss round-trip min/avg/max = 0.3/3.3/6.3 ms 220 Administering SES on the Avaya S8300 Server

223 Alarms screens Unsuccessful ping results If the ping command does not run successfully, the Execute Ping results page displays an error message. Each error message points to one or more possible problems, as follows: 100% packet loss. This error message can indicate a variety of things, including: The network host is down. The host is denying the packets. The network is down. The ping was sent to the wrong address. Packets are rejected. This message indicates that the host is rejecting the packets. Packets did not reach the host. This message indicates there is a problem with the network so that the ping packets cannot reach the host. Issue 2.0 May

224 System Management Interface Traceroute screen Use this page to see the full connection path between your site and another network address. The traceroute command tracks how IP packets move through the gateways connecting the Avaya server network hardware. The traceroute command does this by launching probe packets with a small time to live and then listening for an Internet Control Message Protocol (ICMP) Time Exceeded reply from a gateway. You can use the traceroute command to evaluate the hops taken between the links in your TCP/ IP network. Hops are the short, individual trips that packets take from one router to another on the way to their destinations. Traceroute screen field descriptions Host Name or IP Address Options (Required) Enter the destination host name or IP address. Print address numerically. Select this option to print the hop addresses numerically rather than by symbolic name and number. If you do not select this option, the system looks up symbolic names for the host addresses. To do so, the system uses the domain name server, which translates the IP address to a symbolic name. If the domain name server is unavailable, the traceroute command will be unsuccessful. Bypass routing tables and send directly to host. Select this option to run the traceroute to a local host through an interface that has no route through it. That is, select this option to run the traceroute to a local host on an attached network. If the host is not on a network that is directly attached, the traceroute will be unsuccessful and you will receive an error message. Use IP address as the source address. This option lets you specify an alternate IP address as the source address. Doing so enables you to force the source address to be something other than the IP address of the interface from which the probe packet was sent. Click Execute Traceroute. 222 Administering SES on the Avaya S8300 Server

225 Alarms screens Traceroute results screen When you run the traceroute command, the Execute Traceroute results page shows whether the command was successful or not. The following sections describe successful and unsuccessful traceroute results. Successful traceroute results If the traceroute command runs successfully, the Execute Traceroute results page displays a summary that looks something like this: traceroute to server.mycompany.com ( ), 30 hops max, 38 byte packets 1 server1.mycompany.com ( ) ms ms ms 2 server2.mycompany.com ( ) ms ms ms 3 server.mycompany.com ( ) ms ms ms As shown in the example given above, the traceroute output in the first line differs from the output in subsequent lines. The following two sections describe the traceroute output. Issue 2.0 May

226 System Management Interface First line of output The first line of traceroute output describes the parameters within which the command was run. It shows: Destination host name and IP address (server.mycompany.com ( )) Maximum number of hops (30 hops max) Packet size (38 byte packets) Subsequent lines of output The subsequent lines of traceroute output describe each hop completed for the traceroute. These lines show: Hop number (1, 2, and 3) Address of the gateway computer, which is the host name, followed by the IP address. For example, server.mycompany.com ( ). If you elected to print the addresses numerically, no host name appears in the output. For example: ms ms ms ms ms ms Round-trip time to the gateway computer (for example, ms ms ms) Note: Note: Note that each hop is measured three times. If you see an asterisk (*) in the round-trip time part of the output, it indicates that a hop has exceeded some limit. Unsuccessful traceroute results If the traceroute command does not run successfully, the Execute Traceroute results page displays information about the error, as follows: traceroute: unknown host This is because the host cannot be reached. If you see an asterisk (*) in the round-trip time part of the output, it indicates that a hop has exceeded some limit. 224 Administering SES on the Avaya S8300 Server

227 Alarms screens Netstat screen Use this Netstat page to obtain information about server connections over TCP/IP. The netstat command provides statistics about the following network-related data structures: domain sockets routing tables, and Internet connections. Netstat screen field descriptions Output type View the status of network connections by listing the open sockets. Choose this default selection to view the active Internet connections, except those associated with the server processes. View all sockets. Choose this selection to view the state of all domain sockets, including those used by server processes. View listening sockets only. Choose this selection to view only those active domain sockets that are used by server processes. Display routing table. Choose this selection to view the routing table for specific IP addresses. Display networking interfaces. Choose this selection to view the kernel interface table, which provides information about the packet traffic on the network interfaces. Output format To ensure that the addresses display numerically on the results page, click Show Numeric Addresses.! CAUTION: CAUTION: If you do not select this option, the system searches for symbolic names for the addresses using the domain name server. If the domain name server is unavailable, the netstat command will be unsuccessful. Show only the following output families inet Select this option to limit the statistics or address control block reports to inet addresses. The socket type is AF_INET. UNIX Select this option to limit the statistics or address control block reports to unix addresses. The socket type is AF_UNIX, that is, local machine socket. Issue 2.0 May

228 System Management Interface Note: Note: To view results for inet and unix address families on the same page, select both options. Click Execute Netstat. Netstat results screen The information displayed in the Netstat results page depends on your output type selection using the Execute Netstat command. The sample results below combine output for inet and UNIX address families, and may not be applicable to each output type selection. Active Internet connections (w/o servers) State Local Send- Recv- Proto Foreign PID/Program Address Q Q Address name 831/ Established Srv2.:2402 tcp 0 mycom- 0 srv1:www Established Srv3:1077 tcp 0 mycom / srv1:telnet Established Srv3:1076 tcp 0 mycom- 0 srv1:telnet Active UNIX domain sockets (w/o servers) Path State Type Flags RefCnt Proto INode /dev/log DGRAM [ ] unix DGRAM [ ] unix DGRAM [ ] unix 0 The sample result given above shows output for both inet and unix address families. The following sections describe the two types of output. Output for inet address families Proto is the protocol used by the socket. Recv-Q is the number of bytes not copied by the user program connected to the socket. Send-Q is the number of bytes not acknowledged by the remote host. Local Address is the host name of the socket. Foreign Address is the remote host name and port number of the socket. 226 Administering SES on the Avaya S8300 Server

229 Alarms screens State is the state of the socket. The state might have one of the following values: ESTABLISHED. The socket has established a connection. SYN_SENT. The socket is actively attempting to establish a connection. SYN_RECV. The socket has received a connection request from the network. FIN_WAIT1. The socket is closed, and the connection is shutting down. FIN_WAIT2. The connection is closed, and the socket is waiting for a shutdown from the remote end. TIME_WAIT. The socket is waiting after being closed to handle packets still in the network. CLOSED. The socket is not being used. CLOSE_WAIT. The remote end has shut down, and it is waiting for the socket to close. LAST_ACK. The remote end has shut down, and the socket is closed. The socket is waiting for acknowledgment. LISTEN. The socket is listening for incoming connections. CLOSING. Both local and remote sockets are shut down, but all the data are still not sent. UNKNOWN. The state of the socket is unknown. Output for unix address families Proto is the protocol used by the socket. RefCnt is the reference count of processes attached via this socket. Flags is used for unconnected sockets if their corresponding processes are waiting for a connect request Type is the type of socket access, as follows: SOCK_DGRAM. The socket is used in Datagram mode (without connections). SOCK_STREAM. The socket is a stream socket. SOCK_RAW. The socket is used as a raw socket. SOCK_RDM. The socket serves reliably delivered messages. SOCK_SEQPACKET. The socket is a sequential packet socket. SOCK_PACKET RAW. The socket is an interface access socket. UNKNOWN. The socket is unknown. State is the state of the socket. For a list of possible socket states, see the description for Output for inet address families on page 226. I-Node is the associated file for this socket, shown as an I-node number. Path is the path name of the processes attached to the socket. Issue 2.0 May

230 System Management Interface Modem Test screen Use this screen to test the modem and ensure it is working properly. The modem reports Avaya server alarms (see Alarm-reporting options for details). It also enables you to dial in to an interface through which you can fix problems as they occur. 228 Administering SES on the Avaya S8300 Server

231 Alarms screens Modem Test screen field descriptions Test Options Use these steps to test the modem: 1. Select one of the following tests by clicking the corresponding radio button: Performs handshake and offhook tests. Choose this default selection to run both the handshake and the offhook tests. If these tests fail, run the handshake test and the offhook test individually to determine the reason for the failure. Resets the modem. Choose this selection to reset the modem. Performs handshake test. Choose this selection to verify that the modem is connected to the USB port and responding (that is, the drivers are functioning and the modem is sane). Performs offhook test. Choose this selection to take the modem offhook and search for a dial tone. This test is important because some configurations have two modems, one for each server, and the modems share a single analog line. 2. Click Test. Troubleshooting modem problems To verify that your modem is functioning properly, use the following procedure to test for problems. If the handshake test is successful, run the offhook test. 1. Run the handshake test. If the handshake test fails, check the modem connection to the telephone line and the server, make sure the modem is powered on, and then continue with Step Run the handshake test again. 3. If the handshake test is successful, run the offhook test. If the offhook test fails, check the modem connection line and hardware, then continue with Step Perform the offhook test again. 5. If either the handshake or the offhook test fails again, reset the modem. 6. After you reset the modem, run the handshake and offhook tests again. If you get an output message stating that the tests were unsuccessful because they failed to open a device (tty), it indicates that some other program is using the modem. In this case, check to see if someone else is using the modem. 7. If there are no problems with the connection line and hardware, restart the server. Issue 2.0 May

232 System Management Interface Network Time Synch screen This Web page displays the status of the Network Time sync command. An Network Time sync summary similar to the following is displayed. Remote displays the IP address or the host name of the reference time source, where LOCAL refers to the local clock. refid (reference ID) displays the type of the reference clock. If the value of refid is then the refid is unknown. st displays the stratum number of the reference time source. A stratum of 16 indicates the remote peer is unsynchronized. t displays the type of the peer when the last packet was received. One of the following protocols will be used: local is the local system (not a true peer). This will be active if no NTP peer is providing time-of-day sync. unicast this protocol sends messages directly to the client (Avaya server). multicast this protocol sends messages to many clients. broadcast this protocol sends messages to the entire network. when displays the count (in seconds) since the previous sync. poll displays the cycle (in seconds) when the NTP daemon queries the time from the corresponding time source. reach (reachability register) displays if a reference time source could be reached at the last polling interval, for example, data could be read from the reference time source and the reference time source was synchronized. This polling interval is an octal number. This eight bit number indicates the success/failure of the eight most recent requests. This value starts at 0. If all eight recent requests are successful then this value will be 377 (in octal). Any number less than 377 indicates that either your local server was recently started or some requests did not receive responses. delay displays the time interval (in milliseconds) to add to timestamps included in requests which require authentication. offset displays the difference between the reference time and the system clock (in milliseconds). jitter displays the magnitude of jitter between several time queries (in milliseconds). 230 Administering SES on the Avaya S8300 Server

233 Server screens Server screens Status Summary screen Use this page to quickly see everything you need to know about the status and overall state-of-health for your server. Status Summary screen field descriptions Mode SIP Role Use the Summary Status page to quickly see virtually everything you need to know about Avaya server status. For example, you can view duplication status information about both servers from this page, and see which server is in primary or backup mode. In addition, you can see the following state-of-health/status information about your server or servers. (Read-Only) This shows whether the server is primary or backup. This field shows if the server is a home, edge, or combined home/edge, a CM home or an SES home. *** Major Alarms (Read-Only) This shows whether this server has any Major Alarms, yes or no. Minor Alarms (Read-Only) This shows whether this server has any Major Alarms, yes or no. Control Network *** Server Hardware (Read-Only) This shows whether the server is okay or otherwise. Issue 2.0 May

234 System Management Interface Processes (Read-Only) This shows whether the processes running on the server are okay or otherwise. Refresh page Select Refresh page repeatedly every seconds before you click View, or the system displays an error message. 232 Administering SES on the Avaya S8300 Server

235 Server screens Server Status To view overall status information about the servers: Information about server duplication appears on the top part of the page. Information about the server's mode and state of health appears on the bottom part of the page. For detailed information about the fields on the Status Summary page, see Status Summary screen field descriptions on page 231. To refresh the page periodically: Click Refresh page every seconds. Select the number of seconds to wait before a page refresh (or accept the default value). Click View. Note: Note: You must select a value in the Refresh page repeatedly every 05 seconds drop down list before you click View, or the system displays an error message. Issue 2.0 May

236 System Management Interface Process Status screen Use the Process Status page to view status information of server applications. Each application is a collection of processes. View information about each entire application or its individual processed. You can also choose whether you want a static display or one refreshed periodically. Process Status screen field descriptions Content Summary. This default option provides information about each server application as a whole, including a count of the application processes running compared to the total number of processes available (for example, 2/16). It also shows if the application is up, partially up, or down. Detailed. This option provides the same information as the summary display, but also provides information about each of the processes associated with each server application. Frequency Display once. This default option displays the status results once in the Process Status results page. The page is not refreshed even when the status changes. Refresh page every 05 seconds. This option displays the status results every few seconds, based on the value you select from the drop-down box. Note: Note: These settings apply to both the summary and detailed displays. Click View to display the process status for all the server applications. Troubleshooting partially up processes James, Steve Adelfio This procedure is for home servers only. PARTIAL UP is an indication of the initial state of the sipserver process when these cannot get the needed SES server setup information from the database. When watching this screen for the correct progression of processes, the Partially Up status may not transition for these processes: sipserver imlogger 234 Administering SES on the Avaya S8300 Server

237 Server screens There are several possible root causes: Postgresql service is not up Postgresql service is up, but the database schema was not set up properly The database schema has been set up, but does not have the initial setup information of the SES server, such as domain information, server information, licenses, passwords, and so on. In the list above, the first and second items are unlikely if the installer had success with the initial_setup script. The third item, no or incorrect setup information, is the most common cause. Forcing a duplicated server interchange does not resolve the problem. Instead, take one of the following actions: Provide the setup information through administration screens. Check all the fields on these screens for correct information: Domain screen Server screen Host screen Configure Server screen Authentication File screen Restore the database from previous backup. Perform Force All on the edge server. This pushes the database information onto this home server. Process Status results This page displays status information for the server applications based on the selection you made on the Process Status screen. Regardless of which view you chose, status information appears for the following applications: Application Name Watchdog TraceLogger INADSAlarmAgent CCSTrapAgent Description Brings the system up, recovers from failures, and brings the system down cleanly. Creates and maintains the log files where most applications running on an Avaya SES server write messages. Sends alarms to the Initialization and Administration System (INADS) using SNMP traps defined in the INADS MIB. Acts to send Simple Network Management Protocol (SNMP) traps defined for SES. Issue 2.0 May

238 System Management Interface Application Name GMM (Global Maintenance Manager) SNMPManager ImLogger SipServer drbdeventsvc MtceMgr mon SME (Server Maintenance Engine) Description Collects, processes, and reports system-wide alarms. Acts as the SNMP trap receiver for the server. The received traps are decoded and written to the syslog. Creates and maintains the log files where the Instant Messaging application writes messages. Controls the SIP communications sessions and their associated messaging. (Is not running when in backup mode.) The distributed redundant block device synchronizes database information between duplicated servers. The Maintenance Manager monitors application alarms and mon information to determine when to interchange servers for local failover in a duplicated server configuration. Monitors system health via certain processes on the primary server. When these required processes fail to respond to mon, this signals an interchange of servers may need to occur. Tests server components periodically. The SME tests components as the result of both specific requests and asynchronous errors. Interchange Busy Out Server Release Server Interchange Servers screen This screen is seen only on duplicated pairs. Use the Interchange Servers page to make a primary server the backup, and the backup server to assume the role of the primary server. Interchange Servers screen field descriptions Force Interchange Click this check box to force the interchange between primary and standby regardless of the status of the server. If a server is out of service, it will be brought into service with this checked. 236 Administering SES on the Avaya S8300 Server

239 Server screens Busy-Out Server screen This screen is seen only on duplicated pairs. Use the Busy Out Server page to remove a server from service. Having a server busied out prevents it from taking part in an interchange, a risky situation. This screen operates on only one server in the duplicated pair. That server is identified in the upper right corner. Issue 2.0 May

240 System Management Interface Release Server screen This screen is seen only on duplicated pairs. Use the Release Server page to remove a server from a busy out operation. The one server of the duplicated pair that you release from busy out is specified in the upper right corner. This screen does not affect both servers in the pair. 238 Administering SES on the Avaya S8300 Server

241 Server screens Shutdown Server screen The Shutdown server page indicates whether the server is a primary or backup server. Also use this server page to safely bring down the server immediately or later on, and whether it reboots after the shutdown. Realize that when you Shut down this server, the web server stops the process in which you are communicating. You can not access the web pages until the system starts. Shutdown Server screen field descriptions Options to Shut down Delayed Shutdown. When you choose this option (the default), the system notifies all processes that the server will be shut down. The system waits for the processes to close files and perform other clean-up activities before it shuts the server down. Immediate Shutdown. When you choose this option, the system does not wait for processes that are running to terminate before it shuts the server down. Data may be lost. Restart Server after shutdown. Select this option to reboot after shutting down. Shutdown even if this is the primary server. Select this option if this server is the primary one. Click Shutdown to begin the process. Issue 2.0 May

242 System Management Interface Server Date/Time screen Use this page to set or adjust the time on a new or in-service Avaya server. Compare the use of this screen with Network Time Server screen fields on page 247. Server Date/Time screen field descriptions The Avaya server can use its local clock as a time source, or be synchronized with an external time source on the corporate network. If this server is using its own clock as a time source, use this page to adjust the time. General Notes on Timeserving on page 240. To use Network Time Protocol (NTP) see Configure Server on page 244. If the Avaya server is synchronizing its time with a Network Time Server (NTS) external time source, set the time using this page only during initial configuration to bring the server's time close enough (within about 5 minutes) to the NTS's time so that synchronization can occur.! CAUTION: CAUTION: If synchronization with an external time source is enabled, do not use this page to adjust the time after the server is in operation. Time changes greater than 15 minutes will disrupt the synchronization with the NTS and NTP will shut down. General Notes on Timeserving The Avaya SES software relies on the time of day setting for many functions, including these: Time stamp data elements including error logs and record files Set time-out intervals (including automatic wake-up messages and do-not-disturb intervals) Perform scheduled tasks (such as system maintenance and backups) Synchronize time of day with other processors on the network Out-of-sync timing messages are ignored, so an outsider cannot easily reset the server's clock by sending it a wildly inaccurate time. 240 Administering SES on the Avaya S8300 Server

243 Server screens! CAUTION: CAUTION: The screen displays the current time near the top of the page. If an Avaya server is synchronizing its time with a Network Time Server (NTS) external time source, you only set the time during initial configuration to bring the server's time close enough to the NTS's time so that synchronization can occur (within about 5 minutes). Do not use this screen to adjust the time after the server is in operation. Time changes greater than 15 minutes disrupt the synchronization with the NTS. Date Enter the month, day, and year. Double-check your day entry. If incorrect, the server will adjust it. For example, if you enter February 31, the server changes it to March 3 on the results page. If you do not select a year, it supplies a default year, which may not be current. Select Time Enter the hours and minutes. Time Zone Using the scroll box, choose the correct time zone for this server's location. If you reset the time zone, the server software needs to be restarted. Click Submit when you are satisfied with the settings. Issue 2.0 May

244 System Management Interface Software Version screen Use the Software Version screen to determine the software version, BIOS, and firmware an Avaya server is running. You may want to check your software version before, during, or after you install new software. This screen is also helpful during troubleshooting. w_swversion.gif Software Version screen field descriptions Operating System The release and issue number of the Linux operating system that is running on the server. For example: Linux AV15 is the release (by field: major release, minor release, development release - subrelease, Avaya release). i686 is the processor type. SES Release String The release and issue number of the Avaya software that is running on the SES server. For example: SES is the release (by field: major release, minor release, development release, Avaya build). Software Load SES is the full version of the software release name. The major release, minor release, development release, subrelease, followed by the load number, such as 018, that increments for each new software build, and the final number, an additional release number, for internal use only. Server BIOS Build ID This label shows the build ID of the BIOS of the server. This information is critical at install time, but can be checked at any time, perhaps as an aid in troubleshooting. 242 Administering SES on the Avaya S8300 Server

245 Server screens SAMP Version ID This field shows the firmware version of the SAMP or RSA remote maintenance board. This ID must be correct at install time, but you may check it at any time. If you find that your SAMP/RSA version is incorrect, use a procedure titled Verify Firmware on the SAMP module. Issue 2.0 May

246 System Management Interface Server Configuration Server Configuration items consist of these two choices: Configure Server Restore Defaults 830 only Eject CD-ROM screen Configure Server The Configure Server item under the Server Configuration section of the menu contains these screens. Some are only available if you are looking at an S8300 co-resident system: Review Notices screen Set Identities Configure Interface new 83 Configure LSP new 83 Configure Switches new 83 SET DNS/DHCJP new 83 Set Static Routes Network Time Server screen Network Time Server screen Set Modern Interface screen These screens provide a web interface to perform the tasks indicated in their name. Restore Defaults screen Use the Restore Defaults page to return an Avaya server to its factory default configuration, so the server is set up the same way as a new server shipped from the factory. Use this procedure in either of the following situations: You are installing an Avaya server that was previously configured for another system, or You chose the wrong configuration type when you first configured your Avaya server, and now you must the configuration. Resetting the server defaults causes the Choose Server page to appear. Normally, the Configure Server wizard does not display this page after a server is configured. 244 Administering SES on the Avaya S8300 Server

247 Server Configuration The following interfaces will be removed If you restore defaults, a list appears with the following interfaces that are deleted as a result. The following files will be altered If you restore defaults, a list appears with the following files altered as a result.! CAUTION: CAUTION: You must perform this procedure from a laptop computer that is connected to the services interface on the server. When the server defaults are reset, the only Ethernet interface that is operational is the Ethernet interface 1 link to the laptop. To return a server to its default configuration: 1. If the system is providing service, make sure the server you intend to configure is on standby, not active. Connect the laptop to the services interface on the Avaya server to be reset. If the services interface has been changed from its default value of Ethernet 1, the link will stop working after the server's default values are reset. However, you must initially connect to the administered link to run this procedure. 2. Log on to the server. 3. Click Restore Defaults. You see the same type of status readout as the Update system page in the Configure Server wizard. This takes about 5 minutes to complete. When it finishes, verify that all configuration information was reset without problems. If the configuration status stops at some point and the page appears to freeze, you may have lost contact with the server. The server is now ready for configuration. Issue 2.0 May

248 System Management Interface Set Static Routes Use the Set Static Routes page only if the network administrator instructs you. This person may specify a particular route for the server to send information over the network, otherwise, leave the fields blank on this page blank and click Change. Each row represents a different static network route. IP Address Enter the address of the endpoint the server is trying to reach. Subnet Mask Gateway Interface Enter the subnet mask required for the endpoint. Enter an IP address for the gateway only if this gateway is part of the static network route. Select the applicable Ethernet interface to use for this static network route, or select N/A if instructed. If no route is specified, leave the setting as N/A (not applicable). When you finish, click Change. 246 Administering SES on the Avaya S8300 Server

249 Server Configuration Network Time Server screen Use the Configure Time Server page to specify the time source that the SES server uses to set the time of day. The time of day of the server can be controlled by its local clock or it can be controlled by an external time source on the corporate network. To set the date and time on the server s local clock, use the Server Date/Time page. Network Time Server screen fields Time of Day Synchronization To specify the time source for the Avaya server, choose either Use Local Clock or Use These Network Time Servers. Use Local Clock If this server is to use its own clock, choose the Use Local Clock button and adjust the time on the Server Date/Time page. Use these Network Time Servers If this server is to synchronize its clock with a Network Time Server, choose the Use these Network Time Servers button. Upon initial server installation, adjust this server s time on the Server Date/Time page. The setting should be within 5 minutes, if possible, of the NTS's time for synchronization. Specify up to three network time servers by IP address or DNS name in the order you want the SES server to check them. Primary, Secondary, and Tertiary is the sequence in which the SES server will check the time servers. Enter IP addresses or DNS names for the primary, secondary, and tertiary servers. Leave extra fields blank if you use only one or two servers. Multicast Client Support Select Yes if the NTS routinely broadcasts its timing messages to multiple clients. Select No if the Avaya server is to poll the time directly from the NTS. Additional Trusted keys: Functions like a checksum to make sure the time packets are valid. Request key: Allows an administrator to send a remote query request. Control key: Allows an administrator to query and request changes to an NTS. Issue 2.0 May

250 System Management Interface Providing The Keys.install File For SES, no files need to be loaded. Always choose the second radio button, Do Not Install a new keys file. Install keys file from /var/home/ftp/pub/keys.install: Locate the keys.install file on your computer or network, then select Load File. The file is uploaded to the /var/home/ ftp subdirectory. Do not install a new keys file: Lengthy key files can be transferred from the network time server to the Avaya server as follows: Use the Download Files screen to transfer the file to the /var/home/ftp subdirectory. Select CHANGE to confirm the changes in the values. 248 Administering SES on the Avaya S8300 Server

251 Server Configuration Set Modem Interface screen Use the Set Modem Interface screen to enable Avaya services, or another trouble-tracking service, to monitor your SES server for alarms. Also, Services personnel can dial into this interface to fix problems as they occur. If an Avaya maintenance contract is in place, the values on this page must be provided by the Avaya services center. Set Modem Interface screen field descriptions IP Address If this system is serviced by Avaya Services, a modem IP address should already be entered in this field. If the system is not serviced by Avaya, consult with your maintenance provider for the correct IP address. Change Modem Settings Select the check box only to change to modem settings different from the factory defaults. You most likely do not need to change settings of an Avaya-recommended modem (MultiTech MT5634ZBA-USB-V92) manufactured in the United States. However, if the modem is purchased in another country, possibly its default settings are US-configured and subsequently must be changed according to the country. If you need to change modem settings, select the check box and click Continue to proceed. You will see a page beginning with the message Non-Avaya Designated Modem Found. If you decide at this time that you do not need to change modem settings, click Close Window and re-launch the Maintenance Web Interface. To proceed with changes, you must make entries in the form of AT commands in the Extra Modem Initialization Commands field. Multiple commands can be entered, each separated by a semicolon. If your modem is a MultiTech MT5634ZBA-USB-V92, you can link to the Country Commands table for the modem settings appropriate to your country. If you do not have a MultiTech MT5634ZBA-USB-V92 modem, see your modem documentation. For example, to change the country code from US to Japan, enter on this web page: AT%T19,0,10 Note: Note: The command for the United States is AT%T19,0,34, the same modem code used by many countries. Issue 2.0 May

252 System Management Interface RMB Network Configuration screen Use this page to configure IP connectivity for the SAMP installed in the server. The SAMP is a remote maintenance board for the S8500. The RMB allows remote servicing of the SES host. This board simplifies system management by providing around-the-clock remote access, independent of the main server s status. RMB Configure screen field descriptions Services Laptop These settings (LAN IP Address, Gateway IP Address, and Subnet Mask) for the local Services port on the RMB are configured automatically during server installation. They are displayed as read-only on this screen. Reserved (Services Future Use) (Optional) This section is applicable to only S8500B and S8500C servers. The LAN IP Address, Gateway IP Address, and Subnet Mask for the Services interface on the SAMP board are configured on this page. This interface can provide access to the SAMP from the customer s network. The customer s network administrator must provide the values for these settings. To modify these settings, enter new values in the three fields and select Change. 250 Administering SES on the Avaya S8300 Server

253 Server Configuration Eject CD-ROM screen Eject CD-ROM screen commands Eject Use the Eject CD ROM page to eject the software application CD. Before you eject the CD, make sure you are not running an Install New Software Release procedure. If so, click Cancel from that browser and close it. Return to the Eject CD ROM page, and click the Eject. Issue 2.0 May

254 System Management Interface Server Upgrades screens Manage Software screen Make Upgrade Permanent screen Boot Partition screen Manage Updates screen BIOS Upgarde screen Manage Software screen This is the first page of the Manage Software wizard, which is displayed in a separate browser window. Use the Manage Software wizard to upgrade the version of software that the server is running.! CAUTION: CAUTION: Complete this procedure with few interruptions to prevent the configuration information from being lost. Most information is only written to the server at the end of the process. If you quit the process (log off or time-out), the data that you entered is lost. You must access a link once every 30 minutes or the server logs you off. Once you start the configuration process you must complete all the screens in sequence. Moving around within the Manage Software wizard You must complete each screen of the wizard in sequence. If you need to move backward within the wizard you must Cancel and run the wizard again from the beginning. Running the Manage Software wizard after a session time-out All Web pages time out if the page is inactive for 30 minutes. If a page times out while you are using one of the wizards: You see a session time-out message in the main Web administration interface window. You must log in again, then click Manage Software to access the wizard. You have the option to resume the installation. A message stating that a session is already in progress is displayed. If you choose to take over the session, the wizard will return you to the screen where the installation was interrupted. 252 Administering SES on the Avaya S8300 Server

255 Server Upgrades screens CAUTION:! CAUTION: If you lose data after a time-out, it must be re-entered manually. Run the configuration procedure in one session without interruptions greater than 30 minutes. Using progress indicators Each wizard lists the steps or screens in the wizard along the left side of the window. The page that you are working on currently is highlighted. This list is provided to show your progression through the wizard. The screens listed on the left side of the window cannot be used for navigation. Working with the Manage Software wizard window When you click Manage Software in the main Web administration window, the wizard pops up in a new window on your screen. To move between this window and other windows on your computer, use the features of your computer, such as Alt+tab or the task bar. Choose task From this page, select one of the options: copy, install, or delete. Your progress through the Manage Software wizard is displayed on the left side of the window. You can return to the main browser window at any time. Note: Note: If the Web session times out, you can recover the software upgrade. To recover the upgrade, log in again. On the main menu, click Manage Software. A status display indicates the release that the server is currently running: Select the task to perform: Copy a release to the local hard drive, but do not install the release. Install one of the software releases that currently reside on the local hard disk drive. This page displays the available software releases. Delete one of the available software releases from the local hard disk drive. Note: Note: Deleting a release from the hard drive does not affect the release currently running on your system. Only three software releases are permitted on the hard disk drive of the server. Continue: Proceed with the copy, install or delete. Cancel: Close the Manage Software wizard without modifying the software release. Issue 2.0 May

256 System Management Interface Install New Software Wizard Steps/Pages Choose Software The Choose Software page is the first page of the Install New Software wizard. Run this wizard to upgrade software on the server. Install new software from a laptop computer in the server room, an administration computer over the network, or a remote computer using a PPP dial-up connection. Install new license or authentication files to install new software. To select software for installation, click one of the radio buttons to find the software files. For example, Note: Release SES R5.1 in the FTP directory on the server's hard drive. Note: The software_releases subdirectory on the server's hard drive, contains the current software load that the server is running, and is used only to reinstall the current software. Release SES R in the CD-ROM drive of the server Click Continue to finish the installation, or Cancel to stop the process. Note: Note: If the system cannot locate software installation files, an error message appears. To resolve this: If you have a CD-ROM containing new software, make sure it is installed in the drive of the Avaya server that you are currently logged into. If Avaya remote services copied new software to the server, a copy should exist in the FTP directory on both servers. Choose License Source You must have a software license file before you install this software release. If you do not have this file available, use tools in the main window to transfer it to the system. DO NOT continue this installation until it is available. 254 Administering SES on the Avaya S8300 Server

257 Server Upgrades screens Select a source for the license files: I will supply the license files myself when prompted later in this process. I want to reuse the license files from the currently active partition on this server. It is not normally necessary to update the authentication information, but if the new software documentation instructs you to, you may update it as well. Do not update authentication information. Update authentication information as well as license information. Click Continue to proceed. Click Cancel to cancel the install. Review Notices What you need to know about the Install Software Wizard: Install New Software wizard: Use this to upgrade the software running on the server. Access this wizard from the Maintenance interface item Server Upgrades. Moving backward or forward in a wizard The wizards are used serially. If you change any data: Install New Software wizard: Cancel the installation wizard, and run it again. This is the safest way to prevent possible problems. The first time you run this wizard, a lot of data are entered manually. If you need to change something you entered on a previous page: - Use your browser's Back button to page back through the Configure Server screens. - Check or change the item. - Always click Continue to move forward, whether you change anything or not. If you do not do this, information in the wizard may not be processed correctly. You can (if desired) cancel the Software Wizard, and run it again from the beginning. Running the wizard after a session time-out All Web pages time out if left inactive for 30 minutes (see Log Off). If this occurs while you are using one of the wizards: 1. You see a session time-out message in the main web administration interface window. 2. You must log in again, then: Install New Software wizard: You have the option to resume the installation. When you click the Install New Software Release link, you see a message saying that a session is already in progress. If you choose to take over the session, the wizard will return you to whatever point the installation was interrupted. Issue 2.0 May

258 System Management Interface! CAUTION: CAUTION: If you lose data after a time-out, you must re-enter the data manually. Run the configuration procedure in one session without interruptions greater than 30 minutes. Using progress indicators Each wizard lists the steps (screens) in the wizard along the left side of the window. The page that you are working on currently is highlighted. This listing is provided to show your progression through the wizard. The screens cannot be used for navigation (to back up or move forward in the wizard). Working with the wizard window When you click the Install New Software in the main web administration window, the wizard pops up in a new window on your page. You can switch between this window and other windows on your computer using the features supported by your computer, such as Alt+tab or your computer's task bar. Begin Installation Use the Begin Installation page to verify your software installation options before you begin the installation. To start the installation: 1. Review the software and license file information on the page to make sure it is correct. If you need to make any changes, click Cancel and run the Install New Software wizard again. Once you verify the information is correct, go to Click Continue to proceed. At this point, the server: Copies the currently active software to the inactive partition. Unpacks the new software files and copies them to the inactive partition, and prepares the server to reboot from the new software. This preserves any translations and modifications made to the active software. This takes several minutes, and the status appears on the Install in Progress page. 256 Administering SES on the Avaya S8300 Server

259 Server Upgrades screens Install in Progress This Install in Progress page displays the status of the server copying and unpacking software files, and preparing to reboot from the new software release. The Reboot Server page automatically appears when this process is complete. During the installation-preparation phase, choose either of the following options, if available. The button options on the page change as the installation progresses: 1. Refresh. Update the progress display instantly. If you click Refresh, the status of the software installation is instantly updated and reported to the page. If you do not click Refresh, the status of the software installation is updated and reported to the page every few seconds. 2. Cancel. This button only appears if the software installation fails. If you see this button: Review the progress information for clues about why the installation failed. Click the Cancel button to close the Install New Software window.! CAUTION: CAUTION: If the software installation fails or you cancel it, the partially installed software release remains on the server's hard disk. You will see this entry the next time you access the Choose Software page. If the software did not install correctly, you must install it from the original. If you cancelled the installation, install this software again. Reboot Server At this point in the software installation, all new software files have been copied to the inactive partition on the server's hard drive. When you reboot the server, the partition containing the new software will come up as the new active partition. This is the final page that appears before the new software is installed.! CAUTION: CAUTION: When you reboot the server to install the new software, service may be interrupted. Reboot Procedure Before you reboot the server: 1. Check the message at the top of the page to verify that the software was copied successfully. If the copy was successful, go to Step 2. If the page indicates any problems, see Problems during software installation. Issue 2.0 May

260 System Management Interface 2. Understand the impact that this software installation may have on current telephony service, summarized in Service impacts below. If you are working on the primary server and a backup server is available, Interchange Servers now to minimize any impact on call processing. If the server you are upgrading is not yet in service, it will give you a primary server warning. Proceed in spite of this warning. 3. Make sure you are ready to reboot the server. This is your last chance to Cancel the software installation. If you want to make any changes, click Cancel now, then run the Install New Software wizard again. If you are ready, click Continue. While the server is rebooting, you will not be able to access any web administration interface screens. Service Impacts When you click Continue to install new software: If you have only one Avaya server (no operational backup server is installed) all calls will be dropped, and service will be unavailable for up to 15 minutes while the server reboots. If you are working on the primary server and a backup server is available, service will continue as follows: - The servers will automatically interchange. Some transient (non-stable) calls in progress may be dropped when this happens. - Service is now available on the new primary server. The server that you are logged into becomes the current backup server. - The current backup server is now busied out, then rebooted to install the new software. - If you are working on the backup server, call processing is unaffected during the 15 minutes that the server needs to reboot. If for some reason the primary server attempts to interchange during this period, it will be unable to do so, and service may stop until the reboot completes and this server is made primary. 258 Administering SES on the Avaya S8300 Server

261 Server Upgrades screens Reboot in Progress When you reboot the server, it can no longer communicate with the web administration interface. The Reboot in Progress web page remains on your page until the reboot completes. While the server reboots: 1. The Reboot in Progress page displays an initial reboot message, then pauses until the reboot is complete and the server is ready to proceed. Allow up to 15 minutes for the reboot to complete. Although the Continue button is visible, do not click it yet. See step Optional. To check status during a reboot, you may try the following: 3. Ping the server by name or IP address using a ping program on your computer. Use the option to run the ping continuously. When ping can find the server, basic data communication through the physical connection is in place. The other services will be starting up shortly. 4. Open a PuTTY session on your computer and try to access the server by name or IP address. When PuTTY responds, the software has started up and the web pages will be available soon. 5. When the reboot should be complete, click the Continue button. If the reboot is complete, the Install License Files page appears. Run some basic software verification tests before proceeding. When basic tests are complete, return to the Install New Software wizard window and continue with the software installation. If you click Continue and nothing happens, the reboot may not yet be complete. Wait a couple of minutes for the Install License Files page to appear. Occasionally your Continue request may time out and you'll see a Can't Access The Server warning. If this happens, either: Reload or refresh the web page to submit the Continue request again, or Click the browser's back button to return to the Reboot in Progress page, then click Continue again. When the Install License Files page appears, proceed.! CAUTION: CAUTION: If the reboot is unsuccessful, the following may happen: An error message may appear and the server comes up running the previous version of software. The server may simply cease to respond. Issue 2.0 May

262 System Management Interface Install License Files This Install License Files page display varies on the option you chose from the Choose License Source page: Supply files when prompted. You must upload the correct software license and Avaya authentication files to the server using screens in the main web-administration interface window. Copy files from duplicated server. If the duplicated server already has the correct copy of the software license and Avaya authentication files, the files are automatically copied from there to the correct directory on this server. If this copy procedure fails, see Problems during software installation. Reuse files on the primary partition of this server. No new license and authentication files are needed. This page does not appear. Click Continue to proceed to install the license files. Installation Complete The software is now installed. It must be verified for correct operation, then made permanent. To complete the software installation process: 1. Review the information on the page to verify that the new software was successfully installed. 2. Click Close to exit the Install New Software wizard window. 3. Verify software operation and make the server upgrade permanent. 260 Administering SES on the Avaya S8300 Server

263 Server Upgrades screens Make Upgrade Permanent screen This Make Server Upgrade Permanent screen is the last step required for completing the installation of a new software release. It sets up the server to reboot from the currently primary (new) software version, instead of rebooting to the previous version. You do not need to change the server status to backup. Because the Install New Software wizard must be run on each server to upgrade it, you need to use this page on each server after you complete a software installation. If you do not commit the new software release (make it permanent), then the next time the server reboots, it runs the previous software version. Any new translations you made to the new release will be lost, and the new software must be installed again. You should commit the new software to operation when you are satisfied that it is functioning. 1. To make a new software release the new permanent version, click Submit. 2. Check that the request to commit the new software (make it permanent) completed correctly. If the commit procedure succeeded, continue working with the web administration interface as needed. If the commit procedure failed, the server has a software problem. Contact Avaya services. Boot Partition screen field descriptions The hard drive on every Avaya server reserves two partitions for system software. Use the Partition Status page for diagnostic purposes to find out the software version installed in each partition of the server's hard disk. Additionally, you can determine which software version is currently active and which partition will become active when the server reboots. Issue 2.0 May

264 System Management Interface Partition Status To view the status of the server's hard disk partitions: Physical Partition This column identifies the two physical areas of the disk drive that are reserved for system software: Hard drive A (hda) is the only hard disk drive in the Avaya server. The server's operating system lists the partitions on the disk by device file name (for example, hda1 and hda6). There is no correlation between the active and inactive partitions between the two servers. For example, assume that both server 1 and server 2 are running the same software on active partition hda1. If server 2 experiences a problem and is replaced with another server, the new server could come into service running its active software on hda6. Service is not affected in any way. Software Release This column shows what software release is installed in each partition. The currently active software and the pre-upgrade version both appear. Boot Partition This column indicates whether or not the server will run this version of software when the system is next rebooted. For a system in service, the boot partition is normally the same as the active partition. To make the boot and active partitions match, use the Make Upgarde Permanent screen.. If the software has not been made permanent (a software upgrade has not been completed), the status and the active partition are not the same. Active Partition This column shows the software that is currently active on this server. Partition status states The following tables show how the partition changes during a software installation. 262 Administering SES on the Avaya S8300 Server

265 Server Upgrades screens Stable system Before a software upgrade, the server software setup looks like this: Partition Software release Reboot next from here Currently active 1 Pre-upgrade version yes yes 6 Previous version (if any) no no Software installed but not made permanent This server is running the new version of software. The pre-upgrade version remains intact on the previously active partition. It is flagged as the version to run on the next reboot, in case there is a problem with the new software. Partition Software release Reboot next from here Currently active 1 Pre-upgrade version yes no 6 New software version no yes Return to stable state As soon as verification testing is complete, the Make Server Upgrade Permanent page commits the new software to operation. When the server reboots, it runs the new software. Partition Software release Reboot next from here Currently active 1 Pre-upgrade version no no 6 New software version yes yes Reboot. If you click Reboot, the system performs a one-time boot to the standby partition. WARNING:! WARNING: Switching the boot partition shuts down the server. Any translations and messages saved since the last partition switch will be lost. Issue 2.0 May

266 System Management Interface Manage Updates screen This page allows you to manage the updates for this server. This page displays the current release that is running on this server. Also displayed are the updates available for this server only. Update ID. The unique update identifier. Status. The current status of the update, i.e. activated, unpacked, etc. Type. Either "hot" or "cold," where cold means the update is service-affecting, hot means the update is not service-affecting. This page prompts the user to continue if the update is of type "cold." There are several options for managing the updates. Select an update and then select one of the following buttons: Unpack. This unpacks the update file - the update file is read from the update repository (/ var/home/ftp/pub). View. This displays the information about the update file. Activate. This activates the update. Deactivate. This deactivates the update. Remove. This removes the update from the server. If the update is in an "unpacked" state and exists in the update repository, the update will show as "packed" once the "unpacked" version is removed. Select the "packed" update and click remove to completely remove the update file. 264 Administering SES on the Avaya S8300 Server

267 Server Upgrades screens BIOS Upgrade screen 8300 Server This page allows a new BIOS to be flashed into ROM.! WARNING: WARNING: When upgrading the BIOS, it is important that the process is NOT interrupted. Interruptions could come from any of the following: loss of power, machine being physically reset, or a reboot. This list is not comprehensive and great care should be taken to make sure the upgrade process is not interrupted. If this process is not completed successfully, it is possible that the computer will become inoperative, and will require the manufacturer to repair it. It is recommended to perform a backup of the system using the Backup Now link from the left menu before proceeding. This page is intended only for use with Avaya provided BIOS upgrades. 1. Select the BIOS Upgrade file from the drop down list. If the BIOS Upgrade file you want to install is not listed, use the Download Files page to download the BIOS file to the server. 2. Click Start to begin the BIOS upgrade. A confirmation screen with a warning about interrupting the process is displayed. To continue with the BIOS upgrade click OK. A progress screen is displayed while the upgrade is running. If the upgrade was successful the server must be rebooted for the changes to take effect. Click Continue to proceed to the Shutdown Server page to reboot the server. If the upgrade was not successful, an error message is displayed. For example, "Digital signature verification of the BIOS upgrade file failed. BIOS updating is only supported for Avaya provided BIOS upgrade files." Issue 2.0 May

268 System Management Interface Backup Now screen Backup both the Master Administrator interface subsystem on the edge server, and the home server to back up all user data. Backup Now screen field descriptions Use this page to immediately back up system data after the server is installed. Additionally, run the backup before changing your system. This ensures that the most recent data are backed up, including new data since the last scheduled backup. Data Sets User Data (Database) Files. Choose this selection to back up the administered information for user contacts in your system. Server and System Files. Choose this selection to back up the variable information to configure the server for a particular installation. Security Files. Choose this selection to back up the variable information to maintain security for the server. Backup Method SCP Secure Copy Protocol. SFTP Secure FTP. Choose this selection to send the backup data as an attachment to an . When you choose this selection, you must also enter a user name, domain name, and mail server name. Note: CAUTION: Note: Do not exceed the size of file your mail server can handle.! CAUTION: If you choose to back up data using , the server software is unable to determine whether or not this backup method succeeds. Additionally, you cannot restore the file unless you move it to a location where it can be restored via a PuTTY client. Alternatively, you could place the attachment on the server using a PuTTY client and then restore it using the local directory option. 266 Administering SES on the Avaya S8300 Server

269 Server Upgrades screens Local CompactFlash card. Using USB flash memory for your backup files has several advantages: - The host server controls the flash memory. The backup process does not depend on the availability of other servers. - You can physically remove USB memory and place it in off site storage for safe keeping. However, flash memory has limited storage space. Also, if it is not sent off site to be stored, it could easily be lost because of fire, flood, or other causes. Retain Data Sets at Destination. Input the number of data sets you need to back up. Format CompactFlash Card. Flash memory must be formatted before you can store information. You only need to format once because formatting again results in losing data. You can also format flash memory separately using the Format PC Card /Compact Flash screen on page 276. Encryption If you want to encrypt the backup data, click the box in the Encryption area of the page and enter a pass phrase using an arbitrary string of 15 to 256 characters. The pass phrase can contain any characters except the following (single quote, back slash, single backquote, quote, percent sign): ' \ & ` "%! CAUTION: CAUTION: We strongly recommend that you encrypt the backup data. Create a password with a combination of letters, numbers, spaces, and special characters in the pass phrase to make it difficult to guess. You must remember the pass phrase because you cannot restore the data without it. Click Start Backup. The Backup Now results screen displays a message indicating the backup is underway. To check the results of the backup, click Backup History. The Backup History screen displays. It provides a list of the most recent data backups (15). Backup History screen field descriptions This page lists the 15 most recent backups. 1. Select one of the backups to review details. The following explains the parts of the backup file name: 1 lzccs Where lzccs1=server name, =backup time (hhmmss)-date(yyyymmdd), and 5179=PID (process ID uniquely identifying this backup). 2. To review backup history, click Check Status. Issue 2.0 May

270 System Management Interface Schedule Backup screen When scheduling a backup, backup both the Master Administrator subsystem on the edge server and the home server to back up all user data. Schedule Backup screen field descriptions The backup procedure runs automatically, based on the schedule you create. Use the Schedule Backup screen to create and view backup schedules. From the Schedule Backup page, create a new backup schedule, change a backup schedule, and delete a backup schedule.! CAUTION: CAUTION: When scheduling the backups, follow the general rules that apply to backup procedures. Be sure to schedule the backups to run outside of peak times when call processing on the server is at a minimum. Data set The data copied during the backup procedure are the variable information used to configure the system for a particular installation. This information falls into the following three categories of data, known as data sets: User Data (Database) Files User data (database) files refers to data entered in the system for SIP users and associated contacts. Server and System Files Server and system files refers to data entered by the service technician or system administrator and used to configure the server for a particular installation, such as the server names, server IP addresses, and routing information. Security Files Security Files refers to data such as logon IDs, passwords or Access Security Gateway keys, firewall information, and file monitoring data bases. Day Year, month, and day the backup was run. 268 Administering SES on the Avaya S8300 Server

271 Server Upgrades screens Time Status Hour, minute, and second the backup was run. Shows whether the backup was successful. Destination Indicates how the data were recorded. It corresponds to the backup method used for the backup. Possible destinations are: SCP, SFTP, FTP, , and local PC card. Issue 2.0 May

272 System Management Interface Add a backup schedule Back up both the Master Administrator subsystem on the edge server and the home server. Although you view SIP PIM data from the Master Administrator interface on the edge, those data reside on the home. Backing up the home separately assures you of having a complete data set. Each home server needs to have it s own backup schedule created. To create a backup schedule, you first decide what type of data you want to back up. Indicate the days and time you want the schedule to run, and the destination to which you want the backup files sent. To create a backup schedule: 1. In the Add New Schedule page, select the type of data you want to back up by selecting the appropriate data set. If backups are already scheduled, the page lists the current backup schedules. Look at it carefully to determine what backup schedule you want to add. If this is the first backup schedule to be created, the Schedule Backup page displays a message that there is no record of any backup schedule. 2. Select a backup method to indicate the destination to which the system sends the backup data. 3. If you selected local PC card as your backup method, indicate how many copies of the selected data sets you want to retain by entering a value in the small text box at the bottom of the Backup Method area of the page. We recommend that you retain two copies of all data sets selected for backup. 4. If you want to encrypt the backup data, click the box in the Encryption area of the page and enter a pass phrase using an arbitrary string of 15 to 256 characters. SECURITY ALERT:! SECURITY ALERT: We strongly recommend that you encrypt the backup data. You must remember the pass phrase because you cannot restore the data without it. 5. Select the days of the week by clicking the appropriate check boxes, and select the hour and minute you want the backup procedure to start by selecting a time from the drop-down boxes. You can select multiple days but only one time for the backup schedule to run. Click Add New Schedule to save the schedule you just created. The system displays the Schedule Backup page, which adds the new backup schedule to the bottom of the schedule list. 270 Administering SES on the Avaya S8300 Server

273 Server Upgrades screens Change a backup schedule You can change the days and time an existing backup schedule runs. You can also change the destination to which the system sends the backup data. Backup both the Master Administrator interface subsystem on the edge server and the home server to back up all user data, including SIP PIM data. 1. On the Schedule Backup screen, select the radio button next to the backup schedule you want to change. 2. Click Change at the bottom of the page. The Change Current Schedule screen displays the information for the backup schedule you selected in Step Make the changes you want to the backup schedule. 4. Click Change Backup Schedule to save the schedule you just created. The system displays the Schedule Backup page, which lists the changed backup schedule. Remove a backup schedule To delete an existing backup schedule: 1. On the Schedule Backup page, click the radio button next to the backup schedule you want to delete. 2. Click Remove at the bottom of the page. The backup schedule you deleted is removed from the list displayed in the Schedule Backup page. Backup Logs screen field descriptions Data Set When you back up data, the system creates an image as a tape archive file that contains information, such as what data sets were backed up, whether or not the backup was successful, and how the data were recorded. Use this page to view a log of backup images for all the backups you have run. If appropriate, you can then restore the corresponding backup data. Indicates what data were recorded. Possible sets are: User Data (Database) Files, Server and System Files, and Security Files. Issue 2.0 May

274 System Management Interface File Size Date Time Status Physical size of the backup file. Year, month, and day the backup was run. Hour, minute, and second the backup was run. Shows whether the backup was successful. Destination Indicates how the data were recorded. It corresponds to the backup method used for the backup. Possible destinations are: FTP, , and local PC card. Steps to preview or restore backup data Click one of the following buttons: 1. Scan the log until you see a backup image to preview or restore. Select it by clicking the radio button to the left of the image. 2. If no entries exist in the backup log, you will see a message that there is no record of any backups. 3. Click one of the following buttons: Preview. Use the Preview button if you are not sure you have selected the correct backup image. When you click Preview, the system displays a brief description of the data associated with the backup image. Restore. When you click Restore, the system displays more detailed information about the backup image you selected and then displays a page that tells you whether or not the restore procedure is successful. You must select a backup image before you click Preview or Restore, or an error message appears. To clear it, simply click the browser's Back button, then select a backup image to preview or restore. If the data you want to restore were backed up using , or if the data were backed up using a PuTTY client, but the FTP server does not allow reading, the file to be restored must first be 272 Administering SES on the Avaya S8300 Server

275 Server Upgrades screens copied to this server with FTP or a PuTTY client or with a download function. Once the file is copied to this server, it can be restored. Restore data using Data Backup/Restore onto the machine from which it was originally backed up. For example, do not be restore data onto Machine A that was backed up from Machine B. Ezra View/Restore Data screen field descriptions If your system malfunctions and you lose data, the saved data from the backup can restart the system. Copy the data to the server from the location where saved. Restore a backup image, which is a tape archive (tar) file that contains backed-up data. Network Device SCP Secure copy protocol SFTP Secure FTP Before transfer of the backup image, the server must first log on to the FTP (if it is enabled on the server), the SCP, or the SFTP server. You must also enter the following information: User name. Enter the name anonymous if you are using an anonymous account. Otherwise, enter your real user name. Local directory Password. If you are using an anonymous account, you will typically enter your address as the password. However, you should check with the FTP server administrator to verify this. If you are not using an anonymous account, enter your real password. Host name. Enter the DNS name or IP address of the FTP server on which the data were backed up. Use the dotted decimal notation to enter IP addresses (for example, ). Directory. Enter the path name for the directory in which the data are stored on the FTP server. Contact the FTP server administrator if you have questions. Choose this selection if you know the backup image was saved to a local directory. You must enter the path name for the directory. The default directory is /var/home/ftp/pub. Local PC card Using USB flash memory for your backup files has several advantages: Issue 2.0 May

276 System Management Interface The server controls the flash memory, therefore, the backup process does not depend on other available and accessible servers. You can physically remove USB flash memory for off-site storage. However, flash memory has limited storage space. Also, if it is not sent off site to be stored, it could easily be lost because of fire, flood, or other causes. Click View to ensure the correct backup image is selected. Click Restore to begin. The system displays a View/Restore Data results page indicating whether the restore procedure is successful. 274 Administering SES on the Avaya S8300 Server

277 Server Upgrades screens Restore History screen Restore History screen field descriptions This page lists the 15 most recent restores. 1. Select one of the restores to review details. The parts of the restore file name are defined as follows: 1 lzccs Where lzccs1=server name, =backup time (hhmmss)-date(yyyymmdd), and 5179=PID (process ID uniquely identifying this backup). 2. To review restore history, click Check Status. Issue 2.0 May

278 System Management Interface Format PC Card /Compact Flash screen Flash memory must be formatted before you can store information. New memory requires only one formatting procedure. If the flash memory contains data, it is erased if you format it again. Click Format. You are prompted whether you want to format. Click Yes to continue with the format. Note that you may also format the flash memory in conjunction with the Backup Now screen by checking the check box for Format Compact Flash. Avaya requires the use of industrial grade compact flash media. For more information, see Hardware Description and Reference for Avaya Communication Manager ( ). 1. Connect the compact flash drive to the USB port. 2. Insert the compact flash media into the drive. 3. Go to the Maintenance screens, and select the Backup Now screen. 4. Select all applicable data sets. 5. To back up the data onto the compact flash media, select Local CompactFlash Card. To format new media, also select Format PC Flash You must format the compact flash media before the first use only. 6. Click Start Backup. The system displays a message when the format is completed, which takes approximately 10 seconds. If you click Start Backup without media in the compact flash drive, you cause a system error. In this case, repeat the steps beginning with Step To view the status of the backup, click Backup Status. Format PC Card results screen The results of your PC card format displays. 276 Administering SES on the Avaya S8300 Server

279 Server Upgrades screens Administrator Accounts screen 8300 Server The Administrator Accounts series of pages allow you to manage local logins (accounts) on this server. Note: Note: Logins that are authenticated in an external server such as an LDAP server cannot be managed from this page. Types of logins There are three types of logins, REMOTE logins, CDR logins, and ADMINISTRATIVE logins. REMOTE logins can only be used to establish a PPP session with this server via its modem interface. REMOTE logins cannot be used to access a shell, a SAT, CDR records, or the server web pages. ADMINISTRATIVE logins are used to access a shell, a SAT or the server web pages but cannot be used to establish a PPP session and cannot be used to acquire CDR records. A CDR login is used specifically to retrieve CDR records stored on this server and cannot be used for any other purpose. REMOTE logins When creating a REMOTE login you must specify a name (login ID), but you cannot specify group membership or select a shell. REMOTE logins cannot be changed to an ADMINISTRATIVE or CDR type of login. The REMOTE login must be deleted and a new login created. CDR logins When creating a CDR login you must enter CDR_user as the login group and leave the additional groups field blank. ADMINISTRATIVE logins ADMINISTRATIVE logins are used to administer the server via a shell, the SAT interface or the server web pages. The access provided to an ADMINISTRATIVE login is controlled by whether or not the login is assigned a shell and the access profile assigned to the login. The access profile is assigned by assigning an "additional group" to the login. Types of Linux Groups Access Profile Group Issue 2.0 May

280 System Management Interface An access-profile group identifies a user profile that administers access to the SAT interface and the server web pages. Non-access Profile Group A non-access profile group administers access to files and directories on the SES server. User Profiles A user profile consists of two parts, an identifier and a set of permissions for an application. The identifier is a number from 0 to 69 inclusive. The identifier is assigned to a login by assigning the login to a group whose group number is 10,000 through 10,069. That is, the user profile is determined by "group number minus 10,000". (The 10,000 base value can be changed via the Web Access Mask page.) The group name does not matter, technically, as long as the group number is in the proper range. However, it is best to use a name of the form profnn where nn is the group number; for example, prof22 for the group corresponding to access profile 22. Prof22 would be assigned the group number 10,022. Although the group names do not matter in terms of permission assignment, there is one case where naming the group as described is beneficial. If the base value (10,000) is changed via the Web Access Mask page, that page will search for groups named in this manner and convert the group numbers to the new base. Groups not named in this manner would not be converted. The second part of a user profile is the permissions within an application. There are two applications that recognize profiles, the SAT interface and the web interface. The permissions for each application are defined independently. The SAT form "change user-profile" is used to set the SAT permissions for a user-profile) and the web form, Web Access Mask, is used to set the permissions for the web interface. A login may be assigned to EXACTLY zero or one access-profile group. A login may NOT be assigned to more than one user profile. If a login is not assigned group membership in the range 10,000 to 10,069, that login will not have access to either the SAT or the server web pages. Note: Note: User profiles 0-17 are reserved and should not be assigned to a login; such logins will not function properly. Profiles 18 and 19 are also reserved and cannot be changed. Profile 18 corresponds to what was formerly known as customer-super-user and profile 19 to customer-non-super-user. Profiles 18 and 19 may be assigned to a login as desired. Multiple logins may be assigned to the same profile. When assigning group membership to a login, either the group number or the group name may be entered. However, the group must already exist before this assignment can be made. Creating an administrator account (login) Select a name for the login. Enter a "login group" as: 278 Administering SES on the Avaya S8300 Server

281 Server Upgrades screens "users" for a login with limited access. This type of login was formerly known as a customer non-super-user login. "susers" for a privileged login. Susers logins have wide permissions in the server and assignment of these logins should be limited. Note: Note: Before a group can be assigned to a login, the group name must already exist. Assign an access profile via the "additional groups" field. If the login will not need access to either a SAT or the web pages, then this field can be left blank. Assign the type of shell this user will have. Note: Note: Assignment of no shell access limits the direct access to a shell on login. If this user should not have shell access, ensure they are assigned a SAT profile with shell access (go shell) disabled or are not assigned to any profile. Fill in the remaining fields on the add login form. The PASS_MAX_DAYS, PASS_MIN_DAYS, PASS_WARN_DAYS and days to lock apply only to this login and only as the login is being created. If a license for ASG is not present on this server, an attempt to create an ASG protected login will fail. Define the permission in the SAT for the user profile if this is a new profile. Define the permission on the Web Access Mask page for web access if this is a new profile. Deleting login groups Do not delete a login group if any login is assigned to the group. File synchronization File synchronization will distribute the following files to all the servers in the configuration: /etc/passwd /etc/shadow /etc/group Therefore, when a login or group is created, that login and/or group will eventually appear on all servers in the configuration. The user's home directory will be created (/var/home/user-id) as necessary. However, the content of the user's home directory is not file synchronized. Note: Note: Web access masks can also be file synchronized. This action must be initiated manually from the Web Access Mask page. Issue 2.0 May

282 System Management Interface Login Reports screen 8300 Server The Login Reports series of pages allows you to generate reports for local host logins administered on this server. The reports can be generated for all local host logins or for an individual local host login. Local host logins are the logins whose credentials are maintained on this server. If you are using an external Authentication, Authorization and Accounting (AAA) server, then the credentials for those logins are maintained on the external AAA server and cannot be viewed from this page. Note: Note: Your login may not have permission to view all the data for a particular login. If this is the case, the page will display "access denied" for that information. Select List Local Host Logins to generate a report for all local host logins. Select Display Information for Local Host Login and enter the individual login name to generate a report for the individual local host login. Click Continue to generate the report. List local host logins This page displays information on all the local host logins administered on this server. An example is provided in List Logins screen. Local host logins are the logins whose credentials are maintained on this server. If you are using an external Authentication, Authorization and Accounting (AAA) server, then the credentials for those logins are maintained on the external AAA server and cannot be viewed from this page. All the local host logins are displayed. Some of these logins are system logins and should never be changed or removed. Changing or removing system logins could render the system inoperable. Name: The name of the local host login. Type: The type of login, for example "pw" is a password protected login, and "asg" is a login protected by the Avaya Access Security Gateway method of one-time passwords. Note: Note: A blank in this field either indicates you do not have permission to view this information or this login is a system login. Group: The name of the primary Linux group assigned to the login. Profile: The name of the access profile assigned to the login (if any). Shell: The path to the login shell for the local host login. 280 Administering SES on the Avaya S8300 Server

283 Server Upgrades screens Note: Note: If this field contains "/sbin/nologin" then the local host login does not have shell access from the Linux perspective. This path is not related to and does no affect access to a shell via the SAT "go shell" command, which operates independently from this page. Locked (ASG, Shadow, PAM): The locked status of the login. Status of each login can be Yes or No. If a login is not an ASG login, N/A is displayed for the ASG portion of this field. Expires (Passwd, Account): The date the password and account expires. If the password or account does not expire, "never" is displayed. Display login information This page displays login information for a single local host login. Local host logins are the logins whose credentials are maintained on this server. If you are using an external Authentication, Authorization and Accounting (AAA) server, then the credentials for those logins are maintained on the external AAA server and cannot be viewed from this page. If a field listed on the page displays "Access Denied" then your login does not have permission to view this information. Group Name: The name of the primary Linux group assigned to the login. Profile Name: The access profile assigned to the login, if any. Other Groups: The names of all the Linux groups that this login belongs to, including the primary group and profile group. Authentication: The password protection status of the login, for example "pw" is a password protected login, and "asg" is a login protected by the Avaya Access Security Gateway method of one-time passwords. Note: Note: A blank in this field either indicates you do not have permission to view this information or this login is a system login. Locked logins There are three different ways a login might be "locked." A locked login cannot be used to log into the system. Shadow Locked: The standard way to lock a Linux login. A special character is put in the /etc/ shadow file. If the login has this mark in the /etc/shadow file the login is locked and cannot be used. Issue 2.0 May

284 System Management Interface Note: Note: Logins that are ASG protected will have the /etc/shadow entry permanently locked. The ASG login does not have a password but uses an ASG secret key that is stored in other system files. ASG logins are usable when the shadow file is locked. ASG Account Lock: Since ASG protected logins have their /etc/shadow file permanently locked, another mechanism is used to lock these logins. If the ASG login has been locked, "yes" is displayed in this field. If the login is not an ASG login, "N/A" is displayed. Pam_Tally Locked: If the pam_tally module has been enabled, and if the user has entered too many incorrect passwords in a row, the login will be locked for a short period of time. The amount of time the login is locked is set in the pam_tally parameters. Shell: The path to the login shell for the local host login. Note: If this field contains "/sbin/nologin" then the local host login does not have shell access from the Linux perspective. This path is not related to and does no affect access to a shell via the SAT "go shell" command, which operates independently from this page. Home: The home directory for this user, typically /var/home/"user-name". PW Min Days: The minimum number of days between password changes. PW Max Days: The number of days a password may exist before the user is required to change it. A in this field indicates there is no limit. PW Warn Days: The number of days prior to password expiration the user is given a warning to change their password. PW Last Change: The date when the password was last changed. PW Next Change Allowed: The date when the user may next change their password. PW Expires: The date when the password will expire. This field displays "Never" if the password does not expire. Account Expires: The date when the entire account will be disabled. On this date the entire account will become unusable regardless of the password expiration date. This field displays "Never" if the account does not expire. Last Login: The date when the user last logged in. 282 Administering SES on the Avaya S8300 Server

285 Server Upgrades screens Modem screen Use the Modem screen to allow the server's modem to accept one, unlimited, or no incoming calls. The modem s call-receiving status can be changed to control access to the Avaya server. Modem screen field descriptions Modem Administration To check or change the call-receiving status of this server's modem: Disable modem. Choose this option to prevent all incoming calls. The modem can still report server alarms, but no one can dial in on this line. Enable modem for one incoming call. Choose this option to allow only one incoming call. This option is typically used before a remote services procedure is done at a site where the modem is usually disabled for incoming calls. Enable modem for unlimited incoming calls. Choose this option to allow unlimited incoming calls. The modem is available to support remote services personnel, provided they know the correct access information. To select one of the options, click Submit. Issue 2.0 May

286 System Management Interface Solving modem problems Modem problems: 1. No modem found - modem access disabled. The modem for this server is not installed or has been disconnected. Connect the modem and try again. 2. Modem currently in use - try again later. The modem is currently engaged in a call. Do the following: Try this operation again. If one of the servers was reporting an alarm, the line should be clear. If the line is busy, find out who is using the modem. If Services personnel are logged in, the line could be busy for some time. However, ensure that an authorized user is using the line. 3. Modem NOT enabled - error. This message can occur if you try to enable the modem to accept unlimited incoming calls if the mgetty process (in charge of the modem) does not start. To solve this: 4. Wait a few seconds, click Enable/Disable Modem on the main web administration menu to see if the mgetty process is running. 5. If a modem access set for multiple calls but currently disabled message appears, the mgetty process is still not running. Go to If no error message appears, select Enable for unlimited incoming calls. 7. Disable the modem, select Enable for unlimited incoming calls. If the modem NOT enabled - error message appears again, there is a serious problem. The system should be examined by services personnel. Modem access set for multiple calls but currently disabled. The mgetty (modem program) process is not running, although the server has been set to accept unlimited incoming calls. To solve this, follow the same steps as for 3 modem NOT enabled - error, above. 284 Administering SES on the Avaya S8300 Server

287 Server Upgrades screens Server Access screen 8300 Server The Server Access Web page lets you enable or disable various services on the Avaya server. When enabled, the selected service allows the communications application running on another computer or server to access the server. In order to use a service, the service must be enabled and the firewall must be enabled for that service. Make your server access selections and click Submit. Issue 2.0 May

288 System Management Interface Syslog Server screen 8300 Server This page allows you to select logs to be sent to an external syslog server. By default control logging to an external syslog server is disabled. Only one server may be specified. The following logs may be sent to the external server: security log command history log CM IP events log kernel, boot, cron, *.emerg logs If the server is a duplicated server, you may file sync the syslog.conf file to the standby server and all ess/lsp servers. 286 Administering SES on the Avaya S8300 Server

289 Server Upgrades screens License File screen 8300 Server Use the Install page to install a new license file on the Avaya server, or to undo up to three previous license installations. Undo Last Install Whenever a new license is installed, the existing license file (if any) is saved. Up to 4 licenses (1 current and 3 previous licenses) can exist on one system at a time. If a license file is installed and you want to return to the previous license, select the "undo" option. This option deletes the current license file, and reinstalls the license file that was previously in use. Use this option if the new license file is not working correctly. Up to three Undo operations can be carried out sequentially. You cannot undo the installation of the only remaining license file. The Undo operation operates backwards; you cannot undo an Undo because the current license is erased when the previous license is installed. Install the license file I previously downloaded A new license file (with.lic extension) is moved from the /var/home/ftp subdirectory on the server hard disk and installed on the system. The existing license file, if present, is saved for a possible "undo" operation. If the installation fails, the old license file remains in the /var/home/ftp subdirectory for debugging purposes. Install the license file specified below This option lets you download the license on your computer from the URL. For the file path, browse to the directory where you want to install. Enter the URL where the license file is located, and complete the proxy server information. Issue 2.0 May

290 System Management Interface Solve license file installation problems Errors you may encounter Invalid version on install file <filename>. The license file named <filename> is corrupted (damaged) or has a version mismatch. Invalid License file error nnn. The content in the license file is corrupted (nnn is the error code). License file not in <filename>. The file named <filename> does not contain the correct content. Multiple or no.lic files in directory /var/ home/ftp Solutions to fix errors Transfer a new license file to the server. Access the Install License page again, and select Submit. Transfer a new license file to the server. Access the Install License page again, and select Submit. Transfer a new license file to the server. Access the Install License page again, and select Submit. Telnet into the server and navigate to the /var/ home/ftp directory. Search for license (.lic) files. If no.lic file is present, copy a current license file into this directory. If multiple license files are present, delete those that are not needed, and keep only the one that is valid (usually the newest one). Access the Install License page again, and select Submit. 288 Administering SES on the Avaya S8300 Server

291 Server Upgrades screens Authentication File screen At install time, the installer probably downloaded the authentication file to the directory /var/ home/ftp/pub on the SES server. If the authentication file is there, choose the first radio button, Install the Authentication file I previously downloaded. If the authentication file is on the local network, specify the path to the file's location. Choose the second radio button, Install the Authentication file I specified below button, and then click Install. Specify a URL and proxy server if the file is on a remote network. w_authentication.gif Authentication File screen field descriptions File Path URL Only enter data in this field if you choose the second radio button. This field specifies the file path to the authentication file that is not typical for a SES system. Only enter data in this field if you choose the second radio button. Enter the URL where the authentication file resides. Proxy Server Only enter data in this field if you choose the second radio button. If you need to specify a proxy server to the URL entered above, name that server here. Authentication File screen commands Install the Authentication file I previously downloaded If you select this radio button, do not type any information in the fields below. The SES system has a record of the location of the authentication file. Issue 2.0 May

292 System Management Interface Install the Authentication file I specify below Install If you select this radio button, fill either the Path field, or the URL and Proxy Server fields to indicate where the authentication field resides. You may not need to specify a proxy server, depending on your situation. Submit the information. 290 Administering SES on the Avaya S8300 Server

293 Server Upgrades screens Firewall screen Use the Firewall screen to enable or disable network services on the corporate LAN interface to the Avaya server. You can activate or deactivate these services as needed to control features or access to the server. Your changes to this interface do not affect services on the other Ethernet interfaces. Leave FTP and telnet sessions unchecked to maintain a high level of security. Clear the box for FTP or telnet, receive an incoming file transfer, and then recheck the box. This page is a front-end to the standard Linux command ipchains. Ipchains is used to set up, maintain, and inspect the IP firewall rules in the Linux kernel. These rules can be divided into four categories: the IP input chain, the IP output chain, the IP forwarding chain, and user-defined chains. This page only allows administration of the input chain. The output chain and forwarding chain are set to the value accept. There is no user-defined chain.! CAUTION: CAUTION: The IP services that are checked on the Firewall page are already enabled. To disable IP services, you must deselect the service. Be careful about disabling common IP services, it may adversely affect your Avaya server. Firewall screen field descriptions Input to server The IP service you select for incoming server communications. This selection can be different from outgoing server communications. Output from server The IP service you select for outgoing server communications. This can be different from incoming server communications. Service A list of names of the most commonly used IP services. Their current status is shown: either enabled (checked) or disabled (check box clear). These are standard Linux services. For details on their operation and use, refer to published Linux documentation. FTP-data: Used with FTP. One channel controls the connection to transfer data, and the other channel controls the data transfer. Issue 2.0 May

294 System Management Interface File Transfer Protocol (FTP): Used for uploading or downloading data files, announcements, license files, or firmware. Secure shell (SSH): A secure shell (SSH) remote interface utility can be used as an alternative to telnet. Telnet is no longer supported. SSH commands and passwords are encrypted, and both ends of the client/server connection are authenticated through a digital certificate. The SSH suite includes a secure copy (SCP) program that can be used as an alternative to FTP. The SSH and SCP utilities provide greater security than FTP and telnet, and should be used if available. Telecommunications network (telnet):no longer supported. Simple Mail Transfer Protocol (SMTP): supports service across the web. Domain Name Service (DNS): runs on port 53/tcp and 53/udp. The server uses DNS to resolve host names. For example, if you back up to an FTP server and name it, the port must be open for the server to execute a DNS query to find the IP address of the server name. Network Time Protocol (NTP): allows the server to synchronize its time with an external time source. Secure Hypertext Transport Protocol (HTTPS): A secure extension to HTTP that encrypts all messages between the web server and a browser. It also uses a digital signature to authenticate users and servers. Ping: permits any ICMP requests to be echoed back. You have the option to select this common service. Port/Protocol This column shows what port on the Ethernet interface this service uses, and what protocol it uses. Common protocols include Transmission Control Protocol (TCP) and User Datagram Protocol (UDP). To check or change the services that are allowed on the corporate LAN Ethernet interface: To disable an IP service: Clear the check box to disable this service on the corporate LAN interface. To enable an IP service: Check the box to activate a service on the corporate LAN interface. To view all IP services: Click Advanced Setting to adjust the status of a service that is not listed on the first page. The system redisplays this page, listing all the Linux IP services available for this Ethernet interface.! CAUTION: CAUTION: The changes you input on the basic settings page are erased when you click and move forward to the Advanced Setting Web page. 292 Administering SES on the Avaya S8300 Server

295 Server Upgrades screens Tripwire screen field descriptions Tripwire Status Disabled If tripwire is disabled, a status message informs you. Enabled If Tripwire is enabled and a signature database does not exist, another web page prompts you to add a tripwire database. 1. To add a tripwire database, click Yes. If you select No, a page appears indicating the tripwire is disabled and a signature database will not be created. 2. If tripwire is enabled, a status indicates tripwire is enabled with Fast Audit and frequency, Full Audit and frequency, or both. Audit Frequency Fast Audit Scheduled to run every 15 minutes, 30 minutes, 1 hour, 2 hours, 4 hours, 8 hours and 12 hours. A cron job is created in /etc/cron.d. Audits that run at 15 and 30 minute intervals are started on the.-hour, for example: *:00, *:15, *:30, and *:45 for 15 minute intervals and *:00 and *:30 for 30 minute intervals. The audit does not begin immediately but starts at the next time interval hourly, quarterly, half-past, or three-quarters past the hour Hourly audits are run at 3 minutes past the hour (for example: 12:03) as specified in twcron. Scheduled to run hourly, daily, or weekly. When a full audit is scheduled a cron job is created in /etc/cron.daily, /etc/cron.hourly, or /etc/cron.weekly depending on the standard time selected. It is run at the time specified in /etc/crontab for the corresponding frequency. Full Audit The standard times are: hourly jobs: one minute past the hour, for example, 12:01 daily jobs: 4:02 a.m. weekly jobs: 4:22 a.m. on Sundays To submit your selection, click Submit. Issue 2.0 May

296 System Management Interface Tripwire Commands screen If Tripwire is enabled on the server, this screen provides a list of tripwire audit reports with the most recent 250 audits. Select one of the audit reports to review its details. Click Submit. The following explains the parts of a tripwire audit report: baccarat twr Where server name=baccarat2-date the server is audited (yyyymmdd)-time the server is audited (hhmmss), and.twr identifies the report as a tripwire audit report If tripwire is disabled, the following command appears: View tripwire report To submit your selection, click Submit. 294 Administering SES on the Avaya S8300 Server

297 Server Upgrades screens Install Root Certificate screen 8300 Server Use the Install page to install an Avaya root certificate on your computer to establish Avaya Inc. as a trusted Certificate Authority (CA).! CAUTION: CAUTION: The instructions below are only applicable to Netscape Navigator 6.2x. Other versions of Netscape are different and may require more steps to download. Similarly, different versions of Internet Explorer may require different instructions. Internet Explorer 1. From the File Download dialog box, click Open. Do not save this file to disk! 2. From the Certificate dialog box, under General tab, click Install Certificate. The Certificate Manager Import Wizard guides you through the process. 3. Accept all default values.on the final page, wait for the install to complete, click Finish. A Root Certificate Store message may appear. 4. Click Yes to add the certificate to the Trusted Root Certification Authorities store. Issue 2.0 May

298 System Management Interface SSH Keys screen Secure Shell is a security program to log in to another computer over a network, to execute commands from a remote machine, and to move files from one machine to another. The program features authentication and secure communications over insecure channels. It is a replacement for rlogin, rsh, rcp, and rdist. When using ssh's slogin (instead of rlogin) the entire logon session, including transmission of password, is encrypted; therefore it is almost impossible for an outsider to collect passwords. Current SSH public keys The keys currently installed on your computer are displayed. Generate New SSH Keys To generate new SSH keys, make a selection, and click Generate SSH Keys. RSA keys for SSHv2 RSA keys for SSHv2 For more detailed information about SSH, visit: Authentication File screen on page Administering SES on the Avaya S8300 Server

299 Server Upgrades screens Web Access Mask screen The Web Access Mask page allows you to further restrict individual logins in the SUSERS and USERS login groups based on membership in a secondary Linux login group. Access mask base displays the current profile base number.! CAUTION: CAUTION: Changes to the profile base affect Communication Manager access also. Access Masks and Names There are two types of access masks, default and user-defined. Default fixed masks are 0-17, 18 and 19 and may not be edited. User-defined access masks and names may be modified by the user. Default access masks are: Mask Name 0-17 System profiles 18 Customer Super User 19 Customer Non-Super User You may add, change, delete or view the user-defined access masks. Each mask applies to a specific secondary Linux login group. Commands Add: Click Add to add a new mask. This will bring up the Add Access Mask page. Change: Add or remove check marks in existing access masks, then click Change to update the masks you selected. Delete: Add or remove check marks in existing access masks, then click Delete to remove an existing mask. This will bring up the Delete Access Mask page. View: Add check marks in existing access masks, then click View to view the properties of the access masks selected. View All: Click View All to view the properties of all user-defined access masks. Select All: Click Select All to select all user-defined access masks listed on this page. De-Select All: Click De-Select All to de-select all user-defined access masks listed on this page. Filesync: After the profiles have been added, changed or deleted you must click Filesync to update the LSP and/or ESS servers on a duplicated system. Issue 2.0 May

300 System Management Interface Configuration Screen From this page, launch a device manager associated with a media gateway to enter another network that transmits messages over local-area and wide-area networks.! CAUTION: CAUTION: JRE 1.3 must be first installed to launch the G700 Gateway Device Manager. Then, install JRE 1.4 to launch the G350 Gateway Device Manager. Copies are available at the URL For more information, read Technical Note at support.avaya.com. Name The name of the Media Gateway (MG). MG plus one of four digits identifies the different gateways. Click Launch Device Manager or, Device Manager If you select a G350, the Device Manager launches a java applet and prompts for a logon and a password. If you select a G700 MGP IP address from your Web browser (see steps below), a Logon and Password Web page appears. Provided is information to access the G700 processor, as well as the password and the logon for the stack processor. The associated device manager launches, and you enter this logon and password. Indicated is the IP address of the Device manager for the media gateway. For G350s, the IP address is the same as the IP address field. If the value is NA, the device manager is not recognized. Computer Configuration and Device Manger In the media gateway configuration, your computer is connected to one of the following: The services port of the Communication Manager server. A remote connection. Note: Note: For reasonable loading times from remote access, the appropriate bandwidth should be maintained for acceptable computer connection responses. 298 Administering SES on the Avaya S8300 Server

301 Server Upgrades screens A server that is restricted from accessing the device manager. If you can't access the device manager, follow the steps below: 1. From you browser address line, browse to and select the G350 IP address. The G350 Device Manager launches and prompts for a logon and a password. 2. From your browser address line, browse to and select a G700 MGP IP address, a Logon and Password Web page appears. Provided is information to access the G700 processor, as well as the password and the logon for the stack processor. The associated device manager launches, and you enter this logon and password. Issue 2.0 May

302 System Management Interface File Synchronization screen 8300 Server The File Synchronization feature enhances updating multiple LSPs because it reduces bandwidth between them and relevant primary controllers. Note: Note: The synchronization only applies to translation files. When the S8300 server acts as a primary controller or as a target in LSP mode, it computes and outputs translation file differences through a DIFF file. If more than one target is being synchronized, the sequence is standby server (if present) and then LSPs. Five LSPs can be synchronized simultaneously. Note: Note: Details for the most recent file synchronization are logged to /var/log/ecs/ filesync.log To continue to the next Web page, choose an option: View Current Status of File Synchronization-summary A brief summary of the synchronization View Current Status of File Synchronization-details In-depth details of the current synchronization View History of Past File Synchronization Summary of previous file synchronizations 300 Administering SES on the Avaya S8300 Server

303 Server Upgrades screens IP Phones screen 8300 Server The IP Telephone Configuration Application lets you save custom settings for your IP (Internet Protocol) phones. Create, edit, and save settings in a configuration data file (46xxsettings.txt file) supplied by the system. Note: Files used to operate your IP phones must be downloaded before you install a new IP telephone or upgrade an existing telephone. Follow the instructions at Download Files. Click Phone Settings to go to the IP Telephone Configuration page. Issue 2.0 May

304 System Management Interface Download Files screen Use this screen to download files onto the Avaya server from another server across the network using HTTP protocol. Typical files to download include new license or authentication files, firmware upgrades, or keys.install files, all which may be used with network time servers. Download Files screen field descriptions Prerequisites To use the Download screen, the server must be able to access the: Corporate LAN. and typically its DNS server, for network routing and name resolution. Web server(s) in the selected URLs reference File(s) to download from the machine I'm using to connect to the server To download files from your machine to the server: 1. From the Download Files page, click Browse or enter the path to the file that resides on your machine. Specify 1 to 4 files to download. 2. When finished, click Download. Or, if you need a signed file, at the bottom of the screen, select the option Install this File on the Local Server, and then click Download. Note: Note: This signed file must be a.tar file. For example, /testfile-1-1.i386.rpm.tar File(s) to download from the LAN using URL To download files from a web server to the Avaya media server: 1. Specify 1 to 4 files to download by Universal Resource Locator (URL) address. 2. Specify the complete URL. For example, keys.install 3. If a proxy server is required for an external web server (not on the corporate network), it must be entered in a server:port format. Enter the proxy server's name (such as network.proxy) or IP address. 302 Administering SES on the Avaya S8300 Server

305 Server Upgrades screens If the proxy server requires a port number, add a colon (:) followed by a port number. The default proxy port is When finished, click Download. Or, if you need a signed file, at the bottom of the screen, select the option Install this File on the Local Server, and then click Download. Note: Note: The signed file must be a.tar file. For example, testfile-1-1.i386.rpm.tar Install this file on the local server Use the Install this file on the local server option to download when you are instructed. This option allows you to download and install signed files. The file must be signed. Follow Avaya instructions to obtain your signed file. If you do not select the option, the files are retained in the /var/home/ftp/pub directory location, and are not installed and signatures are not verified. However, files used for server upgrade could be downloaded without verifying the signatures. Issue 2.0 May

306 System Management Interface CM Phone Message File screen 8300 Server The Communication Manager software supports foreign language phone messages though the installation of a unicode message file. The software processes, stores, and transmits foreign language text to Unicode-enabled stations in the same way English text is transmitted. If you have not installed the Unicode Message File, a message indicates it is not available. Avaya Standard File: This file (avaya_unicode.txt) is a direct download to a server that can not be edited by customers. Custom File: This file (custom_unicode.txt) can be downloaded to customer personal computers, edited, and later uploaded to a server. Click the appropriate file, and Install. This action invokes a message indicating the language installed on the message file. 304 Administering SES on the Avaya S8300 Server

307 Server Upgrades screens Tftpboot Directory screen 8300 Server Use this page to determine whether the latest firmware versions are installed for the G700 processors and media modules. This page enables you to compare the already installed software with the contents of the /tftpboot directory. When the S8300 is upgraded, new versions of firmware for the G700 processors and media modules may be delivered to the /tftpboot directory on the S8300 hard drive. If firmware is delivered that is newer than the firmware installed, the newer version should be installed on the G700. To determine if delivered firmware is more current than the installed version, compare the firmware version numbers listed on this page with the installed version numbers. Use the following procedure to view the installed firmware versions. To check the version of installed firmware: For the P330 Stack Processor (EW_Archive): 1. At the P330-1 (configure) prompt, type dir. A table of software appears. 2. Find the number (n.n.n) in the Ver Num column for EW_Archive. 3. Compare this number with n.n.n in P330Tweb.n.n.n.exe in the /tftpboot list. For the P330 Stack Processor (SW_Archive): 1. At the P330-1 (configure) prompt, type show image version. A table of software appears. 2. Find the number (n.n.n) in the Version column for the "Avaya G700 Media Gateway" in the active bank (A or B). NOTE: The version for the inactive bank will have version number Compare this number with n.n.n in viisan.n.n.exe in the /tftpboot list. For the MGP and media modules: 1. At the MG-00x-x (configure) prompt, type show mg list_config. A table of firmware appears. 2. Find the number (n) in the FW Vintage column. (NOTE: n can be one or more numerical digits) Issue 2.0 May

308 System Management Interface 3. Compare this number with n from the following table: Type Code File Name in /tftpboot G700 DAF1 mgp_n_n.bin (MGP) DS1 MM710 mm710vn.fdl ANA MM711 mm711vn.fdl DCP MM712 mm712vn.fdl BRI MM720 mm720vn.fdl VOIP MM760 mm760vn.fdl If the version number in the /tftpboot list is greater than the version number for the corresponding installed firmware, the firmware should be upgraded. 306 Administering SES on the Avaya S8300 Server

309 Server Upgrades screens Serial Numbers screen 8300 Server Use this page to view the serial number for the G700 Media Gateway that is hosting this S8300 media server. This serial number must match the one in the license file in order for Avaya call processing to work correctly. To view the serial number for the Media Gateway that is hosting this S8300 media server: port network MGP serial number. The serial number of the Media Gateway Processor (MGP) installed the G700 Media Gateway that is hosting this S8300 media server. license key. An asterisk (*) indicates that this is the serial number that must match the license file in order for call processing to work correctly. If an error message indicating that the license server query failed appears, go to the Process Status page to verify that the license server process is running. If the license server is not running, you may need to reboot the server to start it. When finished, continue your administration activities as needed.! CAUTION: CAUTION: If the query is unsuccessful, you will see an error message indicating that the license server query failed. In this case, you should go to the Process Status page to verify that the license server is running. If the license server is not running, reboot the server to start the license server. Issue 2.0 May

310 System Management Interface SES Software screen 8300 Server This only applies to a system with the SES component installed. This page provides the functionality to either enable or disable the SES component. The status of SES is displayed on this page. If the status of the SES is enabled, the Disable SES button appears. If the status of the SES is disabled, the Enable SES button appears. Click either Disable SES or Enable SES to change the status of the SES component. 308 Administering SES on the Avaya S8300 Server

311 Server Upgrades screens Messaging Software screen 8300 Server From the Internal Messaging page, you can turn on the internal messaging application Communication Manager Messaging application. Note: Note: You MUST purchase the S8300 license file that provides the Communication Manager Messaging application. Otherwise, the messaging data types listed below do not appear on the System Management Interface. From the System Management Interface screens, Backup Now and Schedule Backup, you must select a messaging data type to manually back up or to schedule automatic backups. The data types are: Announcements Translations and Messages Translations, Names, and Messages Translations and Names Translations Scheduled Backup Scheduled Backups do not require human intervention; however, you must ensure that the FTP or the mail server to which Communication Manager Messaging backs up information has adequate storage space. CAUTION:! CAUTION: Depending on the number of subscribers, the number of announcement sets, and the amount of data storage, one full system backup requires 300 MB data storage or more. This is in addition to the data backed up for the S8300. The system creates a new file based on the date and time the backup is run which prevents overwriting a previously stored backup file. Issue 2.0 May

312 System Management Interface 310 Administering SES on the Avaya S8300 Server

313 Appendix A: Feature requirement specifications These sections in this appendix explain how SES rules are applied: Call processing software Call processing software Call processing software is explained in sections covering domains and routing: RFC 3325 compliance RFC 3325 compliance The material in this book is based on regulatory compliance of RFC 3325 compliance. Compliance with RFC 3325 The SES proxy complies with RFC 3325, Network Asserted Identity. While RFC 3325 provides for a privacy header, this header does not provide complete anonymity to the user. The privacy header only requires that the p-asserted-identity header be removed from the request. FNU requirements The following sections describe how Feature Name URI (FNU) requirements are implemented. In the column heading, PPM denotes Personal Profile Manager. Call Forwarding All Calls FNU on page 312 Call Forward Busy - No Answer FNU on page 313 Directed Call Pickup FNU on page 315 Extended Call Pickup FNU on page 316 Calling Party Number Block FNU on page 316 Calling Party Number Unblock FNU on page 317 Issue 2.0 May

314 Feature requirement specifications Dial Intercom FNU on page 318 Drop FNU on page 318 Exclusion FNU on page 319 Off-PBX Call FNU on page 319 Last Number Dialed FNU on page 320 Malicious Call Trace FNU on page 320 AUDIX One-Step Recording FNU on page 321 Priority Call FNU on page 321 Send All Calls FNU on page 322 Transfer to Voice Mail FNU on page 323 Whisper Page Activation on page 324 Call Forwarding All Calls FNU This FNU Activates or deactivates Call Forwarding All Calls. Case 1 FNU structure where Call Forwarding All Calls, of the endpoint s own (1111) extension: INVITE sip:[email protected];avaya-cm-fnu=call-forwarding-all;avaya-cmdestination= ;avaya-cm-action=on SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=call-forwarding-all;avaya-cm-action=on SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=call-forwarding-all;avaya-cm-action=offsip/ 2.0 Name Values Req/Opt PPM avaya-cm-action on or off Req No avaya-cm-destination Any number within the Communication Manager dial plan, to which this endpoint is being forwarded. Opt No Authorization: This example shows the use of this FNU on the endpoint s own extension. It must be authorized by the extension s class of service. See the next case for how to apply this feature to another extension. Communication Manager button: call-fwd Ext: (left blank) Feature package: Yes 312 Administering SES on S8300

315 FNU requirements SDP required: Only if avaya-cm-action=on and avaya-cm-destination not specified. (if SDP required, line appearance must be requested otherwise line appearance request will be ignored) Case 2 FNU structure where Call Forwarding All Calls, of another endpoint s (2222) extension. INVITE sip:[email protected];avaya-cm-fnu=call-forwarding-all;avaya-cmdestinat ion= ;avaya-cm-action=on SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=call-forwarding-all;avaya-cm-action= on SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=call-forwarding-all;avaya-cm-action= off SIP/2.0 Name Values Req/Opt PPM avaya-cm-destination Any number within the Communication Manager dial plan, to which this endpoint is being forwarded avaya-cm-action on or off Req No Authorization: An endpoint can use this FNU on another extension only if the endpoint has a "call-fwd Ext: 2222 button administered on Communication Manager. Activates or deactivates Call Forwarding All Calls, on the extension specified in the user part of the Request-URI. Communication Manager button: call-fwd Ext: 2222 Feature package: Yes SDP required: Only if avaya-cm-action=on and avaya-cm-destination not specified. (if SDP required, line appearance must be requested otherwise line appearance request will be ignored) Opt No Call Forward Busy - No Answer FNU Call Forward Busy/Don t Answer activates and deactivates call forwarding for calls when the extension is busy or the user does not answer. Case 1 FNU structure where Call Forwarding All Calls of the endpoint s own (1111) extension: INVITE sip:[email protected];avaya-cm-fnu=call-forwarding-busy-no-answer;avayacm-dest ination= ;avaya-cm-action=on SIP/2.0 Issue 2.0 May

316 Feature requirement specifications INVITE on=on SIP/2.0 INVITE on=off SIP/2.0 Name Values Req/Opt PPM avaya-cm-action on or off Req No avaya-cm-destination Any number within the Communication Manager dial plan, to which this endpoint is being forwarded. Opt No Authorization: This example shows the use of this FNU on the endpoint s own extension. It must be authorized by the extension s class of service. See the next case for how to apply this feature to another extension. Communication Manager button: cfwd-bsyda Ext: (left blank) Feature package: Yes SDP required: Only if avaya-cm-action=on and avaya-cm-destination not specified. (if SDP required, line appearance must be requested, otherwise line appearance request will be ignored) Case 2 FNU structure where Call Forwarding All Calls of another endpoint s (2222) extension: INVITE sip:[email protected];avaya-cm-fnu=call-forwarding-busy-no-answer;avaya cm- destination= ;avaya-cm-action=on SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=call-forwarding-busy-no-answer;avaya cm- action=on SIP/ Administering SES on S8300

317 FNU requirements INVITE cm- action=off SIP/2.0 Name Values Req/Opt PPM avaya-cm-action on or off Req No avaya-cm-destination Any number within the Communication Manager dial plan, to which this endpoint is being forwarded. Opt No Authorization: An endpoint can use this FNU on another extension only if the endpoint has a cfwd-bsyda Ext: 2222 button administered on Communication Manager. Description: Call Forward Busy/Don t Answer activates and deactivates call forwarding for calls when the extension is busy or the user does not answer, on the extension specified in the user part of the Request-URI. CM button: cfwd-bsyda Ext: 2222 Feature package: Yes SDP required: Only if avaya-cm-action=on and avaya-cm-destination not specified. (if SDP required, line appearance must be requested, otherwise line appearance request will be ignored). Directed Call Pickup FNU Directed Call Pickup allows the user to answer a call ringing at another extension without having to be a member of a pickup group. Directed Call Pickup FNU Structure: INVITE sip:[email protected];avaya-cm-fnu=call-pickup-directed;avaya-cmextension=3333 SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=call-pickup-directed SIP/2.0 Parameters: Name Values Req/Opt PPM avaya-cm-extension The Communication Manager extension where the call is alerting. Opt No Issue 2.0 May

318 Feature requirement specifications Authorization: The endpoints need not be members of a group, but directed call pickup must be authorized by the class of restriction for both endpoints. Communication Manager button: dir-pkup Feature package: No SDP required: Yes Extended Call Pickup FNU Extended Group Call Pickup allows a user to answer calls directed to another call pickup group. Extended Group Call Pickup FNU structure: INVITE sip:[email protected];avaya-cm-fnu=call-pickup-extended;avaya-cm-pickupnumber=3 SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=call-pickup-extended SIP/2.0 Parameters: Name Values Req/Opt PPM avaya-cm-pickup-number The pickup number from 1 to 24. Opt No Authorization: The endpoint must be a member of a pickup group, and that pickup group must be a member of an extended pickup group, which must also include the group of the endpoint whose telephone is being picked up. Communication Manager button: None. Accessed on the Communication Manager only via an FAC. Feature package: No SDP required: Yes Calling Party Number Block FNU Calling Party Number Block blocks the sending of the calling party number for one call. Calling Party Number Block FNU structure: INVITE sip:[email protected];avaya-cm-fnu=calling-party-block;avaya-cmdestinat ion= SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=calling-party-block SIP/ Administering SES on S8300

319 FNU requirements Parameters: Name Values Req/Opt PPM avaya-cm-destination Any number within the Communication Manager dial plan to which this call is being directed. Opt No Authorization: None Communication Manager button: cpn-blk Feature package: No SDP required: Yes Calling Party Number Unblock FNU Calling Party Number Unblock deactivates calling party number (CPN) blocking and allows the CPN to be sent for a single call. Calling Party Number Unblock FNU structure: INVITE sip:[email protected];avaya-cm-fnu=calling-party-unblock;avaya-cmdestin ation= SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=calling-party-unblock SIP/2.0 Parameters: Name Values Req/Opt PPM avaya-cm-destination Any number within the Communication Manager dial plan to which this call is being directed Opt No Authorization: None Communication Manager button: cpn-unblk Feature package: No SDP required: Yes Issue 2.0 May

320 Feature requirement specifications Dial Intercom FNU Dial Intercom places a call to the station associated with the button. The called user receives a unique alerting indication. The endpoint extension and destination extension must be in the same intercom group. This feature is exactly like Automatic Intercom except for the way that the dial code is specified. PPM can provide the dial code for Automatic Intercom, but not for Dial Intercom. Dial Intercom FNU structure: INVITE sip:[email protected];avaya-cm-fnu=dial-intercom;avaya-cm-group=9;avayacmdial-code=12 SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=dial-intercom;avaya-cm-group=9 SIP/2.0 Parameters: Name Values Req/Opt PPM avaya-cm-group Any number within the Communication Manager dial Intercom group number from 1 to 32. Req Yes avaya-cm-dial-code 1- or 2-digit number Opt No Authorization: An endpoint can use this FNU for a intercom group that matches an administered Communication Manager button for this extension. Communication Manager button: dial-icom Grp: 9 Feature package: No SDP required: Yes Drop FNU Drop FNU allows users to drop calls. Users can drop calls from automatic hold or drop the last party they added to a conference call. Drop FNU structure: INVITE sip:[email protected];avaya-cm-fnu=drop SIP/2.0 Parameters: None Authorization: None Communication Manager button: drop Feature package: No SDP required: No 318 Administering SES on S8300

321 FNU requirements Exclusion FNU Exclusion allows multi-appearance telephone users to keep other users with appearances of the same extension from bridging onto an existing call. If the user activates the Exclusion button while other users are already bridged onto the call, the other users are dropped. There are two ways to activate Exclusion. Manual Exclusion when the user presses the exclusion button (either during dialing or during the call) Automatic Exclusion as soon during a call, the user presses the exclusion button Exclusion FNU structure: INVITE sip:[email protected];avaya-cm-fnu=exclusion ;avaya-cm-action=on SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=exclusion ;avaya-cm-action=off SIP/2.0 Parameters: Name Values Req/Opt PPM avaya-cm-action on or off Opt No Authorization: This request always applies to the endpoint s own extension. Automatic exclusion must be authorized by the extension s class of service. Description: Communication Manager button: exclusion Feature package: No SDP required: No Off-PBX Call FNU This FNU provides the capability to enable and disable the extending of an EC500 call. Off-PBX Call FNU structure: INVITE sip:[email protected];avaya-cm-fnu=off-pbx;avaya-cm-action=on SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=off-pbx;avaya-cm-action=off SIP/2.0 Issue 2.0 May

322 Feature requirement specifications Parameters: Name Values Req/Opt PPM avaya-cm-action on or off Req No Authorization: This request always applies to the endpoint s own extension. Communication Manager button: ec500 Feature package: Yes SDP required: No Last Number Dialed FNU Last Number Dialed (redial) originates a call to the number last dialed by the station. Last Number Dialed FNU structure: INVITE sip:[email protected];avaya-cm-fnu=last-number-dialed SIP/2.0 Parameters: None Authorization: None Communication Manager button: last-numb Feature package: No SDP required: Yes Malicious Call Trace FNU Malicious Call Trace Activation sends a message to the MCT control extensions stating that the user wants to trace a malicious call. MCT activation also starts recording the call, if the system has a MCT voice recorder. Malicious Call Trace FNU structure: INVITE sip:[email protected];avaya-cm-fnu=mct SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=mct-cancel SIP/2.0 Parameters: None Authorization: Must be authorized by the endpoint s class of restriction Communication Manager button: mct-act (to activate). Only an FAC to cancel. Feature package: No SDP required: No 320 Administering SES on S8300

323 FNU requirements AUDIX One-Step Recording FNU This feature allows a station user to start and end the recording of an in-progress conversation using the AUDIX system recording facility. Note that avaya-cm-extension is optional when avaya-cm-action is "off" (because a station can only have one of these buttons). AUDIX One-Step Recording INVITE sip:[email protected]; avaya-cm-fnu=one-touch-recording; avaya-cmextension=3333;avaya-cm-action=on SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=one-touch-recording;avaya-cmaction=off SIP/ 2.0 Parameters: Name Values Req/Opt PPM avaya-cm-action on or off Req No avaya-cm-extension The Communication Manager extension of an AUDIX hunt group Req Yes Authorization: An endpoint can use this FNU on another extension only if the endpoint has a Communication Manager button audix-rec button with a matching extension. Communication Manager button: audix-rec Ext: 3333 Feature package: No SDP required: No Priority Call FNU Priority Calling allows a user to place priority calls or change an existing call to a priority call. Priority Call FNU structure: INVITE sip:[email protected];avaya-cm-fnu=priority-call;avaya-cm-destination= SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=priority-call SIP/2.0 Issue 2.0 May

324 Feature requirement specifications Parameters: Name Values Req/Opt PPM avaya-cm-destination Any number within the Communication Manager dial plan, to which this call is being directed Opt No Authorization: None Communication Manager button: priority Feature package: No SDP required: Yes Send All Calls FNU Send All Calls allows users to temporarily direct all incoming calls to coverage regardless of the assigned call-coverage redirection criteria. Send All Calls of the endpoint s own (1111) extension FNU structure INVITE sip:[email protected];avaya-cm-fnu=sac;avaya-cm-action=on SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=sac;avaya-cm-action=off SIP/2.0 Parameters: Name Values Req/Opt PPM avaya-cm-action on or off Req No Authorization: This example shows the use of this FNU on the endpoint s own extension. No authorization is required. See the next case for how to apply this feature to another extension. Communication Manager button: send-calls Ext: (left blank) Feature package: Yes SDP required: No 322 Administering SES on S8300

325 FNU requirements Send All Calls of another endpoint s (2222) extension FNU structure INVITE sip:[email protected];avaya-cm-fnu=sac;avaya-cm-action=on SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=sac;avaya-cm-action=off SIP/2.0 Parameters: Name Values Req/Opt PPM avaya-cm-action on or off Req No Authorization: An endpoint can use this FNU on another extension only if the endpoint has a "send-calls Ext: 2222" button administered on Communication Manager. Description: Applied to another extension. Communication Manager button: send-calls Ext: 2222 Feature package: Yes SDP required: No Transfer to Voice Mail FNU Transfer to Voice Mail FNU allows coverage to transfer the caller to the original call recipient s AUDIX mail where the caller can leave a message. Transfer to Voice Mail FNU structure: INVITE sip:[email protected];avaya-cm-fnu=transfer-to-voic SIP/2.0 Parameters: None Authorization: None Communication Manager button: None. Accessed on the Communication Manager only by an FAC. Feature package: No SDP required: No Issue 2.0 May

326 Feature requirement specifications Whisper Page Activation Whisper Page Activation allows a user to make and receive whisper pages. A whisper page is an announcement sent to another extension that is active on a call where only the person on the extension hears the announcement. Other parties on the call cannot hear the announcement. Whisper Page Activation FNU structure: INVITE sip:[email protected];avaya-cm-fnu=whisper-page;avaya-cm-extension=3333 SIP/2.0 INVITE sip:[email protected];avaya-cm-fnu=whisper-page SIP/2.0 Parameters: Name Values Req/Opt PPM avaya-cm-extension The Communication Manager extension to which you want to whisper Req No Authorization: The user must have a class of restriction (COR) that allows intra-switch calling to use whisper paging, and the extension to which you are whispering must not have blocked whispers. Communication Manager button: whisp-act Feature package: No SDP required: Yes 324 Administering SES on S8300

327 Appendix B: Terminal requirements for SIP This appendix discusses Communication Manager s terminal requirements with respect to SIP. Terminals Terminals Avaya Communication Manager OPTIM requirements Outgoing From header OPTIM formats the outgoing From: URI field in the call that leaves the server from a non-sip telephone to a SIP IP telephone. The From header is determined as follows: Display parameter followed by administered digits at authoritative URI. The digits depend on the configuration set option calling number style. There are two choices: network and PBX. PBX is the station extension. Network is the network station, modified by either the public or the private numbering table. The domain is taken from the Network Regions screen. If this is not properly administered in Avaya Communication Manager, then the default will be the following: anonymous.unknown.domain. For an incoming Integrated Services Digital Network (ISDN) call terminating to an OPTIM OPS station, the display information comes from the display information element (IE), and the handle is from the calling number. The domain is taken from the Network Regions screen, as above. Issue 2.0 May

328 Terminal requirements for SIP 326 Administering SES on S8300

329 Glossary A access code Access Security Gateway (ASG) American National Standards Institute (ANSI) Avaya Communication Manager B bearer channel (B-channel) bus C Call Detail Recording (CDR) Call Detail Recording utility (CDRU) carrier CCRON central office (CO) A dial code of 1 to 3 digits that activates a feature, cancels a feature, or accesses an outgoing trunk. A software module that secures Avaya Global Services log in accounts on many Avaya servers. Each login attempt on these accounts is met with a one-time challenge string that must be answered with the correct one-time response. A professional technical association that supports standards for transmission, protocol, and high-level languages, and that represents the U.S. in the International Organization for Standards. ANSI standards are for voluntary use in the U.S. An open, scalable, highly reliable, and secure telephony application. Communication Manager provides user functionality and system management functionality, intelligent call routing, application integration and extensibility, and enterprise communications networking. A 64-kbps channel or a 56-kbps channel that carries a variety of digital information streams. A B-channel carries voice at 64 kbps, data at up to 64 kbps, WebLM voice encoded at 64 kbps, and voice at less than 64 kbps, alone or combined. See also data channel (D-channel). A multiconductor electrical path that transfers information over a common connection from any of several sources to any of several destinations. See also packet bus; time-division multiplex (TDM) bus. A file that uses software and hardware to record call data. CDR was formerly called Station Message Detail Recording (SMDR). See also Call Detail Recording utility (CDRU). Software that collects, stores, filters, and provides output of call detail records. See also Call Detail Recording (CDR). An enclosed shelf that contains vertical slots that hold circuit packs. coverage of calls redirected off-network. Telephone switching equipment that provides local telephone service and access to toll facilities for long distance calling. Issue 2.0 May

330 channel channel circuit circuit pack Class of Restriction (COR) Class of Service (COS) CCITT communications system Controlled Local Area Network (CLAN) circuit pack CPN CPN/BN CSP customer-premises equipment (CPE) D data channel (D-channel) (1) A circuit-switched call. (2) A communications path that transmits voice and data. (3) In WebLM transmission, all the contiguous time slots or noncontiguous time slots that are necessary to support a call. For example, an H0-channel uses six 64-kbps time slots. (4) A digital signal-0 (DS0) on a T1 facility or an E1 facility that is not specifically associated with a logical circuit-switched call. See also data channel (D-channel). (1) An arrangement of electrical elements through which electric current flows. (2) A channel or a transmission path between two or more points. A circuit card on which electrical circuits are printed, and integrated circuit (IC) chips and electrical components are installed. A circuit pack is installed in a SSH carrier. One example is the TN2302. A feature that allows up to 96 classes of call-origination restrictions and call-termination restrictions for telephones, telephone groups, data modules, and trunk groups. See also Class of Service (COS). A feature that uses a number to specify whether telephone users can activate the Automatic Callback (ACB), Call Forwarding All Calls, Data Privacy, or Priority Calling features. See also Class of Restriction (COR). Comitte Consultatif International Telephonique et Telegraphique. See International Telecommunications Union (ITU). A software-controlled processor complex that interprets dial pulses, tones, and keyboard characters, and makes the proper connections within the system and externally. The communications system consists of a digital computer, software, storage devices, and carriers, with special hardware to perform the connections. A communications system provides communications services for the telephones on customer premises and the data terminals on customer premises, including access to public networks and Point-to-Point Protocol (PPP)s. See also SSH. A circuit pack (TN799B) in an Avaya DEFINITY port network (PN) that provides TCP/IP connectivity to adjuncts over Ethernet or Point-to-Point Protocol (PPP). The CLAN circuit pack serves as the network interface for a DEFINITY server. The CLAN terminates IP (TCP and UDP), and relays those sockets and connections up to the Avaya DEFINITY server. Called-party number Calling-party number/billing number Cellular Service Provider. Equipment that is connected to the telephone network, and that resides on a customer site. CPE can include telephones, modems, fax machines, video conferencing devices, switches, and so on. A 16-kbps channel or a 64-kbps channel that carries signaling information or data on an Integrated Services Digital Network Basic Rate Interface (ISDN-BRI) 328 Administering SES on S8300

331 feature data communications equipment (DCE) data module data terminal data terminal equipment (DTE) digital Digital Communications Protocol (DCP) dual-tone multifrequency (DTMF) Dynamic Host Configuration Protocol (DHCP) E edge extension F FNE FNU FTP feature or Integrated Services Digital Network Primary Rate Interface (ISDN-PRI). See also bearer channel (B-channel). Equipment on the network side of a communications link that makes the binary serial data from the source or the transmitter compatible with the communications channel. DCE is usually a modem, a data module, or a packet assembly/disassembly (PAD). An interconnection device between a Basic Rate Interface (BRI) or a Digital Communications Protocol (DCP) interface of the SSH, and the data terminal equipment (DTE) or data channel (D-channel). An input/output (I/O) device that has either switched access or direct access to a host computer or to a processor interface. Equipment that comprises the endpoints in a connection over a data circuit. In a connection between a data terminal and a host, the terminal, the host, and the associated modems or data modules comprise the DTE. The representation of information by discrete steps. Compare with analog. A proprietary protocol that transmits both digitized voice and digitized data over the same communications link. A DCP link consists of two 64-kbps information (I) channels, and one 8-kbps signaling (S) channel. The DCP protocol supports two information-bearing channels, and thus two telephones or data modules. The I1 channel is the DCP channel that is assigned on the first page of the 8411 Station screen. The I2 channel is the DCP channel that is assigned on the analog adjunct page of the 8411 Station screen, or on the data module page. The touchtone signals used for in-band telephone signaling. An IETF protocol (RFCs 951, 1534, 1542, 2131, and 2132) that assigns IP addresses dynamically from a pool of addresses instead of statically. An Edge server handles user requests sent to and from SES home server(s). A number that routes calls through a communications system. With a Uniform Dial Plan (UDP) or a main-satellite dialing plan, extensions also route calls through a Point-to-Point Protocol (PPP). Feature Name Extension Feature Name URI File transfer protocol. A specifically defined function or service that the system provides Issue 2.0 May

332 H.323 H H.323 An International Telecommunications Union (ITU) standard for switched multimedia communication between a LAN-based multimedia endpoint and a gatekeeper. home An SES Home server handles user requests sent to it from the edge server. host computer A computer that is connected to a network, and that processes data from data-entry devices. I IE IEEE IETF IM information element (IE) Initialization and Administration System (INADS) IP interface Institute of Electrical and Electronics Engineers (IEEE) Integrated Services Digital Network (ISDN) Integrated Services Digital Network Basic Rate Interface (ISDN-BRI) See information element (IE). See Institute of Electrical and Electronics Engineers (IEEE). See Internet Engineering Task Force (IETF). Instant Messaging. The instant-messaging client software required for the Avaya Communication Manager release 2.0 or later is a version of the Avaya IP Softphone R5 and later, and the SIP Softphone R2 and later. The name for the data fields within an Integrated Services Digital Network (ISDN) Layer 3 message. A software tool that is used by Avaya Services personnel for communication, remote management and troubleshooting of customers alarms and traps. A CLAN, ethernet processor interface, or procr that lets the server connect using internet protocol. An organization that produces standards for local area network (LAN) equipment. A public network or a Point-to-Point Protocol (PPP) that provides end-to-end digital communications for all services to which users have access. An ISDN uses a limited set of standard multipurpose user-network interfaces that are defined by the CCITT. Through internationally accepted standard interfaces, an ISDN provides digital circuit switching communications or packet switching communications within the network. An ISDN provides links to other ISDNs to provide national digital communications and international digital communications. See also Integrated Services Digital Network Basic Rate Interface (ISDN-BRI); Integrated Services Digital Network Primary Rate Interface (ISDN-PRI). The interface between a communications system and terminal that includes two 64-kbps bearer channel (B-channel)s for transmitting voice or data, and one 16-kbps data channel (D-channel) for transmitting associated B-channel call control and out-of-band signaling information. ISDN-BRI also includes 48 kbps for transmitting framing and D-channel contention information, for a total interface speed of 192 kbps. ISDN-BRI serves ISDN terminals and digital 330 Administering SES on S8300

333 Internet Protocol (IP) Integrated Services Digital Network Primary Rate Interface (ISDN-PRI) International Organization for Standards International Telecommunications Union (ITU) International Telegraph and Telephone Consultative Committee Internet Engineering Task Force (IETF) Internet Protocol (IP) terminals that are fitted with ISDN terminal adapters. See also Integrated Services Digital Network Primary Rate Interface (ISDN-PRI). The interface between multiple communications systems that in North America includes kbps channels that correspond to the North American digital signal-level 1 (DS1) standard rate of Mbps. The most common arrangement of channels in ISDN-PRI is kbps bearer channel (B-channel)s for transmitting voice and data, and one 64-kbps data channel (D-channel) for transmitting associated B-channel call control and out-of-band signaling information. With nonfacility-associated signaling (NFAS), ISDN-PRI can include 24 B-channels and no D-channel. See also Integrated Services Digital Network (ISDN); Integrated Services Digital Network Basic Rate Interface (ISDN-BRI). A worldwide federation of standards bodies who issue International Standards for technological, scientific, intellectual, and economic activity. The federation is called ISO, and the US representative to the federation is the American National Standards Institute (ANSI). An international organization that sets universal standards for data communications, including Integrated Services Digital Network (ISDN). ITU was formerly known as International Telegraph and Telephone Consultative Committee (CCITT). See International Telecommunications Union (ITU). One of two technical working bodies of the Internet Activities Board. The IETF develops new Transmission Control Protocol (TCP)/Internet Protocol (IP) (for example, TCP/IP) standards for the Internet. A connectionless protocol that operates at Layer 3 of the Open Systems Interconnect (OSI) model. IP protocol is used for Internet addressing and routing packets over multiple narrowbands to a final destination. IP protocol works in conjunction with Transmission Control Protocol (TCP), and is usually identified as TCP/IP. Issue 2.0 May

334 local area network (LAN) L local area network (LAN) M MAC address (or MAC name) media server interface MWI MIB N NAME1 NAME2 narrowband network network region node nonce A networking arrangement that is designed for a limited geographical area. Generally, a LAN is limited in range to a maximum of 6.2 miles, and provides high-speed carrier service with low error rates. Common configurations include daisy chain, star (including circuit-switched), ring, and bus. A 48-bit number, uniquely identifying and programmed into each network interface card or device. A CLAN card in an Avaya server running Avaya Communication Manager. messaging waiting indication. For example, a visual alert of new voice mail. management information base. A type of hierarchical database, addressing object identifiers, used to manage devices in a communications network. Legacy name, Latin characters, usually displayable, for example Eurofont and Kanafont encoding. UTF-8 encoding. Used for multibyte character sets such as Chinese ideograms Hiragana, Katakana, and Hangul A circuit-switched call at a data rate of 64 kbps or less. All switch calls that are not WebLM are considered to be narrowband. Compare with wide band. A series of points, nodes, or stations that are connected by communications channels. Network Region is a flexible administrative concept. A network region is an attribute associated with Communication Manager resources. It is used in the administration of, among other things, resource allocation and security. For example, when an H.323, or SIP, IP endpoint requires a Gateway Resource to set up a talk path with a non-ip endpoint, like a DCP telephone, for example, Communication Manager checks the network region parameter to attempt to get that gateway resource from the same Network Region, that is, as near to the endpoint as possible, to minimize trunk usage and delay. A switching point or a control point for a network. Nodes are either tandem or terminal. Tandem nodes receive signals, and pass the signals on. Terminal nodes originate a transmission path, or terminate a transmission path. Random value sent in a communications protocol exchange, often used to detect replay attacks. This specifically refers to the use of random information inserted in a challenge for SIP digest authentication. The algorithms are essentially the same as for HTTP, and are described in RFC Administering SES on S8300

335 Plain Old Telephone Service (POTS) O OATS off-pbx station (OPS) OPS Open Systems Interconnect (OSI) origination-based call flow O/S P packet packet assembly/ disassembly (PAD) packet bus packet switching PBX Plain Old Telephone Service (POTS) Origination and Termination Signaling. Formerly known as an origination-based call flow or W call flow. In a call-flow diagram, this describes the direction, initiation, and termination of signaling. A telephone that Avaya Communication Manager does not control, such as a cellular telephone or the home telephone of a user. The features of Communication Manager can be extended to an OPS through switch administration by associating the extension of the office telephone with the off-site telephone. Outboard Proxy SIP. A system of seven independent communication protocols defined by the International Organization for Standards or ISO. Each of the seven layers enhances the communications services of the layer below, and shields the layer above from the implementation details of the lower layer. In theory, this structure can be used to build communications systems from independently developed layers. See OATS. Operating System. A group of bits that is used in packet switching and that is transmitted as a discrete unit. A packet includes a message element and a control information element (IE). The message element is the data. The control IE is the header. In each packet, the message element and the control IE are arranged in a specified format. The process of packetizing control data and user data from a transmitting device before the data is forwarded through the packet network.the receiving device disassembles the packets, removes the control data, and then reassembles the packets, thus reconstituting the user data in its original form. A bus with a wide bandwidth that transmits packets. A data-transmission technique that segments and routes user information in discrete data envelopes that are called packets. Control information for routing, sequencing, and error checking is appended to each packet. With packet switching, a channel is occupied only during the transmission of a packet. On completion of the transmission, the channel is made available for the transfer of other packets. private branch exchange. See SSH. Basic voice communications with standard, single-line phones accessing the public switched telephone network (PSTN). Issue 2.0 May

336 PPM PPM Point-to-Point Protocol (PPP) port private network processor ethernet procr protocol proxy trust domain public network public switched telephone network (PSTN) R RAS Real-time Transfer Protocol (RTP) RFA RFC Personal Profile Manager (PPM) is a centralized repository of personalized data, such as contact lists or access control lists. PPM provides a Web Services interface that allows a client, such as a SIP telephone or SIP Softphone, to download a particular user's profile, thus allowing the user the mobility to move around to different devices but maintain access to the user's unique information. As an example, a user might log in one day at a telephone at a service desk, and then the next from a Softphone while working from home. In each case, the user's personal profile would appear at each of those devices. A standard (largely replacing SLIP) allowing a computer to use TCP/IP with a regular telephone line. A data-transmission access point or voice-transmission access point on a device that is used for communicating with other devices. A network exclusively for the telecommunications needs of a particular customer. A logical connection between the server itself and a network interface card. The way this connection is administered in Communication Manager determines what type of traffic the NIC allows. See processor ethernet. A set of conventions or rules that governs the format and the timing of message exchanges. A protocol controls error correction and the movement of data. Includes those SIP servers and gateways, but not endpoints with identities administered on the server running SES. A network to which all customers have open access for local calling and long distance calling. The public worldwide voice telephone network. Remote Access Server (or in Microsoft Windows operating systems, Remote Access Service). An Internet Engineering Task Force (IETF) protocol (RFC 1889) that addresses the problems that occur when video and other exchanges with real-time properties are delivered over a local area network (LAN) that is designed for data. RTP gives higher priority to video and other real-time interactive exchanges than to connectionless data. Remote Feature Activation is a web-based application which is used to obtain Avaya authentication and licensing files. Request for Comments designates Internet Engineering Task Force (IETF) standards that are drafts. 334 Administering SES on S8300

337 tie trunk RNIS RPM RTC RTCP Remote Network Implementation Services is a contract installation services group within Avaya Inc. RedHat Package Manager Real Time Communication Real Time Control Protocol S S8400 S8500 S8500B SAMP SCCAN Session Initiated Protocol (SIP) SIP Enablement Services SSH SSL subscriber switch A hardware platform for use as an Avaya server that is a single module. The S8400 uses a flash drive, and the SAMP functionality is on the board. No separate chassis is required. A hardware platform from the IBM x305 series. This machine uses an RSA for a remote maintenance board. A hardware platform from the IBM x306 series. This machine uses a SAMP for a remote maintenance board. Server Availability Management Processor. A remote maintenance board. The Seamless Converged Communications Across Networks (SCCAN) solution offers voice and data access from a single SCCAN handset integrated with a desk phone across the corporate Wireless Local Area Network (WLAN) and public Global System for Mobile communication (GSM) and cellular networks. A signaling protocol for Internet conferencing, telephony, presence, events notification, and instant messaging. SIP initiates call setup, routing, authentication, and other feature messages to endpoints within an IP domain. See also H.323; Voice over IP (VoIP). SES. SIP Enablement Services is the name for Avaya s solution that was previously called Converged Communication Server. Secure SHell is a protocol for secure remote login and other secure network services over an insecure network. It provides for server authentication, and data integrity with perfect port-forwarding secrecy. Secure Socket Layer. A subscriber is one of the following: a SIP Enablement Services host or other SIP node, a SIP user (per Contact), or a server (running Avaya Communication Manager 2.0 or later). Any kind of telephone switching system. See also communications system. T TAC TCP TCP/IP tie trunk trunk-access code See Transmission Control Protocol (TCP). See Internet Protocol (IP). See also Transmission Control Protocol (TCP). A telecommunications channel that directly connects two private switching systems. Issue 2.0 May

338 time-division multiplex (TDM) bus time-division multiplex (TDM) bus time-division multiplexing (TDM) time slot Transmission Control Protocol (TCP) Transport Layer Security (TLS) trunk trunk access code (TAC) trunk group U UDP URI URL V VoIP W W call flow A bus that is time-shared regularly by pre allocating short time slots to each transmitter. In a SSH, all Plain Old Telephone Service (POTS) circuits are connected to the time-division multiplex (TDM) bus, and any port can send a signal to any other port. See also time-division multiplexing (TDM). A form of multiplexing that divides a transmission channel into successive time slots. See also time-division multiplex (TDM) bus. In the SSH, a time slot refers to either a digital signal level-0 (DS0) on a T1 facility or an E1 facility, or a 64-kbps unit on the time-division multiplex (TDM) bus or fiber connection between port networks (PNs) that is structured as 8 bits every 125 microseconds. A connection-oriented transport-layer protocol, IETF STD 7. RFC 793, that governs the exchange of sequential data. Whereas the Internet Protocol (IP) deals only with packets, TCP enables two hosts to establish a connection and exchange streams of data. TCP guarantees delivery of data, and also guarantees that packets are delivered in the same order in which the packets are sent. An IETF standard (RFC 2246) to supersede Netscapes Secure Socket Layer (SSL) and provide host-to-host data connections with encryption and certification at the transport layer. A dedicated communications channel between two communications systems or central office (CO)s. A dial access code used to access a specific trunk. Telecommunications channels that are assigned as a group for certain functions, and that can be used interchangeably between two communications systems or central office (CO)s. User Datagram Protocol Uniform Resource Identifier Uniform Resource Location Voice over Internet Protocol (IP) See OATS. 336 Administering SES on S8300

339 Index Index Numerical Parameters Edit System Properties screen A Add Another Handle command Add Another User command Add Contact command , 146 Add Contact screens Add Group screens Add Handle in a New Group screens Add Handle in New Group command Add Handle screens Add Host Contact for user screens Add Host screen Add Media Server screen add or prevent permissions Add User screens administer stations administering Feature-Related System Parameters screen IP Network Region screen Locations screen Signaling Group screen , 69 SIP SIP trunks System Capacity screen System-Parameters Call Coverage/Call Forwarding screen System-Parameters Customer-Options screen.20, 80 Trunk Group screen , 86, 97 Trunk Group screen page Trunk Group screens administration administering stations call routing detailed screens enable SIP on Communication Manager set SIP device as OPTIM extension SIP trunks visiting user Administration web interface administration, Top-level screens administrative screens Alarms screens allow permissions ARS Digit Analysis Table ANI Reqd field Call Type (for AAR only) field Call Type (for ARS only) field Dialed String field Location Max field Min field Node Number field Percent Full field Route Pattern field Audix One-Step recording FNU Authentication File screen Avaya CM OPTIM terminals B backup backup schedule block permissions C call appearances call capacity call coverage Call Forward Busy FNU Call Forward FNU call forwarding call processing SES call routing calling party block FNU calling party number unblock FNU capacity change permissions , 186 Choose Interface screen commands Add Another Handle Add Another User Add Contact Group Details screen My Contact List screen Add Group Add Handle in New Group Back to My Contact List Delete Extensions Also Delete Group Edit User Handles screen Group Details screen Issue 2.0 May

340 Index Delete Handle Edit Handle for Off-PBX Station Mapping screen Free List Media Server Extensions screen Install Install the Authentication File previously downloaded specify below Reload Configuration Speed Dial track availability Update Group Configuration Set screen Configuration Set Description field Configure Server screen Confirm Delete User screens connected party name connection path connections internet modem server Contact Details screen Contact List screens Contact List task , 132 contacts end user s buddy list of the end user co-residency port assignments server types Current Alarms screen D Data Backup/Restore screen delete all displayed users screen Delete Contact screens Delete Extensions Also command Delete Group command Edit User Handles screen Group Details screen Delete Group screen Delete Handle command delete multiple users , 155 delete selected users screen Devices Menu screens Devices task , 149 Diagnostics screen Dial Intercom FNU Dial Plan Analysis screen Call Type field Dialed String field Percent Full field Total Length field DID/Tie/ISDN/SIP Intercept Treatment field Feature-Related System Parameters screen DiffServ/TOS Parameters Edit System Properties screen Directed Call Pickup FNU distinctive alerting Distributed Office domain authoritative , 51 far-end network region Download Files screen Drop FNU E Edit Default User Profile screen Edit Handle command Edit Handle detail screens Edit Host Contact screens Edit System Properties screen Edit User Handles screen Edit User Handles screens Edit User Profile screens Eject CD-ROM screen Exclusion FNU Extension tasks Extensions task , 158, 159 F Feature Access Codes screen page 1 Auto Route Selection (ARS) Access Code1 field.. 43 Feature Related System Parameters screen EMU Inactivity Interval for Deactivation Feature-Related System Parameters screen Trunk-to-Trunk Transfer field , 78 features meet me conferencing visiting user fields Parameters ACA Assignment Access Control Policy Add Host screen Ack Add Entry Add Media Server Extension Add Memo Address Add Contact screen One Touch Dial List screen Address 1, Address 2 Add User screen Administering SES on the Avaya S8300 Server

341 Index Edit Default User Profile screen Edit User Profile screen Search Users screen Alias Add Contact screen Group Details screen My Contact List screen Allow Emergency Contacts Allow List Allow List/Block List ANI Reqd Application Auth Code Authoritative Domain Auto Route Selection (ARS) Access Code Backup Method Block List Bridged Appearance Bridged calls Busy Threshold Button One Touch Dial List screen Ringer Settings screen Bypass If IP Threshold Exceeded Call Limit Call Type Call Type (for AAR only) Call Type (for ARS only) Calls Allowed CCS Version CDR Reports Change Modem Settings Change Permissions Change Permissions Type Choose License Source Choose Software City Add User screen Edit Default User Profile screen Edit User Profile screen Search Users screen CM FQD Name or IP Address Add Media Server screen CM Login Add Media Server screen CM Password/CM Password Confirm Add Media Server screen Configuration Set Configuration Set Description Contact Add Host Contact screen , 171 Add User screen Contact List screen Edit Host Contact screen Edit User Handles screen Contact List Members Contact Phones Contact Type Content COR Country Add User screen Edit Default User Profile screen Edit User Profile screen Search Users screen Crit_High Crit_Low Current Permissions Type Current SSH public keys Data Set Data Sets Backup Now screen Schedule Backup screen Date Backup Log screen Current Alarms screen Server Date/Time screen Day Schedule Backup screen Default Receiver Volume Add Host screen Default Ringer Cadence Add Host screen Default Ringer Volume Add Host screen Default Speaker Volume Add Host screen Delete Delete all contacts Description Destination Backup Logs screen Schedule Backup screen Dial Access Dial Prefix , 63 Dialed String , 42 DID/Tie/ISDN/SIP Intercept Treatment DiffServ/TOS Parameters Digital Loss Group Direct IP-IP Audio Connections Direction Disable call classifier for CCRON over SIP trunks. 79 Display Format Domain Edit Handle detail screen DTMF over IP Eject Encryption Enhanced EC Issue 2.0 May

342 Index EvtID Execute Ping Extension Add Media Server Extension screen List Media Server Extensions screen Far-end Domain Far-end Network Region Far-end Node Name Feature File Size File(s) to download from the LAN using URL File(s) to download from the machine connected to the server First Name Edit User Profile screen Search Users screen Frequency FTP Gateway IP Address Generate New SSH Keys Group Name Add Contact screen Add Group screen Trunk Group screen page Group Number Signaling Group screen p , 74 Trunk Group screen page Group Type Signaling Group screen page Trunk Group screen page Handle Add Another Handle screen Add Group screen Add Host Contact screen Edit Handle detail screen Edit User Handles screen Group Details screen My Contact List screen Permissions screen Home Domain Host Add Media Server screen Add User screen Edit Default User Profile screen Edit User Profile screen List Media Server Extensions screen List Users screen , 124, 125 Search Users screen Host IP Address Add Host screen Host Name or IP Address Ping screen Traceroute screen Host Type Add Host screen ID Input to server Install this file on the local server Inter-region IP-IP Direct Audio Intra-region IP-IP Direct Audio IP Address Set MOdem Interface screen IP Audio Hairpinning Label Last Name Add User screen Edit User Profile screen Search Users screen Line Reservation Timer Add Host screen Link Protocol Link Protocols Add Host screen List of memos Listen Protocols Add Host screen Local directory Local PC card Location (for the ARS Digit Analysis Table) Logon ID Lvl Maintenance Maintenance Tests Major Alarms Management system access login Management system access password Mapping Mode Mark Users as Phone Match Pattern Max Maximum Administered SIP Trunks Maximum Off-PBX Telephones - EC Maximum Off-PBX Telephones - OPS Measured Media Server Add Media Server Extension screen Media Server Name Min Minimum Registration Setup screen Minor Alarms Mode Modem Administration Move all contacts Name Add Contact screen Group Details screen List Users screen My Contact List screen Near-end Listen Port Near-end Node Name Administering SES on the Avaya S8300 Server

343 Index Network Properties Network Region Night Service Node Number Notes Number of Members Numbering Format Office Add User screen Edit User Profile screen Old Group Name Operating System Options Ping screen Traceroute screen Outbound Direct Domains Add Host screen Outbound Port Add Host screen Outbound Proxy Add Host screen Outbound Routing Allowed From Add Host screen Outgoing Display Output format Output from server Output type Parent Add Host screen Partition Status Password Logon screen Password/Confirm Password Add User screen Edit User Profile screen Percent Full , 42 Phone Number Port/Protocol Preferred Minimum Session Refresh Interval Prefix Prerequisites Primary Handle Processes Product ID Profile Service Password Providing The Keys.install File Proxy Selection Route Pattern Queue Length Receiver Volume Redirect on OPTIM failure Redundant Properties Region IP Address Mapping screen Network Region screen Registration Expiration Timer Add Host screen Replace Unavailable Numbers Reserved Review Notices Ringer ON/OFF Ringer Volume Route Pattern SAMP/RSA Version ID Secure SIP Route Pattern screen Select a View Select Event Range Select Log Types Select Time Server Alarms Server BIOS Build ID Server Hardware Server IP Address Server Port Service Service Type Services Laptop Session Establishment Timer Setup Default User Profile Setup Hosts Setup SIP Domain Show only the following output families Shutdown options Signaling Group SIP Domain SIP License Host SIP Trunk IP Address Add Media Server screen SIP Trunks SMS Connection Type Add Media Server screen Software Load Source Speaker Volume State Add User screen Edit Default User Profile screen Edit User Profile screen Search User screen Station Extension , 64 Status Backup Logs screen Schedule Backup screen TAC Telephone # Telephone #1/Telephone #2 Group Details Screen My Contact List screen Test Options Time Issue 2.0 May

344 Index Backup Logs screen Schedule Backup screen Time of Day Synchronization Time Zone TN Total Length Track Availability Transport Method Tripwire Status Trunk Selection Type Unicode Name Unknown SIP Users URL Use Local Clock Use these Network Time Servers Used User User ID Add Another Handle screen Add Group screen Add Host Contact screen Add User screen Edit Handle detail screen Edit Host Contact screen Edit User Handles screen Edit User Profile screen List Users screen , 124, 125 Search Users screen Select User screen Update Password screen User Memo screen Value View VMM Information Warn_High Warn_Low ZIP Add User screen Edit Default User Profile screen Edit User Profile screen Search Users screen Firewall screen firmware checking version downloading FNU AUDIX One-Step recording call forward call forward busy calling party number block calling party number unblock dial intercom directed call pickup drop exclusion extended call pickup FNU Last number dialed Malicious call trace off-pbx priority call send all calls transfer to voice mail whisper page activation FNU requirements FNUs Format PC Card screen Format PC Card results screen FRC 3325 compliance Free command List Media Server Extensions screen G Gateway IP Address field Edit System Properties screen Group Details screens H Handles task , 161 I Incoming Call Handling Treatment screen Install New Software screen Install New Software Wizard Steps/Pages Begin Installation page Install in Progress page Install License Files page Installation Complete page Reboot in Progress page Reboot Server page Review Notices page Install Root Certificate screen Prerequisites intercept treatment intercom interface administration interfaces maintenance master administration international calls IP Address Mapping screen Region field IP Codec Set screens IP Network Region screen Authoritative Domain field Administering SES on the Avaya S8300 Server

345 Index Home Domain field IP Node Names screen Administering IP Address field Name field ISDN protocol ARS Digit Analysis Table L last number dialed FNU licenses alarm code host server List Media Server Extensions screens List Users screen , 128 Locations screen Proxy Selection Route Pattern Proxy Selection Route Pattern field Logon screen logon URL M malicious call trace FNU Manage Updates screen Management system access login Edit System Properties screen Management system access password Edit System Properties screen Media Gateway screen Network Region field Meet Me conferencing feature Memos task , 175 Modem screen Solving modem problems Modem Test screen Troubleshooting problems move user move user to new home , 182, 191 N Netstat results screen active internet connections Active UNIX domain sockets Netstat screen Network Region screen Authoritative Domain field Inter-region IP-IP Direct Audio Intra-region IP-IP Direct Audio Region field Server IP Address Server Port field Network Time Server screen new Add Another Media Server Extension screen Delete All Displayed Users task Delete Selected Users task Mark Users as Phone field Move User on Task pull down Move User on task pull down name for Converged Communication Server Preferred Minimum Session Refresh Interval Prepend + to Calling Number field reload configuration select free extension Select Free Extension screen Trunk Group screen page Watchers task , 185 non-sip user as contact , 138 Numbering-Public/Unknown Numbering screen O off-pbx FNU Off-PBX Station Mapping screen page 1 Application field Configuration Set field Dial Prefix field , 63 Phone Number field Station Extension field Trunk Selection field Off-PBX Station Mapping screen page 2 Bridged Calls field Call Limit field Calls Allowed field Mapping Mode field Station Extension field One Touch Dial List screens OPS extensions OPTIM extensions and SIP outgoing queue P p-a-i partially up p-asserted-identity password CM password logon Profile Service Password user password , 182 passwords. 111, 121, 129, 182, 190, 267, 268, 273, 292 Permissions permissions add an entry Issue 2.0 May

346 Index allow block changing Permissions screens Permissions task physical connections checking Pickup directed FNU expanded FNU Ping results success unsuccessful Ping screen Presence Access Policy priority call FNU procedures add a backup schedule alarms for specific server change a backup schedule install new software wizard move all contacts move user move user to another home server preview or restore backup data remove a backup schedule troubleshooting modem troubleshooting partially up processes Process Status results screen Process Status screen Profile task , 182 progress indicators Proxy Selection Route Pattern field Locations screen publication note Q queue outgoing R redirection coverage of calls off-net OPTIM failure Redundant Properties Edit System Properties screen release number Reload Configuration definition requirement specifications FNU requirements SES call processing software requirements terminal Restore History screen Ringer Settings screens RMB Network Configuration screen ROOF Route Pattern screen Route Pattern screen page 2 Secure SIP field S SAC , 323 Schedule Backup screen procedure add a backup schedule change a backup schedule remove a backup schedule SCP screens Add Contact Add Group Add Handle Add Handle in a New Group Add Host Add Host Contact for user Add Media Server Add User Alarms ARS Digit Analysis Table , 31 Authentication File Choose Interface Configuration Set , 37 Configure Server Confirm Delete User Contact Details Current Alarms Data Backup/Restore Delete Contact Delete Group Devices Menu Diagnostic Dial Plan Analysis , 38 Download Files Edit Default User Profile Edit Handle detail screen Edit Host Contact Edit System Properties Edit User Handles Edit User Profile Eject CD-ROM Extensions tasks Feature Access Code Feature Access Code page Feature Related System Parameters Feature Related System Parameters page 3. 28, Administering SES on the Avaya S8300 Server

347 Index Feature-Related System Parameters Firewall Format PC Card Group Details Incoming Call Handling Treatment Install New Software IP Address Mapping , 49 IP Codec Set , 48 IP Network Region , 51 IP Node Names , 55 List Media Server Extensions List Users Locations Locations screen Logon Manage Updates screen Media Gateway , 57 Modem Test My Contact List Netstat Netstat results Network Time Server Numbering Public/Unknown Numbering Numbering-Public/Unknown Numbering....23, 58 Off PBX Station Mapping page Off-PBX Station Mapping page Off-PBX Station Mapping page One Touch Dial List Permissions Ping Process Status Process Status Results Restore History Ringer Settings RMB Network Configuration Route Pattern Route Pattern screen Schedule Backup Search User Select User Server Server Configuration Server Date/Time Server Upgrade Set Modem Interface Setup Shutdown Server Signaling Group , 69 SNMP Traps screen200, 207, 211, 212, 230, 265, 277, 280, 285, 286, 287, 295, 297, 300, 301, 304, 305, 307, 308, 309 software version Speed Dial List SSH Keys Station Status Summary System Capacity , 76 System Logs System Parameters System Parameters Customer Options page System Parameters Customer Options page 2 20, 82 System Parameters Customer Options page 420, 83, 85 System Parameters Features page System Parameters-Call Coverage/Call Forwarding28, 79 System-Parameters Customer-Options System-Parameters Customer-Options screen page 180 Temperature/Voltage Tone and Volume Settings Top Top-level Traceroute results Trunk Group Trunk Group page , 86 Trunk Group page , 94, 97 Trunk Group page Trunk Group page , 101 Update Contact Update Group Update Password User User Memos Watchers Search User screens security files , 268, 271 issues log file remote access utilities select free extension screen Select User screens Send All Calls send all calls FNU Server Configuration screen Server Date/Time screen Server screen Server Status Server Upgrades screen SES call processing FRC 3325 compliance Session Initiated Protocol glossary definition Set Modem Interface screen settings.txt file Setup screen Setup screens screens Setup Shutdown Server screen Signaling Group screen Bypass If IP Threshold Exceeded field Issue 2.0 May

348 Index Enable Layer 3 Test field Far-end Domain field Far-end Listen Port field Far-end Network Region field Far-end Node Name field Group Number field Group Type field illustration IP Audio Hairpinning field Near-end Listen Port field Transport Method field Signaling Group screen page 1 Bypass If IP Threshold Exceeded field Direct IP-IP Audio Connections field DTMF over IP field Enable Layer 3 field Far-end Domain field Far-end Network Region field Far-end Node Name field Group Number field Group Type field IP Audio Hairpinning field Near-end Listen Port field Near-end Node Name field Session Establishment Timer field Transport Method field SIP administration administrative screens intercept treatment station screen SIP as OPTIM extension SIP trunks administering , 24 SNMP Traps screen200, 207, 211, 212, 230, 265, 277, 280, 285, 286, 287, 295, 297, 300, 301, 304, 305, 307, 308, 309 Software Version screen Speed Dial List screens SSH Keys screen Station screen Station screen page 1 Type field Status Summary screen subdomain survivable call processor System System Capacity screen SIP Trunks field System Logs screen System Parameters Call Coverage / Call Forwarding screen 79 System Parameters Customer Options page 4 Enhanced EC500 field System Parameters Customer Options screen System Parameters screen page 1 DID/Tie/ISDN/SIP Intercept Treatment field System Parameters screen page 2 Disable call classifier for CCRON over SIP trunks field79 System Parameters-Call Coverage/Call Forwarding screen 79 System-Parameters Customer-Options screen page 1 80 Maximum Off-PBX Telephones - EC500 field Maximum Off-PBX Telephones - OPS field Used field System-Parameters Customer-Options screen page 2 Maximum Administered SIP Trunks field T tasks Contact List , 132 Devices , 149 Extensions , 158, 159 Handles , 161 Memos , 175 Permissions Profile User Profile Watchers , 185 Temperature/Voltage screen terminal requirements terminals Avaya CM OPTIM timeserving Tone and Volume Settings screens Top-level screens Traceroute results screen intro success track availability transfer to voice mail FNU Troubleshooting administering survivable call processors troubleshooting 403 Screening failure call routing disabling connection to Communication Manager 121 domain name incorrect, can t get license modem problems modems no license registrations phones don t work correctly , 121 unblocked watchers version checking Trunk Group screen ACA Assignment field Auth Code field Busy Threshold field CDR Reports field COR field Administering SES on the Avaya S8300 Server

349 Index Dial Access field Digital Loss Group field , 95 Direction field Group Name field Group Number field Group Type field Maintenance Tests field Measured field Night Service field Number of Members field Numbering Format field Outgoing Display field page 1 illustration page 2 illustration Queue Length field Replace Unavailable Numbers field Service Type field Signaling Group field TAC field TN field Trunk Hunt field , 95 Trunk Group screen page Auth Code field Busy Threshold field CDR Reports field COR field Dial Access field Direction field Group Name field Group Number field Group Type field Night Service field Number of Members field Outgoing Display field Queue Length field Service Type field Signaling Group field TAC field TN field Trunk Group screen page Digital Loss Group field Preferred Minimum Session Refresh Interval field. 96 Redirect on OPTIM failure field Unicode Name field Trunk Group screen page 3 ACA Assignment field Maintenance Tests field Measured field Numbering Format field Replace Unavailable Numbers field Trunk Group screen page 4 Mark Users as Phone field Trunk Group screens trunk groups displaying capacities U Unicode Update Contact screens Update Group command Group Details screen Update Group screens Update Password screens Upgrade See "Remaster" upgrade make permanent User Memos screen User Memos screens User screens V version BIOS SAMP or RSA SES software software , 261, 262 software release visiting user , 44, 45 W Watchers task , 185 whisper page activation wizard window Issue 2.0 May

350 Index 348 Administering SES on the Avaya S8300 Server