administering sip enablement services on the avaya s8300 ... · contents issue 1.0 january 2008 1...

Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.

Administering SIP Enablement Services on the Avaya S8300 Server

03-602508Issue 1.0

January 2008

Copyright 2008, Avaya Inc.All Rights Reserved

NoticeWhile 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 03-600758.To locate this document on the web site, simply go to http://www.avaya.com/support and search for the document number in the search box.

Documentation disclaimerAvaya 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 disclaimerAvaya 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.

WarrantyAvaya 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:http://www.avaya.com/support

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 http://support.avaya.com/ThirdPartyLicense/.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 supportAvaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site:http://www.avaya.com/support

http://www.avaya.com/support

http://support.avaya.com/ThirdPartyLicense/

http://www.avaya.com/support/

http://www.avaya.com/support

Contents

Issue 1.0 January 2008 1


Chapter 1: SIP Support in Avaya Communication Manager . . . . . . . 17Introduction to SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17SIP-related support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Requirements for SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 2: Administering Communication Managerfor SIP Enablement Services . . . . . . . . . . . . . . . . . 27

Administering Communication Manager for SIP . . . . . . . . . . . . . . . . . . 27Prepare Communication Manager . . . . . . . . . . . . . . . . . . . . . . . . 28Administer call routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Administer SIP signaling and trunks . . . . . . . . . . . . . . . . . . . . . . . 32Administer stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Redirect calls off the network. . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 3: Communication Manager screen details for SIP . . . . . . . 37SIP administrative screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

ARS/AAR Digit Analysis Table screen . . . . . . . . . . . . . . . . . . . . . . 39ANI Reqd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Call Type (for AAR only) . . . . . . . . . . . . . . . . . . . . . . . . . . 40Call Type (for ARS only) . . . . . . . . . . . . . . . . . . . . . . . . . . 41Dialed String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Location (for the ARS Digit Analysis Table) . . . . . . . . . . . . . . . 42Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Node Num . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Percent Full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Route Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Configuration Set screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Configuration Set Description . . . . . . . . . . . . . . . . . . . . . . . . 45

Dial Plan Analysis screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Call Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Dialed String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Percent Full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Total Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Feature Access Codes screen page 1 . . . . . . . . . . . . . . . . . . . . . . 51Auto Alternate Routing (AAR) Access Code . . . . . . . . . . . . . . . . . 51Auto Route Selection (ARS) Access Code1 . . . . . . . . . . . . . . . . . 51

Feature Related System Parameters screen, page 3 . . . . . . . . . . . . . . 52EMU Inactivity Interval for Deactivation . . . . . . . . . . . . . . . . . . . 52

Incoming Call Handling Treatment screen . . . . . . . . . . . . . . . . . . . . 54

Contents

2 Administering SES on the Avaya S8300 Server


Called Len . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Called Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Del. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Insert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Service/Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

IP Codec Set screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56IP Network Map screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Emergency Location Extension . . . . . . . . . . . . . . . . . . . . . . . 58

IP Network Region screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Authoritative Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Intra-region IP-IP Direct Audio . . . . . . . . . . . . . . . . . . . . . . . . 60Inter-region IP-IP Direct Audio . . . . . . . . . . . . . . . . . . . . . . . . 61Use Default Server Parameters . . . . . . . . . . . . . . . . . . . . . . . . 62Server IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Server Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

IP Node Names screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Proxy Selection Route Pattern . . . . . . . . . . . . . . . . . . . . . . . 65

Media Gateway screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Network Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Numbering—Public/Unknown screen . . . . . . . . . . . . . . . . . . . . . . 66Off-PBX Station Mapping screen page 1 . . . . . . . . . . . . . . . . . . . . . 67

Command parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Station Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Dial Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Phone Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Trunk Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Configuration Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Dial Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Off-PBX Station Mapping screen page 2 . . . . . . . . . . . . . . . . . . . . . 72Station Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Call Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Mapping Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Calls Allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Bridged Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Configuration considerations for SIP phones . . . . . . . . . . . . . . . . 74

Route Pattern screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Contents



Secure SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Signaling Group Page 1 screen. . . . . . . . . . . . . . . . . . . . . . . . . . 77

Group Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Group Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Transport Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Near-end Node Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Far-end Node Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Near-end Listen Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Far-end Listen Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Far-end Network Region . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Far-end Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Bypass If IP Threshold Exceeded . . . . . . . . . . . . . . . . . . . . . 80DTMF over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Session Establishment Timer . . . . . . . . . . . . . . . . . . . . . . . . 80Direct IP-IP Audio Connections . . . . . . . . . . . . . . . . . . . . . . . 81IP Audio Hairpinning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Enable Layer 3 Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Station screen, page 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

System Capacity screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84SIP Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

System-Parameters screens . . . . . . . . . . . . . . . . . . . . . . . . . . . 85DID/Tie/ISDN/SIP Intercept Treatment . . . . . . . . . . . . . . . . . . . . 86Disable call classifier for CCRON over SIP trunks . . . . . . . . . . . . . 87

System-Parameters Customer-Options screen, page 1. . . . . . . . . . . . . 88Maximum Off-PBX Telephones - EC500 . . . . . . . . . . . . . . . . . . . 88Maximum Off-PBX Telephones - OPS . . . . . . . . . . . . . . . . . . . . 88Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

System Parameters Customer Options screen, page 2 . . . . . . . . . . . . . 90Maximum Administered SIP Trunks . . . . . . . . . . . . . . . . . . . . . 90

System Parameters Customer Options screen, page 4 . . . . . . . . . . . . 91ISDN PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Enhanced EC500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91IP Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

System Parameters Customer Options screen, page 5 . . . . . . . . . . . . . 93Private Networking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Trunk Group screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Group Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Group Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95CDR Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Group Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Contents



COR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96TN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97TAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Outgoing Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Dial Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Busy Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Night Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Queue Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Service Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Auth Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Signaling Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Number of Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Trunk Group screen, Page 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 102UNICODE Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Redirect on OPTIM failure . . . . . . . . . . . . . . . . . . . . . . . . . . 102Digital Loss Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Preferred Minimum Session Refresh Interval (sec) . . . . . . . . . . . . 104

Trunk Group screen, Page 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . 105ACA Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Measured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Maintenance Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Numbering Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Prepend '+' to Calling Number?. . . . . . . . . . . . . . . . . . . . . . . . 107Replace Unavailable Numbers . . . . . . . . . . . . . . . . . . . . . . . 107Show ANSWERED BY on Display field . . . . . . . . . . . . . . . . . . . . 108

Trunk Group screen, page 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Mark Users as Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Important: SIP device as an OPS extension . . . . . . . . . . . . . . . . . . . 110

Chapter 4: Administration web interface . . . . . . . . . . . . . . . . . 111Top Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Logon ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Setup screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Setup SIP Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Setup Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Setup Default User Profile and Media Servers . . . . . . . . . . . . . . . . 118

Contents



Setup Default User Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . 118Setup Media Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Edit System Properties screen . . . . . . . . . . . . . . . . . . . . . . . . . . 119SES Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Host Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120SIP Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120SIP License Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Management System Access Login . . . . . . . . . . . . . . . . . . . . . 120Management System Access Password . . . . . . . . . . . . . . . . . . 121DiffServ/TOS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 121802.1 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121DB Log Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Network Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Redundant Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Add Host screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Host IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Profile Service Password . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Host Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Parent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Listen Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Link Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Access Control Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Emergency Contacts Policy . . . . . . . . . . . . . . . . . . . . . . . . . 126Minimum Registration (seconds) . . . . . . . . . . . . . . . . . . . . . . . 127Registration Expiration Timer (seconds). . . . . . . . . . . . . . . . . . . 127Line Reservation Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Outbound Routing Allowed From. . . . . . . . . . . . . . . . . . . . . . . 127Outbound Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Outbound Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Outbound Direct Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . 128Default Ringer Volume. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Default Ringer Cadence . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Default Receiver Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Default Speaker Volume. . . . . . . . . . . . . . . . . . . . . . . . . . . . 128VMM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129VMM Server Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129VMM Server Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129VMM Report Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Edit Default User Profile screen . . . . . . . . . . . . . . . . . . . . . . . . . 130Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Contents



Address 1, Address 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131City . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Country . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131ZIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Add Media Server screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Media Server Interface Name . . . . . . . . . . . . . . . . . . . . . . . . . 133Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133SIP Trunk Link Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133SIP Trunk IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133SIP Trunk Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Media Server Admin Address . . . . . . . . . . . . . . . . . . . . . . . . . 134Media Server Admin Login . . . . . . . . . . . . . . . . . . . . . . . . . . 134Media Server Admin Password/ Password Confirm . . . . . . . . . . . . 134SMS Connection Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Core Router screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Branch Prefix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Branch Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Core Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Total Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

List Handle Maps screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Branch Prefix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137IM Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

User screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Add User task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Contact List task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Devices task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Delete All Displayed Users task . . . . . . . . . . . . . . . . . . . . . . . 140Delete Selected Users task . . . . . . . . . . . . . . . . . . . . . . . . . . 140Extensions task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Handles task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Memos task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Move User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Watchers for User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Contents



Submit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Add User screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Primary Handle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Password, Confirm Password . . . . . . . . . . . . . . . . . . . . . . . 144Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144First Name, Last Name . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Address 1, Address 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145City . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Country . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145ZIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Survivable Call Processor . . . . . . . . . . . . . . . . . . . . . . . . . 145Add Media Server Extension . . . . . . . . . . . . . . . . . . . . . . . . . 145Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

My Contact List task screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Alias. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Telephone #1 / Telephone #2 . . . . . . . . . . . . . . . . . . . . . . . . . 147Handle (link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Group (link). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Add Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Add Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Speed Dial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Reload Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Contact Details screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Update Contact screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Add Contact screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Alias. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Group Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154E-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Track Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Contact Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Contents



Add Group screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Group Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Submit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Speed Dial List screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Alias. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Telephone # . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Delete Contact screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Group Details screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Alias. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Telephone #1 and Telephone #2 . . . . . . . . . . . . . . . . . . . . . . . 161Back to My Contact List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Add Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Delete Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Update Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Delete Group screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Delete all contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Move all contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Back to My Contact List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Yes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164No . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Update Group screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Old Group Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Group Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Back to My Contact List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Submit Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Devices Screen menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167One Touch Dial List screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Save. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Ringer Settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Bridged Appearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Contents



Ringer ON/OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Save. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Tone and Volume Settings screen . . . . . . . . . . . . . . . . . . . . . . . . 172Ringer Cadence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Ringer Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Receiver Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Speaker Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Delete All Displayed Users task . . . . . . . . . . . . . . . . . . . . . . . . 173Delete Selected Users task . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Extensions tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Free . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Edit User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

List Media Server Extensions when user has none . . . . . . . . . . . . . . . 177Add Another Media Server Extension . . . . . . . . . . . . . . . . . . . . 177Assign Free Media Server Extension . . . . . . . . . . . . . . . . . . . . . 177

Add Media Server Extension screen . . . . . . . . . . . . . . . . . . . . . . . 178Add Media Server Extension screen field descriptions . . . . . . . . . . . 178Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Select Free Extension screen . . . . . . . . . . . . . . . . . . . . . . . . . . 180Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Handles task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Edit (Handle) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Delete (Handle) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Add Another Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Edit (Contact). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Delete (Contact) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Add Another Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Add Handle in New Group. . . . . . . . . . . . . . . . . . . . . . . . . . . 184Delete Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Edit Handle detail screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Contents



User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Edit Host Contact screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Contact Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Media Server option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188User option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Add Handle screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Add Host Contact screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Contact and Contact Type. . . . . . . . . . . . . . . . . . . . . . . . . . . 192Media Server option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192User option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Add Handle in a New Group screen . . . . . . . . . . . . . . . . . . . . . . . 193User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Add Group screen commands . . . . . . . . . . . . . . . . . . . . . . . . 194Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

User Memos screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196List of memos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Add Memo box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Add Memo button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Move User Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Moving a user to another home server . . . . . . . . . . . . . . . . . . . . . 199Permissions screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Current Permissions Type . . . . . . . . . . . . . . . . . . . . . . . . . . 200Change Permissions Type . . . . . . . . . . . . . . . . . . . . . . . . . . 201Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Change Permissions Type . . . . . . . . . . . . . . . . . . . . . . . . . . 201Allow List/Block List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Contents



Add Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Edit User Profile screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Password, Confirm Password . . . . . . . . . . . . . . . . . . . . . . . . 204Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204First Name, Last Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Address 1, Address 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205City . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Country . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205ZIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Watchers Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Current Permissions Type . . . . . . . . . . . . . . . . . . . . . . . . . . 206Contact List Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Unknown (SIP Users) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Go to Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Go to Contact List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Search User screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209First Name, Last Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Address 1, Address 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210City . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Country . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210ZIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Select User screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Update Password screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Password, Admin_Password_Confirm . . . . . . . . . . . . . . . . . . . 213Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Default Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Moving a user to another home server from Edit Profile screen . . . . . . . . 214Confirm Delete User screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Confirm Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Delete Extensions Also . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216OK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Contents



Cancel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Chapter 5: Maintenance Web Interface . . . . . . . . . . . . . . . . . . 217Alarms screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Current Alarms screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Product ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219EvtID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Lvl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220Server Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

SNMP Traps screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222SNMP Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Community or User Name. . . . . . . . . . . . . . . . . . . . . . . . . . . 222V3 Security Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Authentication Password (v3 only) . . . . . . . . . . . . . . . . . . . . . . 222Privacy Password (v3 only) . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Diagnostics screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223System Logs screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Select Log Types (multiple log output will be merged) . . . . . . . . . . . 225Select a View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Select Event Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Match Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Display Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Temperature/Voltage screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 228Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Crit_Low . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Warn_Low . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Warn_High . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Crit_High . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Ping screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230Host Name Or IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Contents



UPS Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Execute Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Successful ping results . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Unsuccessful ping results . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Traceroute screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Host Name or IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Successful traceroute results. . . . . . . . . . . . . . . . . . . . . . . . . 234Unsuccessful traceroute results . . . . . . . . . . . . . . . . . . . . . . . 235

Netstat screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Output type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Output format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Show only the following output families . . . . . . . . . . . . . . . . . . . 237Active Internet connections (w/o servers) . . . . . . . . . . . . . . . . . . 237Active UNIX domain sockets (w/o servers) . . . . . . . . . . . . . . . . . 238

Modem Test screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Test Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Troubleshooting modem problems. . . . . . . . . . . . . . . . . . . . . . . . 241Server screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Major Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Minor Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Server Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Process Status screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Shutdown Server screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247Options to Shut down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Server Date/Time screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248General Notes on Timeserving . . . . . . . . . . . . . . . . . . . . . . . . 249Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Select Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Software Version screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250SES Release String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Software Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Server BIOS Build ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Contents



SAMP Version ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Data Backup/Restore screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Backup Now screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Backup Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Backup History screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256Schedule Backup screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Data set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257Day . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Add a backup schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Backup Logs screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Data Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261File Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

View/Restore Data screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263Network Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264Local directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264Local PC card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Restore History screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Format PC Card screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Security screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268Modem screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Modem Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269Solving modem problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270FTP screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273Transfer procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Authentication File screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275File Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276Install the Authentication file I previously downloaded . . . . . . . . . . . 276Install the Authentication file I specify below . . . . . . . . . . . . . . . . 276

Contents



Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276Firewall screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Input to server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Output from server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Port/Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Tripwire screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Tripwire Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Audit Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Trusted Certificate screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284Trusted Certificate screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285Issued To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285Issued By . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286Expiration Date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Certificate Information—General screen . . . . . . . . . . . . . . . . . . . . 287Certificate Information—Details . . . . . . . . . . . . . . . . . . . . . . . . . 288Certificate Export screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Certificate Import screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290SSH Keys screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Current SSH public keys . . . . . . . . . . . . . . . . . . . . . . . . . . . 292Generate New SSH Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Miscellaneous screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294File(s) to download from the machine I'musing to connect to the server. . . . . . . . . . . . . . . . . . . . . . . . 294

File(s) to download from the LAN using URL . . . . . . . . . . . . . . . . 294Install this file on the local server . . . . . . . . . . . . . . . . . . . . . . 295

Appendix A: Feature requirement specifications . . . . . . . . . . . . . 297Call processing software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

RFC 3325 compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Compliance with RFC 3325 . . . . . . . . . . . . . . . . . . . . . . . . . . 297

FNU requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Send All Calls of the endpoint’s own (1111) extension FNU structure. . . 308

Contents



Send All Calls of another endpoint’s (2222) extension FNU structure . . . 309

Appendix B: Terminal requirements for SIP . . . . . . . . . . . . . . . . 311Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323


Chapter 1: SIP Support in Avaya Communication Manager

This chapter describes the support for Session Initiated Protocol (SIP) that is incorporated into release 5.0 of Avaya Communication Manager, which runs on Avaya S8300, S8400, S8500- series, or S8700-series servers, or coresident with SIP Enablement Services on a new S8300C.

This section contains these major topics:

● Introduction to SIP on page 19

● SIP-related support on page 21

● Requirements for SIP on page 23

● SIP administrative screens on page 37

● SIP device as an OPS extension on page 107

Introduction to SIPThis section introduces SIP for release 5.0 of Communication Manager and is divided into two sections:

● What is SIP? on page 19

● How does SIP integrate into your system? on page 20

What is SIP? SIP is an endpoint-oriented signalling standard that is defined by the Internet Engineering Task Force (IETF). SIP is a text-based protocol based on elements of Hypertext Transfer Protocol (HTTP) and Simple Mail Transfer Protocol (SMTP). SIP supports several types of communication sessions that include voice, video, or instant text messaging.

As implemented by Avaya in Communication Manager, SIP trunking functionality is available on the Linux-based Avaya S8300, S8400, S8500-series, and S8700-series servers.

SIP uses an OATS call-flow model, in addition to others, and a Uniform Resource Indicator, or URI-based, feature access extension.

Because SIP-enabled endpoints are managed by Communication Manager, many Communication Manager features can be extended to these endpoints.

SIP Support in Avaya Communication Manager

18 Administering SES on S8300

The server(s) running Communication Manager in an Avaya system function in three ways:

● As Plain Old Telephone Service (POTS) gateways

● As support for name and number delivery between and among the various non-SIP endpoints that Communication Manager supports. These endpoints can be, for example, analog, Digital Communications Protocol (DCP), or H.323 stations, and analog, digital or Internet Protocol (IP) trunks.

● As support for new SIP-enabled endpoints, such as the Avaya 9600 SIP IP telephones.

In addition to its calling capabilities, the SIP-enabled release of Avaya IP SoftPhone R5 and later, and Avaya one-X™ Desktop Edition R2.1, include Instant Messaging (IM) client software, as well as providing full support for the existing H.323 standard for call control.

How does SIP integrate into your system?The support for SIP that is built into Avaya Communication Manager is designed to help SIP supplement your present system:

● SIP offloads registrations to SES servers, and this improves registration and recovery time of system outages.

● SIP is built around published standards. These standards include both IETF Requests for Comments (RFCs) and Internet-Drafts. The standards that the Avaya SIP solution implements include, but are not limited to, these standards:

- RFC 3261 (SIP)

- RFC 3265 (SIP Event Notification)

- RFC 3515 (SIP REFER Method)

- RFC 3842 (SIP Message Summary and Message Waiting Indication Event Package)

- RFC 2327 (Session Description Protocol)

- RFC 3264 (SDP Offer/Answer Model)

- RFC 2617 (HTTP Digest Authentication)

- RFC 3325, "Network Asserted Identity" is complied with on the SES proxy servers

- RFC 3891, "The SIP ’Replaces’ Header"

- RFC 4028, "Session Timers in the SIP"

● SIP integrates with traditional circuit-switched interfaces and IP-switched interfaces. With this integration, the telecommunication system can evolve easily from a circuit-switched telephony infrastructure to the next-generation IP infrastructure, including SIP.

● SIP positions customers to leverage, as needed, the increasing number and power of SIP-enabled applications, such as instant messaging and presence.

SIP-related support


Note:Note: Building SIP support into Communication Manager adds another element to the

modular family of Avaya components, which seamlessly delivers a business’s voice and messaging capabilities over an IP network. Avaya continues enhancing the value it provides to customers in a standards-based, IP communications infrastructure.

Avaya uses a modular and extensible system architecture to implement SIP support. This architecture has a unique benefit for Avaya customers: the set of features SIP supports is augmented by those features that Communication Manager supports. Any server running a SIP-enabled release of Communication Manager becomes, in effect, a telephony feature server. The server running Communication Manager is accessible from any SIP endpoint and provides access transparently to many telephony features that published SIP standards currently do not address.

SIP-related supportThe following sections describe the areas that support SIP in Communication Manager running on the Avaya S8300, S8400, S8500-series, and S8700-series servers, or with release 5.0, concurrently and coresident with SIP Enablement Services on a new Avaya S8300 server:

● Trunking on page 21

● Stations on page 22

● CDR on page 22

● Access control on page 22

TrunkingWith support for SIP trunks, an enterprise can connect servers to a SIP-enabled proxy server, specifically, a server running Avaya SIP Enablement Services, which can then extend to a third-party SIP service provider. The trunk support provided in Communication Manager complies with SIP standards, specifically IETF RFC 3261, and so interoperates with any SIP-enabled endpoint/station that also complies with the standard.

In complex configurations with Avaya S8700 series servers, the signaling-group properties in Communication Manager must be administered to match in certain ways. For more information see SIP trunk engineering notes on page 24.



StationsSupport for SIP stations that use SIP trunks allows any fully compliant SIP telephone to interoperate with Avaya telephones. This means that any SIP telephone, from Avaya or a third party, that complies with the appropriate RFC or Internet-Draft standards can:

● Dial and be dialed as an extension in the enterprise dial plan.

● Put calls on hold, perform transfers and participate in conference calls.

SIP stations that are administered in Communication Manager as off-PBX station (OPS) stations support most Extended Access features, such as call park, call pick-up, and priority calls. To activate these features, use station buttons set up to dial special extensions, that is, Feature Name Extensions (FNEs).

For more details, see Avaya Extension to Cellular User’s Guide, Issue 6, doc ID 210-100-700, and the Avaya Extension to Cellular and OPS Installation and Administration Guide, Issue 7, doc ID 210-100-500.

CDR Avaya provides support for complete Call Detail Recording (CDR) for all SIP calls based on the URIs of the calls.

Access controlAvaya provides support for full access control to external trunks from any telephone. Both SIP trunks and SIP endpoints require network access to Avaya SIP Enablement Services. Note that some other means of access control, such as a firewall, is usually required to control network access from outside the enterprise, that is, to the SES system and through it, to SIP trunks or SIP endpoints inside the enterprise.

Requirements for SIP


Requirements for SIPThe minimum requirements for SES added to a Communication Manager installation on an S8300 server are described in these sections:

● Software on page 23

● Hardware on page 23

● Firmware on page 24

● SIP trunk engineering notes on page 24

