Cisco 7960/7940 Phones€¦ · 7 7 1 V a q u e r o s S u n n y v a l e , C a l i f o r n i a , U S...

Z u l t y s , I n c . 7 7 1 V a q u e r o s S u n n y v a l e , C a l i f o r n i a , U S A 9 4 0 8 5 w w w . z u l t y s . c o m

Author: Zultys Technical Support Department

This document discuses using the MXadministrator to create generic configuration files for Cisco 7940 and 7960 phones. The Cisco Device profile is by design to create configuration files for each device that will have all devices look exactly the same. The default profile will work out of the box, no customization is required. For highly customized devices you may need to create your own set of configuration files, following “Cisco_Provision_Using_Custom_Files” as provided from Zultys Technical Support. All Cisco phones MUST previously be conferred to SIP before attempting to configure for use on the MX. Zultys technical support cannot provide the firmware or conversion process. This document covers only the 7940/7960 phones and up to Cisco firmware version 8.12. This document was written for Cisco Firmware version 4.x to 7.x, newer cisco firmware requires a completely different file set, and is not covered by this document. Please contact your Cisco support center for additional information on configuring and building the proper files for version 8.x of the Cisco firmware. Zultys technical support recommends 7.x firmware for all local Cisco phones, due to Cisco firmware issues remote phones must use version 8.x.

April 14

Cisco 7960/7940 Phones

Z

Technical Publications

Cisco 7940/7960 (0000000010) / Revision 9 April 15, 2014

© 2014 Zultys, Inc. No reproduction of distribution without permission of 14


No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Zultys, Inc. Under the law, “reproducing” includes translating the document’s content into another language or format.

Information in this document is subject to change without notice. Every effort has been made to ensure that the information in this document is accurate. Zultys, Inc. is not responsible for printing or clerical errors. Any troubleshooting suggestions or suggestions for resolving common issues included in this document are recommendations made by Zultys Technical Support team and are not guaranteed to resolve every issue the reader may encounter.




1 Contents

2 USE WITH MXIE ...................................................................................................................... 4

3 INTRAOPERATIVE NOTES ..................................................................................................... 4

3.1 PARKING .................................................................................................................................. 4 3.2 TRANSFER ................................................................................................................................ 4 3.3 PAGING.................................................................................................................................... 4 3.4 BLF ......................................................................................................................................... 4

4 ADDING A NEW DEVICE ........................................................................................................ 4

4.1 USING THE DEFAULT CISCO PROFILE ........................................................................................ 6 4.2 DEFAULT CISCO PROFILE:......................................................................................................... 6

5 CUSTOM PROFILE OPTIONS ................................................................................................. 7

5.1 1.6.1 LOGO (OPTIONAL) ........................................................................................................... 7 5.2 1.6.2 DIRECTORY (OPTIONAL) .................................................................................................. 7 5.3 1.6.3 TELNET (OPTIONAL) ........................................................................................................ 7 5.4 1.6.4 FIRMWARE VERSION......................................................................................................... 8 5.5 1.6.5 TIME / DAYLIGHT SAVINGS .............................................................................................. 8

6 GLOBAL CONFIGURATION FILES FOR CISCO VERSION 4.X THROUGH 7.X ................. 8

6.1 SIPDEFAULT.CNF (FULL EXAMPLE) ........................................................................................... 9

7 FIRMWARE SUPPORTED BY ZULTYS ON THE CISCO 7940/7960 PHONES ................... 10

8 CONVERTING CISCO PHONES TO SIP .............................................................................. 11

9 CUSTOMIZING THE DIAL PLAN OF THE CISCO PHONE ................................................ 11

9.1 EXAMPLE DIAL PLAN: ............................................................................................................. 11

10 LOGO DISPLAYED ON 7940/7960 SCREEN ...................................................................... 11

11 COMPANY TELEPHONE DIRECTORY ............................................................................... 12

12 REBOOT 7960/7940 PHONE ............................................................................................... 13

12.1 RESET THE 7940 AND 7960 IP PHONES NETWORK SETTINGS TO THE FACTORY DEFAULT ..... 13 12.2 RESET THE 7940 AND 7960 IP PHONES TO THE FACTORY DEFAULT ...................................... 13




2 Use with MXIE The Cisco 7940/7960 will integrate with MXIE and all MXIE functions are supported, EXCEPT

