Avaya 9640 Series Instruction Manual

Avaya one-X™ Deskphone Edition
for 9600 Series SIP IP Telephones
Developer Guide
16-603173
Issue 1
September 2008

© 2008 Avaya Inc.
All Rights Reserved.
Notice
While 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 Hardware Documentation, Document number 03-600759.
To locate this document on our Web site, simply go to
http://www.avaya.com/support and search for the document number in
the search box.
Documentation disclaimer
Avaya 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 disclaimer
Avaya 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.
Warranty
Avaya 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.
Avaya support
Avaya 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
Software License
USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER’S
ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL
LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE AT
http://support.avaya.com/LicenseInfo/ (“GENERAL LICENSE TERMS”). IF
YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST
RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN
(10) DAYS OF DELIVERY FOR A REFUND OR CREDIT.
Avaya grants End User a license within the scope of the license types
described below. The applicable number of licenses and units of capacity for
which the license is granted will be one (1), unless a different number of
licenses or units of capacity is specified in the Documentation or other
materials available to End User. “Designated Processor” means a single
stand-alone computing device. “Server” means a Designated Processor that
hosts a software application to be accessed by multiple users. “Software”
means the computer programs in object code, originally licensed by Avaya and
ultimately utilized by End User, whether as stand-alone Products or
pre-installed on Hardware. “Hardware” means the standard hardware
Products, originally sold by Avaya and ultimately utilized by End User.
License Type(s):
Designated System(s) License (DS). End User may install and use each copy
of the Software on only one Designated Processor, unless a different number
of Designated Processors is indicated in the Documentation or other materials
available to End User. Avaya may require the Designated Processor(s) to be
identified by type, serial number, feature key, location or other specific
designation, or to be provided by End User to Avaya through electronic means
established by Avaya specifically for this purpose.
Third-party Components
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/
Interference
Using a cell, mobile, or GSM telephone, or a two-way radio in close proximity to
an Avaya IP Telephone might cause interference.

Issue 1 September 2008 3
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Intended Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Issue Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
How to Use This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Terms Used in This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Conventions Used in This Document . . . . . . . . . . . . . . . . . . . . . . . . 9
Symbolic Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Typographic Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Online Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
IETF Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
ITU Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
ISO/IEC, ANSI/IEEE Documents. . . . . . . . . . . . . . . . . . . . . . . . 10
Avaya Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Other Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 1: Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
New Features in Release 2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Ways of Customizing the Avaya SIP IP Phone. . . . . . . . . . . . . . . . . . . . 14
Using the Push Feature.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configuring XML Settings Files. . . . . . . . . . . . . . . . . . . . . . . . . . 15
Overview of Configuring the XML Files . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 2: Customizing the Content . . . . . . . . . . . . . . . . . . . . 17
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Enable Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Create a Customized Content File . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Example content.xml file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
IPTML Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Basic Structure of an IPTML Document . . . . . . . . . . . . . . . . . . . . . 21
Card Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Label Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Item Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Action Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Contents