● Related systems on page 26

Software Support for SES can be enabled in Avaya Communication Manager release 5.0 or greater running on the Linux-based S8300 server. The appropriate (separate from Communication Manager) Avaya remote feature activation (RFA) licensing files for SIP are also required.

Hardware The SIP-enabled releases of Communication Manager run on the following Avaya servers:

● S8300 (including concurrently and coresident with SES 5.0 on a new S8300 server)

● S8400 and the new S8400B, when available

● S8500 series: S8500 (through release 4.x), S8500B and S8500C

● S8700 series: S8700, S8710, S8720, and the new S8730.

Note:Note: Any of these servers may also control one or more Avaya gateways.

All processor ethernet interfaces on S8400 or S8500-series hardware, control LAN (CLAN) or processor CLAN (procr) IP interfaces, must be configured correctly. For more information, see this document:

Administration for Network Connectivity for Avaya Communication Manager, doc ID 555-233-504

For more information see Installing, Administering, Maintaining, and Troubleshooting SIP Enablement Services, doc ID 03-600768, Avaya’s SIP proxy, endpoint registration and instant- messaging server. This product connects to Avaya Communication Manager, and provides SIP-enabled applications such as enterprise instant messaging (IM) that uses the client available in Avaya IP SoftPhone R5 or later, or the Avaya one-X™ Desktop Edition R2 or later.



Firmware Note that SIP standards dictate that dual-tone multifrequency (DTMF) tones be supported within the Real-time Transfer Protocol (RTP) data stream. Interoperability with certain third-party, SIP-enabled devices may depend on this. This requirement further demands that the newest releases of Avaya’s VoIP engine be installed throughout your system to support RTP-payload.

For example, any TN2302AP circuit packs that are present in your system must have the most recent firmware version to support DTMF tones within the RTP data stream. Table 1 shows what circuit pack you need for various versions of firmware and hardware.

SIP trunk engineering notesThe SIP signaling group administered on Communication Manager defines the characteristics of a signaling connection.

The total number of calls that can be carried over a single signaling connection is limited by the bandwidth available. There is no true physical trunk when using SIP. Because of this, there is no physical limit on how many calls or trunk members you can set up with a particular signaling connection.

However, using the signaling group and trunk group administrative screens in Communication Manager is also useful for SIP. Doing so extends several Communication Manager features to SIP. Communication Manager normally limits signaling groups to 255 trunk members, limiting each signaling group to 255 calls. For SIP groups, Avaya has removed the restriction that each combination of far-end and near-end IP address/port must be unique for each signaling group. Therefore, for SIP groups, multiple signaling groups can use the same signaling connections.

More than one signaling group may be administered to share a signaling connection with exactly the same properties of:

● far-end node-name (fe-nn)

● far-end port (fe-pt)

● near-end node-name (ne-nn)

● near-end port (ne-pt).

Table 1: TN2302AP hardware and firmware combinations

Media Processor Avaya G700/G350/G250 Gateway VoIP

Minimum for SIP V72 V22 or greater

Highly recommended

V93 V93



This kind of administration supports more than 255 calls on the same SIP-based signaling connection, where a signaling connection is defined as <near-end node-name, near-end port, far-end node-name, far-end port>.

For an incoming call, Communication Manager 5.0 compares the caller’s domain, as specified in the header of the SIP INVITE message, with the far-end domains specified for the administered SIP signaling groups. If there is a signaling group with a matching far-end domain, that signaling group and its associated trunking resources will be used to handle the incoming SIP call. If there is not a match, then a signaling group with a blank entry for far-end domain will be used. Avaya recommends that at least one SIP signaling group per signaling connection be administered with a blank domain. This blank domain terminates calls from any far-end domains not specifically assigned to other groups. Otherwise, if no matching or blank groups exist, then any SIP signaling group that has trunks available may be used.

All signaling groups that have identical node names/ports, as well as the SIP trunk groups using each of these signaling groups, should be administered with identical properties. That is, fields on this screen should match the analogous fields on the administrative screens. Of course, different SIP signaling connections will differ with respect to their near-end and/or far-end node names/port numbers, and they should have their SIP trunk’s signaling groups administered accordingly. It is not appropriate to administer them identically.

In Communication Manager, the number of simultaneous SIP signaling connections is limited to 16. These must be administered as TLS connections. You may administer more than 16, but the run-time limit of simultaneous signaling connections is 16. Remember that a signaling connection is not the same as a signaling group, and that more than one SIP signaling group can and should share the same signaling connection.

TLS links for failoverThere are 16 available TLS links in SES 5.0 and Communication Manager 5.0. For each SIP signaling group administered, when active, it will utilize 1 link on each system (near-end and far-end). In duplexed home-server configurations, reserve some TLS links to support failover.

If your configuration is a duplexed SES home server, and some fault occurs that causes a failover to the standby home server, the newly active home server sets up another TLS link to the server running Communication Manager. (It might take 15 minutes to bring down the TLS link to the previously active SES Home).

TLS link utilization is real-time. SES and Communication Manager set up TLS links for SIP when they send the very first SIP request, such as INVITE, or SUBSCRIBE/NOTIFY. The link remains active as long as there is SIP message traffic.

Note that the limit of 16 TLS links is a restriction of Communications Manager.

For example, if you have 10 SIP trunk groups, you have the possibility of a maximum of 10 TLS links in use at one time.



You can have multiple CLANs associated with SES. With multiple CLANs, you can administer them for load-sharing purposes. The Avaya SIP solution does not support alternate CLANs to handle CLAN failure scenarios.

From the SES administrator’s perspective, each SIP endpoint is administered so that it uses one of the available CLANs. If there is an SES home supporting 3,000 users, and you administer two CLANs to support that SES home, administer 1,500 SIP endpoints to use CLAN #1 and the other 1,500 to use CLAN #2. If CLAN #1 goes down, then those 1,500 SIP endpoints would not be able to make calls. In this case, the users on CLAN #2 would not be affected. Currently, there is no mechanism to administer an alternate CLAN on the SES Administration web-interface screens.

Related systemsSee the Installing, Administering, Maintaining and Troubleshooting SIP Enablement Services document, Issue 5 or later, doc ID 03-600768, for details on the SIP proxy registrar server.

See the Administration for Network Connectivity for Avaya Communication Manager, 555-233-504, for details on assuring that IP interfaces are set up properly for an SES system.

See the Avaya Server Availability Management Processor (SAMP) User Guide for details on the remote maintenance board for the Avaya S8500-series servers.

SIP Support in Avaya Communication Manager, 555-245-206, for details on setting up SIP trunks on the server running Communication Manager.

See the following documents for details on setting up endpoints as OPS-type stations in Avaya Communication Manager:

● Avaya Extension to Cellular User’s Guide, 210-100-700

● Avaya Extension to Cellular and OPS Installation and Administration Guide, 210-100-500

See the following documentation for details on setting up and using your Avaya 9600-series SIP IP telephone as a station for SIP voice calling:

● Avaya one-X™ Deskphone Edition for 9600 Series SIP IP Telephones Installation and Maintenance Guide, 16-601943

● Avaya one-X™ Deskphone Edition for 9600 Series SIP IP Telephones Administrator Guide, 16-601944

● Avaya one-X™ Deskphone SIP for 9620 IP Telephone User Guide, 16-601945

● Avaya one-X™ Deskphone SIP for 9630/9630G IP Telephone User Guide, 16-601946

● Avaya one-X™ Deskphone SIP for 9640/9640G IP Telephone User Guide, 16-602403

● Avaya one-X™ Deskphone SIP for 9620 IP Telephone Quick Reference, 16-601947



● Avaya one-X™ Deskphone SIP for 9630/9630G IP Telephone Quick Reference, 16-601948

● Avaya one-X™ Deskphone SIP for 9640/9640G IP Telephone Quick Reference, 16-602408.

See the following documentation for details on setting up and using your Avaya 4600-series SIP IP telephone as a station for SIP voice calling:

● 4600 series SIP Telephone User’s Guide, doc ID 16-300035

● 4600 series SIP Telephone Administrator’s Guide, doc ID 16-300037

● 4600 series SIP Telephone Quick Setup Guide, doc ID 16-300158

● 4600 Series IP Telephone R2.2 LAN Administrator’s Guide, doc ID 555-233-507

● 4600 Series IP Telephone R2.2 Installation Guide, doc ID 555-233-128

● 4602/4602SW SIP Telephone R2.2 User’s Guide, doc ID 16-300470

● 4602/4602SW SIP Telephone Quick Reference, doc ID 16-3004715

● 4610SW SIP Telephone R2.2 User’s Guide, doc ID 16-300472

● 4610SW SIP Telephone Quick Reference, doc ID 16-300473

● 4620SW/4621SW SIP Telephone R2.2 User’s Guide, doc ID 16-300474

● 4620SW/4621SW SIP Telephone Quick Reference, doc ID 16-300475

● 4600 Series IP Telephone Documentation Library, doc ID 16-300091.

See the following documentation for details on setting up and using your Avaya 16CC (Call Center) SIP IP telephone as a station for SIP voice calling:

● Getting Started with Avaya Call Center 5.0 and Avaya Agent Deskphone 16CC, 129214

● Avaya Agent Deskphone 16CC Quick Reference, 16-602097

● Avaya Agent Deskphone 16CC Administrator Guide, 16-602093

● Avaya Agent Deskphone 16CC Installation and Maintenance Guide, 16-602095

● Avaya Agent Deskphone 16CC User Guide, 16-602096.

See the following documentation for details on setting up SIP softphone clients as stations:

● Avaya one-X™ Desktop Edition Quick Setup Guide

● Avaya one-X™ Desktop Edition Getting Started

For an overview of all the different components and the associated tasks that support Avaya’s SIP solution, see the SIP Implementation Guide, doc ID 16-300140.


Chapter 2: Administering Communication Managerfor 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 37

● Important: SIP device as an OPS extension on page 110

Administering Communication Manager for SIPThis 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 28

● Administer call routing on page 30

● Administer SIP signaling and trunks on page 32

● Administer stations on page 35

● Redirect calls off the network on page 36

● Administration for visiting users on page 36.

Administering Communication Manager for SIP Enablement Services


Prepare Communication ManagerComplete these steps to prepare Communication Manager for SES.

1. Verify that your system supports and is correctly configured for IP connectivity.

See Administration for Network Connectivity for Avaya Communication Manager, doc ID 555-233-504.

2. Go to the System Capacity screen.

Figure 19: System Capacity screen on page 84.

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 91.

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 90

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)


Administering Communication Manager for SIP


5. Go to the System Parameters Customer Options screen, page. 1Figure 22: System Parameters Customer Options screen, page 1 on page 88.

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 phonesIn 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.


6. Go to the IP Node Names screen.

Figure 10: IP Node Names screen on page 63.

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 57.

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 59.

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.



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 51.

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 93.

2. Go to the ARS Digit Analysis Table screen.

Figure 1: ARS Digit Analysis Table screen on page 39.

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 32.

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 75.

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.



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 66.

6. Go to the Locations screen.

Figure 11: Locations screen on page 64.

Type the appropriate Proxy Selection Route Pattern in the field corresponding to each location employing a SIP proxy server.



Administer SIP signaling and trunksUse 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 77.

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. In the Near-end Node Name field, type the name of the IP interface at the near (local) end of the SIP trunk signaling group.

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.

d. In the Far-end Node Name field, enter the name of the node that you administered as the SIP proxy server (that is, an SES Edge 5.0 server) in Step 7.

e. In the Near-End Listen Port field, type the recommended TLS port value of 5061.

f. In the Far-end Listen Port field, type the recommended TLS port value of 5061.

g. 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.

h. 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.

i. In the field DTMF over IP, make sure that the value is rtp-payload.

j. 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.

k. 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 86.

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 94:

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 94, 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 28). For more information, see Figure 19: System Capacity screen on page 84.

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 102.

Set the field Group type to sip.

Administer the other fields on this screen as necessary for your Avaya system.


Trunk Group screen, page 3 on page 105.

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.




Trunk Group screen, page 4 on page 109.

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 66.



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 83.

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 45.

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 67.

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 72.

Add more station-mapping data for SIP endpoints on page 2 of this screen.



Redirect calls off the networkOne 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 87.

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 52. 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.


Chapter 3: 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 screensThis section explains how to administer the following Communication Manager screens to support SIP trunking:

● ARS/AAR Digit Analysis Table screen on page 39

● Configuration Set screen on page 45

● Dial Plan Analysis screen on page 46

● Feature Access Codes screen page 1 on page 51

● Feature Related System Parameters screen, page 3 on page 52

● Incoming Call Handling Treatment screen on page 54

● IP Codec Set screen on page 56

Communication Manager screen details for SIP


● IP Network Map screen on page 57

● IP Network Region screen on page 59

● IP Node Names screen on page 63

● Locations screen on page 64

● Media Gateway screen on page 65

● Numbering—Public/Unknown screen on page 66

● Off-PBX Station Mapping screen page 1 on page 67

● Off-PBX Station Mapping screen page 2 on page 72

● Route Pattern screen on page 75

● Signaling Group Page 1 screen on page 77

● Station screen, page 1 on page 83

● System Capacity screen on page 84

● System-Parameters screens on page 85

● Important: SIP device as an OPS extension on page 110

● Trunk Group screens on page 94These 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 Administration for Network Connectivity for Avaya Communication Manager and the Avaya Communication Manager Administrator Guide, 03-300509, for more details about all the Avaya 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 110. 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 110.

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

ANI Reqd

change ars analysis Page 1 of XARS DIGIT ANALYSIS TABLE

Location: ___ Percent Full: ___

Dialed Total Route Call Node ANI ReqdString Min Max Pattern Type Num

_________________ __ __ _____ ____ ___ n_________________ __ __ _____ ____ ___ n_________________ __ __ _____ ____ ___ n_________________ __ __ _____ ____ ___ n_________________ __ __ _____ ____ ___ n_________________ __ __ _____ ____ ___ n_________________ __ __ _____ ____ ___ n_________________ __ __ _____ ____ ___ n

Valid entries Usage

y/n 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.

r 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.



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.

ISDN Protocol

Valid entries Usage

aar Regular AAR calls.

intl The Route Index contains public network ISDN trunks that require international type of number encodings.

pubu The Route Index contains public network ISDN trunks that require international type of number encodings.

lev0 to lev2 Specify ISDN Private Numbering Plan (PNP) number formats.

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)



Call Type (for ARS only)

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 297-1234 and the AAR or ARS Digit Analysis Table has dialed string entries of 297-1 and 297-123, the match is on the 297-123 entry.

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



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.

Location (for the ARS Digit Analysis Table)

This is a display-only field on the ARS Digit Analysis Table screen shown in Figure 1.

Max

In Figure 1 this is appears as the Total Max field.

Valid entries Usage

0 to 9 Enter up to 18 digits that the call-processing server analyzes.

*, x, X Wildcard characters

Valid entries Usage

1 to 64 Defines the location of the server running Avaya 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.

Valid entries Usage

Between Min and 28 Enter the maximum number of user-dialed digits the system collects to match to the dialed string.



Min

In Figure 1 this appears as the Total Min field.

Node Num

In Figure 1, enter the number of the node.

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 Avaya Communication Manager to use for this dialed string.

Valid entries Usage

1 to Max Enter the minimum number of user-dialed digits that the system collects to match to the dialed string.

Valid entries Usage

1 to 999orblank

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.

Valid entries Usage

p1 to p2000 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.



node Designates node number routing.

deny Block the call.

Valid entries Usage



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

Configuration Set Description

Describes the purpose of the configuration set.

change off-pbx-telephone configuration-set 1 Page 1 of 1

CONFIGURATION SET: 1

Configuration Set Description: ___________________Calling Number Style: networkCDR for Origination: phone-number

CDR for Calls to EC500 Destination? yFast Connect on Origination? n

Post Connect Dialing Options: dtmfCellular Voice Mail Detection: none

Barge-in Tone? nCalling Number Verification? y

Identity when Bridging: principal

Valid entries Usage

Up to 20 alphanumeric characters or blank

For example, EC500 handsets.For SIP, enter SIP Phone.



Dial Plan Analysis screenThe 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 Avaya 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

Call Type

display dialplan analysis Page 1 of xDIAL PLAN ANALYSIS TABLE

Percent Full: 7Dialed Total Call Dialed Total Call Dialed Total CallString Length Type String Length Type String Length Type

00 2 attd1 3 dac2 4 ext3 4 ext3 1 aar4 1 ars4 5 ext5 5 ext5 7 ext

Valid entries Usage

aar 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.



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 Avaya Distributed Office 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 attendantusing 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.

Valid entries Usage



dac 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.

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.

ext 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 theAAR or ARS access code, then it must have the longest total length in the dial plan.

Valid entries Usage



pext 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.

Valid entries Usage



Dialed String

The dialed string in the Dial Plan Analysis screen contains the digits that Avaya 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.

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 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.

Valid entries Usage

1 to 2 for attd1 to 4 for dac1 to 4 for fac1 to 7 for ext2 to 6 for pext

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.



Feature Access Codes screen page 1This 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.

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.

change feature-access-codes Page 1 of xFEATURE 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 Code1: ____ 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: ____



Feature Related System Parameters screen, page 3For 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

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 2 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.

display system-parameters feature Page 3 of 17

FEATURE-RELATED SYSTEM PARAMETERSTTI/PSA PARAMETERS

WARNING! SEE USER DOCUMENTATION BEFORE CHANGING TTI STATE

Terminal Translation Initialization (TTI) Enabled? n

Customer Telephone Activation (CTA) Enabled? nDon’t Answer Criteria For Logged Off IP/PSA?TTI Stations? n

EMU PARAMETERSEMU Inactivity Interval for Deactivation (hours): 1

CALLPROCESSING OVERLOAD MITIGATIONRestrict Calls: stations-first



Table 2: Compare SIP Visiting User timer with EMU timer

SES’s SIP Visiting User Timer

Communication Manager EMU Timer

Phone types SIP phones, incl. Avaya one-X™ Deskphone SIP

H.323 or DCP type phones

E911 call routed locally/ CPN sent from visited phone*

*. 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.

Supported Supported

Login Same login from any phone

Requires FAC/PIN for login at visited phone

Designating active phone

Most-recently registered phone is the active phoneOR The active phone is set in the SIP PIM web interface.

Most recent registration is "active"

Three states: Active, inactive, unregistered

Supports all three states Supports only two states: active and unregistered states

Phone features dependencies

Depends on home phone functionality/user profile

Depends on visited phone functionality

Inactivity timer Supported Supported



Incoming Call Handling Treatment screenFor 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)

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

change inc-call-handling-trmt trunk-group1 Page 1 of X

INCOMING CALL HANDLING TREATMENT

Service/ Called Called Del Insert Feature Len Number _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________ _____________ ___ _______________ ___ ______________



with the specified Service/Feature can match in this field. Valid entries are up to 16 digits, or leave blank.

Del

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.

Insert

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.



IP Codec Set screenWhat 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

Figure 7: IP Codec Set screen page 2

change ip-codec-set n Page 1 of xIP Codec Set

Codec Set: 1

Audio Silence Frames PacketCodec Suppression Per Pkt Size (ms)

1: G.711MU y 3 302:_______________ _ _ __3:_______________ _ _ __4:_______________ _ _ __5:_______________ _ _ __6:_______________ _ _ __7:_______________ _ _ __Media Encryption:1: aes2: aea3: srtp-aescm128-hmac80

change ip-codec-set n Page 2 of xIP Codec Set

Allow Direct-IP Multimedia? yMaximum 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



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

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.

change ip-network-map Page 1 of x IP ADDRESS MAPPING

EmergencySubnet Location

From IP Address (To IP Address) or Mask) Region VLAN Extension__1.__2.__3.__0 __1.__2.__3.255 24 _1_ __3 __________1.__2.__4.__4 __1.__2.__4.__4 32 _2_ __0 __________1.__2.__4.__5 __1.__2.__4.__5 __ _3_ __0 __________1.__2.__4.__6 __1.__2.__4.__9 __ _4_ __4 ________



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 59.

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 64, 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 59.

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:

● 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).

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.

Valid entries Usage1 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.

Valid entries Usage0 to 9 (up to 7 digits) Enter the emergency location extension for this station.

Default is blank.



IP Network Region screenThe SIP-related fields are in bold in Figure 9.

Figure 9: IP Network Region screen

Region

You can change the properties of each region administered in the IP Network Map screen on page 57 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.

change ip-network-region 1 Page 1 of 19 IP NETWORK REGION Region: 1Location: 1 Authoritative Domain: Name: Intra-region IP-IP Direct Audio: yMEDIA PARAMETERS Inter-region IP-IP Direct Audio: y Codec Set: 1 IP Audio Hairpinning? yUDP Port Min: 2048 UDP Port Max: 3028 RTCP Reporting Enabled? y RTCP MONITOR SERVER PARAMETERSDIFFSERV/TOS PARAMETERS Use Default Server Parameters? n Call Control PHB Value: Server IP Address: . . . Audio PHB Value: Server Port: 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 PARAMETERSH.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



This field designates the name or IP address of the domain for which this network region is responsible or authoritative.

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.

Subdomains are not supported. You may not 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 Usage

Up to 20 characters or blank.

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.

Valid entries Usage

y/n 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.



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 22.

native(NAT) 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.

translated(NAT) 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.

Valid entries Usage

Valid entries Usage

y/n 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.

native(NAT) 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.

trnslated(NAT) 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.



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.

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

0 to 255 in a series of four octets.

Enter the IP address for the RTCP Monitor server

Valid entries Usage

1 to 65535 Enter the port number for the RTCP Monitor server.



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

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.

change node-names ip Page 1 of XIP NODE NAMES

Name IP Address Name IP Address1. ______________ ___.___.___.___ 17. ______________ ___.___.___.___2. ______________ ___.___.___.___ 18. ______________ ___.___.___.___3. ______________ ___.___.___.___ 19. ______________ ___.___.___.___4. ______________ ___.___.___.___ 20. ______________ ___.___.___.___5. ______________ ___.___.___.___ 21. ______________ ___.___.___.___6. ______________ ___.___.___.___ 22. ______________ ___.___.___.___7. ______________ ___.___.___.___ 23. ______________ ___.___.___.___8. ______________ ___.___.___.___ 24. ______________ ___.___.___.___9. ______________ ___.___.___.___ 25. ______________ ___.___.___.___10. ______________ ___.___.___.___ 26. ______________ ___.___.___.___11. ______________ ___.___.___.___ 27. ______________ ___.___.___.___12. ______________ ___.___.___.___ 28. ______________ ___.___.___.___13. ______________ ___.___.___.___ 29. ______________ ___.___.___.___14. ______________ ___.___.___.___ 30. ______________ ___.___.___.___15. ______________ ___.___.___.___ 31. ______________ ___.___.___.___16. ______________ ___.___.___.___ 32. ______________ ___.___.___.___