Answer incoming calls from MXIE, you must answer from the device Disconnect calls from MXIE, you must disconnect from the device

3 Intraoperative Notes

3.1 Parking When transferring a call from the device to the Park Server you must using “Blind Transfer” followed by either *77 or *77+Park ID, where *77 is the dial access code for the Park Server.

After parking a call the Parked On will NOT be displayed on the screen of the phone.

3.2 Transfer When transferring a call from the device, and you are not performing a supervised transfer (AKA, consulting with the transfer to party before completing the transfer) it is highly suggested you use Blind Transfer to perform this action. Failure to do this will cause the Caller ID to be incorrectly displayed on the transferred parties’ phone, or in a MXNetworked environment the transfer may fail.

3.3 Paging This device cannot be a member of a page group to receive a page, it may make a page to the page group it is a member of.

3.4 BLF No BLF Functions supported including Login buttons, Park Slot Monitored, MWI buttons as well as BLF for users.

4 Adding a new device In the MXadministrator select Configure | Devices, and right mouse click in the field or press the INS key to add a new device.

Select the device type of Cisco 7960




If you are requested to create a new device profile do so, no need to make any modifications to the device profile.




Enter in the MAC address, Phone Label, the Device ID will be default be set to the MAC address, and optionally add SIP Proxy Password. It is recommended to use the MAC address as the Device ID. To use a custom Device ID, clear the check box “Use MAC Address as Device ID” and you will be allowed to enter in a custom Device ID.

When done click Finish

4.1 Using the Default Cisco Profile Using the default Cisco Profile, no modification is required at all to the device profile; this is why the text field for customization is left blank in the profile. The MX will automatically build the configuration files using the information provided when defining the device. The Device ID will be used as the authorization name, and the SIP Proxy Password will be used as the authorization password. This information does not need to be added in the profile, as profiles are used for all devices assigned to it.

4.2 Default Cisco Profile: No modifications are required for the default profile, unless you wish to customize the display for each of the devices assigned to this profile.




5 Custom profile options These options can be configured at the per device profile level to override the default settings, and SIPDefault configuration file. All devices using this profile will have this options applied to them.

5.1 1.6.1 Logo (optional) # Pointer to Zultys logo on the MX250. logo_url:" http://192.168.1.1/images/7960_LCD_screen5.bmp "

This image does reside on the MX250/MX30, and does not need to be installed.

5.2 1.6.2 Directory (optional) #Directory directory_url: "http://10.0.0.220/cisco/phone_book.php"

This directory file is a custom file that reads from the CDR Database on the MX and needs to be hosted on a separate web server. Please refer to document Cisco_Phonebook.pdf (0000000009) for further information.

5.3 1.6.3 Telnet (optional) # Open telnet access to Cisco




telnet_level:2

5.4 1.6.4 Firmware version # Version number 7.5 image_version: P0S3-07-5-00

5.5 1.6.5 Time / Daylight savings sntp_mode : DirectedBroadcast sntp_server : 192.168.1.1

time_zone : EST dst_offset : 1 dst_start_month : Mar dst_start_day : 2 dst_start_day_of_week : Sun dst_start_week_of_month : 1 dst_start_time : 02 dst_stop_month : Nov dst_stop_day : 1 dst_stop_day_of_week : Sun dst_stop_week_of_month : 1 dst_stop_time : 2 dst_auto_adjust : 1 time_format_24hr : 1

date_format : M/D/Y

6 Global Configuration Files for Cisco version 4.x through 7.x There are several configuration files used in the provisioning of a Cisco phone (From Cisco’s SIP Conversion document). All files listed here must be obtained from Cisco.

• OS79XX.TXT This file tells the Cisco 7940/7960 which binary to download from the TFTP

server. This file is case sensitive and must only contain the name of the file that you want to load, without the .bin extension. For example, if you attempt to load the SIP version 2.3 software, it must contain only the line P0S30203. If you try to load versions 3.0 and later, the file name must be in the format P0S3-xx-y-zz. For example, if you attempt to load the SIP version 7.1 software, OS79XX.TXT must contain the line P0S3-07-1-00. The binary referenced here must also be present in the TFTP root directory. Without this file, the phone does not know which file it needs to retrieve, in order to replace its existing software.

• SIPDefaultGeneric.cnf




This file is an example of a default configuration file. This file contains configuration information relevant to all phones.