Contents
4 Avaya 9600 Series IP Telephone Developer Guide
Disabling Functions of Hard Buttons . . . . . . . . . . . . . . . . . . . . . . . . 24
Using a Password to Hide Screens. . . . . . . . . . . . . . . . . . . . . . . . . . 25
Language Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Language Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Support Multiple Languages on the Customized Screen . . . . . . . . . . . . 27
Bind the Language Resource . . . . . . . . . . . . . . . . . . . . . . . . . 28
Utilizing the Go Command to Launch an Application. . . . . . . . . . . . . . . . 30
Navigate to a card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Launch an Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Open a URL in the WML Browser. . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 3: Customizing the Skin . . . . . . . . . . . . . . . . . . . . . . 33
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Using a Sample Skin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Using the 46xxSettings.txt file to Modify the Skin. . . . . . . . . . . . . . 33
Create a Skin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Image Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Renaming Image File Names . . . . . . . . . . . . . . . . . . . . . . . . . 35
Positioning the Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Screen Size for Avaya 9600 Series IP Phones . . . . . . . . . . . . . . . . 39
Chapter 4: Validate the Content and Skin Files . . . . . . . . . . . . . . 41
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Installing the Avaya 9600 XML Validator . . . . . . . . . . . . . . . . . . . . . . . 41
Starting the Avaya 9600 XML Validator. . . . . . . . . . . . . . . . . . . . . . . . 42
About the Avaya 9600 XML Validator. . . . . . . . . . . . . . . . . . . . . . . . . 43
Menu Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Action Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Text Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Status Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Editing XML Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Using the Log to View All Problems . . . . . . . . . . . . . . . . . . . . . . . 47
Appendix A: IPTML Reference . . . . . . . . . . . . . . . . . . . . . . . 49
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
IPTML Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
IPTML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Issue 1 September 2008 5
About This Guide
About this Document
This document describes how to customize the contents, and "look and feel" for the 9640 SIP IP
Telephone. This document applies to Release SIP 2.2 for the 9640 SIP IP Telephone and also
covers, in part, the behavior of the Avaya 9620 and 9630 Series SIP IP Telephones. The
performance and behavior of the application or application server(s) are not addressed.
Intended Audience
This document is intended for the application developers and System Administrators who
develop or implement:
●customized content for the Avaya 9620, 9630, and 9640 SIP IP Telephones
●a customized "look and feel" for the Avaya 9640 SIP IP Telephone.
!CAUTION:
CAUTION: Avaya does not provide product support for many of the products mentioned in
this document. Take care to ensure that there is adequate technical support
available for the servers involved, including, but not necessarily limited to, HTTP,
HTTPS, and DHCP servers. If the servers are not functioning correctly, the IP
telephones might not be able to operate correctly.

About This Guide
6 Avaya 9600 Series SIP IP Telephone Developer Guide
Document Organization
This guide contains the following chapters:
Issue Date
This is the first release of this document, issued in September 2008.
How to Use This Document
This guide is organized to help you find topics in a logical manner. Read it from start to finish to
get a thorough understanding of the interfaces or use the Table of Contents or Index to locate
specific features.
Chapter 1: Overview Lists prerequisite hardware and software required. The
methods that can be used and an overview of steps for
customizing content and the user interface on applicable
9600 Series IP Telephones.
Chapter 2: Customizing the
Content Describes steps needed to enable customization, then
details steps required to create customized content on the
9600 seriesSIP IP phones. Also provides an overview and
some examples of the IP Telephony Markup Language
(IPTML). A generic description is provided, followed by
further details about various IPTML elements, and how to
implement changes to an Avaya IP Telephone using
IPTML.
Chapter 3: Customizing the
Skin Describes steps needed to change and create the "look and feel" such as background image, logo, etc. of the
9640 SIP IP phone.
Chapter 4: Validate the
Content and Skin Files Explains how to ensure the XML files are formed correctly and ready to be used.
Appendix A: IPTML Reference Provides a list of IPTML elements and functions.

Terms Used in This Document
Issue 1 September 2008 7
Terms Used in This Document
Term Description
Action The Action element defines the actions associated with an Item. Each action is
triggered by an Event and has an attribute specifying what initiates it. An Action
Element can contain a sequence of individual actions.
Application Area The usable display area between the Prompt Line and Softkey labels.
Application Line The display area line that indicates application-specific messages.
Card An IPTML document contains zero or more IPTML Cards. Each Card consists
of Lists and Labels.
Deck A deck can be described as a stack of cards. When the browser downloads a
WML page, it really is downloading a deck of cards but only one card in the
deck is visible at a time.
DTD Document Type Definition. The DTD defines the names and contents of all
elements that permissible on a WML page, the order in which the elements
must appear, the contents of all elements, attributes and default values.
Elements Elements are the essential components that make up a single IPTML
document.
FLOW The flow type represents “card-level” information. In general, flow is used
anywhere general markup can be included.
Focus Since the phone has nomouse to navigatearound the screen, the line buttons if
shown, or the OK button are used to select a particular line on the display.
Selecting a line serves to “to bring that line into focus.” Focusing on a line is
used to select a line for text entry or to select a line that contains a link to
another URL (card). Additionally, new titles can (not always) be presented to
the user as each line on the screen is individually brought “into focus” (selected
by pressing the Line or OK buttons).
H.323 A TCP/IP-based protocol for VoIP signaling.
HTML HyperText Markup Language is a text-based way of describing data for
transmission over the Internet HTML is usually used with larger, color displays.
HTTP HyperText Transfer Protocol, used to request and transmit pages on the World
Wide Web.
HTTPS HyperText Transfer Protocol Secure. A secure version of HTTP over SSL
(Secure Socket Layer). Designed to provide encrypted communications for
handling secure transactions.
1 of 3