Valid entries Usage

1 to 15 alphanumeric characters

Used as a label for the associated IP address. The node names must be unique for each server and switch.



IP Address

The IP Address column in Figure 10 identifies for the node named in the previous field by it’s dotted octet address.

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

Valid entries Usage

32-bit address (4 decimalnumbers, each in the range 0 to 255)

A unique IP address is assigned to each port onany IP device that is used for a connection.See the Administration for Network Connectivityfor Avaya Communication Manager,doc ID 555-233-504 for more information.

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:00 1 3122. Denver-01______ - 01:00 1 303 ____ ____ __ ____ _______ 3. Lincroft-01____ + 01:00 1 953 ____ ____ __ ____ _______xxx _______________ _ __:__ __ ___ ____ ____ __ ____ _______ xxx _______________ _ __:__ __ ___ ____ ____ __ ____ _______



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.

Media Gateway screen

Figure 12: Media Gateway screen

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.

Valid entries Usage

1 to 999 or blank Type the number of the routing pattern to be used to get to the proxy server.

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 NameV1: # ICC MMV2: ANA MMV3: DCP MMV4: DS1 MM

V8:V9: gateway-announcements

Max Survivable IP Ext:

Announcement board must also be enabled; use ’enable announcement-board’



Numbering—Public/Unknown screenAccess the Numbering — Public/Unknown screen with the command change public-unknown-numbering 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 Page 1 of XNUMBERING - PUBLIC/UNKNOWN FORMAT

TotalExt Extension Trk CPN CPNLen Code Grp(s) Prefix Len12 1234567890123 123456789 123456789012345 12

5 4 777777 105 4 250 30379 105 4 253 30379 105 41 40 303222 115 41 45 55 41 87 30323 105 43 538 75 45 222 75 47 2222 95 61 45 55 406 250 30379 105 406 253 30379 105 418 303538 115 419 222222222222222 155 770 970 8



Off-PBX Station Mapping screen page 1Use 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 Feature Description and Implementation for Avaya Communication Manager, 555-245-205.

This screen relates to the System-Parameters Customer-Options screen, page 1 on page 88.

Figure 14: Off-pbx station mapping screen page 1

Command parameters

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

change off-pbx-telephone station-mapping 67001 Page 1 of 2

STATIONS WITH OFF-PBX TELEPHONE INTEGRATION

Station Application Dial Phone Number Trunk ConfigurationExtension Prefix Selection Set67001 OPS 221 - 67001 aar 1

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>



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.

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 Usage

A valid number in your dial plan

Type an extension number of the office phone up to eight digits. Default is blank.

Valid entries Usage

blank Default is blank.

EC500 Cell phone with Extension to Cellular

OPS SIP-enabled phone

CSP Cell phone with Extension to Cellular provided by the cellular service provider



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.

Phone Number

Enter the phone number of the off-PBX phone.

Trunk Selection

Defines which trunk group you will use for outgoing calls.

Valid entries Usage

blank0 through 9, *, #

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.

Valid entries Usage

0 through 9 Type up to fifteen digits. Enter the complete 10-digit number. Default is blank.

Valid entries Usage

arsaartrunk groupnumber

Indicate which trunk group to use for outgoing calls.



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 Usage

1 through 99blank

Type the number of the Configuration set or sets. Default is blank



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 Usage

blank0 through 9, *, #

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.



Off-PBX Station Mapping screen page 2Finish 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

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.

Call Limit

See Figure 15.

add off-pbx-telephone station-mapping 67001 Page 2 of 2

STATIONS WITH OFF-PBX TELEPHONE INTEGRATION

Station Call Mapping Calls BridgedExtension Limit Mode Allowed Calls67001 10 both all none

Valid entries Usage

a valid number in your dial plan

Type an extension number of the office phone up to eight digits. Default is blank.

Valid entries Usage

blank1 through 10

Set the maximum number of calls that can be active simultaneously. Default is 2.



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.

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 Usage

both 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.

termination 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.

origination 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.

none In the none mode, users cannot originate or receive calls from the office phone with the cell phone.

Valid entries Usage

all Default is all.The cell phone receives both internal and external calls.

internal The cell phone receives only internal calls.

external The cell phone receives only external calls.

none The cell phone does not receive any calls made to the associated office phone.



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.

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 SIPDOMAIN = 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 Avaya Communication Manager instead of the local feature in the phone.

Valid entries Usage

both Default is both.

termination

origination

none For OPS, which SIP often is, you must use none. This enables bridged appearances on OPS phones to work correctly.



Route Pattern screenThe 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

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.

change route-pattern 1 Page 1 of 2 Pattern Number: 1_

Secure SIP? nNo. 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 LAR0 1 2 3 4 W Request Dgts Format

Subaddress1: y y y y y n y none ___ both ept outwats-bnd____ ____ _ ________ none2: y y y y y n y rest _______________ _ ________ next3: y y y y y n y rest _______________ _ ________ rehu4: y y y y y n y rest _______________ _ ________ none5: y y y y y n y rest _______________ _ ________ none6: y y y y y n y rest _______________ _ ________ none



In most instances, leave this field set to n.

To administer the Secure SIP field, choose the behavior you want from the following table.

Valid entries Usage

y/n 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.

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



Signaling Group Page 1 screenThe 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. SIP-specific fields are in bold.

Figure 17: Signaling Group screen, Page 1

Group Number

This is a display-only field showing the signaling group, as shown in Figure 17.

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.

add signaling group 1 Page 1 of 6

SIGNALING GROUP

Group Number _1__ Group Type: sipTransport Method: tls

Near-end Node Name: Far-end Node Name:Near-end Listen Port: 5061 Far-end Listen Port: __5601__

Far-end Network Region: __Far-end Domain: __________________________________

Bypass If IP Threshold Exceeded? n

DTMF over IP: rtp-payload Direct IP-IP Audio Connections? ySession Establishment Timer (min): 3 IP Audio Hairpinning? yEnable Layer 3 Test y

Valid entries Usage

sip 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.

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. Type the node name for the CLANS/procr/PE IP interface in this server.

Additionally, the node name must be administered on the IP Node Names screen and the IP Interfaces screen.

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. Type the node name for the SIP proxy server used for trunks assigned to this signaling group. The node name must be administered on the IP Node Names screen. See Figure 17.

Tip:Tip: If either the node name or port differs for each SIP signaling group, you have

different SIP signaling connections, and you should administer a maximum of 10 using TLS. If you administer more than 10 TLS signaling connections, and they are all in use at the same time, the results may be unpredictable. Note that if the node names and ports match, you may administer as many identical SIP signaling groups using TLS as desired.

Valid entries Usage

tls Default (secure) transport method is TLS. This is the only method supported.

Valid entries Usage

Name of an administered IP node Uniquely identifies the near- end node.

Valid entries Usage

Name of an administered IP node. 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 5061 for SIP over TLS. See Figure 17.

For SIP, set this to 5061.

Far-end Listen Port

The screen displays this field when the Group Type field is either h.323 or sip. See Figure 17.


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 Usage

1719, 1720, or 5000 through 5999

Type an unused port number. The recommended port for SIP over TLS is 5061.

Valid entries Usage

1 through 65535

Type the same number as entered in the Near-end Listen Port field, that is, port entry 5061 for SIP over TLS.

Valid entries Usage

1-250orblank

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.

Bypass If IP Threshold Exceeded

The screen displays this field when the Group Type field is either h.323 or sip. See Figure 17.

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.

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.

Valid entries Usage

Maximum of 40-character string, or blank

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.

Valid entries Usage

y/n 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.

Valid entries Usage

rtp-payload SIP trunks require rtp-payload.



For SIP, the recommendation is to set this to 3 minutes.

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.

For SIP, leave this at the default of y. This value must match the setting for the IP Audio Hairpinning field.

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.

Enable Layer 3 Test

Set this field to y for SIP.

Valid entries Usage

3 through 120 The time in minutes Communication Manager waits before tearing down a ring no answer call.

Valid entries Usage

y/n Type y to save bandwidth resources and improve sound quality of VoIP transmissions for H.323 or SIP trunk groups.

Valid entries Usage

y/n Type y to enable hairpinning for H.323 or SIP trunk groups.Default is y.



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 17.



Station screen, page 1This 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

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.

change station 1014 Page 1 of XSTATION

Extension: 1014 Lock Messages? n BCC: 0Type: 46xx Security Code: TN: 1Port: Coverage Path 1: COR: 1Name: Coverage Path 2: COS: 1

Hunt-to Station:STATION OPTIONS

Loss Group: 2 Personalized Ringing Pattern: 3Data Module? n Message Lamp Ext: 1014Speakerphone: 2-way Mute button enabled? y

Display Language? English Authentication Required?Model: Expansion Module?

Survivable GK Node Name: Media Complex Ext:Survivable COR: IP Softphone? y

Survivable Trunk Dest? Remote Office Phone? yIP Video Softphone?

IP Video?



System Capacity screenThe SIP-related fields are in bold on this screen, as shown in Figure 19:

Figure 19: System Capacity screen

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.

display capacity Page 7 of 12 SYSTEM CAPACITY System Used Available Limit - - - - - - - - - - - - - TRUNKS DS1 Circuit Packs: 10 390 400 DS1 With Echo Cancellation: 0 400 400 ICHT For ISDN Trunks: 0 576 576 ISDN CBC Service Selection Trunks: 1 199 200 Trunk Groups: 34 1966 2000 Trunk Ports: 608 7392 8000 H.323 Trunks (included in ’Trunk ports’): 604 3396 4000Remote Office Trunks (included in ’Trunk ports’): 0 4000 4000 SBS Trunks (included in ’Trunk ports’): 0 1000 1000

SIP Trunks(included in ’Trunk ports’): 764 4236 5000



System-Parameters screensThis 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 85

● System Parameters Call Coverage/Call Forwarding screen, page 2 on page 87

● System-Parameters Customer-Options screen, page 1 on page 88

● System Parameters Customer Options screen, page 2 on page 90



System Parameters Features screen, page 1The Feature-Related System Parameters screen in Figure 20 shows the SIP-related information in bold.

Administer other fields as necessary for your system.



Figure 20: System Parameters Feature screen Page 1

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.

change system-parameters features page 1 1-FEATURE-RELATED SYSTEM PARAMETERS

Self Station Display Enabled? nTrunk-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 Intercept Treatment: attdInternal 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: BellcoreDisplay Calling Number for Room to Room Caller ID Calls?

Valid entries Usage

Extension of a recorded announcement

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.

attd 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.



System Parameters Call Coverage/Call Forwarding screen, page 2The SIP-related fields are in bold on Figure 21.

Figure 21: System Parameters—Call Coverage/Call Forwarding screen

For more details on the other fields on this screen, see the Avaya Communication Manager Administrator Guide, 03-300509.

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.

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? yIgnore Network Answer Supervision? y

Disable call classifier for CCRON over ISDN trunks? nDisable call classifier for CCRON over SIP trunks? n

Valid entries Usage

y Use y to disable the call classifier for CCRON calls over interworked trunk facilities.

n Use n to enable the call classifier for CCRON calls over interworked trunk facilities.



System-Parameters Customer-Options screen, page 1Administer 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

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 22.

display system-parameters customer-options page 1 of 10OPTIONAL FEATURES

UsedG3 Version: V12Location: 1 RFA System ID (SID): 1Platform: 2 RFA Module ID (MID): 1

UsedPlatform Maximum Ports: 44000 597

Maximum Stations: 36000 552Maximum XMOBILE Stations: 1000 0

Maximum Off-PBX Telephones - EC500: 0 0Maximum Off-PBX Telephones - OPS: 600 545

(NOTE: You must logoff & login to effect the permission changes.)



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 67.



System Parameters Customer Options screen, page 2


Maximum Administered SIP Trunks

This field in Figure 23 limits the number of SIP trunks administered.

display system-parameters customer-options page 2 of 10OPTIONAL FEATURES

IP PORT CAPACTIES USED

Maximum Administrered H.323 Trunks: 200 20Maximum Concurrently Registered IP Stations: 50 0

Maximum Administered Remote Office Trunks: 0 0Maximum Concurrently Registered Remote Office Stations: 0 0

Maximum Concurrently Registered IP eCons: 0 0Maximum Video Capable H.323 Stations: 0 0Maximum Video Capable IP Softphones: 0 0

Maximum Administered SIP Trunks: 500 25

Maximum Number of DS1 Boards with Echo Cancellation: 0 0Maximum TN2501 VAL Boards: 10 0

Maximum G250/G350/G700 CAL Sources: 10 0Maximum TN2602 VoIP Channels: 10000 96

Maximum Number of Expanded Meet-me Conference Ports: 0 0




System Parameters Customer Options screen, page 4 The SIP-related fields on this screen are in bold.


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.

display system-parameters customer-options Page 4 of 10OPTIONAL FEATURES

Emergency Access to Attendant? y IP Stations? yEnable ’dadmin’ Login? y Internet Protocol (IP) PNC? yEnhanced Conferencing? y ISDN Feature Plus? y

Enhanced EC500? y ISDN Network Call Redirection? yEnterprise Survivable Server? n

Enterprise Wide Licensing? y ISDN-BRI Trunks? yESS Administration? n

Extended Cvg/Fwd Admin? y ISDN PRI? yExternal Device Alarm Admin? y Local Survivable Processor? y

y Malicious Call Trace? yMedia Encryption Over IP? y

External Device Alarm Admin? y Mode Code for Centralized Voice Mail? yFive Port Networks Max per MCC? y

Flexible Billing? y Multifrequency Signaling? yForced Entry of Account Codes? y Multimedia Appl.Server Interface (MASI)? y

Global Call Classification? y Multimedia Call Handling (Basic)? yHospitality (Basic)? y Multimedia Call Handling (Enhanced)? y

Hospitality (G3V3 Enhancements)? yIP Trunks? y

IP Attendant Consoles? y




IP Trunks

Controls permission to administer H.323 trunks. Must be y for IP trunks. See Figure 24.



System Parameters Customer Options screen, page 5The SIP-related fields on this screen are in bold.


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.

display system-parameters customer-options page 5 of xOPTIONAL FEATURES

Multinational Locations? Station and Trunk MSP? nMultiple Level Precedence and Preemption? Station as Virtual Extension? n

Multiple Locations?System Management Data Transfer? n

Personal Station Access (PSA)? yPosted Messages? n Tenant Partitioning? nPNC Duplication? n Terminal Trans. Init. (TTI)? y

Port Network Support? y Time of Day Routing? yProcessor and System MSP? n Uniform Dialing Plan? y

Private Networking? y Usage Allocation Enhancements? yProcessor Ethernet? y TN2501 VAL Maximum Capacity? y

Remote Office? n Wideband Switching? yRestrict Call Forward Off Net? y Wireless? n

Secondary Data Module? y



Trunk Group screensThis 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 94



Trunk Group screen, Page 1The 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

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.

change trunk-group 7 Page 1 of 20

TRUNK GROUP

Group Number: 7 Group Type: sip CDR Reports: yGroup Name: to sip-proxy1 COR: 1 TN: 1 TAC: 999Direction: two-way Outgoing Display? yDial Access? n Busy Threshold: 255 Night Service:Queue Length: 0Service Type: tie Auth Code? n

Signaling Group: 1

Number of Members: 10



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.

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 Usage

sip Use SIP trunks to connect a server running Communication Manager to a "home" SIP proxy server.

Valid entries Usage

y 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.

n Calls over this trunk group will not generate call detail records.

r (ring-intvl) 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.



Group Name

On Trunk Group screen, page 1, set this field to uniquely identify a trunk group.

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 555-025-600, for details on using COR and FRLs.

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.

Valid entries Usage

1 to 27 characters

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.

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.



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.

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 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.

Valid entries Usage

1- to 4-digit number

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.

asterisk (*) and pound sign (#)

* and # may be used as the first character in a TAC.



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.

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.

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 Usage

incoming

outgoing

two-way Enter two-way for Network Call Redirection.

Valid entries Usagey Displays the trunk group name and number.n Displays the digits the caller dials.

Valid entries Usage

n 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.



Busy ThresholdIn 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.

The S8700/S8710 supports a maximum of 30000 busy hour call completions (BHCC).

The S8300 remains at a maximum of 3600 BHCC.

Night Service

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 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.

Valid entries Usage

blank Leave this field blank if the Trunk Type (in/out) field is not auto.

An extension number (can be a VDN)

Type the extension of your night service destination.

attd Calls go to the attendant and are recorded as Listed Directory Number (LDN) calls on call detail records.



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.

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 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.

Valid entries Usage

public-ntwrk 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 Tie trunks. General purpose. This setting is used for systems inside the Avaya network, not for customers.



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 86.

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.

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 Usage

y or n 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.

Valid entries Usage

1 through 650

Type the number of the SIP signaling group associated with this trunk group on the Signaling Group Page 1 screen on page 77, Group Number field.

Valid entries Usage

1 through 255

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.



Trunk Group screen, Page 2


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.

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.


TRUNK GROUP

TRUNK PARAMETERS

UNICODE Name? y

Redirect on OPTIM failure: 5000 Digital Loss Group: 18

Preferred Minimum Session Refresh Interval (sec): 1800

Valid entries Usage

y or n 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.

Valid entries Usage

250 to 32000 milliseconds

See EC500 documents for the SIP-related uses of OPTIM, that is, OPS.



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.



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. Avaya 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.


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.



Trunk Group screen, Page 3The 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.


ACA Assignment

In Trunk Group screen, page 3, this field may have a y or n entry.


TRUNK FEATURES

ACA Assignment? n Measured: none

Maintenance Tests? y

Numbering Format: public

Prepend '+' to Calling Number? n

Replace Unavailable Numbers? n

Show ANSWERED BY on Display field? y

Valid entries Usage

y/n 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.



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.

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 Usage

internal Type internal if the data can be sent to the BCMS, the VuStats data display, or both.

external Type external to send the data to the CMS.

both Type both to collect data internally and to send it to the Communication Manager.

none Type none if trunk group measurement reports are not required. NOTE: This is the default for SIP trunk groups.

Valid entries Usage

y/n 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.



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.

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 Usage

Public 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 Indicates that the Numbering Plan Indicator is unknown and that the Type of Number is unknown.

Private Indicates the Numbering Plan Indicator is PNP and the Type of Number is determined from the Private-Numbering screen.

unk-pvt Also determines the Type of Number from the Private-Numbering screen, but the Numbering Plan Indicator is unknown.

Valid entries Usage

y/n 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.



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 Usage

y/n 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.



Trunk Group screen, page 4When 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

Mark Users as Phone

display trunk-group 7 Page 4 of 20

PROTOCOL VARIATIONS

Mark Users as Phone? n

Valid entries Usage

n Default.

y 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.



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.



Chapter 4: Administration 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 112

● Setup screens on page 115

● Core Router screens on page 135

● User screens on page 138

● Extensions tasks on page 175

● Add Host screen on page 123 (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 132

● Trusted Certificate screens on page 284

● System Logs screen on page 224

Publication NoteMost of the screen examples in this document were taken from a distributed SES configuration featuring a simplex Edge 5.0 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.

Administration web interface



Top ScreensThese screens are the first ones you use when you log on.

● Logon screen on page 112

● Logon screen field descriptions on page 113

● Choose Interface screen on page 114

Logon screen

To display the Logon screen to administer a co-resident system running Avaya Communication Manager and SIP Enablement Services, enter this URL:

https://_IP address of CM server_/

And for SIP Personal Information Manager (PIM), the application that an end user views, enter:

https://_IP address of CM server_/user

To display the Logon screen for a standalone system, enter this URL:

https://_IP address of SES server_/admin

The URL for the SIP PIM application that an end user views on a standalone SES server is:

https://_IP address of SES server_/user



Figure 30: Logon screen

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.

After completing both fields, select Logon or press Enter.




Choose Interface screenUse the Choose Interface screen after logging on to select from either the Administration Web Interface or the Maintenance Web Interface, depending on what functions you need to perform on the server.

Figure 31: Choose Interface screen

Choose Interface screen commands

Administration

The CM Administration and SES Administration 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. When you have installed and want to configure SES, select the link to the right to Launch SES Administration Web Interface.

Setup screens



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.0 and SES 5.0 concurrently are shared by the software. Select the link to the right to Launch Maintenance Web Interface.

Setup screensWhen 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 116

● Edit System Properties screen on page 119

● Add Host screen on page 123

● Edit Default User Profile screen on page 130

● Add Media Server screen on page 132

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.




Figure 32: Setup Master Administration screen

Setup screenThe 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. The first Setup screen is shown in Figure 33.

Figure 33: 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 screens



Setup screen field descriptions

Setup SIP Domain

Select this link to go to the Edit System Properties screen on page 119. 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 on page 123.

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.

Figure 34: Setup Hosts screen




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.

Figure 35: Setup Default User Profile and Media Servers screen

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 on page 130, 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 on page 132 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: Note that 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.

Setup screens



Edit System Properties screenThe Edit System Properties screen defines the server’s type and domain.

Figure 36: Edit System Properties screen

Note that in Figure 36, the local and logical IP addresses differ, indicating that this is a duplex configuration. The Management Device is shown as SAMP, indicating that this server is an S8500B or S8500C. The network properties were provided at installation time.

combo




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.

Management System Access Login

This is the login for the server that performs core-routing functions for an Avaya Distributed Office 1.x network.

Setup screens



You must first specify the login for Distributed Office Central Manager in Avaya Distributed Office 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 Avaya Distributed Office 1.x network.

You must first specify the password for Distributed Office Central Manager in Avaya Distributed Office 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 0-63.

802.1 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.

Log Both Before And After Values both Log both the original values in the database and new or changed values.

(continued on next page)




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.

Figure 37: Setup Continue screen

Log After Values Only new Log the new or changed values only.

Log No Values none Log the database access but, no values.

Setup screens



Add Host screenA 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.




Figure 38: Add Host screen

Setup screens



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, 123.45.67.89).

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.

Parent

Select one of the following from the drop-down list to indicate the server this host uses:

● 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.




Listen Protocols

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.

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.

Setup screens



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.

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 (1-65535) 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 123 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 116 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.

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).

Setup screens



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, 555-233-510. 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 5005.


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.





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.

Figure 39: Edit Default User Profile screen

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.

Setup screens



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

Enter the name of the city or town of the default address for users. You may use alphanumeric characters.

State

Enter the name of the state or province of the default address for. You may use alphanumeric characters.

Country

Enter the name of the country of the default address for users. You may use alphanumeric characters.

ZIP

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.




Add Media Server screenThis 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.

Figure 40: Add Media Server screen

Select Add to submit the Communication Manager server interface with the properties entered to the database for this SES home server.

Setup screens



Add Media Server screen field descriptions

Media Server Interface Name

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 Administration for Network Connectivity for Avaya Communication Manager, 555-233-504.

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.

