You are on page 1of 24

NOTICE The information contained in this document is believed to be accurate in all respects but is not warranted by Mitel Networks

s Corporation (MITEL ). The information is subject to change without notice and should not be construed in any way as a commitment by Mitel or any of its affiliates or subsidiaries. Mitel and its affiliates and subsidiaries assume no responsibility for any errors or omissions in this document. Revisions of this document or new editions of it may be issued to incorporate such changes. No part of this document can be reproduced or transmitted in any form or by any means electronic or mechanical - for any purpose without written permission from Mitel Networks Corporation.

TRADEMARKS Mitel is a trademark of Mitel Networks Corporation. Windows and Microsoft are trademarks of Microsoft Corporation. Other product names mentioned in this document may be trademarks of their respective companies and are hereby acknowledged.

Mitel Technical Configuration Notes Configure the Mitel 3300 ICP for use with the Cisco 7960 July 2009, 09-5159-00052_2

, Trademark of Mitel Networks Corporation Copyright 2009, Mitel Networks Corporation All rights reserved

ii

Table of Contents

OVERVIEW ............................................................................................................... 1
Interop History.................................................................................................................... 1 Interop Status .................................................................................................................... 1 Software & Hardware Setup ............................................................................................... 1 Tested Features ................................................................................................................. 2 Device Limitations .............................................................................................................. 2 Device Recommendations ................................................................................................. 3 Network Topology .............................................................................................................. 4

CONFIGURATION NOTES ....................................................................................... 5


3300 ICP Configuration Notes ............................................................................................ 5
Network Requirements .................................................................................................................... 5 Assumptions for the 3300 ICP Programming .................................................................................. 5 Licensing and Option Selection SIP Licensing ............................................................................ 6 Multiline IP Set Configuration .......................................................................................................... 7 Class of Service Assignment .......................................................................................................... 7 SIP Device Capabilities Assignment ............................................................................................... 9 Station Service Assignment .......................................................................................................... 11 Multiline Set Key Assignment ........................................................................................................ 12 Reroute Assignment ...................................................................................................................... 13

CISCO 7960 SIP PHONE SETUP NOTES .............................................................. 15


Required Files .................................................................................................................. 15
XMLDefault.cnf.xml ....................................................................................................................... 16 SIPDefault.cnf ............................................................................................................................... 17 SIP<MAC address>.cnf ................................................................................................................. 19 dialplan.xml ................................................................................................................................... 20

iii

Overview
This document provides a reference to Mitel Authorized Solutions providers for configuring the Mitel 3300 ICP to host the Cisco 7960 Phone. The different devices can be configured in various configurations depending on your VoIP solution. This document covers a basic setup with required option setup.

Interop History
Version 1 2 Date April 23, 2009 July 20, 2009 Reason Initial Interop with Mitel 3300 9.0 UR2 and Cisco 7960 P0S3-08-1100 Interop with Mitel 3300 10.0.010_2 UR2 and Cisco 7960 P0S-8-12-0

Interop Status
The Interop of Cisco 7960 has been given a Certification status. This device will be included in the SIP CoE Reference Guide. The status the Cisco 7960 achieved is: The most common certification which means the device/service has been tested and/or validated by the Mitel SIP CoE team. Product support will provide all necessary support related to the interop, but issues unique or specific to the 3rd party will be referred to the 3rd party as appropriate.

Software & Hardware Setup


This was the test setup to generate a basic SIP call between the Cisco 7960 SIP device and the 3300 ICP.

Manufacturer Mitel Mitel Mitel Mitel Cisco

Variant 3300 ICP Mxe Platform MBG - Teleworker 5340, 5212 SIP Phones 5340, 5215 IP Phones 7960 IP Phone

Software Version 10.0.010_2 5.0.13.0


R7.1.01.03.00.26, R7.2.07.02.00.03

Minet P0S-8-12-00

Mitel Technical Configuration Notes for Cisco 7960

Tested Features
This is an overview of the features tested during the Interop test cycle and not a detailed view of the test cases. Please see the SIP Line Side Interoperability Test Pans for detailed test cases.