About This Guide
8 Avaya 9600 Series SIP IP Telephone Developer Guide
IP Internet Protocol – a suite of information-exchanged message sets widely used
for data transmission and increasingly used for the transmission of voice.
IPTML IP Telephony Markup Language. A simple XML based language that allows
applications to exchange information with an IP endpoint.
Item The Item element is the most often used element in an IPTML document. It can
refer to an application line, a softkey, or a hard button on the IP phone.
Label The Label element is used to define text for the Top Line, Title Line and Prompt
Line.
Link The URI that is used to chain cards together.
List Used in a Card Element to identify application lines, softkeys, or hard buttons.
Prompt Line The third line in the top display area. The current application uses the Prompt
Line to provide context-specific prompts, hints, explanations, help, or similar
information.
Registration The registration is a scheme of allowing an Avaya IP Telephone to authenticate
itself with the Avaya Communication Manager. The Avaya Media Server switch
supports registering and authenticating Avaya IP Telephones using the
extension and password.
Skin The "look and feel" of an Avaya IP Telephone, specifically the display area.
Title Line The second line in the top display area. Comprised of the current application
title, subtitle (if applicable), and choice or Web paging indicators as applicable.
Top Line The top area of the display is subdivided horizontally into a Top Line, a Title
Line, and a Prompt Line, each extending across the entire width of the 318 pixel
usable area for the 9600 Series IP Telephones. The Top Line contains current
status information. Examples of status information are the extension number,
time and date, and icons for phone- or call-related data. For the 9610 IP
Telephone, which has only a Top Line, messages and prompts appear there.
Type Type specifies a tag or attribute.
VDATA A DTD data type representing a string that can contain variable references. This
type is only used in attribute values.
W3C World Wide Web Consortium.
WAP Wireless Application Protocol. An open global standard for wireless solutions
that includes WML.
WML Wireless Markup Language is a subset of XML, used by the Avaya IP
Telephone Web browser to communicate with WML Servers.
Term Description (continued)
2 of 3

Conventions Used in This Document
Issue 1 September 2008 9
Conventions Used in This Document
This guide uses the following textual, symbolic, and typographic conventions to help you
interpret information.
Symbolic Conventions
Note:
Note: This symbol precedes additional information about a topic.
!CAUTION:
CAUTION: This symbol is used to emphasize possible harm to software, possible loss of
data, or possible service interruptions.
Typographic Conventions
This guide uses the following typographic conventions:
XML eXtensible Markup Language. W3C's standard for Internet Markup Languages.
WML is one of these languages.
xml:lang The xml:lang attribute specifies the natural or formal language of an element
or its attributes. This is a DTD term.
Term Description (continued)
3 of 3
Document Underlined type indicates a section or sub-section in this document
containing additional information about a topic.
“Document” Italic type enclosed in quotes indicates a reference to specific
section or chapter of an external document.
italics Italic type indicates the result of an action you take or a system
response in step by step procedures.

About This Guide
10 Avaya 9600 Series SIP IP Telephone Developer Guide
Online Documentation
The online documentation for this guide and related Avaya documentation for 9600 Series IP
Telephones is located at the Avaya Support Web site: http://www.avaya.com/support
Related Documentation
IETF Documents
The following documents provide information relevant to IP telephony and are available for free
from the IETF Web site:
●IETF RFC 2616: http://www.ietf.org/rfc/rfc2616.txt?number=2616
●IETF 1945: http://www.ietf.org/rfc/rfc1945.txt?number=1945
ITU Documents
Access the ITU Web site for more information about ITU guidelines and documents, available
for a fee from the ITU Web site: http://www.itu.int.
ISO/IEC, ANSI/IEEE Documents
Access the ISO/IEC standards Web site for more information about IP Telephony standards,
guidelines, and published documents: http://www.iec.ch.
Conference In step by step procedures, words shown in bold represent a single
telephone button that should be pressed/selected.
message Words printed in this type are messages, prompts, code excerpts,
code samples, and XML tags.