Host

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.

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 0-255. 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 6001. 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.

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.

Core Router screens



Core Router screensThe Core Router screens menu option appears depending on your SES configuration. It is a component of a Distributed Office 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 on page 135

● List Handle Maps screen on page 137

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 screenThe 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.

A typical List Prefix Maps screen is shown in Figure 41.




Figure 41: List Prefix Maps screen

List Prefix Maps screen field descriptions

Branch Prefix

Branch Prefix is the prefix used to uniquely identify each Distributed Office platform, including each optional SIP Server in the main or headquarters location.

Branch Address

Branch Address is the IP address of the Distributed Office 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.

Core Router screens



List Handle Maps screen This screen is a read-only summary page listing the current alphanumeric handles associated with users at Distributed Office 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 Distributed Office Central Manager.

A typical Handles Map screen is shown in Figure 42.

Figure 42: List Handle Maps screen

List Handle Maps screen field descriptions

Branch Prefix

Branch Prefix is the string of digits uniquely identifying each Distributed Office 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.




User screensThe User screens permit customizing aspects of the system for each user.

List Users screen A typical List Users screen is shown in Figure 43. To use this screen, check a box next to a user ID, select an action from the task drop-down menu, select Submit.

This screen is viewed only from the edge server’s Master Administrator interface.

Figure 43: List Users screen

Note that this Tasks menu is available if you are logged in to a co-resident home/edge server.

User screens



List Users screen field descriptions

User ID

Lists the IDs of administered users in the SES database.

Host

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.

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.


List Users screen commandsAll 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.

Add User task

Use the Add User screen on page 142 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 on page 146.




Devices task

Manage the tones, volume, and cadence of certain SIP-enabled devices with the Devices Screen menu on page 167.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 Figure 44. This screen indicates that the end user’s telephone does not support the Devices feature.

Figure 44: No compatible devices screen

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. See the full discussion on Delete All Displayed Users task on page 173.

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, as on the Delete Selected Users task on page 174.

Extensions task

Add, delete, and make available the extensions assigned to a user with the Extensions tasks on page 175.

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 181.

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 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.

User screens



Memos task

Write short notes about the user for other administrators to read using the User Memos screen on page 195. 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. See Move User Task on page 197.

You can also move a user from one home server to another using the Edit Profile screen. See Moving a user to another home server from Edit Profile screen on page 214.

Permissions

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. Selecting this task displays the Permissions screen on page 200.

Note that presence cannot be matched properly if the handle of the watched user does not match exactly, including its case.

Profile

Edit the full profile of a user and customize it with the Edit User Profile screen on page 203.

Watchers for User

This task choice lets you select for the user who on the system may observe the user’s presence. Selecting this task displays the screens for the Watchers Task on page 206.


Submit

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.




Add User screenAdd 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.

Figure 45: Add User screen

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.

User screens



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 the @sip_domain.com 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.

● 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

Enter a password of at 6 to 12 alphanumeric characters. Both field entries must match exactly.

Host

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




(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.


User screens



Office

Enter a designation for the user’s office suite or perhaps floor, in alphanumeric characters.

City

Enter the name of the city or town of the user’s address in alphanumeric characters.

State

Enter the name of the state or province of the user’s address in alphanumeric characters.

Country

Enter the name of the country of the user’s address in alphanumeric characters.

ZIP

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 on page 132, 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.

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.




My Contact List task screenThis series of screens displays the sites and friends an end user wants to contact. The contact address can be IP addresses, e-mail address, or web pages with which an end user would like to communicate.

In Figure 46, the first four items are common endpoints the user frequently contacts. Group1 is a collected set of endpoints.

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.

Figure 46: My Contact List screen

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.

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 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.




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.

See the Contact Details screen on page 150.

Group (link)

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.

See the Group Details screen on page 160

View

View details about the contact or group.

See the Contact Details screen on page 150.

Delete

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.

See the Add Contact screen on page 152.

Add Group

Add a group name to which this contact belongs. At this time, only one level of hierarchy for groups are supported.

See the Add Group screen on page 156.

User screens



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.

See the Speed Dial List screen on page 157.

Reload Configuration

If you have made changes on this end user’s list of contacts, select Reload Configuration to refresh the list.

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.

Figure 47: Reload Configuration screen




Contact Details screenThis 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.

Figure 48: Contact Details screen

All fields on this screen are view only.

In Figure 48, SIP User dlaser wants to be able to contact user Digi Minky. User dlaser 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.

Select Update Contact to make changes.

Select Delete Contact to remove this contact’s information from access by the user.

User screens



Update Contact screen Change the contact information for the end user’s contact with this screen. See the Add Contact screen on page 152 for information on field descriptions.

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.

Figure 49: Update Contact




Add Contact screenFrom the SIP PIM interface an end user builds a list of friends, e-mail 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.

User screens



Figure 50: Add Contact screen




Add Contact and Update Contact screen field descriptions

Address

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.

Name



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.


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.

User screens



E-mail

Enter a string in this field as the e-mail 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 on page 150, this becomes a clickable mailto: link on the web page.

Notes

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 in Figure 50, for example [email protected]. The user dminky has the option of not allowing herself to be tracked.


Contact Phones

This group of fields lists up to six ways for a user to reach a contact.

● Phone Type—The drop-down menu for this field provides identification for the rest of the information in the row.

● Phone Number—SIP handle, e-mail, 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.




Add Group screenPart 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.

Figure 51: Add Group screen

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.

User screens



Speed Dial List screen This screen is view only. It reflects the settings made in Contact Details screen on page 150. 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 on page 151. Entries on this list typically appear as soft button labels on the SIP user’s device.

Figure 52: Speed Dial List screen

Handle




NameOn this screen, the Name field is the label you assigned to the phone number for this contact.




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 web browser’s language setting.


Prefix

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 #



Select Handle to view the associated user’s detailed contact information.

User screens



Delete Contact screenAs 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.

Figure 53: Delete Contact screen

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. See the example for the Confirm Delete User screen field descriptions on page 216.




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.

Figure 54: Group Detail Screen

Group Details screen field descriptions

Handle




After viewing the details of this group, select the Add Contact link to go to the Add Host screen on page 123 and associate a contact with this group in your list of user contacts. Select the Delete Group link to go the Delete Group screen on page 163 and delete this group name from your contact list. Select the Update Group link to go to the Update Group screen on page 165 and change the name of this group in your user contact list.

User screens



Name



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.


Telephone #1 and Telephone #2



Group Details screen commands

Back to My Contact List

Select this link to return to the My Contact List task screen on page 146.

Add Contact

Select this to display the Add Contact screen on page 152 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. See the example for the Confirm Delete User screen on page 216.

Deleting a group does not remove the contacts in the group from use. The contacts automatically become members of the default group.




Update Group

Select this to display the Update Group screen on page 165 to change the group’s name.

View

Select a contact for the user and click View to show a view-only screen of the contact’s details.

Delete

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.

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.

Figure 55: Delete Group screen

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


Select this link to return to the My Contact List task screen on page 146.

Yes

Go ahead and submit your selections.

No

Cancel the selections on the screen and do nothing. The system displays the My Contact List task screen again.

User screens



Update Group screenModify the group name here. All contacts associated with the original group name now are associated with the new group name.

Figure 56: Update Group Screen

Update Group screen field descriptions

Old Group Name

Displays the name of the existing group that you are about to change.

Group NameEnter 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


Select this link to return to the Contact List

Submit Update

Select this to submit the group name change to the database.

User screens



Devices Screen menuFigure 57: 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).

Figure 57: Devices screen




One Touch Dial List screenThis 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.

Figure 58: One Touch Dial List screen

One Touch Dial List screen field descriptions

Button

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.

Address

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.

User screens



Label

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.

One Touch Dial List screen commands

Save

Submit the one touch dial information to the database.




Ringer Settings screenThis 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.

Figure 59: Ringer Settings screen

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.

User screens



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.




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.

Figure 60: View Tones and Volumes screen

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 VolumeDisplays 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 VolumeDisplays 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 VolumeDisplays 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).

User screens



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.

Figure 61: Delete All Displayed Users screen

In the example in Figure 61, a search operation returned all users whose names start with d or D. Click Delete All Displayed Users, then the Submit button to delete all the users listed. You may also select individual users’ check boxes to the left of their User IDs, then highlight Delete Selected Users in the drop-down list, and then the Submit button.




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.

Figure 62: Delete Selected Users task screen

In Figure 62, an example of a search found all the users’ names starting with D or d. Users 2346, 2400, and 2506 are retained, and users dlaser and dminky are selected for deletion.

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.

User screens



Extensions tasksThis section describes administering a specific user’s extension.

Tip:Tip: Another screen with the same name is discussed in List Media Server Extensions

when user has none on page 177. Go there if you want to look up information about extensions administered in Avaya Communication Manager 5.0, perhaps to make more extensions available for SES users.

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 you find that a user has no extension assign, that List Media Server Extensions screen is shown in List Media Server Extensions when user has none on page 177.

Figure 63: List Media Server Extensions screen

List Media Server Extensions screen field descriptions

Extension

The numeric telephone extension in the database.

This is the extension for the user named at the top of the screen.




User

This is the User ID assigned when the user was added to the SES system.

See User ID on page 144.

Media Server

The name of the server running Avaya Communication Manager (in a distributed SES 5.0 system) to which the extension was assigned.

Host

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. See the example for the Confirm Delete User screen on page 216.

Edit User

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 138. Pick a task from the drop-down list.

Delete

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 216.

User screens



List Media Server Extensions when user has noneSometimes, 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 in Figure 64.

Tip:Tip: If you want to look up information about extensions in Avaya Communication

Manager 5.0, perhaps to make more extensions available for SES users, then see the Extensions tasks on page 175.

Figure 64: List Media Server Extension screen for a user

Add Another Media Server Extension

This link takes you to the Add Media Server Extension screen on page 178 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 on page 180.

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.




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 175.

Figure 65: Add Media Server Extension screen for a user

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 Administration for Network Connectivity for Avaya Communication Manager, 555-233-504.

User screens



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.




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 177, 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.

Figure 66: Select Free Extension screen

Extension

Select this drop-down list to see what extensions are currently available for assignment. Select a free extension from this list.

Select

Make your list selection permanent.

User screens



Handles taskThe 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.

Figure 67: Edit User Handles screen

In the example in Figure 67, the user dlaser uses four handles: 2222, dlaser, dlaser_webpage, and dlaser_e-mail. Note that dlaser is the Primary handle (his User ID) and may not be deleted.

If a person wants to contact dlaser, they may try the extension 2222. That message first goes to the SIP Uniform Resource Indicator (URI) of 3035381234. 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:







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.



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).

User screens



Handle




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.

In the example in Figure 67, The User ID for dlaser has four handles:2222, dlaser, dlaser_webpage, and dlaser_email. Contacts for dlaser show the user’s10-digit extension and a 4-digit SIP telephone number. Contacts for dlaser also show a web page where the user posts the latest information regarding work, and a personal e-mail account.

Edit User Handles screen commands

Edit (Handle)

Go to the Edit Handle detail screen on page 185 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. See the Add Handle screen on page 189.




Edit (Contact)

Select Edit next to the contact information to change the information about this user’s personal point of contact. See the Edit Host Contact screen on page 187.

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. See the Add Host Contact screen on page 191.

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 on page 193. There, you can create a new group to add a handle to.

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.

User screens



Edit Handle detail screenChange the users handle at with this screen.

Figure 68: Edit Handle, Detail screen

Edit Handle detail screen field description

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.



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.

Domain

The domain name of the home server to which this user is assigned.




Handle





● event-server

● cm-resubscribe

● confsvr

● handle_list

● presenceserver

In addition:







Edit Handle detail screen command

Update

Select Update to submit the modified information to the database.

User screens



Edit Host Contact screenThis 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.

Figure 69: Edit Host Contact screen

Edit Host Contact screen field descriptions

User ID

The user ID for whom you want to name a new host contact to redirect calls to.

Contact

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

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

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.

Update

Submit your additions or changes to the database.

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.

Figure 70: Add Handle screen

Add Another Handle screen field descriptions

User ID

An identifier of at least three alphanumeric characters in length, used to authenticate a user.

Handle




This is never the Primary handle, which is defined on the Add User screen on page 142.





● event-server

● cm-resubscribe

● confsvr

● handle_list

● presenceserver

In addition:







Add Another Handle screen command

Add

Submit this additional information to the user database.

User screens



Add Host Contact screenThe 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.

Figure 71: Add Host Contact screen

Add Host Contact screen field descriptions

User ID


Handle







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.

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

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.

Add

Confirm to add into the database the new host contact you have set up.

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.

Figure 72: Add Group screen

Add Group screen field descriptions

User ID

An identifier of at least three alphanumeric characters in length, used to authenticate.

HandleIn this screen, enter a handle of any end user to include them in this group.


● event-server

● cm-resubscribe

● confsvr




● handle_list

● presenceserver

In addition:







Add Group screen commands

Add

Add the handle to the user database in the new group of handles that you specified.

User screens



User Memos screenThis 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.

Figure 73: User Memo screen




User Memo field descriptions

User ID


List of memos

The available memos display in chronological order, most recent at the top.

Add Memo box

Write a new memo about the user inside this text box.

Delete

Remove the memo to the left.

Add Memo button

Select this button to store the memo in the area above.

User screens



Move User TaskThe 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 Figure 74. 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.

See also Moving a user to another home server from Edit Profile screen on page 214.

Figure 74: Move Users Screen

The system displays a confirmation screen in order to allow you to cancel the move.




Figure 75: Move User Continue screen

User screens



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.

See also the Edit User Profile screen described in Moving a user to another home server from Edit Profile screen on page 214.




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.

Figure 76: Permissions screen

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 on page 200.

User screens



Change Permissions Type

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.

Handle

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 the @ sign. The system automatically appends the @systemdomain.com 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.





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.


User screens



Edit User Profile screenThe 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.

Figure 77: Edit User Profile screen




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.




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. See Moving a user to another home server from Edit Profile screen on page 214.




User screens



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.


Office

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.

City



State



Country



ZIP

Enter the number of the ZIP or postal code of the user in numeric characters.


After entering or changing entries, select Update to submit the user’s profile to the user database on this host.




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.

Figure 78: Watcher’s screen

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 on page 200.

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.

User screens



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.


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 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 on page 200.

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. See My Contact List task screen on page 146.




Search User screenLocate 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 screen in Figure 79.

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.

Figure 79: Search Users screen

User screens



Search Users screen field descriptions

Host

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.

User ID

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.


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.



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.





Office

Enter a designation for the user’s office suite or floor, for example, in alphanumeric characters

City


State


Country


ZIP

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, fully explained on List Users screen on page 138.

An example list follows in Figure 80: Search Users result screen.

User screens



Figure 80: Search Users result screen




Select User screenThe 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.

Figure 81: Select User screen

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.




Select the Edit User button to edit the profile of the user with the chosen User ID.

User screens



Update Password screenThis 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.

Figure 82: Update User Password screen

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.




Default ProfileUse of this screen usually occurs when the system is first installed and configured. See the Edit Default User Profile screen on page 130.

Moving a user to another home server from Edit Profile screenIn 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. See Moving a user to another home server on page 199.

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.

User screens



Figure 83: Move Users screen

Figure 84: Move User Continue screen




Confirm Delete User screenThis screen is preceded by a Select User screen that requires the user ID of the user you want to delete.

Figure 85: Confirm Delete User screen

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). See the example for the Confirm Delete User screen on page 216.

Cancel

Select Cancel to ignore the deletion, keeping the user and associated extension(s) unchanged.



Chapter 5: Maintenance Web Interface

This section describes in detail the use and meaning of the screens in the Maintenance interface.

● Alarms screens on page 217

● Diagnostics screens on page 223

● Server screens on page 242

● Data Backup/Restore screens on page 252

● Security screens on page 268

● Miscellaneous screen on page 293

Alarms screensAlarm screens are these:

● Current Alarms screen on page 218

● SNMP Traps screen on page 221

A helpful adjunct to these alarm screens are the Diagnostics screens on page 223.

Maintenance Web Interface



Current Alarms screen

Figure 86: Current Alarms screen

Current Alarms screen field descriptionsUse 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

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:

ID

This is a unique identification number assigned to the alarm.

Alarms screens



Source

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

● _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.

Alarms screens



SNMP Traps screenAdminister SNMP destination at both the primary and the backup servers of a duplex system. connect to the backup server by entering the physical IP address of the backup serve, not the logical IP address for the duplex pair.

Figure 87: SNMP Traps screen

SNMP Traps screen field descriptionsUse the Configure screen 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 that the CCS-AVAYA MIB is located in the /var/home/ftp/pub/mib directory.

Status

Shows if the configured destination is enabled or disabled.

● 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.

IP Address

This is the IP address of the server that sends traps. In a duplex pair, this must be the physical IP address of the backup server, not the logical address for the duplex pair.




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.

● 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.

Authentication Password (v3 only)

This is a pass phrase for the user specified in the User Name field, used to digitally sign or sanction v3 traps.

Privacy Password (v3 only)

This field is a pass phrase for the user specified in the User Name field, used to encrypt v3 traps.

Select Add for a new trap destination, Change to modify the trap destination, or Delete to remove the trap destination.

The SNMP Trap page may display the following error:

Unable to contact alarm agent: The 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.

Alarms screens



Diagnostics screens● System Logs screen on page 224

● Temperature/Voltage screen on page 228

● Ping screen on page 230

● Traceroute screen on page 233

● Netstat screen on page 236

● Netstat results screen on page 237

● Modem Test screen on page 240




System Logs screenThis 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.

Figure 88: System Logs screen

Alarms screens



System Logs screen field descriptions

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 Description

lm 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.

lxboot Linux boot messages.

lxcron Linux Scheduled Task log (CRON). Shows information from the Linux scheduling daemon.

lxsys Linux Syslog. Collects all the system messages produced by the various subsystems (processes) running on Linux.

lxsec Linux Access Security log. Information pertaining to logon connections to the Linux system. Actions logged in this file include opening or closing a telnet session and modem messages.

lxwtmp Linux login/logout/reboot log. Information about Linux logon and logout procedures, as well as system reboots.

lxxfer 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.

wd 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.

cmds 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.




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:

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.

httperr 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.

httpssl 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.

Log Type Description

View Description

bashhist 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.

hwerr Hardware error and alarm events. The events that go into the SES hardware error and alarm logs.

swerr Software events. The events that go into the SES server’s software error log.

Alarms screens



3. You cannot skip fields (such as specifying the year and the day, but not specifying the 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.




Temperature/Voltage screen The Temperature/Voltage screens are different for the S8500A, S8500B, and S8500C server hardware platforms. Consult this sub-section for the information you need.

● Temperature/Voltage screen on S8500B or S8500C on page 228

Figure 89: Temperature/Voltage screen on S8500B or S8500C

Temperature/Voltage screen field descriptionsUse 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.

Alarms screens



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 causing an alarm, go to the System Logs screen on page 224 and view the Linux system log (syslog) file to see the message that corresponds with the condition.

The row SAMP Temp shows what’s used to determine if the actual temperature reading is high.

Value

The current reading of the component being measured.

Crit_Low

The excessively low value at which at which a major alarm is generated.

Warn_Low

The somewhat low value at which a warning alarm is generated.

Warn_High

The moderately high value at which at which a major alarm is generated.

Crit_High

The excessively high value at which at which a major alarm is generated.

Status

A generalization stating that the reading is either within normal limits or not.




Ping screen

Figure 90: Ping screen

Ping screen field descriptionsUse 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

Enter or select the host name or IP address you want to ping.

UPS Endpoints

Select this option to ping all Uninterruptible Power Supply (UPS) endpoints.

Alarms screens



Options

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 screenWhen 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.

Successful ping results

If the ping command runs successfully, the Execute Ping results page displays a brief summary that looks something like this:

PING www.asite.com (135.9.4.93) from 135.9.77.30: 56 (84) bytes of data.

64 bytes from www.asite.com (135.9.4.93): icmp_seq=0 ttl=245 time=6.3 ms

64 bytes from www.asite.com (135.9.4.93): icmp_seq-1 ttl=245 time=6.3 ms

--- www.asite.com ping statistics ---

2 packets transmitted, 2 packets received, 0% loss

round-trip min/avg/max = 0.3/3.3/6.3 ms




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.

Alarms screens



Traceroute screenUse 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.

Figure 91: Traceroute screen

Traceroute screen field descriptions

Host Name or IP Address

(Required) Enter the destination host name or IP address.




Options

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.

Traceroute results screenWhen 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 (192.168.1.126), 30 hops max, 38 byte packets

1 server1.mycompany.com (192.168.1.254) 0.324 ms 0.226 ms 0.206 ms

2 server2.mycompany.com (192.168.2.254) 0.446 ms 0.372 ms 0.288 ms

3 server.mycompany.com (192.168.1.126) 0.321 ms 0.227 ms 0.212 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.

Alarms screens



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 (192.168.1.126))

● 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 (192.168.1.254).

If you elected to print the addresses numerically, no host name appears in the output. For example:

1 192.168.1.254 0.778 ms 0.590 ms 0.216 ms

2 192.168.2.254 0.507 ms 0.449 ms 0.311 ms

