Summary of the content on the page No. 1
Avaya Solution & Interoperability Test Lab
Configuring SIP IP Telephony Using Avaya Converged
Communications Server, Avaya Communication Manager,
and Cisco 7940/7960 SIP Telephones – Issue 1.0
Abstract
These Application Notes describe the configuration steps required to connect Cisco 7940/7960
SIP telephones to a SIP infrastructure consisting of the Avaya Converged Communications
Server and Avaya S8300 Media Server with G700 Media Gateway. Also described i
Summary of the content on the page No. 2
1. Introduction 1.1. Background With the introduction of the SIP protocol standard that supports telephony as well as a wide range of other communication modes, there is a much broader range of SIP telephones available to customers. This allows customers to replace their existing telephony infrastructure with Avaya servers and re-use their existing telephones. In addition, Avaya Communication Manager running on Avaya Media Servers and Gateways has the capability to extend advanced te
Summary of the content on the page No. 3
Avaya S8300 Media Server 10.1.1.0/24 G700 Media Gateway IA770 INTUITY Messaging System .103 .10 Web Browser Avaya TFTP Server P333T Modular Stackable Switch .5 .50 Avaya Converged Communication Server (CCS) Avaya 4602 SIP Phones .170-172 Cisco 7940 and 7960 SIP Telephones Figure 1: Avaya SIP Test Configuration with Cisco 7940/7960 SIP Phones Configuration files, Telnet Administration mechanisms Administration levels Administrator File transfer server TFTP Error log
Summary of the content on the page No. 4
2. Equipment and Software Validated The following equipment and software were used in the configuration shown in Table 2. Be sure to use the software version combination shown when following these Application Notes. Equipment Software Avaya Converged Communication Server 2.0 Avaya P333T Modular Stackable Switch 3.12.1 Avaya S8300 Media Server with G700 Media Gateway Communication Manager 2.0.1 Avaya IA770 INTUITY®AUDIX™ Messaging N1.2-5.2 System Cisco 7940/7960 SIP Telephones POS3-0
Summary of the content on the page No. 5
Telephone + CCS + Telephone + Communication CCS No. FEATURE Manager/OPS COMMENTS Call Hold 1 YES YES Consultation Hold 2 YES YES Music On Hold Available in OPS (future release) 3 NO NO 4 Unattended Transfer YES YES 5 Attended Transfer YES YES Transfer - IM 6 NO NO Call Forward Unconditional 7 YES YES Call Forward Busy OPS 8 NO YES 9 Call Forward No Answer NO YES OPS 3-way conference - 3rd party added by user 10 YES YES 3-way conference - 3rd party calls and is 11 NO NO joined by user 12
Summary of the content on the page No. 6
3.2. Message Waiting Indicator (MWI) With the Outboard Proxy SIP extended feature set, a SIP telephone that supports IETF RFC 3265 and MWI Draft 4 (Subscribe/Notify method) will illuminate/extinguish its MWI lamp when voice messages are left/read for that extension. Since the Cisco 7940/7960 SIP phones support only the unsolicited Notify method for MWI, this feature is not currently supported in Communication Manager. 4. Configuring for the Basic Feature Set 4.1. Administer Users on th
Summary of the content on the page No. 7
Steps Description 2. The Converged Communications Server administration web interface will be displayed. Expand the Users link on the left side of the page and click on Add. FAS; Reviewed: Solution & Interoperability Test Lab Application Notes 7 of 35 WCH 10/22/2004 ©2004 Avaya Inc. All Rights Reserved. Cisco7960SIP.doc
Summary of the content on the page No. 8
Steps Description 3. The Add User page will be displayed. Fill in the required fields (indicated by *). In the screen below, the user corresponding to a Cisco 7960 SIP telephone is being added. Enter the extension number in the Handle and User ID fields. The Host field should be set to the name of the Converged Communications Server Home or Home/Edge server to which the user’s phone will register. In this configuration, there is only one Home/Edge Converged Communications Server, so
Summary of the content on the page No. 9
Steps Description 4. The confirmation page will be displayed. Click Continue. Repeat Steps 2-4 for each user to be supported. 5. To apply the administration in the above steps, click on Update on the left side of the page. This link appears on the current page whenever updates are outstanding, and can be used at any time to save the administration performed to that point. FAS; Reviewed: Solution & Interoperability Test Lab Application Notes 9 of 35 WCH 10/22/2004 ©2004 Avaya
Summary of the content on the page No. 10
4.2. Configure the Cisco 7940/7960 SIP Telephone Cisco 7940/7960 SIP telephones can be configured using two methods: 1. Configuration files downloaded from a TFTP server specified via DHCP at boot time. Two such files are installed on the TFTP server: a default configuration file containing parameter settings that apply to all phones (SIPDefault.cnf), and a phone-specific configuration file containing settings applicable only to that phone (SIP.cnf, where is t
Summary of the content on the page No. 11
Steps Description 1. Edit the default and phone-specific configuration file(s). The table below shows the relationship between the parameters that must be configured for the phone and those administered in the Converged Communications Server for a telephony user. A sample value is shown for the configuration in Figure 1. Parameter names have the form ObjectNameXParamName, where “X” refers to the line appearance number to which the parameter applies (1-2 for the 7940 and 1-6 for the 79
Summary of the content on the page No. 12
Steps Description 2. Reboot the phone. If TFTP support has been properly configured, the phone will download the default and specific configuration files, and register with the Avaya Converged Communications Server. Registration can be verified by the absence of an “X” near the phone icon for the line appearance, as shown below. Registered Unregistered For basic feature set operation, the dial plan can be specified using: 1. Address maps in the Avaya Converged Communications Ser
Summary of the content on the page No. 13
# SIP Default Generic Configuration File # Image Version image_version: P0S3-06-3-00 # Proxy Server proxy1_address: "10.1.1.50" ; Can be dotted IP or FQDN proxy2_address: "" ; Can be dotted IP or FQDN proxy3_address: "" ; Can be dotted IP or FQDN proxy4_address: "" ; Can be dotted IP or FQDN proxy5_address: "" ; Can be dotted IP or FQDN proxy6_address: "" ; Can be dotted IP or FQDN # Proxy Server Port (default - 5060) proxy1_port: 5060 proxy2_port: 5060 proxy3_port
Summary of the content on the page No. 14
# SIP Configuration Generic File # Line 1 appearance line1_name: 23071 # Line 1 Registration Authentication line1_authname: "23071" # Line 1 Registration Password line1_password: "hello123" # Line 2 appearance line2_name: "" # Line 2 Registration Authentication line2_authname: "" # Line 2 Registration Password line2_password: "" ####### New Parameters added in Release 2.0 ####### # All user_parameters have been removed # Phone Label (Text desired to be
Summary of the content on the page No. 15
5. Configuring for the Extended Feature Set In addition to the steps outlined in Section 4, the following additional administration steps are required to support the extended feature set on the Cisco 7940/7960 SIP telephones: 1. On Communication Manager, define stations corresponding to those specified on the Avaya Converged Communications Server, off-PBX station mappings to route call requests involving those stations to the Avaya Converged Communications Server, and off-PBX Feature Nam
Summary of the content on the page No. 16
(NOTE: You must logoff & login to effect the permission changes.) 5.1.2. Define Outboard Proxy SIP Feature Access Codes (FACs) In order to define the FNEs for the Outboard Proxy SIP features listed in Table 3, a FAC must also be specified for each feature. Use the change dialplan analysis command to specify the format of the FAC, and then the change feature-access-codes command to define the codes themselves. change dialplan analysis Page
Summary of the content on the page No. 17
change feature-access-codes Page 2 of 6 FEATURE ACCESS CODE (FAC) Data Origination Access Code: Data Privacy Access Code: Directed Call Pickup Access Code: 607 Emergency Access to Attendant Access Code: Enhanced EC500 Activation: Deactivation: Extended Call Fwd Activate Busy D/A All: Deactivation: Extended Gr
Summary of the content on the page No. 18
5.1.3. Define Feature Name Extensions (FNEs) Now the FNEs can be defined using the change off-pbx-telephone feature-name-extensions command. It is recommended that a uniform format for these extensions be used as shown (e.g., all beginning with 70xxx), so that the definition of the address map in the Avaya Converged Communications Server later (Section 5.2) will be as simple as possible. change off-pbx-telephone feature-name-extensions Page 1 of 1 EXTENSIONS TO C
Summary of the content on the page No. 19
5.1.5. Add stations Use the add-station command to add a station for each SIP phone to be supported. Use 4620 for the Station Type and be sure to include the Coverage Path for voice messaging if it is available. Use the COS value specified in the previous section. The Name field is optional and is shown on the display of the destination phone when making calls. Use default values for the other fields on Page 1. Note: For Outboard Proxy SIP configuration, the station extension must be
Summary of the content on the page No. 20
For most applications, the default values can be used for Page 2. add station 24071 Page 2 of 4 STATION FEATURE OPTIONS LWC Reception: spe Auto Select Any Idle Appearance? n LWC Activation? y Coverage Msg Retrieval? y LWC Log External Calls? n Auto Answer: none CDR Privacy? n