Related Documentation
Issue 1 September 2008 11
Avaya Documents
●Avaya one-X™ Deskphone Edition for 9600 Series IP Telephone Administrator Guide
(Document Number 16-603158)
This guide provides a description of administrative duties like HTTP server setup, and how
to set up Push parameters in the settings file.
●Avaya one-X™ Deskphone Edition for 9600 Series SIP IP Telephones Installation and
Maintenance Guide (Document Number 16-603159)
This guide provides information on administering Avaya Communication Manager, DHCP,
HTTP/HTTPS servers for 9600 Series SIP IP Telephones, a Local Area Network (LAN), SIP
Enablement Services (SES) or a Network Time server.
●IP Telephone WML Server Setup Guide (Document Number 16-300507)
This guide provides information on setting up a Web server.
Other Documents
●Extensible Markup Language (XML) 1.0 (Second Edition), W3C Recommendation 6
October 2000.

About This Guide
12 Avaya 9600 Series SIP IP Telephone Developer Guide

Issue 1 September 2008 13
Chapter 1: Overview
Prerequisite
The following hardware and software is required to customize your Avaya 9600 Series IP
Phone.
Note:
Note: Refer to the Pre-Installation Checklist in Avaya one-X™ Deskphone Edition for
9600 Series SIP IP Telephones Installation and Maintenance Guide (Document
Number 16-603159).
Hardware
●Avaya 9620, 9630, or 9640 SIP IP Phone
●Desktop computer
●Web server
Software
●96xx SIP phone with R2.2 firmware from the Avaya Support Web site: http://
www.avaya.com/support
●Microsoft Windows XP (or later) with Internet Explorer, or a web browser of your choice
●Microsoft XML Notepad, or an xml editor of your choice
●Microsoft Paint or an image editor of your choice
●Avaya 9600 XML Validator
New Features in Release 2.2
Previous versions of the 9600 Series IP Phone firmware allowed an administrator the capability
of pushing content including text, web pages and audio files to the phone.
The release of version 2.2 firmware includes the following features:
●Clear the call log
●Clear the web history

Overview
14 Avaya 9600 Series SIP IP Telephone Developer Guide
●Change the phone language
●Change the user name
●Control the backlight
●Change the appearance of the phone by updating the skin and logo
●Change the display screen
●Update the user profile
Note:
Note: Further information about the Push feature is available in Avaya one-X™
Deskphone Edition for 9600 Series IP Telephones Application Programmer
Interface (API) Guide (Document Number 16-600888).
Ways of Customizing the Avaya SIP IP Phone
There are two ways for you to customize your Avaya SIP IP phone, the Push feature and
configuring XML settings files.
The table below depicts the main difference between both methods.
Using the Push Feature.
The Push feature provides the ability for an application to send content to the Web browser, to
the Top Line of the display, or to the audio transducers of 9600 Series IP Telephones. With the
Push interface, the application can ’push’ unsolicited information to the telephone without the
user having to click a link.
Feature Push Configuring XML Files
Interaction is... remote local
Configuration
through... a web browser XML files native to the phone
Customized screen
updated... in ’real-time’ when phone boots up

Overview of Configuring the XML Files
Issue 1 September 2008 15
Some uses of the Push interface include:
●Broadcasting company news
●Sending meeting reminders with conference bridge numbers, so that users don’t have to
search for the conference number
●Streaming music, such as wake-up alarms in hotel rooms
●Streaming audio announcements
●Sending critical stock news information
●Broadcasting critical emergency notices and weather alerts
●Building intelligent databases to target information to an individual or groups of phones
Configuring XML Settings Files
By configuring XML files you can change the content and "look and feel" of your phone.
XML files can be downloaded from the Avaya Support Web Site: http://www.avaya.com/
support
The image below shows which files are used during the IP phone’s boot-up sequence.
Overview of Configuring the XML Files
Customizing the content and design of the 9640 SIP IP Phone involves the following steps:

Overview
16 Avaya 9600 Series SIP IP Telephone Developer Guide
●Enable Customization
●Create a Customized Content File
●Customizing the Skin
●Validate the Content and Skin Files
Note:
Note: Content on the Avaya 9620 and 9630 IP Phones can also be customized.
However, only the Avaya 9640 IP Phone in the 9600 Series can have its "llok and
feel" (skin) customized. The Avaya 9610 IP Phone is not listed here since it does
not support the features described in this document.

Issue 1 September 2008 17
Chapter 2: Customizing the Content
Introduction
This chapter provides the steps needed to enable customization, then details steps required to
create customized content on the 9600 series SIP IP phones.
Enable Customization
To enable customization on the 9600 series SIP IP Phone:
1. Download the 9600template.zip file from the Avaya Support Web site:
http://www.avaya.com/support.
2. Extract the zip file and copy the sample files to the root folder of your file server.
Note:
Note: The generic term "file server" refers to both "HTTP server" and "HTTPS server".
3. Configure the 46xxSettings.txt file
4. Navigate to the section SETTINGS9640, and modify the following parameters:
SET CURRENT_CONTENT "http://<webserver>/content.xml"
SET SKINS "example=http://<webserver>/skins/example/9640.xml"
SET CURRENT_SKIN "example"
In the above example, <webserver> should be replaced with HTTP server which is
deployed in your environment.
!Important:
Important: The SET SKINS value must be on one line.
Refer to the Avaya one-X™ Deskphone Edition for 9600 Series IP Telephone Administrator
Guide (Document Number 16-603158) for more information.
5. You will also need to modify the content.xml file to customize the content that displays on
your IP phone. This file is available from the Avaya Support Web site
6. Reboot the phone.

Customizing the Content
18 Avaya 9600 Series SIP IP Telephone Developer Guide
7. The content provided in content.xml should be displayed on the screen when the phone has
started up.
The example below shows how the display can be customized using this procedure.
Create a Customized Content File
You can customize content such as menu items on the 9600 Series IP Phone.
Alternatively, refer to the samples provided in the 9600template.zip file.
See IPTML Overview for more information about the structure and elements in an IPTML
document.
Example content.xml file
The instructions and files referenced below are provided as a sample of the changes required.
To customize content:
1. Start an xml editor of your choice, such as XML Notepad.

Create a Customized Content File
Issue 1 September 2008 19
2. Open the content.xml file. A screen similar to the example below displays.
3. Navigate to the label Concierge and replace this with Housekeeping.
4. Enter a new extension number of 40648. Edit the Dial attribute value of 40647 that was
previously used for Concierge to reflect the new Housekeeping extension.
5. Enter a new display in the DisplayLabel attribute value; Press OK to dial the
Housekeeper
6. Copy the HouseKeeping item and paste it into the content.xml document to create a new
menu item.
a. Rename Housekeeping to Help Desk

Customizing the Content
20 Avaya 9600 Series SIP IP Telephone Developer Guide
b. Change the extension number to 45150
c. Enter a new prompt message within the DisplayLabel attribute, Press OK to dial
the Help Desk.
The content.xml file should now include the following:
<Item>
<Label>Help Desk</Label>
<Actions trigger="OnActivate">
<Dial>45150</Dial>
</Actions>
<Actions trigger="OnFocus">
<DisplayLabel>Press Ok to dial the Help Desk</DisplayLabel>
</Actions>
</Item>
7. Save the content.xml file and copy to your file server.
8. Restart the IP phone.
IPTML Overview
IPTML is a simple XML based language that allows applications to exchange information with
IP endpoints.
The key aspect of IPTML is to present an interface for applications to interact with various IP
telephony events, such as attaching content to home screens and to various call handling
screens.
An IPTML document is an ordinary XML document containing the following elements:
●A number of Card elements that contain the content of the customized screens.
●A number of Label elements that contain information to display on the Title Line or Prompt
Line on the 9600 Series IP phones.
●Optional elements to disable hard buttons on an IP phone.
●Optional language resource elements to provide multiple languages for the IPTML
document.