● Round-trip time to the gateway computer (for example, 0.324 ms 0.226 ms 0.206 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 www.unknown.com

● This is because the host www.unknown.com 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.




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.

Figure 92: Netstat screen

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.

Alarms screens



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.

Note:Note: To view results for inet and unix address families on the same page, select both

options.

Click Execute Netstat.

Netstat results screenThe 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- 0 1969/ 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 33148 DGRAM [ ] unix 7 42350 DGRAM [ ] unix 0 38530 DGRAM [ ] unix 0The 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.

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.

Alarms screens



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 238.

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.




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.

Figure 93: Modem Test screen

Alarms screens



Modem Test screen field descriptions

Test OptionsUse 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 problemsTo 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, verify the modem connection to the telephone line and the server, ensure that the modem is powered on, and then continue with Step 2.

2. Run the handshake test again.

3. If the handshake test is successful, run the offhook test. If the offhook test fails, verify the modem connection’s telephone line and hardware, then continue with Step 4.

4. 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, verify to see if someone else may be using the modem.

7. If there are no problems with the connection line and hardware, restart the server.




Server screens● Status Summary screen on page 242

● Process Status screen on page 244

● Shutdown Server screen on page 247

● Server Date/Time screen on page 248

● Software Version screen on page 250

Status Summary screen

Figure 94: Status Summary screen

Status Summary screen field descriptionsUse 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.

Server screens



Mode

(Read-Only) This shows whether the server is primary or backup.

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.

Server Hardware

(Read-Only) This shows whether the server is okay or otherwise.

Processes

(Read-Only) This shows whether the processes running on the server are okay or otherwise.

Server StatusTo 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 242.

● 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.




Process Status screenUse 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.

Figure 95: Process Status screen

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.

Server screens



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 This procedure is for SES home servers only.

PARTIAL UP is an indication of the initial state of the sipserver and eventserver processes 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 three processes:

● sipserver

● eventserver

● imlogger

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 and Communication Manager 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 duplex server interchange does not resolve the problem. Instead, take one of the following actions:

● Provide the setup information through administration screens. Verify all the fields on these screens to ensure that they contain the correct information for your system:● Domain screen● Media Server screen● Host screen● Configure Server screen● Authentication File screen

● Restore the database information from a previous backup copy. SES data services pushes the database information onto this SES home server.




Process Status resultsThis page displays status information for the server applications based on the selection you made on the Process Status screen on page 244: Summary or Detailed. Regardless of which view you chose, status information appears for the following applications:

Application Name Description

Watchdog Brings the system up, recovers from failures, and brings the system down cleanly.

TraceLogger Creates and maintains the log files where most applications running on an Avaya SES server write messages.

INADSAlarmAgent Sends alarms to the Initialization and Administration System (INADS) using SNMP traps defined in the INADS MIB.

CCSTrapAgent Acts to send Simple Network Management Protocol (SNMP) traps defined for SES.

GMM (Global Maintenance Manager)

Collects, processes, and reports system-wide alarms.

SNMPManager Acts as the SNMP trap receiver for the server. The received traps are decoded and written to the syslog.

ImLogger Creates and maintains the log files where the Instant Messaging application writes messages.

SipServer Controls the SIP communications sessions and their associated messaging. (Is not running when in backup mode.)

drbdEventSvc The distributed redundant block device synchronizes database information between duplex servers.

MtceMgr The Maintenance Manager monitors application alarms and mon information to determine when to interchange servers for local failover in a duplex server configuration.

mon 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.

SME (Server Maintenance Engine)

Tests server components periodically. The SME tests components as the result of both specific requests and asynchronous errors.

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.

Figure 96: Shutdown Server screen

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.




Server Date/Time screenUse this page to set or adjust the time on a new or in-service Avaya server.

Figure 97: Server Data/Time screen

Server Date/Time screen field descriptionsThe 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 249.

● 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.

Server screens



! 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.

! 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 ZoneUsing 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.




Software Version screenUse the Software Version screen to determine the software version, BIOS, and firmware an Avaya server is running. You may want to verify your software version before, during, or after you install new software. This screen is also helpful during troubleshooting.

Figure 98: Software Version screen

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 2.6.11-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-05.0-05.0.018.54 is the release (by field: major release and minor release number, development release number, Avaya build number, and internal ID).

Server screens



Software Load

SES-05.0-05.0.018.54 is the full version of the software release name. The major and minor release (05.0), development release and subrelease (also -05.0), followed by the load number, such as 018 in this example, that increments for each new software build, and the final number (54 in this example), an additional identifier 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.

SAMP Version ID

This field shows the firmware version of the SAMP remote maintenance board. This ID must be correct at installation time, but you may verify it at any time. If you find that your SAMP version is incorrect, use the procedures in Installing, Administering, Maintaining and Troubleshooting SIP Enablement Services, 03-600768, for how to "Verify firmware on the SAMP module."




Data Backup/Restore screens● Backup Now screen on page 252

● Backup History screen on page 256

● Schedule Backup screen on page 257

● Backup Logs screen on page 261

● View/Restore Data screen on page 263

● Restore History screen on page 265

● Format PC Card screen on page 266

Backup Now screenBackup both the Master Administrator interface subsystem on the edge server, and the home server to back up all user data.

Data Backup/Restore screens



Figure 99: Backup Now screen




Backup Now screen field descriptionsUse 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.

● FTP—Choose this selection to send the backup data to an FTP server. When you choose this selection, you must also enter a user name, password, host name, and directory. The default directory for backup data on the FTP server is /var/home/ftp. If you want to use the default directory, enter a forward slash (/) in the directory field. You must start the FTP server before backing up. To enable the FTP server, seeFTP screen on page 271.

● E-mail—Choose this selection to send the backup data as an attachment to an e-mail. When you choose this selection, you must also enter a user name, domain name, and mail server name.

Note:Note: Do not exceed the size of file your mail server can handle.

! CAUTION:CAUTION: If you choose to back up data using e-mail, 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 e-mail attachment on the server using a PuTTY client and then restore it using the local directory option.




● 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 screen on page 266.

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 verify 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

Figure 100: Backup History screen

Backup History screen field descriptionsThis 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 lzccs1.163608-20040719.5179

Where lzccs1=server name, 163608-20040719=backup time (hhmmss)-date(yyyymmdd), and 5179=PID (process ID uniquely identifying this backup).

2. To review backup history, click Check Status.




Schedule Backup screenWhen scheduling a backup, backup both the Master Administrator subsystem on the edge server and the home server to back up all user data.

Figure 101: Schedule Backup screen

Schedule Backup screen field descriptionsThe 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) FilesUser data (database) files refers to data entered in the system for SIP users and associated contacts.




Server and System FilesServer 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 FilesSecurity Files refers to data such as logon IDs, passwords or Access Security Gateway (ASG) keys, firewall information, and file monitoring data bases.

Day

Year, month, and day the backup was run.

Time

Hour, minute, and second the backup was run.

Status

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, e-mail, and local PC card.




Add a backup scheduleBack 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.




Change a backup scheduleYou 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 1.

3. 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 scheduleTo 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

Figure 102: Backup Logs screen

Backup Logs screen field descriptionsWhen 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.

Data Set

Indicates what data were recorded. Possible sets are: User Data (Database) Files, Server and System Files, and Security Files.

File Size

Physical size of the backup file.

Date

Year, month, and day the backup was run.

Time

Hour, minute, and second the backup was run.




Status

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, e-mail, and local PC card.

Steps to preview or restore backup dataClick 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 e-mail, 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 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.




View/Restore Data screen

Figure 103: View/Restore Data screen

Starting Event Server after restoring security filesWhen you restore security files, manually restart the Event Server.

You must manually start the Event Server on the Services page (SES Admin > Services). This step is needed only on the SES server that has the security files restored, regardless if the server is an SES Edge, Home or combined Home/Edge. Security files can be restored to a combined SES Home/Edge, SES Edge 5.0 or Home server.

View/Restore Data screen field descriptionsIf 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 it was 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

● FTP —File transfer protocol

Before a transfer of the backup image occurs, you must first log on to the FTP (if it is enabled on the server), the SCP, or the SFTP server.

You must enter the following information:

● User name. Enter the name anonymous if you are using an anonymous account. Otherwise, enter your real user name.

● Password. If you are using an anonymous account, you will typically enter your e-mail address as the password. However, you should double-check with the FTP server administrator to verify this. If you are not using an anonymous account, enter your real user account password on this server.

● 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, 192.11.13.6).

● 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.

Local directory

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:

● 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.




Restore History screen

Figure 104: Restore History screen

Restore History screen field descriptionsThis 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 lzccs1.163608-20040719.5179

Where lzccs1=server name, 163608-20040719=backup time (hhmmss)-date(yyyymmdd), and 5179=PID (process ID uniquely identifying this backup).

2. To review restore history, click Check Status.




Format PC Card 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.

Figure 105: Format PC Card screen

Avaya requires the use of industrial grade compact flash media. For more information, see Hardware Description and Reference for Avaya Communication Manager (555-245-207).

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

Note:Note: 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.

Note:Note: 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 1.

7. To view the status of the backup, click Backup Status.




Format PC Card results screen The results of your PC card format displays.




Security screensThis section discusses the following security screens:

● Modem screen on page 269

● Solving modem problems on page 270

● FTP screen on page 271

● Steps to Start or Stop FTP service on page 271

● FTP operation on page 272

● Authentication File screen on page 275

● Firewall screen on page 277

● Tripwire screen on page 281

● Tripwire Commands screen on page 283

● Trusted Certificate screens on page 284 (significantly enhanced in SES 5.0)

● SSH Keys screen on page 291

Security screens



Modem screenUse 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.

Figure 106: Modem screen

Modem screen field descriptions

Modem Administration

To verify 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.




Solving modem problemsModem 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 2.

6. 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.

Security screens



FTP screenSIP Enablement Services 5.0 does not support FTP for incoming files, by default.

Use the FTP page to activate file transfer protocol (FTP) service on the Avaya server. Activate this service for an FTP application that resides on another computer or server for which you want to transfer files to or from the Avaya server.

! CAUTION:CAUTION: To keep your Avaya server secure, always deactivate FTP service when your file

transfers are complete. When you deactivate FTP service, unauthorized users cannot use FTP to transfer files to or from the Avaya server.

Figure 107: FTP screen

By default, incoming FTP file transmission are not permitted. To allow incoming FTP files temporarily, go to the Firewall screen on page 277, set the check box to allow the FTP file format, and then do the FTP file transfer from this screen.

When finished, go back to the Firewall screen and clear the check box to keep a high level of security on your machine.

Steps to Start or Stop FTP serviceTo start or stop FTP service:

1. The FTP Server page shows the current state of FTP service: enabled or disabled. Normally, the FTP service is disabled between file transfers.




2. If service is enabled and you need to transfer files, continue to step 5. Otherwise, you should secure the server against potentially unauthorized files transfers as follows:

● Click Stop Server to deactivate FTP service on the Avaya server. The FTP Server page shows a new status of disabled. You can continue working with the web administration interface as needed.

3. If service is disabled and you need to transfer files:

4. Click Start Server to activate FTP service on the Avaya server. The FTP Server page shows a new status of enabled.

5. On the computer or server that contains the files to copy, transfer files to the Avaya server as follows (see Copy files using FTP for details):

● Open an FTP application on your computer. (Run FTP or open a GUI FTP application.)

● Log on as anonymous, with your e-mail address as your password.

● Set mode to binary, then put the correct files on the Avaya server.

● When you finish, close the FTP application.

● When file transfer is complete, click the web administration interface window to access the FTP Server page.

● Click Stop Server to deactivate FTP service. This prevents unauthorized users from transferring files to or from the Avaya server using FTP.

FTP operationThe FTP service operates on the Avaya server as follows:

● Files are transferred to the /var/home/ftp subdirectory on the server. Files (such as keys.install files) may also be copied to the /tmp subdirectory.

● FTP service is normally available on the services and corporate LAN interfaces. However, FTP service to the corporate LAN interface may be blocked as follows:

- On the main menu under Security, click the Firewall link. When the page appears, note the setting for the FTP service on port 21.

- If FTP service is disabled (the check box is clear), devices that connect to the Avaya server across the corporate network interface cannot use their FTP applications to transfer files to or from the server. However, a laptop connected to the services interface should still be able to transfer files using its FTP client application.

- If FTP service is enabled (the box is checked), devices that connect to the Avaya server across the corporate network interface can use their FTP client applications to transfer files to or from the server.

- If you change the FTP setting, click Set Security. Review the page when it refreshes to ensure that changes were made correctly.

Security screens



Copy files using FTPUse this procedure to copy (put) files onto the Avaya server using an FTP application on your computer. Typical files to transfer include new license or authentication files, firmware upgrades, system announcements, or keys.install files that may be used with network time servers.

Prerequisites

To use this page, FTP service must be available for the Ethernet interface you are using. Occasionally, this service may be blocked on the customer LAN interface for security reasons FTP service must be enabled on the FTP Server screen.

Transfer procedure

To copy files to the server using an FTP application on your computer:

1. Log on to the Avaya server.

2. On the main menu under the Security section, click Start/Stop FTP Server.

3. Verify the current state of FTP service: enabled or disabled. FTP service should be disabled between file transfers.

4. Click Start Server to activate FTP service on the Avaya server.

! SECURITY ALERT:SECURITY ALERT: You cannot start FTP service if it is blocked on the Firewall page.

5. On the computer or server that contains the files to copy, run an FTP application.

6. You can use a GUI FTP application if one is installed on your computer. Alternatively, you could run a command-line version of FTP. For example:

● From the Start menu on a Windows system, select Run.

● In the Run window, type ftp <hostname or IP address> at the prompt.

Note:Note: You can only enter the server name, instead of an IP address, if you are

accessing the server over a network with DNS service. Direct connections using a laptop (the services link) must use the server's IP address if DNS is disabled.

7. Specify the following to connect to the Avaya server: ● Host name: the name or the IP address of the server ● User ID: anonymous ● Password: your e-mail address ● Terminal type: the appropriate type for your computer if prompted




8. Set mode to binary as follows:

● In the FTP application window, select the Binary option.

● For a command-line session, type bin at the prompt.

9. Put the files onto the server.

● In the FTP application window, choose the correct files and copy them as required by your application.

● For a command-line session, type put </directory/filename> at the prompt for each file you need to copy, where </directory/filename> is the location of the file on your computer. Files are always placed in the /var/home/ftp subdirectory on the server.

Note:Note: For a Windows system, you may need to preface the put destination with a drive

letter. For example, put <drive:\directory\filename>. Note that Linux systems use forward slashes in the directory name.

10. When the file transfer is complete:

● Close the FTP application window.

● For a command-line session, type quit. 11. Disable FTP service on the Avaya server to prevent unauthorized users from transferring

files there:

● Click on the Avaya server's web interface window to access the Start/Stop FTP screen.

● Click Stop Server to deactivate FTP service.

Security screens



Authentication File screenAt 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.

Figure 108: Authentication File screen

Authentication File screen field descriptions

File Path

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.

URL

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.

Install the Authentication file I specify below

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.

Install

Submit the information.

Security screens



Firewall screenUse 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.

FTP and telnet sessions should be left 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. See FTP screen on page 271.

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.




Figure 109: Firewall screen

Security screens



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.

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. 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): provides a command-line interface for running server platform commands and applications such as the System Access Terminal (SAT).

Simple Mail Transfer Protocol (SMTP): supports e-mail 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 verify or modify the services that are allowed on the corporate LAN Ethernet interface, you may want to:

● Disable an IP service:

Clear the check box to disable this service on the corporate LAN interface.

● Enable an IP service:

Check the box to activate a service on the corporate LAN interface.

● 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.

Security screens



Tripwire screen

Figure 110: Tripwire screen

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.

Security screens



Tripwire Commands screen

Figure 111: 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:

baccarat2-20030111-0416213.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.




Trusted Certificate screensThis release of SES supports the capability to install server certificates signed by the CA of the customer’s choice. This section discusses administration to trust more CAs than were trusted in previous versions of SES.

The screens available in the Trusted Certificates series are:

● Trusted Certificate screen on page 285

● Certificate Information—General screen on page 287

● Certificate Information—Details on page 288

● Certificate Export screen on page 289

● Certificate Import screen on page 290

Visit this page when you want to verify the current available root certificates, or when you want to manage the list of root certificates.

The following Avaya CA (certificate authority) certificates are pre-loaded on an SES edge proxy:

● Avaya Root CA Certificate

● Avaya SIP CA Certificate

Best Practices● After you select Trusted Certificates from the menu on the left, click Yes in the Security

Information dialog box.

● Root certificates are preserved during upgrades, remaster, and migrate procedures.

● Trusted certificates are backed up and restored during upgrades, remaster, and migrate procedures.

Note:Note: After restoration of data, a cron job checks trusted and server certificates for

expiration. If a certificate has expired, an alarm is raised.

Security screens



Trusted Certificate screen This screen displays the current trusted certificates information, for telephony purposes only, on the SES server.

Use this screen to select a specific certificate to view, export, or delete. From this screen, you can view both general and detailed information about the certificate.

This screen is shown in Figure 112.

Figure 112: Trusted Certificate screen

Trusted Certificate screen field descriptions

Status

The Status column uses several indicators to show the status of the certificate on that line:

● Green check—the certificate is valid and in effect.

● Red X— the certificate has expired.

● Yellow exclamation point—the certificate has 30 days or less until it expires.

Issued To

This field is taken from the certificate when it is downloaded from the issuer. It shows to whom the certificate has been issued.




Issued By

This column shows what authority or agent issued the certificate. This field is taken from the certificate when it is downloaded from the issuer.

Expiration Date

This shows the date the certificate expires as expressed in the certificate itself.

Trusted Certificate screen commands

Refresh

Click this to refresh the screen display.

View

Click this button to view either the general or specific details about the certificate you have highlighted. You will see the Certificate Information—General screen on page 287.

Import

The Import button allows CA certificates to be imported from the issuer into the trusted certificate directory. Import displays a field where you can either type in the File Path or use a Browse button to traverse to the location. You will see the Certificate Import screen on page 290.

Export

Click Export if you want to move a certificate to another SES server. You will see the Certificate Export screen on page 289.

Delete

You may delete any certificates no longer desired with this button.

The Avaya Root CA is never available for deletion.

Security screens



Certificate Information—General screen This screen provides general information about the certificate you have selected. After viewing, you may choose to export this specific certificate to another SES server.

Figure 113: Certificate Information—general screen




Certificate Information—Details The Details tab on the Certificate information screen provides full details about the certificate you selected earlier. After viewing, you may choose to export this specific certificate to another SES server.

Figure 114: Certificate Information—Detail screen

Security screens



Certificate Export screen The Certificate Export screen lets you move the certificate you selected earlier to another SES server.

Figure 115: Certificate Export screen




Certificate Import screen The Certificate Import screen lets you bring a certificate from one SES host computer to a different SES host.

Figure 116: Certificate Import screen

Security screens



SSH Keys screen

Figure 117: SSH Keys screen

SSH Keys screen field descriptionsSecure Shell is a security program that enables you log in to another computer over a network, to execute commands from a remote machine, and to move files from one machine to another. SSH features authentication and secure communications over insecure channels. It is a replacement for rlogin, rsh, rcp, and rdist.




When using slogin instead of rlogin, the entire logon session, including transmission of password, is encrypted. Because of this, 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

● DSA keys for SSHv2

For more detailed information about SSH, visit: http://www.ssh.com.

http://www.ssh.com

Miscellaneous screen



Miscellaneous screen● Download Files screen on page 293

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.

Figure 118: Download Files screen




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'musing 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 server:

1. Specify 1 to 4 files to download by Universal Resource Locator (URL) address.

2. Specify the complete URL. For example, https://networktime.com/security/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.

● If the proxy server requires a port number, add a colon (:) followed by a port number. The default proxy port is 80.

4. 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

Miscellaneous screen



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.


Appendix A: Feature requirement specifications

These sections in this appendix explain how SES rules are applied:

● Call processing software

Call processing softwareCall processing software is explained in sections covering domains and routing:

● RFC 3325 compliance

RFC 3325 complianceThe 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 requirementsThe 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 298

● Call Forward Busy - No Answer FNU on page 299

● Directed Call Pickup FNU on page 301

● Extended Call Pickup FNU on page 302

● Calling Party Number Block FNU on page 302

● Calling Party Number Unblock FNU on page 303

Feature requirement specifications


● Dial Intercom FNU on page 304

● Drop FNU on page 304

● Exclusion FNU on page 305

● Off-PBX Call FNU on page 305

● Last Number Dialed FNU on page 306

● Malicious Call Trace FNU on page 306

● AUDIX One-Step Recording FNU on page 307

● Priority Call FNU on page 307

● Send All Calls FNU on page 308

● Transfer to Voice Mail FNU on page 309

● Whisper Page Activation on page 310

Call Forwarding All Calls FNUThis 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=

4444444;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

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

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

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-cmdestination= 4444444;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

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


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)

Call Forward Busy - No Answer FNUCall 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-destination=4444444;avaya-cm-action=on SIP/2.0


avaya-cm-destination Any number within the Communication Manager dial plan, to which this endpoint is being forwarded

Opt No




INVITE sip:[email protected];avaya-cm-fnu=call-forwarding-busy-no-answer;avayacm-action=on SIP/2.0

INVITE sip:[email protected];avaya-cm-fnu=call-forwarding-busy-no-answer;avayacm-action=off SIP/2.0

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)


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;avayacm- destination=4444444;avaya-cm-action=on SIP/2.0

INVITE sip:[email protected];avaya-cm-fnu=call-forwarding-busy-no-answer;avayacm- action=on SIP/2.0




Opt No

FNU requirements


INVITE sip:[email protected];avaya-cm-fnu=call-forwarding-busy-no-answer;avayacm- action=off SIP/2.0

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


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 FNUDirected 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:




Opt No


avaya-cm-extension The Communication Manager extension where the call is alerting.

Opt No



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 FNUExtended 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:

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 FNUCalling 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-cmdestination=4444444 SIP/2.0

INVITE sip:[email protected];avaya-cm-fnu=calling-party-block SIP/2.0


avaya-cm-pickup-number The pickup number from 1 to 24.

Opt No

FNU requirements


Parameters:

Authorization: None

Communication Manager button: cpn-blk

Feature package: No

SDP required: Yes

Calling Party Number Unblock FNUCalling 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-cmdestination=

4444444 SIP/2.0

INVITE sip:[email protected];avaya-cm-fnu=calling-party-unblock SIP/2.0

Parameters:

Authorization: None

Communication Manager button: cpn-unblk

Feature package: No

SDP required: Yes


avaya-cm-destination Any number within the Communication Manager dial plan to which this call is being directed.

Opt No


avaya-cm-destination Any number within the Communication Manager dial plan to which this call is being directed

Opt No



Dial Intercom FNUDial 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;avayacm-

dial-code=12 SIP/2.0

INVITE sip:[email protected];avaya-cm-fnu=dial-intercom;avaya-cm-group=9 SIP/2.0

Parameters:

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 FNUDrop 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


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

FNU requirements


Exclusion FNUExclusion 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:

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 FNUThis 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


avaya-cm-action on or off Opt No



Parameters:

Authorization: This request always applies to the endpoint’s own extension.

Communication Manager button: ec500


SDP required: No

Last Number Dialed FNULast 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 FNUMalicious 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



FNU requirements


AUDIX One-Step Recording FNUThis 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 RecordingINVITE sip:[email protected]; avaya-cm-fnu=one-touch-recording; avaya-cmextension=3333;avaya-cm-action=on SIP/2.0INVITE sip:[email protected];avaya-cm-fnu=one-touch-recording;avaya-cmaction=off SIP/2.0

Parameters:

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 FNUPriority 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=4444444 SIP/2.0

INVITE sip:[email protected];avaya-cm-fnu=priority-call SIP/2.0



avaya-cm-extension The Communication Manager extension of an AUDIX hunt group

Req Yes



Parameters:

Authorization: None

Communication Manager button: priority

Feature package: No

SDP required: Yes

Send All Calls FNUSend 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:

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)


SDP required: No


avaya-cm-destination Any number within the Communication Manager dial plan, to which this call is being directed

Opt No



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:

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


SDP required: No

Transfer to Voice Mail FNUTransfer 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-voicemail 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





Whisper Page ActivationWhisper 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:

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


avaya-cm-extension The Communication Manager extension to which you want to whisper