• SIPConfigGeneric.cnf This file is similar to the previous one, except that it contains information

relevant to a specific phone instead of to all phones. • RINGLIST.DAT

Lists audio files that are the custom ring type options for the phones. The audio files listed in the RINGLIST.DAT file must also be in the root directory of the TFTP server.

• ringer1.pcm This file is a sample ring tone that is used by the Cisco 7940/7960.

• P003.........bin Nonsecure universal application loader for upgrades from images earlier than

5.x. • P003.........sbn

Secure universal application loader for upgrades from images 5.x or later. • P0a3.........loads

File that contains the universal application loader and application image, where a represents the protocol of the application image LOADS file: 0 for SCCP, and S for SIP.

• P0a3.........sb2 Application firmware image, where a represents the application firmware

image: 0 for SCCP, and S for SIP.

6.1 SIPDefault.cnf (full example) This is modified from the default 7.5 version. These are the default settings that will be applied to all phones unless overridden by the device profile. The below example is a Zultys recommended version of the default file from Cisco.

tftp_cfg_dir: ./Cisco7960/

logo_url: "http://192.168.1.1/images/7960_LCD_screen5.bmp" image_version: "P0S3-07-5-00"

network_media_type : Auto

network_port2_type : Hub/Switch dscpForAudio : 184

phone_password : "cisco"

phone_prompt : ">>"

language : english

voip_control_port : 5060

start_media_port : 16384 end_media_port : 32766

sync : "1"

xml_card_dir : "" xml_card_file : "CARD.XML"

http_proxy_addr : UNPROVISIONED

http_proxy_port : 80 garp_enable : 0

enable_vad : 0




dial_template : "dialplan" callerid_blocking : 0

anonymous_call_block : 0

autocomplete : 1 dtmf_outofband : avt

dtmf_avt_payload : 101

dtmf_db_level : 4 dtmf_inband : 0

sip_retx : 10

sip_invite_retx : 6 timer_t1 : 500

timer_t2 : 4000

timer_invite_expires : 180 timer_register_expires : 3600

nat_received_processing : 0

call_waiting : 1 user_info : ""

cnf_join_enable : 1

remote_party_id : 1 semi_attended_transfer : 0

transfer_onhook_enabled : 1

call_hold_ringback : 1 stutter_msg_waiting : 0

cfwd_url : ""

call_stats : 0 auto_answer : 0

local_cfwd_enable : 0

timer_register_delta : 5 sip_max_forwards : 70

rfc_2543_hold : 0

version_stamp : ""

timer_keepalive_expires : 120

connection_monitor_duration : 120

7 Firmware supported by Zultys on the Cisco 7940/7960 phones

Supported Firmware on Cisco phones are

• 4.0 • 5.5 • 6.5 • 7.5 • 8.12

All other firmware is NOT supported by Zultys; the 8.x firmware is not supported by Cisco on systems other than the Call Manager. Firmware can ONLY be obtained from Cisco.

8 Converting Cisco Phones to SIP Please see Cisco Document 5455 for information. This document is also available from Zultys Technical Support with NO SUPPORT.

http://www.cisco.com/application/pdf/paws/5455/handset_to_sip.pdf

9 Customizing the Dial Plan of the Cisco Phone The dial plan of the phone is derived from the Dialplan.xml file that is loaded to the root of the TFTP server of the MX.

9.1 Example Dial Plan:

<DIALTEMPLATE>

<TEMPLATE MATCH="0" Timeout="1" User="Phone"/> 

<TEMPLATE MATCH="9,011*" Timeout="6" User="Phone"/> 

<TEMPLATE MATCH="9,0" Timeout="8" User="Phone"/> 

<TEMPLATE MATCH="9,11" Timeout="0" User="Phone" Route="Emergency" Rewrite="9911"/>

<TEMPLATE MATCH="w!" Timeout="1" User="PHONE" Route="Emergency" Rewrite="9911"/>

<TEMPLATE MATCH="9,.11" Timeout="0" User="Phone"/> 

<TEMPLATE MATCH="9,1.........." Timeout="0" User="Phone"/> 

<TEMPLATE MATCH="9,......." Timeout="0" User="Phone"/> 

<TEMPLATE MATCH="8,......." Timeout="0" User="Phone"/> 

<TEMPLATE MATCH="2..." Timeout="0" User="Phone"/> 