Feature Basic Call DTMF Signal Call Hold Call Transfer Call Forward Conference Redial MWI Dynamic Extension Resiliency T.38 Fax Video Teleworker

Feature Description Making and receiving a call Sending DTMF after call setup (i.e. mailbox password) Putting a call on hold Transferring a call to another destination Forwarding a call to another destination Conferencing multiple calls together Last Number Redial Message Waiting Indication Personal Ring Group configuration Basic calls through a Secondary SIP proxy Fax Messages Video Capabilities Mitel remote connectivity with Teleworker

Issues

N/S N/S

- No issues found

- Issues found, cannot recommend to use

- Issues found

Device Limitations
This is a list of problems or not supported features when the Cisco 7960 SIP device is connected to the Mitel 3300.

Feature Message Waiting Indication (MWI)

Problem Description The Cisco 7960 does not support MWI since it does not send out SUBSCRIBE message. Recommendation: At this time, it is impossible to configure the phone in such a manner that the MWI will work.

Call Forwarding

The Cisco 7960 only has the option on the phone to do Call Forwarding Always. Call Forwarding when Busy or No Answer can not be enabled using the device features. Recommendation: Use the call rerouting forms for all call forwarding purposes. See the Reroute Assignment section below.

Teleworker

The MWI will not work while the Cisco 7960 is connected to the Teleworker Server. Recommendation: At this time, it is not possible to configure the phone in such a manner that the MWI will work.

Teleworker

No MWI suppported. Recommendation: Contact Mitel support for further information.

Call Conferencing

If the phone is in System Based mode, as configured in the Sip Device Capabilities, the Conference initiation could be tricky: you need to press Hold+Transfer (for next call)+ dial FAC. Recommendation: Use the device is Device Based Mode.

Device Recommendations
The Cisco 7960 is recommended for deployment with Device Based In-Call Features enabled. See Sip Device Capabilities Assignment form below for more information.

Mitel Technical Configuration Notes for Cisco 7960

Network Topology
This diagram shows how the testing network is configured for reference.

Configuration Notes
This section is a description of how the SIP Interop was configured. These notes should give a guideline how a device can be configured in a customer environment and how the Cisco 7960 was configured in our test environment. We recommend that the Cisco 7960 is configured in Device Mode. You will configure the Device mode in the SIP Device Capabilities Form as described in this section. Disclaimer: Although Mitel has attempted to setup the interop testing facility as closely as possible to a customer premise environment, implementation setup could be different onsite. YOU MUST EXERCISE YOUR OWN DUE DILIGENCE IN REVIEWING, planning, implementing, and testing a customer configuration.

3300 ICP Configuration Notes


The following steps show how to program a 3300 ICP to connect with the Cisco 7960Phone.

Network Requirements
There must be adequate bandwidth to support the voice over IP. As a guide, the Ethernet bandwidth is approx 85 Kb/s per G.711 voice session and 29 Kb/s per G.729 voice session (assumes 20ms packetization). As an example, for 20 simultaneous SIP sessions, the Ethernet bandwidth consumption will be approx 1.7 Mb/s for G.711 and 0.6Mb/s. Almost all Enterprise LAN networks can support this level of traffic without any special engineering. Please refer to the 3300 Engineering guidelines for further information. For high quality voice, the network connectivity must support a voice-quality grade of service (packet loss <1%, jitter < 30ms, one-way delay < 80ms).

Assumptions for the 3300 ICP Programming


The SIP signaling connection uses UDP on Port 5060.

Mitel Technical Configuration Notes for Cisco 7960

Licensing and Option Selection SIP Licensing


Ensure that the 3300 ICP is equipped with enough SIP Device licenses for the connection of SIP end points. This can be verified within the License and Option Selection form.

Figure 1 License and Option Selection form

Multiline IP Set Configuration


On the Mitel 3300 ICP, a SIP device type can be programmed either in the User Configuration form or the Multiline IP Set Configuration form and it should be programmed as a Generic SIP Phone. Enterprise Manager can also be used to provision where this application is installed. The User PIN is the SIP authentication password and the Number is the Directory Number (DN a telephone number). The Number and User PIN must match the information in the Cisco 7960 phones configuration XML file. All other field names should be programmed according to the site requirements or left at default.