Req No


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.

Terminal requirements for SIP




Glossary

Aaccess code A dial code of 1 to 3 digits that activates a feature, cancels a feature, or

accesses an outgoing trunk.Access Security Gateway (ASG)

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.

American National Standards Institute (ANSI)

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.

Avaya Communication Manager

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.

Bbearer channel (B-channel)

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).

bus 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.

CCall Detail Recording (CDR)

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).

Call Detail Recording utility (CDRU)

Software that collects, stores, filters, and provides output of call detail records. See also Call Detail Recording (CDR).

carrier An enclosed shelf that contains vertical slots that hold circuit packs.CCRON coverage of calls redirected off-network. central office (CO) Telephone switching equipment that provides local telephone service and

access to toll facilities for long distance calling.

channel



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).

circuit (1) An arrangement of electrical elements through which electric current flows. (2) A channel or a transmission path between two or more points.

circuit pack 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.

Class of Restriction (COR)

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).

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).

CCITT Comitte Consultatif International Telephonique et Telegraphique. See International Telecommunications Union (ITU).

communications system

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.

Controlled Local Area Network (CLAN) circuit pack

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.

CPN Called-party number CPN/BN Calling-party number/billing number CSP Cellular Service Provider. customer-premises equipment (CPE)

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.

Ddata channel (D-channel)

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)

feature



or Integrated Services Digital Network Primary Rate Interface (ISDN-PRI). See also bearer channel (B-channel).

data communications equipment (DCE)

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).

data module 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).

data terminal An input/output (I/O) device that has either switched access or direct access to a host computer or to a processor interface.

data terminal equipment (DTE)

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.

digital The representation of information by discrete steps. Compare with analog. Digital Communications Protocol (DCP)

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.

dual-tone multifrequency (DTMF)

The touchtone signals used for in-band telephone signaling.

Dynamic Host Configuration Protocol (DHCP)

An IETF protocol (RFCs 951, 1534, 1542, 2131, and 2132) that assigns IP addresses dynamically from a pool of addresses instead of statically.

Eedge An Edge server handles user requests sent to and from SES home server(s).extension 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).

FFNE Feature Name ExtensionFNU Feature Name URIFTP File transfer protocol.feature A specifically defined function or service that the system provides

H.323



HH.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.

IIE See information element (IE).IEEE See Institute of Electrical and Electronics Engineers (IEEE).IETF See Internet Engineering Task Force (IETF).IM 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.

information element (IE)

The name for the data fields within an Integrated Services Digital Network (ISDN) Layer 3 message.

Initialization and Administration System (INADS)

A software tool that is used by Avaya Services personnel for communication, remote management and troubleshooting of customers’ alarms and traps.

IP interface A CLAN, ethernet processor interface, or procr that lets the server connect using internet protocol.

Institute of Electrical and Electronics Engineers (IEEE)

An organization that produces standards for local area network (LAN) equipment.

Integrated Services Digital Network (ISDN)

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 multipurposeuser-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).

Integrated Services Digital Network Basic Rate Interface (ISDN-BRI)

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

Internet Protocol (IP)



terminals that are fitted with ISDN terminal adapters. See also Integrated Services Digital Network Primary Rate Interface (ISDN-PRI).

Integrated Services Digital Network Primary Rate Interface (ISDN-PRI)

The interface between multiple communications systems that in North America includes 24 64-kbps channels that correspond to the North American digital signal-level 1 (DS1) standard rate of 1.544 Mbps. The most common arrangement of channels in ISDN-PRI is 23 64-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).

International Organization for Standards

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).

International Telecommunications Union (ITU)

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).

International Telegraph and Telephone Consultative Committee

See International Telecommunications Union (ITU).

Internet Engineering Task Force (IETF)

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.

Internet Protocol (IP)

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.

local area network (LAN)



Llocal area network (LAN)

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.

MMAC address (or MAC name)

A 48-bit number, uniquely identifying and programmed into each network interface card or device.

media server interface

A CLAN card in an Avaya server running Avaya Communication Manager.

MWI messaging waiting indication. For example, a visual alert of new voice mail.MIB management information base. A type of hierarchical database, addressing

object identifiers, used to manage devices in a communications network.

NNAME1 Legacy name, Latin characters, usually displayable, for example Eurofont and

Kanafont encoding. NAME2 UTF-8 encoding. Used for multibyte character sets such as Chinese ideograms

Hiragana, Katakana, and Hangulnarrowband 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.network A series of points, nodes, or stations that are connected by communications

channels.network region 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.

node 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.

nonce 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 RFC2617.

Plain Old Telephone Service (POTS)



OOATS 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.

off-PBX station (OPS)

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.

OPS Outboard Proxy SIP. Open Systems Interconnect (OSI)

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.

origination-based call flow

See OATS.

O/S Operating System.

Ppacket 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.

packet assembly/disassembly (PAD)

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.

packet bus A bus with a wide bandwidth that transmits packets.packet switching 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.

PBX private branch exchange. See SSH.Plain Old Telephone Service (POTS)

Basic voice communications with standard, single-line phones accessing the public switched telephone network (PSTN).

PPM



PPM 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.

Point-to-Point Protocol (PPP)

A standard (largely replacing SLIP) allowing a computer to use TCP/IP with a regular telephone line.

port A data-transmission access point or voice-transmission access point on a device that is used for communicating with other devices.

private network A network exclusively for the telecommunications needs of a particular customer.

processor ethernet 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.

procr See processor ethernet. protocol 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.proxy trust domain Includes those SIP servers and gateways, but not endpoints with identities

administered on the server running SES. public network A network to which all customers have open access for local calling and long

distance calling.public switched telephone network (PSTN)

The public worldwide voice telephone network.

RRAS Remote Access Server (or in Microsoft Windows operating systems, Remote

Access Service).Real-time Transfer Protocol (RTP)

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.

RFA Remote Feature Activation is a web-based application which is used to obtain Avaya authentication and licensing files.

RFC Request for Comments designates Internet Engineering Task Force (IETF) standards that are drafts.

tie trunk



RNIS Remote Network Implementation Services is a contract installation services group within Avaya Inc.

RPM RedHat Package ManagerRTC Real Time CommunicationRTCP Real Time Control Protocol

SS8400 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.

S8500 A hardware platform from the IBM x305 series. This machine uses an RSA for a remote maintenance board.

S8500B A hardware platform from the IBM x306 series. This machine uses a SAMP for a remote maintenance board.

SAMP Server Availability Management Processor. A remote maintenance board.SCCAN 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.

Session Initiated Protocol (SIP)

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).

SIP Enablement Services

SES. SIP Enablement Services is the name for Avaya’s solution that was previously called Converged Communication Server.

SSH 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.

SSL Secure Socket Layer. subscriber 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).

switch Any kind of telephone switching system. See also communications system.

TTAC trunk-access code TCP See Transmission Control Protocol (TCP).TCP/IP See Internet Protocol (IP). See also Transmission Control Protocol (TCP).tie trunk A telecommunications channel that directly connects two private switching

systems.

time-division multiplex (TDM) bus



time-division multiplex (TDM) bus

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).

time-division multiplexing (TDM)

A form of multiplexing that divides a transmission channel into successive time slots. See alsotime-division multiplex (TDM) bus.

time slot 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.

Transmission Control Protocol (TCP)

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.

Transport Layer Security (TLS)

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.

trunk A dedicated communications channel between two communications systems or central office (CO)s.

trunk access code (TAC)

A dial access code used to access a specific trunk.

trunk group 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.

UUDP User Datagram ProtocolURI Uniform Resource IdentifierURL Uniform Resource Location

VVoIP Voice over Internet Protocol (IP)

WW call flow See OATS.



Index

Index

Numerical802.1 Parameters

Edit System Properties screen. . . . . . . . . . 121

AAdd Another Handle command . . . . . . . . . . . 183Add Another User command . . . . . . . . . . . . 139Add Contact command . . . . . . . . . . . . 148, 161Add Contact screens . . . . . . . . . . . . . . . . 152Add Group screens . . . . . . . . . . . . . . . . 156Add Handle in a New Group screens . . . . . . . . 193Add Handle in New Group command . . . . . . . . 184Add Handle screens . . . . . . . . . . . . . . . . 189Add Host Contact for user screens . . . . . . . . . 191Add Host screen . . . . . . . . . . . . . . . . . . 123Add Media Server screen. . . . . . . . . . . . . . 132add or prevent permissions . . . . . . . . . . . . . 202Add User screens . . . . . . . . . . . . . . . . . 142administer stations . . . . . . . . . . . . . . . . . 35administering

Feature-Related System Parameters screen . . . 85IP Network Region screen. . . . . . . . . . . . 59Locations screen . . . . . . . . . . . . . . . . 64Signaling Group screen . . . . . . . . . . . .32, 77SIP . . . . . . . . . . . . . . . . . . . . . . 27SIP trunks . . . . . . . . . . . . . . . . . . . 27System Capacity screen . . . . . . . . . . . . 84System-Parameters Call Coverage/Call Forwarding

screen . . . . . . . . . . . . . . . . . . . . 87System-Parameters Customer-Options screen .28, 88Trunk Group screen. . . . . . . . . . . 33, 94, 105Trunk Group screen page 2 . . . . . . . . . . . 105Trunk Group screens . . . . . . . . . . . . . . 94

administrationadministering stations . . . . . . . . . . . . . . 35call routing . . . . . . . . . . . . . . . . . . . 30detailed screens . . . . . . . . . . . . . . . . 37enable SIP on Communication Manager . . . . . 28set SIP device as OPTIM extension . . . . . . . 110SIP trunks . . . . . . . . . . . . . . . . . . . 32visiting user . . . . . . . . . . . . . . . . . . 36

Administration web interface . . . . . . . . . . . . 111administration, Top-level screens . . . . . . . . . . 112administrative screens . . . . . . . . . . . . . . . 37Alarms screens . . . . . . . . . . . . . . . . . . 217allow permissions . . . . . . . . . . . . . . . . . 202ARS Digit Analysis Table

ANI Reqd field . . . . . . . . . . . . . . . . . 39Call Type (for AAR only) field. . . . . . . . . . . 40Call Type (for ARS only) field. . . . . . . . . . . 41Dialed String field . . . . . . . . . . . . . . . . 41Location . . . . . . . . . . . . . . . . . . . . 42Max field . . . . . . . . . . . . . . . . . . . . 42Min field . . . . . . . . . . . . . . . . . . . . 43Node Number field . . . . . . . . . . . . . . . 43Percent Full field . . . . . . . . . . . . . . . . 43Route Pattern field. . . . . . . . . . . . . . . . 43

Audix One-Step recording FNU . . . . . . . . . . 307Authentication File screen. . . . . . . . . . . . . 275Avaya CM OPTIM terminals . . . . . . . . . . . . .311

Bbackup. . . . . . . . . . . . . . . . . . . . . . 259Backup History screen . . . . . . . . . . . . . . 256Backup Logs screen . . . . . . . . . . . . . . . 261backup schedule . . . . . . . . . . . . . . . . . 259block permissions . . . . . . . . . . . . . . . . 202

Ccall appearances . . . . . . . . . . . . . . . . . .110call capacity . . . . . . . . . . . . . . . . . . . . 84call coverage . . . . . . . . . . . . . . . . . . . . 87Call Forward Busy FNU . . . . . . . . . . . . . . 299Call Forward FNU . . . . . . . . . . . . . . . . 298call forwarding . . . . . . . . . . . . . . . . . . . 87call processing

SES . . . . . . . . . . . . . . . . . . . . . 297call routing . . . . . . . . . . . . . . . . . . . . . 30calling party block FNU . . . . . . . . . . . . . . 302calling party number unblock FNU . . . . . . . . . 303capacity . . . . . . . . . . . . . . . . . . . . . . 84certificate import screen. . . . . . . . . . . . . . 290certificate information . . . . . . . . . . . . . . . 287change permissions . . . . . . . . . . . . . 201, 207Choose Interface screen . . . . . . . . . . . . . .114commands

Add Another Handle . . . . . . . . . . . . . . 183Add Another User . . . . . . . . . . . . . . . 139Add Contact

Group Details screen . . . . . . . . . . . . 161My Contact List screen . . . . . . . . . . . 148

Add Group . . . . . . . . . . . . . . . . . . 148Add Handle in New Group . . . . . . . . . . . 184Back to My Contact List . . . . . . . . . . . . 161



Index

Delete Extensions Also . . . . . . . . . . . . . 216Delete Group

Edit User Handles screen . . . . . . . . . . 184Group Details screen . . . . . . . . . . . . 161

Delete Handle . . . . . . . . . . . . . . . . . 183Edit Handle. . . . . . . . . . . . . . . . . . . 183for Off-PBX Station Mapping screen . . . . . . . 67Free

List Media Server Extensions screen . . . . . 176Install . . . . . . . . . . . . . . . . . . . . . 276Install the Authentication File

previously downloaded. . . . . . . . . . . . 276specify below . . . . . . . . . . . . . . . . 276

Reload Configuration . . . . . . . . . . . . . . 149Speed Dial . . . . . . . . . . . . . . . . . . . 149track availability . . . . . . . . . . . . . . . . 155Update Group . . . . . . . . . . . . . . . . . 162

Configuration Set screenConfiguration Set Description field . . . . . . . . 45

Confirm Delete User screens . . . . . . . . . . . . 216connected party name . . . . . . . . . . . . . . . 98connection path . . . . . . . . . . . . . . . . . . 233connections

internet. . . . . . . . . . . . . . . . . . . . . 236modem. . . . . . . . . . . . . . . . . . . . . 241server . . . . . . . . . . . . . . . . . . . . . 236

Contact Details screen . . . . . . . . . . . . . . . 150Contact List screens . . . . . . . . . . . . . . . . 146Contact List task . . . . . . . . . . . . . . . 139, 146contacts

end user’s buddy list . . . . . . . . . . . . . . 139of the end user . . . . . . . . . . . . . . . . . 140

copy files with FTP. . . . . . . . . . . . . . . . . 273co-residency

port assignments . . . . . . . . . . . . . . . . 133server types . . . . . . . . . . . . . . . . . . 125

Current Alarms screen . . . . . . . . . . . . . . . 218

DData Backup/Restore screen . . . . . . . . . . . . 252delete all displayed users screen . . . . . . . . . . 173Delete Contact screens . . . . . . . . . . . . . . 159Delete Extensions Also command. . . . . . . . . . 216Delete Group command

Edit User Handles screen . . . . . . . . . . . . 184Group Details screen . . . . . . . . . . . . . . 161

Delete Group screen . . . . . . . . . . . . . . . . 163Delete Handle command . . . . . . . . . . . . . . 183delete multiple users . . . . . . . . . . . . . 140, 174delete selected users screen . . . . . . . . . . . . 174Devices Menu screens . . . . . . . . . . . . . . . 167Devices task. . . . . . . . . . . . . . . . . 140, 167Diagnostics screen. . . . . . . . . . . . . . . . . 223Dial Intercom FNU . . . . . . . . . . . . . . . . . 304

Dial Plan Analysis screenCall Type field. . . . . . . . . . . . . . . . . . 46Dialed String field . . . . . . . . . . . . . . . . 50Percent Full field . . . . . . . . . . . . . . . . 50Total Length field . . . . . . . . . . . . . . . . 50

DID/Tie/ISDN/SIP Intercept Treatment fieldFeature-Related System Parameters screen . . . 86

DiffServ/TOS ParametersEdit System Properties screen . . . . . . . . . 121

Directed Call Pickup FNU . . . . . . . . . . . . . 301distinctive alerting . . . . . . . . . . . . . . . . 304Distributed Office . . . . . . . . . . . . . . . . . 135domain

authoritative. . . . . . . . . . . . . . . . . 29, 59blank . . . . . . . . . . . . . . . . . . . . . . 23far-end . . . . . . . . . . . . . . . . . . . 23, 80network region . . . . . . . . . . . . . . . . . 29

Download Files screen . . . . . . . . . . . . . . 293Drop FNU . . . . . . . . . . . . . . . . . . . . 304

EEdit Default User Profile screen . . . . . . . . . . 130Edit Handle command . . . . . . . . . . . . . . 183Edit Handle detail screens . . . . . . . . . . . . 185Edit Host Contact screens. . . . . . . . . . . . . 187Edit System Properties screen. . . . . . . . . . . .119Edit User Handles screen . . . . . . . . . . . . . 181Edit User Handles screens . . . . . . . . . . . . 181Edit User Profile screens . . . . . . . . . . . . . 203Exclusion FNU . . . . . . . . . . . . . . . . . . 305Extension tasks . . . . . . . . . . . . . . . . . 175Extensions task . . . . . . . . . . 140, 175, 177, 178

Ffar-end domain . . . . . . . . . . . . . . . . . . . 23Feature Access Codes screen page 1

Auto Route Selection (ARS) Access Code1 field. . 51Feature Related System Parameters screen

EMU Inactivity Interval for Deactivation . . . . . . 52Feature-Related System Parameters screen . . . . . 85

Trunk-to-Trunk Transfer field . . . . . . . . . 85, 86features

failover . . . . . . . . . . . . . . . . . . . . . 23meet me conferencing . . . . . . . . . . . . . . 27visiting user . . . . . . . . . . . . . . . . . . . 36

fields802.1 Parameters . . . . . . . . . . . . . . . 121ACA Assignment . . . . . . . . . . . . . . . 105Access Control Policy

Add Host screen . . . . . . . . . . . . . . 126Ack . . . . . . . . . . . . . . . . . . . . . . 219Add Entry . . . . . . . . . . . . . . . . . . . 202Add Media Server Extension . . . . . . . . . . 145



Index

Add Memo . . . . . . . . . . . . . . . . . . . 196Address

Add Contact screen . . . . . . . . . . . . . 154One Touch Dial List screen. . . . . . . . . . 168

Address 1, Address 2Add User screen . . . . . . . . . . . . . . 144Edit Default User Profile screen . . . . . . . 131Edit User Profile screen . . . . . . . . . . . 205Search Users screen . . . . . . . . . . . . 209

AliasAdd Contact screen . . . . . . . . . . . . . 154Group Details screen . . . . . . . . . . . . 161My Contact List screen. . . . . . . . . . . . 147

Allow Emergency Contacts . . . . . . . . . . . 126Allow List. . . . . . . . . . . . . . . . . . . . 202Allow List/Block List . . . . . . . . . . . . . . . 202ANI Reqd . . . . . . . . . . . . . . . . . . . 39Application . . . . . . . . . . . . . . . . . . . 68Auth Code . . . . . . . . . . . . . . . . . . . 101Authentication Password (v3 only) . . . . . . . . 222Authoritative Domain . . . . . . . . . . . . . . 59Auto Route Selection (ARS) Access Code1 . . . 51Backup Method. . . . . . . . . . . . . . . . . 254Block List . . . . . . . . . . . . . . . . . . . 202Bridged Appearance . . . . . . . . . . . . . . 171Bridged calls . . . . . . . . . . . . . . . . . . 74Busy Threshold. . . . . . . . . . . . . . . . . 99Button

One Touch Dial List screen. . . . . . . . . . 168Ringer Settings screen. . . . . . . . . . . . 170

Bypass If IP Threshold Exceeded . . . . . . . . 80Call Limit . . . . . . . . . . . . . . . . . . . . 72Call Type. . . . . . . . . . . . . . . . . . . . 46Call Type (for AAR only) . . . . . . . . . . . . 40Call Type (for ARS only) . . . . . . . . . . . . 41Calls Allowed. . . . . . . . . . . . . . . . . . 73CCS Version . . . . . . . . . . . . . . . . . . 120CDR Reports . . . . . . . . . . . . . . . . . . 95Change Permissions . . . . . . . . . . . . . . 201Change Permissions Type . . . . . . . . . . . 201City

Add User screen . . . . . . . . . . . . . . 145Edit Default User Profile screen . . . . . . . 131Edit User Profile screen . . . . . . . . . . . 205Search Users screen . . . . . . . . . . . . 210

CM FQD Name or IP AddressAdd Media Server screen . . . . . . . . . . 134

CM LoginAdd Media Server screen . . . . . . . . . . 133

CM Password/CM Password ConfirmAdd Media Server screen . . . . . . . . . . 134

Community or User Name. . . . . . . . . . . . 222Configuration Set . . . . . . . . . . . . . . . . 70Configuration Set Description . . . . . . . . . . 45Contact

Add Host Contact screen . . . . . . . . 186, 192Add User screen . . . . . . . . . . . . . . 143Contact List screen. . . . . . . . . . . . . 147Edit Host Contact screen . . . . . . . . . . 187Edit User Handles screen. . . . . . . . . . 183

Contact List Members . . . . . . . . . . . . . 207Contact Phones . . . . . . . . . . . . . . . . 155Contact Type . . . . . . . . . . . . . . . . . 192Content . . . . . . . . . . . . . . . . . . . . 244COR . . . . . . . . . . . . . . . . . . . . . . 96Country

Add User screen . . . . . . . . . . . . . . 145Edit Default User Profile screen . . . . . . . 131Edit User Profile screen. . . . . . . . . . . 205Search Users screen . . . . . . . . . . . . 210

Crit_High . . . . . . . . . . . . . . . . . . . 229Crit_Low . . . . . . . . . . . . . . . . . . . 229Current Permissions Type . . . . . . . . . . . 200Current SSH public keys . . . . . . . . . . . . 292Data Set . . . . . . . . . . . . . . . . . . . 261Data Sets

Backup Now screen . . . . . . . . . . . . 254Schedule Backup screen . . . . . . . . . . 257

DateBackup Log screen. . . . . . . . . . . . . 261Current Alarms screen . . . . . . . . . . . 219Server Date/Time screen . . . . . . . . . . 249

DaySchedule Backup screen . . . . . . . . . . 258

Default Receiver VolumeAdd Host screen . . . . . . . . . . . . . . 128

Default Ringer CadenceAdd Host screen . . . . . . . . . . . . . . 128

Default Ringer VolumeAdd Host screen . . . . . . . . . . . . . . 128

Default Speaker VolumeAdd Host screen . . . . . . . . . . . . . . 128

Delete . . . . . . . . . . . . . . . . . . . . 162Delete all contacts. . . . . . . . . . . . . . . 163Description . . . . . . . . . . . . . . . . . . 220Destination

Backup Logs screen . . . . . . . . . . . . 262Schedule Backup screen . . . . . . . . . . 258

Dial Access . . . . . . . . . . . . . . . . . . . 98Dial Prefix. . . . . . . . . . . . . . . . . . 69, 71Dialed String . . . . . . . . . . . . . . . . 41, 50DID/Tie/ISDN/SIP Intercept Treatment . . . . . . 86DiffServ/TOS Parameters . . . . . . . . . . . 121Digital Loss Group. . . . . . . . . . . . . . . 103Direct IP-IP Audio Connections. . . . . . . . . . 81Direction . . . . . . . . . . . . . . . . . . . . 98Disable call classifier for CCRON over SIP trunks . 87Display Format . . . . . . . . . . . . . . . . 227Domain