<TEMPLATE MATCH="3..." Timeout="0" User="Phone"/> 

<TEMPLATE MATCH="89.." Timeout="0" User="Phone"/> 

<TEMPLATE MATCH="50.." Timeout="0" User="Phone"/> 

<TEMPLATE MATCH="*" Timeout="15"/> 

</DIALTEMPLATE>

Template match = * is sufficient, although you’ll have to wait for the interdigit timeout on every call.

10 Logo Displayed on 7940/7960 Screen A non-Cisco logo can be displayed on the 7960 screen. Cisco's documentation suggests the logo be a Windows Bitmap form (*.BMP) in grayscale, and 90 x 56 pixels in size. Only two colors are displayed, black or white. The image must be saved in grayscale format. In GIMP it is Image->Mode->Grayscale. Microsoft Paint and many other applications can be used to create the logo image.

The image must be exactly 90 x 50 or it will not show up. The image must be gray scale as well or the image will not show up. This image must live on an external web server; the MX cannot be used to house these images.

http://www.cisco.com/application/pdf/paws/5455/handset_to_sip.pdf




Once the image is created, place the *.BMP file on any web site available to you (suggest /zultys/mylogo.bmp, where the /zultys directory is not freely advertised). Modify the SIPDefault.cnt file entry to point to the web site: logo_url: http://www.mywebserver.com/zultys/logo.bmp and reboot the Cisco phone.

Note: the smaller the logo file, the quicker it will load. Typical logo files should be around 10k bytes. Note: 7940/7960 phones actually display two colors at 2-bit depth, or four solid colors. For best results creating images/logos that don't dither and degrade, use

#000000 (black) and #FFFFFF (white or clear on the LCD display), then #404040 (dark grey) and #808080 (light gray) as your alternate solid colors (or as the antialiasing colors for excellent results).

11 Company Telephone Directory The 7960/7940 phones have four panel keys labeled as Messages, Services, Directories, and Settings. The Directory key can be programmed to view your company's telephone directory by displaying Names and Telephone Numbers that are stored on any web site available to you. Modify the SIPDefault.cnf file entry to point to the web site: directory_url: "http://www.mywebserver.com/zultys/directory.xml" The phone must be rebooted in order to read the above file. The web site file /zultys/directory.xml should include xml entries like:

<CiscoIPPhoneDirectory> <Title>IP Telephony Directory</Title> <Prompt>People reachable via VoIP</Prompt> <DirectoryEntry> <Name>Rich</Name> <Telephone>3000</Telephone> </DirectoryEntry> <DirectoryEntry> <Name>Todd</Name> <Telephone>3001</Telephone>

</DirectoryEntry> </CiscoIPPhoneDirectory>

Note: Each time a user presses the Directory key and accesses the External Directory option from the menu, the phone will access the contents of this html file and display whatever text entries included in it. Therefore, changes to the html file do not require




any further rebooting of the Cisco phone. Cisco has published Cisco IP Phone Services Application Development Notes (CMXML_App_Guide.pdf ) that further explains options and file contents.

12 Reboot 7960/7940 phone Press and hold “* + 6 + Settings” keys at the same time until the headset light lights up.

12.1 Reset the 7940 and 7960 IP Phones Network settings to the Factory Default

Complete these steps:

Press Settings.

The Network Configuration lock symbol must be unlocked. If not, exit to the main window and press ** # again. If using newer firmware use the password “cisco”

1. Press 3 on the keypad (or scroll down) for Network Configuration. 2. Press 33 on the keypad (or scroll down) to Erase Configuration. 3. Press the Yes softkey. 4. Press the Save softkey.

The phone must now be reset.

12.2 Reset the 7940 and 7960 IP Phones to the Factory Default

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, or press “* + 6 + Settings” keys at the same time.

The phone begins its power up cycle.

2. Immediately press and hold # while the Headset, Mute, and Speaker buttons flash in sequence.

Release # after the Speaker button is no longer lit. (Newer firmware will say “Reset key detected”.

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.

Cisco 7960/7940 Phones€¦ · 7 7 1 V a q u e r o s S u n n y v a l e , C a l i f o r n i a , U S...

Documents

Transcript of Cisco 7960/7940 Phones€¦ · 7 7 1 V a q u e r o s S u n n y v a l e , C a l i f o r n i a , U S...