Figure 2 Multiline IP Set Configuration form

Class of Service Assignment


The Class of Service Options Assignment form is used to create or edit a Class of Service and specify its options. Classes of Service, identified by Class of Service numbers, are referenced by the Station Service Assignment form for the SIP devices. Many different options may be required for your site deployment, but these are the options that are required to be changed from the default for a Generic SIP Device to work with the 3300 ICP. HCI/CTI/TAPI Call Control Allowed set to Yes HCI/CTI/TAPI Monitor Allowed set to Yes Message Waiting set to Yes

Mitel Technical Configuration Notes for Cisco 7960 Conference Call set to Yes Public Network Access via DPNSS set to Yes Auto Campon Timer is blanked (no value)

Figure 3 Class of Service Options Assignment form

SIP Device Capabilities Assignment


This form provides configuration options that can be applied to various types of SIP devices. The association between the SIP device and the form is similar to how the Class of Service options work. The SIP Device Capabilities number provides a SIP profile that can be applied to particular SIP devices to allow for alternate capabilities as recommended through the Mitel interop process. In the Device Capabilities form, program a SIP Device Capabilities Number for the Cisco 7960 Phone device. Ensure that Replace System based with Device based In-Call Feature is set to Yes.

Mitel Technical Configuration Notes for Cisco 7960

Figure 4 SIP Device Capabilities Assignment form

10

Station Service Assignment


Use the Station Service Assignment form to assign the previously configured Class of Service and SIP Device Capability number to each of the Cisco 7960 phones in the 3300. This form utilizes Range Programming. Select the Cisco 7960 phone device number then select Change. Enter the previously configured SIP Device Capability number and Class of Service for Day, Night 1 & Night 2.

Figure 5 Station Service Assignment form

Mitel Technical Configuration Notes for Cisco 7960

Multiline Set Key Assignment


You use the Multiline Set Key Assignment form to assign the line type, ring type, and directory number to each line selected on the Cisco 7960 device. The Cisco 7960 can be programmed with 6 lines but only 2 were programmed for testing.

Figure 6 Multiline Set Key Assignment form

12

Reroute Assignment
Mitel recommends that call forwarding is programmed using the Call rerouting forms of the 3300. Call forwarding programmed from the Cisco 7960 has also been tested but we suggest that administrators use Call Rerouting. Call Rerouting is configured at the system to allow for extensions to forward on different conditions to different extensions, i.e. forward to voicemail when no answer. The following is a description how to configure call rerouting and does not necessarily show how this Cisco 7960 was programmed. Program the Call Rerouting First Alternative Assignment form with the destination of the call forwarding and the options (Normal, This, Last). Please see the 3300 help files for more info. There is also a Call Rerouting Second Alternative Assignment form for more complicated forwarding needs.

Figure 7 Call Rerouting First Alternative Assignment

If any Call Forwarding Always is required then the Call Rerouting Always Alternative Assignment form would need to be programmed.

Mitel Technical Configuration Notes for Cisco 7960

Figure 8 Call Rerouting Assignment form

Use the Alternative Numbers from the previous forms and fill out the Call Rerouting Assignment form for the Cisco 7960 programmed extension.

14

Cisco 7960 SIP Phone Setup Notes


The following steps show how to program the Cisco 7960 SIP Phone to interconnect with the 3300 ICP A Cisco IP 7960 was used and the firmware updated to Ciscos SIP load P0S3-8-12-00. Cisco provides a document called Converting a Cisco 7940/7960 SCCP Phone to a SIP Phone and the Reverse Process that provides the information on how to convert a Cisco SCCP (skinny) protocol set to SIP. http://www.cisco.com/en/US/products/hw/phones/ps379/products_tech_note09186a0080094584. shtml

Briefly, to enable Cisco 7960 phone on 3300 ICP, the following steps need to be completed: Create a new user on 3300 ICP with the properties mentioned above Download new firmware for the Cisco phone and extract it to a folder on TFTP server Update accordingly configuration files SIP<MAC address>.cnf, XMLDefault.cnf.xml, SIPDefault.cnf, dialplan.xml and copy them to the folder on TFTP server Reboot Cisco 7960 phone