Edit Handle detail screen . . . . . . . . . . 185



Index

DTMF over IP . . . . . . . . . . . . . . . . . 80E-mail . . . . . . . . . . . . . . . . . . . . . 155Encryption . . . . . . . . . . . . . . . . . . . 255Enhanced EC500 . . . . . . . . . . . . . . . . 91EvtID . . . . . . . . . . . . . . . . . . . . . 219Execute Ping . . . . . . . . . . . . . . . . . . 231Extension

Add Media Server Extension screen . . . . . 178List Media Server Extensions screen . . . . . 175

Far-end Domain . . . . . . . . . . . . . . . . 80Far-end Network Region . . . . . . . . . . . . 79Far-end Node Name . . . . . . . . . . . . . . 78Feature . . . . . . . . . . . . . . . . . . . . 229File Size . . . . . . . . . . . . . . . . . . . . 261File(s) to download from the LAN using URL . . . 294File(s) to download from the machine connected to the

server . . . . . . . . . . . . . . . . . . . . 294First Name . . . . . . . . . . . . . . . . . . . 144

Edit User Profile screen . . . . . . . . . . . 204Search Users screen . . . . . . . . . . . . 209

Frequency . . . . . . . . . . . . . . . . . . . 244FTP . . . . . . . . . . . . . . . . . . . . . . 264Gateway IP Address . . . . . . . . . . . . . . 122Generate New SSH Keys . . . . . . . . . . . . 292Group Name . . . . . . . . . . . . . . . . . . 165

Add Contact screen . . . . . . . . . . . . . 154Add Group screen . . . . . . . . . . . . . . 156Trunk Group screen page 1 . . . . . . . . . 96

Group NumberSignaling Group screen p 1 . . . . . . . .77, 81Trunk Group screen page 1 . . . . . . . . . 94

Group TypeSignaling Group screen page 1 . . . . . . . . 77Trunk Group screen page 1 . . . . . . . . . 95

Handle . . . . . . . . . . . . . . . . . . . . . 157Add Another Handle screen . . . . . . . . . 189Add Group screen . . . . . . . . . . . . . . 193Add Host Contact screen. . . . . . . . . . . 191Edit Handle detail screen. . . . . . . . . . . 186Edit User Handles screen . . . . . . . . . . 183Group Details screen . . . . . . . . . . . . 160My Contact List screen. . . . . . . . . . . . 147Permissions screen . . . . . . . . . . . . . 201

Home Domain . . . . . . . . . . . . . . . . . 59Host

Add Media Server screen . . . . . . . . . . 133Add User screen . . . . . . . . . . . . . . 144Edit Default User Profile screen . . . . . . . 130Edit User Profile screen . . . . . . . . . . . 204List Media Server Extensions screen . . . . . 176List Users screen . . . . . . . . . 136, 137, 139Search Users screen . . . . . . . . . . . . 209

Host IP AddressAdd Host screen. . . . . . . . . . . . . . . 125

Host Name or IP AddressPing screen . . . . . . . . . . . . . . . . . 230

Traceroute screen . . . . . . . . . . . . . 233Host Type

Add Host screen . . . . . . . . . . . . . . 125ID . . . . . . . . . . . . . . . . . . . . . . 218Input to server. . . . . . . . . . . . . . . . . 279Install this file on the local server . . . . . . . . 295Inter-region IP-IP Direct Audio . . . . . . . . . . 61Intra-region IP-IP Direct Audio . . . . . . . . . . 60IP Address . . . . . . . . . . . . . . . . . . . 64

SNMP Traps screen . . . . . . . . . . . . 221IP Audio Hairpinning. . . . . . . . . . . . . . . 81Label . . . . . . . . . . . . . . . . . . . . . 169Last Name

Add User screen . . . . . . . . . . . . . . 144Edit User Profile screen. . . . . . . . . . . 204Search Users screen . . . . . . . . . . . . 209

Line Reservation TimerAdd Host screen . . . . . . . . . . . . . . 127

Link Protocol . . . . . . . . . . . . . . . . . 126Link Protocols

Add Host screen . . . . . . . . . . . . . . 126List of memos . . . . . . . . . . . . . . . . . 196Listen Protocols

Add Host screen . . . . . . . . . . . . . . 126Local directory . . . . . . . . . . . . . . . . 264Local PC card . . . . . . . . . . . . . . . . . 264Location (for the ARS Digit Analysis Table) . . . . 42Logon ID . . . . . . . . . . . . . . . . . . . .113Lvl . . . . . . . . . . . . . . . . . . . . . . 219Maintenance . . . . . . . . . . . . . . . . . .115Maintenance Tests . . . . . . . . . . . . . . 106Major Alarms . . . . . . . . . . . . . . . . . 243Management system access login . . . . . . . 120Management system access password . . . . . 121Mapping Mode . . . . . . . . . . . . . . . . . 73Mark Users as Phone . . . . . . . . . . . . . 109Match Pattern . . . . . . . . . . . . . . . . . 227Max . . . . . . . . . . . . . . . . . . . . . . 42Maximum Administered SIP Trunks. . . . . . . . 90Maximum Off-PBX Telephones - EC500 . . . . . 88Maximum Off-PBX Telephones - OPS . . . . . . 88Measured. . . . . . . . . . . . . . . . . . . 106Media Server . . . . . . . . . . . . . . . . . 176

Add Media Server Extension screen . . . . . 178Media Server Name . . . . . . . . . . . . . . 133Min . . . . . . . . . . . . . . . . . . . . . . . 43Minimum Registration

Setup screen . . . . . . . . . . . . . . . 127Minor Alarms . . . . . . . . . . . . . . . . . 243Mode . . . . . . . . . . . . . . . . . . . . . 243Modem Administration . . . . . . . . . . . . . 269Move all contacts . . . . . . . . . . . . . . . 163Name. . . . . . . . . . . . . . . . . . . . . . 63

Add Contact screen . . . . . . . . . . . . 154Group Details screen . . . . . . . . . . . . 161



Index

List Users screen . . . . . . . . . . . . . . 139My Contact List screen. . . . . . . . . . . . 147

Near-end Listen Port . . . . . . . . . . . . . . 79Near-end Node Name. . . . . . . . . . . . . . 78Network Properties . . . . . . . . . . . . . . . 122Network Region . . . . . . . . . . . . . . . . 65Night Service . . . . . . . . . . . . . . . . . . 99Node Number . . . . . . . . . . . . . . . . . 43Notes . . . . . . . . . . . . . . . . . . . . . 155Notification . . . . . . . . . . . . . . . . . . . 222Number of Members . . . . . . . . . . . . . . 101Numbering Format . . . . . . . . . . . . . . . 107Office

Add User screen . . . . . . . . . . . . . . 145Edit User Profile screen . . . . . . . . . . . 205

Old Group Name . . . . . . . . . . . . . . . . 165Operating System . . . . . . . . . . . . . . . 250Options

Ping screen . . . . . . . . . . . . . . . . . 231Traceroute screen . . . . . . . . . . . . . . 234

Outbound Direct DomainsAdd Host screen. . . . . . . . . . . . . . . 128

Outbound PortAdd Host screen. . . . . . . . . . . . . . . 127

Outbound ProxyAdd Host screen. . . . . . . . . . . . . . . 127

Outbound Routing Allowed FromAdd Host screen. . . . . . . . . . . . . . . 127

Outgoing Display . . . . . . . . . . . . . . . . 98Output format. . . . . . . . . . . . . . . . . . 237Output from server . . . . . . . . . . . . . . . 279Output type. . . . . . . . . . . . . . . . . . . 236Parent

Add Host screen. . . . . . . . . . . . . . . 125Password

Logon screen . . . . . . . . . . . . . . . . 113Password/Confirm Password

Add User screen . . . . . . . . . . . . . . 144Edit User Profile screen . . . . . . . . . . . 204

Percent Full . . . . . . . . . . . . . . . . .43, 50Phone Number . . . . . . . . . . . . . . . . . 69Port/Protocol . . . . . . . . . . . . . . . . . . 280Preferred Minimum Session Refresh Interval . . . 104Prefix . . . . . . . . . . . . . . . . . . . . . 158Prerequisites . . . . . . . . . . . . . . . . . . 294Primary Handle . . . . . . . . . . . . . . . . . 143Privacy Password. . . . . . . . . . . . . . . . 222Processes . . . . . . . . . . . . . . . . . . . 243Product ID . . . . . . . . . . . . . . . . . . . 218Profile Service Password . . . . . . . . . . . . 125Proxy Selection Route Pattern . . . . . . . . . . 65Queue Length . . . . . . . . . . . . . . . . . 100Receiver Volume . . . . . . . . . . . . . . . . 172Redirect on OPTIM failure . . . . . . . . . . . . 102Redundant Properties. . . . . . . . . . . . . . 122

RegionIP Address Mapping screen. . . . . . . . . . 58Network Region screen . . . . . . . . . . . . 59

Registration Expiration TimerAdd Host screen . . . . . . . . . . . . . . 127

Replace Unavailable Numbers . . . . . . . . . 107Ringer ON/OFF . . . . . . . . . . . . . . . . 171Ringer Volume . . . . . . . . . . . . . . . . 172Route Pattern . . . . . . . . . . . . . . . . . . 43SAMP Version ID . . . . . . . . . . . . . . . 251Secure SIP

Route Pattern screen . . . . . . . . . . . . . 75Select a View . . . . . . . . . . . . . . . . . 226Select Event Range . . . . . . . . . . . . . . 226Select Log Types . . . . . . . . . . . . . . . 225Select Time . . . . . . . . . . . . . . . . . . 249Server Alarms. . . . . . . . . . . . . . . . . 220Server BIOS Build ID . . . . . . . . . . . . . 251Server Hardware . . . . . . . . . . . . . . . 243Server IP Address . . . . . . . . . . . . . . . . 62Server Port . . . . . . . . . . . . . . . . . . . 62Service . . . . . . . . . . . . . . . . . . . . 279Service Type . . . . . . . . . . . . . . . . . 100Session Establishment Timer . . . . . . . . . . 80Setup Default User Profile . . . . . . . . . . . .118Setup Hosts. . . . . . . . . . . . . . . . . . .117Setup SIP Domain. . . . . . . . . . . . . . . .117Show only the following output families . . . . . 237Shutdown options . . . . . . . . . . . . . . . 247Signaling Group . . . . . . . . . . . . . . . . 101SIP Domain . . . . . . . . . . . . . . . . . . 120SIP License Host . . . . . . . . . . . . . . . 120SIP Trunk IP Address

Add Media Server screen . . . . . . . . . . 133SIP Trunks . . . . . . . . . . . . . . . . . . . 84SMS Connection Type

Add Media Server screen . . . . . . . . . . 134SNMP Version . . . . . . . . . . . . . . . . 222Software Load . . . . . . . . . . . . . . . . 251Source . . . . . . . . . . . . . . . . . . . . 219Speaker Volume . . . . . . . . . . . . . . . 172State

Add User screen . . . . . . . . . . . . . . 145Edit Default User Profile screen . . . . . . . 131Edit User Profile screen. . . . . . . . . . . 205Search User screen . . . . . . . . . . . . 210

Station Extension . . . . . . . . . . . . . . 68, 72Status . . . . . . . . . . . . . . . . . . . . 229

Backup Logs screen . . . . . . . . . . . . 262Schedule Backup screen . . . . . . . . . . 258SNMP Traps screen . . . . . . . . . . . . 221

TAC . . . . . . . . . . . . . . . . . . . . . . 97Telephone # . . . . . . . . . . . . . . . . . 158Telephone #1/Telephone #2

Group Details Screen. . . . . . . . . . . . 161



Index

My Contact List screen. . . . . . . . . . . . 147Test Options . . . . . . . . . . . . . . . . . . 241Time

Backup Logs screen . . . . . . . . . . . . . 261Schedule Backup screen. . . . . . . . . . . 258

Time Zone . . . . . . . . . . . . . . . . . . . 249TN . . . . . . . . . . . . . . . . . . . . . . . 97Total Length . . . . . . . . . . . . . . . . . . 50Track Availability . . . . . . . . . . . . . . . . 155Transport Method. . . . . . . . . . . . . . . . 78Tripwire Status . . . . . . . . . . . . . . . . . 281Trunk Selection. . . . . . . . . . . . . . . . . 69Type . . . . . . . . . . . . . . . . . . . . . . 83Unicode Name . . . . . . . . . . . . . . . . . 102Unknown SIP Users . . . . . . . . . . . . . . 207UPS Endpoints . . . . . . . . . . . . . . . . . 230URL . . . . . . . . . . . . . . . . . . . . . . 275Used. . . . . . . . . . . . . . . . . . . . . . 89User . . . . . . . . . . . . . . . . . . . . . . 176User ID

Add Another Handle screen . . . . . . . . . 189Add Group screen . . . . . . . . . . . . . . 193Add Host Contact screen. . . . . . . . . . . 191Add User screen . . . . . . . . . . . . . . 144Edit Handle detail screen. . . . . . . . . . . 185Edit Host Contact screen. . . . . . . . . . . 187Edit User Handles screen . . . . . . . . . . 182Edit User Profile screen . . . . . . . . . . . 204List Users screen . . . . . . . . . 136, 137, 139Search Users screen . . . . . . . . . . . . 209Select User screen . . . . . . . . . . . . . 212Update Password screen . . . . . . . . . . 213User Memo screen . . . . . . . . . . . . . 196

V3 Security Model . . . . . . . . . . . . . . . 222Value . . . . . . . . . . . . . . . . . . . . . 229View . . . . . . . . . . . . . . . . . . . . . . 162VMM Information . . . . . . . . . . . . . . . . 129Warn_High . . . . . . . . . . . . . . . . . . . 229Warn_Low . . . . . . . . . . . . . . . . . . . 229ZIP

Add User screen . . . . . . . . . . . . . . 145Edit Default User Profile screen . . . . . . . 131Edit User Profile screen . . . . . . . . . . . 205Search Users screen . . . . . . . . . . . . 210

Firewall screen . . . . . . . . . . . . . . . . . . 277firmware

checking version . . . . . . . . . . . . . . . . 250copying . . . . . . . . . . . . . . . . . . . . 273downloading . . . . . . . . . . . . . . . . . . 293

firmware requirements . . . . . . . . . . . . . . . 22FNU

AUDIX One-Step recording . . . . . . . . . . . 307call forward. . . . . . . . . . . . . . . . . . . 298call forward busy . . . . . . . . . . . . . . . . 299calling party number block. . . . . . . . . . . . 302

calling party number unblock . . . . . . . . . . 303dial intercom . . . . . . . . . . . . . . . . . 304directed call pickup . . . . . . . . . . . . . . 301drop . . . . . . . . . . . . . . . . . . . . . 304exclusion . . . . . . . . . . . . . . . . . . . 305extended call pickup FNU . . . . . . . . . . . 302Last number dialed . . . . . . . . . . . . . . 306Malicious call trace . . . . . . . . . . . . . . 306off-PBX . . . . . . . . . . . . . . . . . . . . 305priority call . . . . . . . . . . . . . . . . . . 307send all calls . . . . . . . . . . . . . . . . . 308transfer to voice mail . . . . . . . . . . . . . 309whisper page activation . . . . . . . . . . . . 310

FNU requirements . . . . . . . . . . . . . . . . 297FNUs . . . . . . . . . . . . . . . . . . . . . . 297Format PC Card screen. . . . . . . . . . . . . . 266

Format PC Card results screen. . . . . . . . . 267FRC 3325 compliance . . . . . . . . . . . . . . 297Free command

List Media Server Extensions screen . . . . . . 176FTP operation . . . . . . . . . . . . . . . . . . 272FTP screen . . . . . . . . . . . . . . . . . . . 271

Steps to Start or Stop FTP service . . . . . . . 271

GGateway IP Address field

Edit System Properties screen . . . . . . . . . 122Group Details screens . . . . . . . . . . . . . . 160

HHandles task . . . . . . . . . . . . . . . . . 140, 181hardware requirements . . . . . . . . . . . . . . . 21

IIncoming Call Handling Treatment screen . . . . . . 54Install Root Certificate screen

Prerequisites . . . . . . . . . . . . . . . . . 294intercept treatment . . . . . . . . . . . . . . . . . 86intercom . . . . . . . . . . . . . . . . . . . . . 304interface

administration . . . . . . . . . . . . . . . . . .111maintenance . . . . . . . . . . . . . . . . . 217

interfaceschoose interface screen . . . . . . . . . . . . .114maintenance . . . . . . . . . . . . . . . . . 217master administration . . . . . . . . . . . . . . 111

international calls . . . . . . . . . . . . . . . . . 107introduction . . . . . . . . . . . . . . . . . . . . 17IP Address Mapping screen

Region field . . . . . . . . . . . . . . . . . . . 58IP Codec Set screens. . . . . . . . . . . . . . . . 56



Index

IP Network Region screenAuthoritative Domain field . . . . . . . . . . . . 59Home Domain field . . . . . . . . . . . . . . . 59

IP Node Names screenAdministering. . . . . . . . . . . . . . . . . . 29IP Address field. . . . . . . . . . . . . . . . . 64Name field . . . . . . . . . . . . . . . . . . . 63

ISDN protocolARS Digit Analysis Table . . . . . . . . . . . . 40

Llast number dialed FNU . . . . . . . . . . . . . . 306licenses

alarm code . . . . . . . . . . . . . . . . . . . 219host server . . . . . . . . . . . . . . . . . . . 120

List Media Server Extensions screens . . . . . . . . 175List Users screen . . . . . . . . . . . . . . 138, 142Locations screen. . . . . . . . . . . . . . . . . . 64

Proxy Selection Route Pattern . . . . . . . . . . 65Proxy Selection Route Pattern field . . . . . . . 65

Logon screen . . . . . . . . . . . . . . . . .112, 113logon URL. . . . . . . . . . . . . . . . . . . . . 112

Mmalicious call trace FNU . . . . . . . . . . . . . . 306Management system access login

Edit System Properties screen. . . . . . . . . . 120Management system access password

Edit System Properties screen. . . . . . . . . . 121Media Gateway screen

Network Region field . . . . . . . . . . . . . . 65Meet Me conferencing feature . . . . . . . . . . . 27Memos task . . . . . . . . . . . . . . . . . 141, 195Miscellaneous screen . . . . . . . . . . . . . . . 293Modem screen. . . . . . . . . . . . . . . . . . . 269

Solving modem problems . . . . . . . . . . . . 270Modem Test screen . . . . . . . . . . . . . . . . 240

Troubleshooting problems. . . . . . . . . . . . 241move user . . . . . . . . . . . . . . . . . . . . . 199move user to new home . . . . . . . . . 199, 204, 214

NNetstat results screen . . . . . . . . . . . . . . . 237

active internet connections . . . . . . . . . . . 237Active UNIX domain sockets. . . . . . . . . . . 238

Netstat screen . . . . . . . . . . . . . . . . . . . 236Network Region screen

Authoritative Domain field . . . . . . . . . . . . 59Inter-region IP-IP Direct Audio . . . . . . . . . . 61Intra-region IP-IP Direct Audio . . . . . . . . . . 60Region field . . . . . . . . . . . . . . . . . . 59

Server IP Address . . . . . . . . . . . . . . . . 62Server Port field . . . . . . . . . . . . . . . . . 62

newAdd Another Media Server Extension screen . . 178Delete All Displayed Users task . . . . . . . . 173Delete Selected Users task . . . . . . . . . . 174Mark Users as Phone field . . . . . . . . . . . 109Move User on Task pull down . . . . . . . . . 141Move User on task pull down. . . . . . . . . . 197name for Converged Communication Server. . . 321Preferred Minimum Session Refresh Interval . . 104Prepend + to Calling Number field . . . . . . . 107reload configuration . . . . . . . . . . . . . . 149select free extension. . . . . . . . . . . . . . 180Select Free Extension screen . . . . . . . . . 180Trunk Group screen page 4 . . . . . . . . . . 109Trusted Certificates screens . . . . . . . . . . 284Watchers task. . . . . . . . . . . . . . . 141, 206

non-sip user as contact . . . . . . . . . . . . 146, 152Numbering-Public/Unknown Numbering screen. . . . 66

Ooff-PBX FNU . . . . . . . . . . . . . . . . . . . 305Off-PBX Station Mapping screen page 1

Application field . . . . . . . . . . . . . . . . . 68Configuration Set field . . . . . . . . . . . . . . 70Dial Prefix field . . . . . . . . . . . . . . . 69, 71Phone Number field . . . . . . . . . . . . . . . 69Station Extension field . . . . . . . . . . . . . . 68Trunk Selection field . . . . . . . . . . . . . . . 69

Off-PBX Station Mapping screen page 2Bridged Calls field . . . . . . . . . . . . . . . . 74Call Limit field . . . . . . . . . . . . . . . . . . 72Calls Allowed field . . . . . . . . . . . . . . . . 73Mapping Mode field . . . . . . . . . . . . . . . 73Station Extension field . . . . . . . . . . . . . . 72

One Touch Dial List screens . . . . . . . . . . . 168OPS extensions . . . . . . . . . . . . . . . . . .110OPTIM extensions . . . . . . . . . . . . . . . . .110

and SIP. . . . . . . . . . . . . . . . . . . . .110origination-based call flow. . . . . . . . . . . . . . 17outgoing queue. . . . . . . . . . . . . . . . . . 100

Pp-a-i . . . . . . . . . . . . . . . . . . . . . . . 297partially up . . . . . . . . . . . . . . . . . . . . 244p-asserted-identity . . . . . . . . . . . . . . . . 297password

CM password . . . . . . . . . . . . . . . . . 134logon . . . . . . . . . . . . . . . . . . . . . .113Profile Service Password . . . . . . . . . . . 125user password . . . . . . . . . . . . . . 144, 204



Index

passwords. 125, 134, 144, 204, 213, 222, 254, 255, 258, 264, 273, 279

Permissions . . . . . . . . . . . . . . . . . . . . 201permissions

add an entry . . . . . . . . . . . . . . . . . . 202allow . . . . . . . . . . . . . . . . . . . . . . 202block. . . . . . . . . . . . . . . . . . . . . . 202changing . . . . . . . . . . . . . . . . . . . . 207

Permissions screens . . . . . . . . . . . . . . . . 200Permissions task. . . . . . . . . . . . . . . . . . 141Pickup

directed FNU . . . . . . . . . . . . . . . . . . 301expanded FNU . . . . . . . . . . . . . . . . . 302

Ping resultssuccess . . . . . . . . . . . . . . . . . . . . 231unsuccessful . . . . . . . . . . . . . . . . . . 232

