Zultys, Inc. 771 Vaqueros Sunnyvale, California, USA 94085 www.zultys.com Author: Zultys Technical Support Department At times you wish to have more control, and personalization of the Cisco phones than what is offered by the default profile options provided by the MX’s profile. This document covers how to create your own custom configuration files that will be used instead of the configurations built by the MX. This document is provided as is with limited support from Zultys. It is important to remember to modify the SIPDefault.cnf file to point to a directory other than the /Cisco7960 directory which the MX controls. This document is meant to be an addition to the Cisco 7940/7960 Install and configuration document. Please refer to this document for all details on supported features and functionality of the Cisco 7940/7960 device. April 14 Custom Cisco Configuration Files Z Technical Publications
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
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
At times you wish to have more control, and personalization of the Cisco phones than what is offered by the default profile options provided by the MX’s profile. This document covers how to create your own custom configuration files that will be used instead of the configurations built by the MX. This document is provided as is with limited support from Zultys. It is important to remember to modify the SIPDefault.cnf file to point to a directory other than the /Cisco7960 directory which the MX controls. This document is meant to be an addition to the Cisco 7940/7960 Install and configuration document. Please refer to this document for all details on supported features and functionality of the Cisco 7940/7960 device.
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.
From the MX Administration UI select Configure | Devices | Profile button, and right mouse click “ZultysPhones” and choose “New” to create a new device profile. You must have an existing device profile to add a device.
2 Create Custom Configuration file(s) When creating a custom configuration file you must create a separate file per phone that you are deploying, and it is all or none. You cannot mix custom files with non-custom files.
The configuration files must follow Cisco’s naming convention which is “SIP00036B75ABF1.cnf” that is it always starts with “SIP” in capitals followed by the MAC address all capitals, the extension is “.cnf”.
2.1 Logo (optional)
# Pointer to Zultys logo on the MX250. logo_url:" http://192.168.1.1/images/7960_LCD_screen5.bmp "
This image already resides on the MX250/MX30, and does not need to be installed.
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. It can also be a custom flat file you host as well.
2.3 Telnet (optional)
# Open telnet access to Cisco telnet_level:2
2.4 Firmware version
# Version number 7.5 image_version: P0S3-07-5-00
In this example we will be using firmware version 7.5 which can only be obtained from Cisco.
2.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
2.6 Authentication must be added to the particular configuration files In this example we are registering with the Device ID set to be the MAC address of the device, and that device has extension 5040.
;Authname ; Name used by phone for auth if registration challenges line1_authname : "00036B75ABF1" line2_authname : UNPROVISIONED
line3_authname : UNPROVISIONED line4_authname : UNPROVISIONED line5_authname : UNPROVISIONED line6_authname : UNPROVISIONED ; ;Contact ; The URL that appears in the SIP contact field line1_contact : "5040" line2_contact : UNPROVISIONED line3_contact : UNPROVISIONED line4_contact : UNPROVISIONED line5_contact : UNPROVISIONED line6_contact : UNPROVISIONED ;
;Displayname ; Caller ID as it appears to remote users line1_displayname : "Ext 5040" line2_displayname : UNPROVISIONED line3_displayname : UNPROVISIONED line4_displayname : UNPROVISIONED line5_displayname : UNPROVISIONED line6_displayname : UNPROVISIONED ; ;Name ; Name used for registering with SIP server line1_name : "00036B75ABF1" line2_name : UNPROVISIONED line3_name : UNPROVISIONED
line4_name : UNPROVISIONED line5_name : UNPROVISIONED line6_name : UNPROVISIONED ; ;Password ; Password used by phone for auth if registration challenges -- Put SIP Proxy Password here ; line1_password : "" line2_password : "" line3_password : "" line4_password : "" line5_password : "" line6_password : ""
; ;Shortname ; Used on the phone LCD display next to the line button ; line1_shortname : "5040" line2_shortname : UNPROVISIONED line3_shortname : UNPROVISIONED line4_shortname : UNPROVISIONED line5_shortname : UNPROVISIONED line6_shortname : UNPROVISIONED
This is modified from the default 7.5 version. It is extremely important to change the tftp_cfg_dir so that it is NOT ./Cisco7960 as the MX will overwrite any custom configuration files you create.
Zultys only currently supports the 7970/7971 phones. In configuration files for phones other than the 7970 such as the 7970 you need to set the authName and authPassword fields to be the Device Name in the MX and SIP Proxy Password in the MX. Incomplete sample XML file:
<device>
<deviceProtocol>SIP</deviceProtocol>
<sshUserId>user</sshUserId>
<sshPassword>pass</sshPassword>
<devicePool>
<dateTimeSetting>
<dateTemplate>M-D-Ya</dateTemplate>
“a” indicates time shown in 12 hour format
Setting these parameters will allow you to ssh to the IP phone. Login with these first, and then login with debug/debug to debug the phone.
This file needs to be available in the TFTP server
We didn’t change these as we’re on a Cisco switch and it recognizes Cisco phones connected to it. Changes might be necessary if connected to a non-Cisco switch
5 Firmware Files 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.
5.1 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.
5.2 SIPDefaultGeneric.cnf This file is an example of a default configuration file. This file contains configuration information relevant to all phones.
5.3 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.
5.4 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.
5.5 ringer1.pcm This file is a sample ring tone that is used by the Cisco 7940/7960.
5.6 P003.........bin Nonsecure universal application loader for upgrades from images earlier than 5.x.
5.7 P003.........sbn Secure universal application loader for upgrades from images 5.x or later.
5.8 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.
5.9 P0a3.........sb2 Application firmware image, where a represents the application firmware image: 0 for SCCP, and S for SIP.