Required Files
The files extracted from the Cisco software load ZIP file should include the following files (file names will change for different loads and should be checked for accuracy when extracted): Os79xx.txt P0S3-8-12-00.bin P0S3-8-12-00.sbn P0S3-8-12-00.loads P0S3-8-12-00.sb2 Four more files are required in the TFTP server to make Cisco 7960 phone operational: XMLDefault.cnf.xml SIP<MAC address>.cnf (e.g. SIP0018187B02C9.cnf where 0018187B02C9 is the MAC address of the set). SIPDefault.cnf dialplan.xml

Mitel Technical Configuration Notes for Cisco 7960 NOTE: To edit SIP<MAC address>.cnf and SIPDefault.cnf, keep copies of these files in TXT format and then rename them to .cnf. NOTE: Always check if the settings in XML and CNF were parsed correctly during the phones reboot process. To verify this, on the phone: Press Settings button Navigate to Status menu. Press Select softkey. Navigate to Status Messages menu. Press Select softkey

Make sure that there is no Error Parsing message(s) listed. More details for these files are following. Those file names are case sensitive.

XMLDefault.cnf.xml
File name XMLDefault.cnf.xml is a case sensitive (Be aware that sometimes phone searches the same file named xmlDefault.cnf.xml. So, you can two identical files on TFTP named slightly differently). The file is downloaded to SIP phones via TFTP server. The file includes the firmware version, which you currently use. <Default> <callManagerGroup> <members> <member priority="0"> <callManager> <ports> <ethernetPhonePort>2000</ethernetPhonePort> <mgcpPorts> <listen>2427</listen> <keepAlive>2428</keepAlive> </mgcpPorts> </ports> <processNodeName></processNodeName> </callManager> </member> </members> </callManagerGroup> <loadInformation8 model="IP Phone 7940">P0S3-8-12-00</loadInformation8> <loadInformation7 model="IP Phone 7960">P0S3-8-12-00</loadInformation7> <authenticationURL></authenticationURL> <directoryURL></directoryURL> <idleURL></idleURL> <informationURL></informationURL> <messagesURL></messagesURL>

16

<servicesURL></servicesURL> </Default> NOTE: Load information has to be changed to desired version (e.g. P0S3-8-12-00).

SIPDefault.cnf
The file is also downloaded to Cisco 7960 telephones via TFTP server. If you have configured and loaded the settings like proxy_backup or proxy_emergency and then want to disable or revert them later on, it is insufficient to quote the line(s) in file SIPDefault.cnf and reboot the phone. The previously used settings will continue affecting phones configuration. To really clean these settings from the phone, leave the variable in the file, but change its value to a null value "" "" or "UNPROVISIONED". For example, proxy_backup: "UNPROVISIONED" If both the variable and its value are removed, the phone will use the setting for that variable that it has stored in Flash memory.

; sip default configuration file #Image Version image_version:P0S3-8-12-00; #Proxy server IP or DNS address proxy1_address: 192.168.101.21; proxy_register: 1; The phone must register with a proxy server during initialization. After a phone has initialized and registered with a proxy server, changing the value of this parameter to 0 will unregister the phone from the proxy server. To reinitiate a registration, change the value of this parameter back to 1 #Default Codec. Other choice could be "g711alaw" and "g729a" preferred_codec :g711ulaw; #Optional. Whether to detect and generate the out-of-band signaling #"none" Do not generate DTMF digits out-of-band. #"avt" If requested by the remote side, generate DTMF digits out-of-band (and disable in-band DTMF signaling), otherwise, do not generate DTMF digits out-of-band #"avt_always" Always generate DTMF digits out-of-band. This option disables in-band DTMF signaling. dtmf_outofband:avt; default value - avt

#Registration expiration. Default value is 3600. timer_register_expires :300 ;