Ping screen . . . . . . . . . . . . . . . . . . . . 230Presence Access Policy . . . . . . . . . . . . . . 126priority call FNU . . . . . . . . . . . . . . . . . . 307procedures

add a backup schedule . . . . . . . . . . . . . 259alarms for specific server . . . . . . . . . . . . 218change a backup schedule . . . . . . . . . . . 260move all contacts . . . . . . . . . . . . . . . . 163move user . . . . . . . . . . . . . . . . . . . 199move user to another home server . . . . . . . . 214preview or restore backup data . . . . . . . . . 262remove a backup schedule . . . . . . . . . . . 260start of stop FTP . . . . . . . . . . . . . . . . 271troubleshooting modem . . . . . . . . . . . . . 241troubleshooting partially up processes . . . . . . 245

Process Status results screen . . . . . . . . . . . 246Process Status screen . . . . . . . . . . . . . . . 244Profile task . . . . . . . . . . . . . . . . . 141, 203Proxy Selection Route Pattern field

Locations screen . . . . . . . . . . . . . . . . 65publication note . . . . . . . . . . . . . . . . . . 111

Qqueue

outgoing . . . . . . . . . . . . . . . . . . . . 100

Rredirection

coverage of calls off-net . . . . . . . . . . . . . 87OPTIM failure . . . . . . . . . . . . . . . . . 102

Redundant PropertiesEdit System Properties screen. . . . . . . . . . 122

release number . . . . . . . . . . . . . . . . . . 250Reload Configuration

definition . . . . . . . . . . . . . . . . . . . . 149requirement specifications . . . . . . . . . . . . . 297

FNU requirements . . . . . . . . . . . . . . . 297

SES call processing software . . . . . . . . . 297requirements

firmware . . . . . . . . . . . . . . . . . . . . 22terminal. . . . . . . . . . . . . . . . . . . . .311

requirements for SIP . . . . . . . . . . . . . . . . 21engineering . . . . . . . . . . . . . . . . . . . 22firmware . . . . . . . . . . . . . . . . . . . . 22hardware . . . . . . . . . . . . . . . . . . . . 21related systems . . . . . . . . . . . . . . . . . 24software

software requirements . . . . . . . . . . . . 21Restore History screen . . . . . . . . . . . . . . 265Ringer Settings screens. . . . . . . . . . . . . . 170ROOF . . . . . . . . . . . . . . . . . . . . . . 102Route Pattern screen . . . . . . . . . . . . . . . . 75Route Pattern screen page 2

Secure SIP field . . . . . . . . . . . . . . . . . 75

SSAC . . . . . . . . . . . . . . . . . . . . . 308, 309Schedule Backup screen . . . . . . . . . . . . . 257

procedureadd a backup schedule . . . . . . . . . . . 259change a backup schedule . . . . . . . . . 260remove a backup schedule . . . . . . . . . 260

SCP . . . . . . . . . . . . . . . . . . . . . . . 145screens

Add Contact . . . . . . . . . . . . . . . . . 152Add Group . . . . . . . . . . . . . . . . . . 156Add Handle . . . . . . . . . . . . . . . . . . 189Add Handle in a New Group . . . . . . . . . . 193Add Host . . . . . . . . . . . . . . . . . . . 123Add Host Contact for user . . . . . . . . . . . 191Add Media Server . . . . . . . . . . . . . . . 132Add User . . . . . . . . . . . . . . . . . . . 142Alarms . . . . . . . . . . . . . . . . . . . . 217ARS Digit Analysis Table . . . . . . . . . . 30, 39Authentication File. . . . . . . . . . . . . . . 275Backup History . . . . . . . . . . . . . . . . 256Backup Logs . . . . . . . . . . . . . . . . . 261Choose Interface . . . . . . . . . . . . . . . .114Configuration Set . . . . . . . . . . . . . . 35, 45Confirm Delete User . . . . . . . . . . . . . . 216Contact Details . . . . . . . . . . . . . . . . 150Current Alarms . . . . . . . . . . . . . . . . 218Data Backup/Restore . . . . . . . . . . . . . 252Delete Contact . . . . . . . . . . . . . . . . 159Delete Group . . . . . . . . . . . . . . . . . 163Devices Menu. . . . . . . . . . . . . . . . . 167Diagnostic . . . . . . . . . . . . . . . . . . 223Dial Plan Analysis . . . . . . . . . . . . . . 30, 46Download Files . . . . . . . . . . . . . . . . 293Edit Default User Profile . . . . . . . . . . . . 130Edit Handle detail screen . . . . . . . . . . . 185



Index

Edit Host Contact . . . . . . . . . . . . . . . . 187Edit System Properties . . . . . . . . . . . . . 119Edit User Handles . . . . . . . . . . . . . . . 181Edit User Profile . . . . . . . . . . . . . . . . 203Extensions tasks . . . . . . . . . . . . . . . . 175Feature Access Code . . . . . . . . . . . . . . 51Feature Access Code page 1 . . . . . . . . . . 30Feature Related System Parameters. . . . . . . 85Feature Related System Parameters page 3 . .36, 52Feature-Related System Parameters. . . . . . . 85Firewall . . . . . . . . . . . . . . . . . . . . 277Format PC Card . . . . . . . . . . . . . . . . 266FTP . . . . . . . . . . . . . . . . . . . . . . 271Group Details. . . . . . . . . . . . . . . . . . 160Incoming Call Handling Treatment . . . . . . . . 54IP Address Mapping . . . . . . . . . . . . .29, 57IP Codec Set . . . . . . . . . . . . . . . . .29, 56IP Network Region . . . . . . . . . . . . . .29, 59IP Node Names . . . . . . . . . . . . . . .29, 63List Media Server Extensions . . . . . . . . . . 175List Users . . . . . . . . . . . . . . . . . . . 138Locations . . . . . . . . . . . . . . . . . . . 64Locations screen . . . . . . . . . . . . . . . . 31Logon . . . . . . . . . . . . . . . . . . . . . 112Media Gateway. . . . . . . . . . . . . . . .29, 65Miscellaneous . . . . . . . . . . . . . . . . . 293Modem. . . . . . . . . . . . . . . . . . . . . 269Modem Test . . . . . . . . . . . . . . . . . . 240My Contact List . . . . . . . . . . . . . . . . . 146Netstat . . . . . . . . . . . . . . . . . . . . . 236Netstat results . . . . . . . . . . . . . . . . . 237Numbering Public/Unknown Numbering . . . . . 34Numbering-Public/Unknown Numbering . . . .31, 66Off PBX Station Mapping page 2. . . . . . . . . 35Off-PBX Station Mapping page 1 . . . . . . . . 67Off-PBX Station Mapping page 2 . . . . . . . . 72One Touch Dial List . . . . . . . . . . . . . . . 168Permissions . . . . . . . . . . . . . . . . . . 200Ping . . . . . . . . . . . . . . . . . . . . . . 230Process Status . . . . . . . . . . . . . . . . . 244Process Status Results . . . . . . . . . . . . . 246Restore History . . . . . . . . . . . . . . . . . 265Ringer Settings . . . . . . . . . . . . . . . . . 170Route Pattern . . . . . . . . . . . . . . . . . 75Route Pattern screen . . . . . . . . . . . . . . 30Schedule Backup . . . . . . . . . . . . . . . . 257Search User . . . . . . . . . . . . . . . . . . 208Security . . . . . . . . . . . . . . . . . . . . 268Select User. . . . . . . . . . . . . . . . . . . 212Server . . . . . . . . . . . . . . . . . . . . . 242Server Date/Time . . . . . . . . . . . . . . . . 248Setup . . . . . . . . . . . . . . . . . . . . . 116Shutdown Server . . . . . . . . . . . . . . . . 247Signaling Group . . . . . . . . . . . . . . .32, 77SNMP Traps screen . . . . . . . . . . . . . . 221

software version. . . . . . . . . . . . . . . . 250Speed Dial List . . . . . . . . . . . . . . . . 157SSH Keys. . . . . . . . . . . . . . . . . . . 291Station . . . . . . . . . . . . . . . . . . . . . 83Status Summary . . . . . . . . . . . . . . . 242System Capacity . . . . . . . . . . . . . . 28, 84System Logs . . . . . . . . . . . . . . . . . 224System Parameters . . . . . . . . . . . . . . . 85System Parameters Customer Options page 1 . . 29System Parameters Customer Options page 2 28, 90System Parameters Customer Options page 428, 91, 93System Parameters Features page 1 . . . . . . . 33System Parameters-Call Coverage/Call Forwarding36,

87System-Parameters Customer-Options . . . . . . 88System-Parameters Customer-Options screen page 188Temp/Voltage screen S8500 . . . . . . . . . . 228Temp/Voltage screen S8500B . . . . . . . . . 228Temperature/Voltage . . . . . . . . . . . . . 228Tone and Volume Settings . . . . . . . . . . . 172Top. . . . . . . . . . . . . . . . . . . . . . .112Top-level . . . . . . . . . . . . . . . . . . . .112Traceroute . . . . . . . . . . . . . . . . . . 233Traceroute results . . . . . . . . . . . . . . . 234Tripwire. . . . . . . . . . . . . . . . . . . . 281Tripwire Commands . . . . . . . . . . . . . . 283Trunk Group . . . . . . . . . . . . . . . . . . 94Trunk Group page 1 . . . . . . . . . . . . . 33, 94Trunk Group page 2 . . . . . . . . . . 33, 102, 105Trunk Group page 3 . . . . . . . . . . . . . . . 33Trunk Group page 4 . . . . . . . . . . . . .34, 109Update Contact . . . . . . . . . . . . . . . . 151Update Group . . . . . . . . . . . . . . . . . 165Update Password . . . . . . . . . . . . . . . 213User . . . . . . . . . . . . . . . . . . . . . 138User Memos . . . . . . . . . . . . . . . . . 195View/Restore Data . . . . . . . . . . . . . . 263Watchers . . . . . . . . . . . . . . . . . . . 206

Search User screens . . . . . . . . . . . . . . . 208security

customer . . . . . . . . . . . . . . . . . . . 273files. . . . . . . . . . . . . . . . . .254, 258, 261firewall . . . . . . . . . . . . . . . . . . . . . 20issues . . . . . . . . . . . . . . . . . . . . 224log file . . . . . . . . . . . . . . . . . . . . 225log ins . . . . . . . . . . . . . . . . . . . . 291remote access . . . . . . . . . . . . . . . . .115SNMP v1/v2c . . . . . . . . . . . . . . . . . 222SNMP v3 . . . . . . . . . . . . . . . . . . . 222SNMP v3 traps . . . . . . . . . . . . . . . . 222utilities . . . . . . . . . . . . . . . . . . . . 279

security screens . . . . . . . . . . . . . . . . . 268select free extension screen. . . . . . . . . . . . 180Select User screens . . . . . . . . . . . . . . . 212Send All Calls . . . . . . . . . . . . . . . . . . 309send all calls FNU . . . . . . . . . . . . . . . . 308



Index

Server Date/Time screen . . . . . . . . . . . . . . 248Server screen . . . . . . . . . . . . . . . . . . . 242Server Status . . . . . . . . . . . . . . . . . . . 243SES call processing . . . . . . . . . . . . . . . . 297

FRC 3325 compliance . . . . . . . . . . . . . 297Session Initiated Protocol

description . . . . . . . . . . . . . . . . . . . 17glossary definition . . . . . . . . . . . . . . . 321

settings.txt file . . . . . . . . . . . . . . . . . . . 110Setup screen . . . . . . . . . . . . . . . . . . . 116Setup screens

screensSetup . . . . . . . . . . . . . . . . . . . . 115

Shutdown Server screen . . . . . . . . . . . . . . 247Signaling Group screen . . . . . . . . . . . . . . 77

Bypass If IP Threshold Exceeded field . . . . . . 80Enable Layer 3 Test field . . . . . . . . . . . . 81Far-end Domain field . . . . . . . . . . . . . . 80Far-end Listen Port field. . . . . . . . . . . . . 79Far-end Network Region field . . . . . . . . . . 79Far-end Node Name field . . . . . . . . . . . . 78Group Number field . . . . . . . . . . . . . . . 77Group Type field . . . . . . . . . . . . . . . . 77illustration . . . . . . . . . . . . . . . . . . . 77IP Audio Hairpinning field . . . . . . . . . . . . 81Near-end Listen Port field . . . . . . . . . . . . 79Transport Method field . . . . . . . . . . . . . 78

Signaling Group screen page 1Bypass If IP Threshold Exceeded field . . . . . . 80Direct IP-IP Audio Connections field . . . . . . . 81DTMF over IP field . . . . . . . . . . . . . . . 80Enable Layer 3 field. . . . . . . . . . . . . . . 81Far-end Domain field . . . . . . . . . . . . . . 80Far-end Network Region field . . . . . . . . . . 79Far-end Node Name field . . . . . . . . . . . . 78Group Number field . . . . . . . . . . . . . . . 77Group Type field . . . . . . . . . . . . . . . . 77IP Audio Hairpinning field . . . . . . . . . . . . 81Near-end Listen Port field . . . . . . . . . . . . 79Near-end Node Name field . . . . . . . . . . . 78Session Establishment Timer field . . . . . . . . 80Transport Method field . . . . . . . . . . . . . 78

SIPadministration . . . . . . . . . . . . . . . . . 27administrative screens . . . . . . . . . . . . . 37definition . . . . . . . . . . . . . . . . . . . . 17engineering notes, trunks . . . . . . . . . . . . 22integrate with Communication Manager . . . . . 18intercept treatment . . . . . . . . . . . . . . . 86requirements . . . . . . . . . . . . . . . . . . 21station screen . . . . . . . . . . . . . . . . . 83stations . . . . . . . . . . . . . . . . . 20, 24, 25

SIP as OPTIM extension . . . . . . . . . . . . . . 110SIP trunking . . . . . . . . . . . . . . . . . . . . 19SIP trunks

additions to support . . . . . . . . . . . . . . . 19administering . . . . . . . . . . . . . . . . 27, 32

SIP-related supportaccess control. . . . . . . . . . . . . . . . . . 20additions to Avaya Communication Manager . . . 19CDR . . . . . . . . . . . . . . . . . . . . . . 20stations . . . . . . . . . . . . . . . . . . . . . 20trunking. . . . . . . . . . . . . . . . . . . . . 19

SNMP Traps screen . . . . . . . . . . . . . . . 221field descriptions . . . . . . . . . . . . . . . 221

Software Version screen . . . . . . . . . . . . . 250Speed Dial List screens . . . . . . . . . . . . . . 157SSH Keys screen. . . . . . . . . . . . . . . . . 291Station screen . . . . . . . . . . . . . . . . . . . 83Station screen page 1

Type field . . . . . . . . . . . . . . . . . . . . 83stations . . . . . . . . . . . . . . . . . . 20, 24, 25Status Summary screen. . . . . . . . . . . . . . 242subdomain . . . . . . . . . . . . . . . . . . . . . 60survivable call processor . . . . . . . . . . . . . 145System Capacity screen . . . . . . . . . . . . . . 84

SIP Trunks field . . . . . . . . . . . . . . . . . 84System Logs screen . . . . . . . . . . . . . . . 224System Parameters Call Coverage / Call Forwarding screen

87System Parameters Customer Options page 4

Enhanced EC500 field . . . . . . . . . . . . . . 91System Parameters Customer Options screen . . . . 88System Parameters screen page 1

DID/Tie/ISDN/SIP Intercept Treatment field . . . . 86System Parameters screen page 2

Disable call classifier for CCRON over SIP trunks field87System Parameters-Call Coverage/Call Forwarding screen

87System-Parameters Customer-Options screen page 1 88

Maximum Off-PBX Telephones - EC500 field . . . 88Maximum Off-PBX Telephones - OPS field . . . . 88Used field . . . . . . . . . . . . . . . . . . . . 89

System-Parameters Customer-Options screen page 2Maximum Administered SIP Trunks field . . . . . 90

Ttasks

Contact List . . . . . . . . . . . . . . . . 139, 146Devices. . . . . . . . . . . . . . . . . . 140, 167Extensions . . . . . . . . . . . 140, 175, 177, 178Handles . . . . . . . . . . . . . . . . . 140, 181Memos . . . . . . . . . . . . . . . . . . 141, 195Permissions. . . . . . . . . . . . . . . . . . 141Profile . . . . . . . . . . . . . . . . . . . . 141User Profile . . . . . . . . . . . . . . . . . . 203Watchers . . . . . . . . . . . . . . . . . 141, 206

Temperature/Voltage screen . . . . . . . . . . . 228Temperature/Voltage screens



Index

S8500 . . . . . . . . . . . . . . . . . . . . . 228S8500B . . . . . . . . . . . . . . . . . . . . 228

terminal requirements . . . . . . . . . . . . . . . 311terminals

Avaya CM OPTIM . . . . . . . . . . . . . . . 311timeserving . . . . . . . . . . . . . . . . . . . . 249TLS . . . . . . . . . . . . . . . . . . . . . . . . 23TLS links

for failover . . . . . . . . . . . . . . . . . . . 23Tone and Volume Settings screens . . . . . . . . . 172Top-level screens . . . . . . . . . . . . . . . . . 112Traceroute results screen

intro . . . . . . . . . . . . . . . . . . . . . . 234success . . . . . . . . . . . . . . . . . . . . 234

Traceroute screen . . . . . . . . . . . . . . . . . 233track availability . . . . . . . . . . . . . . . . . . 155transfer to voice mail FNU . . . . . . . . . . . . . 309Tripwire Commands screen. . . . . . . . . . . . . 283Tripwire screen . . . . . . . . . . . . . . . . . . 281Troubleshooting

administering survivable call processors . . . . . 145troubleshooting

403 Screening failure . . . . . . . . . . . . . . 58call routing . . . . . . . . . . . . . . . . . . . 58disabling connection to Communication Manager . 134domain name incorrect, can’t get license . . . . . 120modem problems . . . . . . . . . . . . . . . . 241modems . . . . . . . . . . . . . . . . . . . . 270no license registrations . . . . . . . . . . . . . 120phones don’t work correctly . . . . . . . . . . . 134unblocked watchers. . . . . . . . . . . . . . . 200version checking . . . . . . . . . . . . . . . . 250

Trunk Group screenACA Assignment field . . . . . . . . . . . . . . 105Auth Code field . . . . . . . . . . . . . . . . . 101Busy Threshold field . . . . . . . . . . . . . . 99CDR Reports field . . . . . . . . . . . . . . . 95COR field . . . . . . . . . . . . . . . . . . . 96Dial Access field . . . . . . . . . . . . . . . . 98Digital Loss Group field . . . . . . . . . . 102, 103Direction field. . . . . . . . . . . . . . . . . . 97Group Name field . . . . . . . . . . . . . . . . 96Group Number field . . . . . . . . . . . . . . . 94Group Type field . . . . . . . . . . . . . . . . 95Maintenance Tests field . . . . . . . . . . . . . 106Measured field . . . . . . . . . . . . . . . . . 106Night Service field . . . . . . . . . . . . . . . 99Number of Members field . . . . . . . . . . . . 101Numbering Format field . . . . . . . . . . . . . 107Outgoing Display field . . . . . . . . . . . . . . 98page 1 illustration . . . . . . . . . . . . . . . . 94page 2 illustration . . . . . . . . . . . . . . . . 105Queue Length field . . . . . . . . . . . . . . . 100Replace Unavailable Numbers field . . . . . . . 107Service Type field. . . . . . . . . . . . . . . . 100

Signaling Group field . . . . . . . . . . . . . 101TAC field . . . . . . . . . . . . . . . . . . . . 97TN field . . . . . . . . . . . . . . . . . . . . . 97Trunk Hunt field . . . . . . . . . . . . . . 102, 103

Trunk Group screen page 1 . . . . . . . . . . . . . 94Auth Code field . . . . . . . . . . . . . . . . 101Busy Threshold field . . . . . . . . . . . . . . . 99CDR Reports field . . . . . . . . . . . . . . . . 95COR field . . . . . . . . . . . . . . . . . . . . 96Dial Access field. . . . . . . . . . . . . . . . . 98Direction field . . . . . . . . . . . . . . . . . . 98Group Name field . . . . . . . . . . . . . . . . 96Group Number field . . . . . . . . . . . . . . . 94Group Type field . . . . . . . . . . . . . . . . 95Night Service field . . . . . . . . . . . . . . . . 99Number of Members field . . . . . . . . . . . 101Outgoing Display field . . . . . . . . . . . . . . 98Queue Length field . . . . . . . . . . . . . . 100Service Type field . . . . . . . . . . . . . . . 100Signaling Group field . . . . . . . . . . . . . 101TAC field . . . . . . . . . . . . . . . . . . . . 97TN field . . . . . . . . . . . . . . . . . . . . . 97

Trunk Group screen page 2 . . . . . . . . . . . . 105Digital Loss Group field . . . . . . . . . . . . 103Preferred Minimum Session Refresh Interval field 104Redirect on OPTIM failure field . . . . . . . . . 102Unicode Name field . . . . . . . . . . . . . . 102

Trunk Group screen page 3ACA Assignment field . . . . . . . . . . . . . 105Maintenance Tests field . . . . . . . . . . . . 106Measured field . . . . . . . . . . . . . . . . 106Numbering Format field . . . . . . . . . . . . 107Replace Unavailable Numbers field. . . . . . . 107

Trunk Group screen page 4Mark Users as Phone field . . . . . . . . . . . 109

Trunk Group screens . . . . . . . . . . . . . . . . 94trunk groups

displaying capacities. . . . . . . . . . . . . . . 84trusted certificates . . . . . . . . . . . . . . 284, 285

UUnicode . . . . . . . . . . . . . . . . . . . . . 102Update Contact screens . . . . . . . . . . . . . 151Update Group command

Group Details screen . . . . . . . . . . . . . 162Update Group screens . . . . . . . . . . . . . . 165Update Password screens . . . . . . . . . . . . 213User Memos screen . . . . . . . . . . . . . . . 195User Memos screens . . . . . . . . . . . . . . . 195User screens . . . . . . . . . . . . . . . . . . . 138

Vversion



Index

BIOS. . . . . . . . . . . . . . . . . . . . . . 251SAMP or RSA . . . . . . . . . . . . . . . . . 251SES software. . . . . . . . . . . . . . . . . . 250SNMP . . . . . . . . . . . . . . . . . . . . . 222software . . . . . . . . . . . . . . . . . . . . 250software release . . . . . . . . . . . . . . . . 251

View/Restore Data screen . . . . . . . . . . . . . 263visiting user . . . . . . . . . . . . . . . . . 36, 52, 53

WW call flow. . . . . . . . . . . . . . . . . . . . . 17Watchers task . . . . . . . . . . . . . . . . 141, 206whisper page activation . . . . . . . . . . . . . . 310

administering sip enablement services on the avaya s8300 ... · contents issue 1.0 january 2008 1...

Documents