Mitel Technical Configuration Notes for Cisco 7960 #Voicemail pilot number to be dialed when Messages button is pressed messages_uri: 6900; #Dialplan dial_template: dialplan ; #NOTE: #If you have enabled the settings below and then want to revert them later on, it is insufficient to disable the line(s) in this file and reboot the phone. #If your system has been set up to have the phones retrieve their SIP parameters via a TFTP server, #you will need to edit the configuration file in which a parameter is defined to delete the parameter. #When deleting a parameter, leave the variable in the file, but change its value to a null value "" "" or "UNPROVISIONED". For example, proxy_backup: "UNPROVISIONED" #If both the variable and its value are removed, the phone will use the setting for that variable that it has stored in Flash memory. #Next 3 lines need to be included if you want to change the source port. NAT must be enabled. You can also enable this when configuring Teleworker MBG. #nat_enable:1; Use 1 to enable NAT. Default is 0. #nat_address:66.46.196.196; The WAN IP address of the NAT or firewall server. (For the test sake, IP address of the Cisco phone was set here as displayed) #voip_control_port:5060; The UDP port used for SIP messages. Default is 5060. All SIP REQUESTS use voip_control_port as the UDP source port when nat_enable = 1. Valid values are 1025 to 65535. #Try to use a Secondary SIP proxy. With 3300 ICP 10.0.0.10, the registration was successful but Cisco phone remains unreachable. Outgoing calls are possible (with about 60 seconds dialing delay) #proxy_backup:192.168.101.20; IP address only! #proxy_backup_port:5060

For quick phones reboot, press simultaneously and hold buttons *, 6 and Settings until Headset, Mute and Speaker buttons start flashing. To unlock the phones menus: Press Settings button Navigate to Unlock Config and press Select softkey (Alternatively, you can press Settings button and then press9) Enter the password (default is cisco) and press Accept sofkey

In order to perform a factory reset of a phone if the password is set, complete these steps: 1. Unplug the power cable from the phone, and then plug in the cable again.

18

The phone begins its power up cycle. 2. Immediately press and hold # and while the Headset, Mute, and Speaker buttons begin to flash in sequence, release #. The Headset, Mute, and Speaker buttons flash in sequence in order to indicate that the phone waits for you to enter the key sequence for the reset. 3. Press 123456789*0# within 60 seconds after the Headset, Mute, and Speaker buttons begin to flash. If you repeat a key within the sequence, for example, if you press 1223456789*0#, the sequence is still accepted and the phone resets. If you do not complete this key sequence or do not press any keys, after 60 seconds, the Headset, Mute, and Speaker buttons no longer flash, and the phone continues with its normal startup process. The phone does not reset. If you enter an invalid key sequence, the buttons no longer flash, and the phone continues with its normal startup process. The phone does not reset. If you enter this key sequence correctly, the phone displays this prompt: Keep network cfg? 1 = yes 2 = no 4. In order to maintain the current network configuration settings for the phone when the phone resets, press 1. In order to reset the network configuration settings when the phone resets, press 2. If you press another key or do not respond to this prompt within 60 seconds, the phone continues with its normal startup process and does not reset. Otherwise, the phone goes through the factory reset process.

SIP<MAC address>.cnf
The file name is case sensitive and must include the MAC address of the set. The file contains set specific information and will only be downloaded by the set with the correct MAC address. In this example the MAC address of the set is 001A2F63D80E so the file name is SIP001A2F63D80E.cnf. The example of the working SIP001A2F63D80E.cnf file: ; phone-specific configuration file sample # Line 1 ; Line 1 phone number line1_name : 6308 ; Line 1 name for authentication with proxy server line1_authname : 6308 ; Line 1 authentication name password

Mitel Technical Configuration Notes for Cisco 7960 line1_password : 6308 # Phone Label (Text in top right corner of the screen) phone_label: "Mitel 3300 ICP"

dialplan.xml
The Cisco 7960 series telephones have the ability to download the dial plan via TFTP along with the other settings mentioned. To download the dial plan create the dialplan.xml file in an ASCII editor such as Notepad. Add the following line to the file SIPDefault.cnf to refer the dial plan. dial_template: dialplan ; The example of dialplan.xml file <DIALTEMPLATE> <TEMPLATE MATCH="#..." Timeout="5" User="Phone" /> <TEMPLATE MATCH="*" Timeout="5" User="Phone" /> </DIALTEMPLATE> This dial plan allows placing the call immediately after pressing a pound sign button (#) at the end of dialed number.

20

You might also like