Avaya 4600 Series Application Note
Browse online or download Application Note for Software Avaya 4600 Series. Avaya 4600 Series Application Note [et] User Manual
- Page / 206
- Table of contents
- BOOKMARKS
- 4600 Series IP Telephones 1
- (API) Guide 1
- Contents 3
- Issue 1 April 2005 5 5
- Issue 1 April 2005 7 7
- Document Organization 10
- Issue Date 11
- How to Use This Document 11
- Terms Used in This Document 11
- About This Guide 12
- Issue 1 April 2005 13 13
- Online Documentation 15
- Related Documentation 16
- Overview 17
- Existing Interfaces 18
- Issue 1 April 2005 19 19
- IP Telephone Interfaces 20
- Push Feature Description 22
- Push Architecture 22
- Issue 1 April 2005 23 23
- Push Message Flow 24
- Step 4 – Request Launched 25
- About the Push Agent 26
- HTTP Server 26
- Push Types 27
- Push Interface Overview 28
- The Display Push Type 29
- Display Push Example 1: 30
- Priorities and States 30
- Successful Push Response 31
- Normal Priority 31
- Barge Priority 32
- Display Push XML Messages 33
- Creating Push Messages 34
- Display Push Example 2: 35
- Push Agent 35
- Push Content (PC) 36
- The Topline Push Type 37
- Topline Push Example 1: 38
- Topline Push XML Messages 41
- Topline Push Example 2: 43
- Topline Push Content (PC) 44
- Using the <Topline> tag 45
- The Audio Push Type 46
- Audio Push Example: 47
- Audio Push XML Messages 49
- RTP Port 50
- Audio Push Content (PC) 51
- Issue 1 April 2005 53 53
- The Subscribe Push Type 54
- Subscribe XML Messages 55
- Subscribe Push Content (PC) 57
- Requirements 59
- Security 59
- Push Administration 60
- Validation Scenarios 61
- Subscription Service 62
- Subscriber Service 63
- Subscription Update 65
- Retry Timer 65
- Denial of Service Timer 65
- Issue 1 April 2005 67 67
- HTTP Error Messages 69
- Physical Attributes 72
- Web Browser Navigation 73
- Icons for Navigation Control 74
- Issue 1 April 2005 75 75
- Multiple Paging Indicators 76
- Moving Up and Down a Card 76
- Example: 77
- Truncation Rules and Links 78
- Enabling Text Entry 79
- Text Entry Example: 80
- Text Editing Modes 81
- Input Modes 82
- Issue 1 April 2005 83 83
- Character Set Support 84
- Web History 84
- Display Colors 84
- Call Interaction 85
- Syntax Implementation 87
- Issue 1 April 2005 89 89
- Web: Click-to-Dial Demo 91
- Issue 1 April 2005 93 93
- Page Loading 94
- Error Tones 95
- HTTP Protocol 95
- HTTP Header 95
- Error Messages 97
- Issue 1 April 2005 99 99
- About The Web Browser 100
- Issue 1 April 2005 101 101
- Introduction 103
- General Background 104
- WML Tags and Attributes 104
- Issue 1 April 2005 105 105
- Text Elements 107
- Text Formatting Tags 108
- Anchor Elements 108
- Image Elements 109
- Event Elements 110
- Issue 1 April 2005 111 111
- Task Elements 113
- Input Elements 114
- Issue 1 April 2005 115 115
- Variable Elements 117
- Character Entities 118
- Colors and Fonts 118
- Access Key Input Mode (AIM) 119
- Issue 1 April 2005 121 121
- 8VHGLDOSDGIRUWH[WHQWU\ 123
- 2VFDU+LOODUG 123
- Terminating AIM 125
- Chapter 8: Web Applications 127
- Web Applications 128
- Avaya-Provided Download Files 129
- Issue 1 April 2005 131 131
- Issue 1 April 2005 133 133
- Issue 1 April 2005 135 135
- Return AddToSD 136
- (UURU0HVVDJH 137
- Return Retry 137
- Issue 1 April 2005 139 139
- Issue 1 April 2005 141 141
- Issue 1 April 2005 143 143
- Issue 1 April 2005 145 145
- Issue 1 April 2005 147 147
- Issue 1 April 2005 149 149
- Telephone 151
- Issue 1 April 2005 153 153
- Issue 1 April 2005 159 159
- Issue 1 April 2005 161 161
- Issue 1 April 2005 167 167
- Image Support 170
- JPEG Images 171
- Image Rendering 171
- Scrolling Through Images 172
- Image area 173
- Image Size 174
- Number of Images Supported 175
- Cascading Order 176
- Issue 1 April 2005 181 181
- CSS2 Specifications 182
- CSS Background Properties 183
- CSS Text Properties 183
- Code Examples 184
- <card> Example 185
- <p> tag Example 186
- Another <p> tag Example 187
- First <a> tag Example 188
- Second <a> tag Example 189
- Third <a> tag Example 190
- <do> tag Example 191
- Issue 1 April 2005 193 193
- Colors Specification 195
- Issue 1 April 2005 197 197
- Issue 1 April 2005 199 199
- Issue 1 April 2005 201 201
- Numerical 203
Summary of Contents
4600 Series IP TelephonesApplication Programmer Interface (API) GuideRelease 2.2 for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP TelephonesRelease 2.5
About This Guide10 4600 Series IP Telephones Application Programmer Interface (API) Guide Document OrganizationThis guide contains the following chap
About The Web Browser100 4600 Series IP Telephones Application Programmer Interface (API) Guide <head> No<i> No<img> align alt hei
Summary Of WML Tags and AttributesIssue 1 April 2005 101 <postfield>name value YesYesYes<prev> Yes<refresh> Yes<select>ivalue
About The Web Browser102 4600 Series IP Telephones Application Programmer Interface (API) Guide
Issue 1 April 2005 103 Chapter 7: Web Browser for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP TelephonesIntroductionThis chapter describes the capabil
Web Browser for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP Telephones104 4600 Series IP Telephones Application Programmer Interface (API) Guide Gener
WML Tags and AttributesIssue 1 April 2005 105 ● Common tag attributes: xml:lang, class, and id.The attributes xml:lang, class and id are universal at
Web Browser for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP Telephones106 4600 Series IP Telephones Application Programmer Interface (API) Guide ● <
WML Tags and AttributesIssue 1 April 2005 107 Text ElementsSee Enabling Text Entry on page 79 and Text Editing Modes on page 81 for guidelines to ena
Web Browser for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP Telephones108 4600 Series IP Telephones Application Programmer Interface (API) Guide Text
WML Tags and AttributesIssue 1 April 2005 109 Image Elements● <img> tag - Use the <img> tag to place an image in the text flow. The telep
Issue DateIssue 1 April 2005 11 Issue Date April, 2005 is the first issue of this document, which combines and replaces two previously-issued documen
Web Browser for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP Telephones110 4600 Series IP Telephones Application Programmer Interface (API) Guide Event
WML Tags and AttributesIssue 1 April 2005 111 <do> tags are rendered as softkey labels on the bottom line of the display. <do> tags are s
Web Browser for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP Telephones112 4600 Series IP Telephones Application Programmer Interface (API) Guide ● <
WML Tags and AttributesIssue 1 April 2005 113 Task Elements● <go> tag - The go element can contain one or more postfield elements. If a go elem
Web Browser for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP Telephones114 4600 Series IP Telephones Application Programmer Interface (API) Guide An ex
WML Tags and AttributesIssue 1 April 2005 115 format AaNXxMm*fnfSets the data format for the input field. Default is “M.”A = uppercase alphabetic or
Web Browser for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP Telephones116 4600 Series IP Telephones Application Programmer Interface (API) Guide The 4
WML Tags and AttributesIssue 1 April 2005 117 ● <select> tag - The select tag allows for the definition of a list, embedded in a card. This tag
Web Browser for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP Telephones118 4600 Series IP Telephones Application Programmer Interface (API) Guide ● <
Access Key Input Mode (AIM)Issue 1 April 2005 119 Access Key Input Mode (AIM)The Web browser considers cards that include the accesskey attribute and
About This Guide12 4600 Series IP Telephones Application Programmer Interface (API) Guide CAPPCross-APEX Process Platform, the set of development pro
Web Browser for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP Telephones120 4600 Series IP Telephones Application Programmer Interface (API) Guide In Ta
Access Key Input Mode (AIM)Issue 1 April 2005 121 Example of Text Entry Using AIM:The user wants to look up a person named Oscar in a Directory datab
Web Browser for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP Telephones122 4600 Series IP Telephones Application Programmer Interface (API) Guide Figur
Access Key Input Mode (AIM)Issue 1 April 2005 123 Figure 20: User presses “2” one time for “C” and the search result displays the desired result - Os
Web Browser for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP Telephones124 4600 Series IP Telephones Application Programmer Interface (API) Guide The W
Access Key Input Mode (AIM)Issue 1 April 2005 125 Terminating AIMThe user ends AIM by: ● Pressing the Phone/Exit button or Options button.● Selecting
Web Browser for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP Telephones126 4600 Series IP Telephones Application Programmer Interface (API) Guide
Issue 1 April 2005 127 Chapter 8: Web ApplicationsIntroductionIf you have a corporate database that supports the Lightweight Directory Access Protoco
Web Applications128 4600 Series IP Telephones Application Programmer Interface (API) Guide Figure 21: High-Level Thin Client Architecture As Figure 2
Application Platform RequirementsIssue 1 April 2005 129 Application Platform RequirementsThe LAN Administrator or System Administrator must provide a
Terms Used in This DocumentIssue 1 April 2005 13 PBXPrivate Branch Exchange – A generic name for a premise-based switch supporting telephony features
Web Applications130 4600 Series IP Telephones Application Programmer Interface (API) Guide The other application version available is a Winzip-readab
Installing the Thin Client Directory on the ServerIssue 1 April 2005 131 5. The default user/password combination is ldap/ldap. To change the passwor
Web Applications132 4600 Series IP Telephones Application Programmer Interface (API) Guide Installation for Windows with Apache:1. Extract the file a
Web Application User InterfaceIssue 1 April 2005 133 Note:Note: Specific user instructions regarding the Directory application are not provided in th
Web Applications134 4600 Series IP Telephones Application Programmer Interface (API) Guide Web Application Search Screen The Search screen displays u
Web Application User InterfaceIssue 1 April 2005 135 Web Application Successful Search Screen The Successful Search screen displays when at least one
Web Applications136 4600 Series IP Telephones Application Programmer Interface (API) Guide Web Application Detail Screen The Detail screen displays w
Web Application User InterfaceIssue 1 April 2005 137 Note:Note: You administer the [user interface] Detail screen on the Details Administration scree
Web Applications138 4600 Series IP Telephones Application Programmer Interface (API) Guide Possible reasons for search failure and the resulting mess
Web Application User InterfaceIssue 1 April 2005 139 When the Directory application receives a request for a Search screen, it sends a Search screen
About This Guide14 4600 Series IP Telephones Application Programmer Interface (API) Guide Conventions Used in This DocumentThis guide uses the follow
Web Applications140 4600 Series IP Telephones Application Programmer Interface (API) Guide Directory Database Administration Interface The Directory
Directory Database Administration InterfaceIssue 1 April 2005 141 2. General Directory Application Administration screen - You provide general inform
Web Applications142 4600 Series IP Telephones Application Programmer Interface (API) Guide Configuring the General Directory Application Administrati
Directory Database Administration InterfaceIssue 1 April 2005 143 2. All fields except Directory User ID and Directory Password are required. Table 1
Web Applications144 4600 Series IP Telephones Application Programmer Interface (API) Guide Configuring the Directory Application Search Administratio
Directory Database Administration InterfaceIssue 1 April 2005 145 2. Enter the search fields, corresponding LDAP attribute names, and associated labe
Web Applications146 4600 Series IP Telephones Application Programmer Interface (API) Guide Configuring the Directory Application Details Administrati
Directory Database Administration InterfaceIssue 1 April 2005 147 2. Enter the LDAP attribute names that represent the detail information you want to
Web Applications148 4600 Series IP Telephones Application Programmer Interface (API) Guide Figure 30: Softkey Administration Screen
Directory Database Administration InterfaceIssue 1 April 2005 149 Table 16: List of Drop-Down Attributes available for Search, Query and Details Adm
Online DocumentationIssue 1 April 2005 15 Symbolic ConventionsNote:Note: This symbol precedes additional information about a topic.!CAUTION:CAUTION:
Web Applications150 4600 Series IP Telephones Application Programmer Interface (API) Guide
IntroductionIssue 1 April 2005 151 Chapter 9: Web Browser for the 4625SW IP TelephoneIntroductionThis chapter describes the capabilities and limitati
Web Browser for the 4625SW IP Telephone152 4600 Series IP Telephones Application Programmer Interface (API) Guide The data types and other features s
WML Tags and AttributesIssue 1 April 2005 153 ● <head> tag - The <head> tag is an optional WML tag. This tag contains information that re
Web Browser for the 4625SW IP Telephone154 4600 Series IP Telephones Application Programmer Interface (API) Guide The seven display lines are used to
WML Tags and AttributesIssue 1 April 2005 155 Text ElementsSee Enabling Text Entry in Chapter 6 for text entry guidelines. ● <br/> tag - The &l
Web Browser for the 4625SW IP Telephone156 4600 Series IP Telephones Application Programmer Interface (API) Guide Application developers can create a
WML Tags and AttributesIssue 1 April 2005 157 Image ElementsThe 4625SW display has a higher pixel density, and supports rendering of both grayscale W
Web Browser for the 4625SW IP Telephone158 4600 Series IP Telephones Application Programmer Interface (API) Guide The 4625SW Web browser follows the
WML Tags and AttributesIssue 1 April 2005 159 <do> tags are rendered as softkey labels on the bottom line of the display. <do> tags are s
About This Guide16 4600 Series IP Telephones Application Programmer Interface (API) Guide Related DocumentationAvaya Documents● 4600 Series IP Teleph
Web Browser for the 4625SW IP Telephone160 4600 Series IP Telephones Application Programmer Interface (API) Guide All <do> tags with the type a
WML Tags and AttributesIssue 1 April 2005 161 ● <onevent> tag - The onevent tag serves as a container for code that you want executed automatic
Web Browser for the 4625SW IP Telephone162 4600 Series IP Telephones Application Programmer Interface (API) Guide The template element creates code t
WML Tags and AttributesIssue 1 April 2005 163 Task Elements● <go> tag - The go element can contain one or more postfield elements. If a go elem
Web Browser for the 4625SW IP Telephone164 4600 Series IP Telephones Application Programmer Interface (API) Guide ● <noop> tag - The noop tag d
WML Tags and AttributesIssue 1 April 2005 165 Input Elements● <input> tag supported - The input tag specifies a point where the user is prompte
Web Browser for the 4625SW IP Telephone166 4600 Series IP Telephones Application Programmer Interface (API) Guide The value attribute takes precedenc
WML Tags and AttributesIssue 1 April 2005 167 When a given character is selected, that character is immediately replaced with an asterisk. For exampl
Web Browser for the 4625SW IP Telephone168 4600 Series IP Telephones Application Programmer Interface (API) Guide The user makes a selection as follo
WML Tags and AttributesIssue 1 April 2005 169 Variable Elements● <setvar> tag - There are no visual rendering implications with this tag.● <
Issue 1 April 2005 17 Chapter 1: IP Telephone InterfacesOverviewFigure 1 shows a typical system-wide network diagram that includes Avaya IP Telephones
Web Browser for the 4625SW IP Telephone170 4600 Series IP Telephones Application Programmer Interface (API) Guide For convenience, here are a few of
Image SupportIssue 1 April 2005 171 JPEG ImagesIn addition to WBMP, the 4625SW’s Web browser supports renderings of JPEG images. JPEG stands for the
Web Browser for the 4625SW IP Telephone172 4600 Series IP Telephones Application Programmer Interface (API) Guide Scrolling Through ImagesUsers can s
Image SupportIssue 1 April 2005 173 Images can be a part of a link and be selectable. An image inside an <a> or an <anchor> tag can be se
Web Browser for the 4625SW IP Telephone174 4600 Series IP Telephones Application Programmer Interface (API) Guide The Image Area is the screen area t
Support for Cascading Style SheetsIssue 1 April 2005 175 Number of Images SupportedA maximum of 16 images can be displayed per card, in either the mi
Web Browser for the 4625SW IP Telephone176 4600 Series IP Telephones Application Programmer Interface (API) Guide Cascading Order If more than one st
Issue 1 April 2005 177 Table 17 shows which WML tags are parent and which tags inherit properties. Table 17: WML Inheritance Table Col1 Col2 Col3 C
178 4600 Series IP Telephones Application Programmer Interface (API) Guide go postfield setvar img prev setvar refresh setvar br do go postfield
Issue 1 April 2005 179 setvar noop prev setvar refresh setvar option onevent go postfield setvar noop prev setvar refresh setvar head access
IP Telephone Interfaces18 4600 Series IP Telephones Application Programmer Interface (API) Guide Existing InterfacesAvaya IP Telephones accept the in
180 4600 Series IP Telephones Application Programmer Interface (API) Guide setvar noop prev setvar refresh setvar Table 17: WML Inheritance Table
Support for Cascading Style SheetsIssue 1 April 2005 181 Table 18 provides a list of CSS2-affected WML tags. Applicable tags are indicated by a Yes.
Web Browser for the 4625SW IP Telephone182 4600 Series IP Telephones Application Programmer Interface (API) Guide CSS2 SpecificationsThe browser supp
Support for Cascading Style SheetsIssue 1 April 2005 183 CSS Background PropertiesThe Background properties control an element’s background color, se
Web Browser for the 4625SW IP Telephone184 4600 Series IP Telephones Application Programmer Interface (API) Guide Code Examples<wml> Example wi
Support for Cascading Style SheetsIssue 1 April 2005 185 <card> ExampleThe <wml> tag and the first <card> tag have CSS2 style attri
Web Browser for the 4625SW IP Telephone186 4600 Series IP Telephones Application Programmer Interface (API) Guide <p> tag ExampleThis example s
Support for Cascading Style SheetsIssue 1 April 2005 187 Another <p> tag ExampleThis example illustrates using the background-color specified i
Web Browser for the 4625SW IP Telephone188 4600 Series IP Telephones Application Programmer Interface (API) Guide First <a> tag ExampleCSS2 pro
Support for Cascading Style SheetsIssue 1 April 2005 189 Second <a> tag ExampleThe CSS attributes for the <a> tag are inherited from its
Existing InterfacesIssue 1 April 2005 19 TAPI: This is a Telephony Application Programmer’s Interface. TAPI is primarily used for call control applic
Web Browser for the 4625SW IP Telephone190 4600 Series IP Telephones Application Programmer Interface (API) Guide Third <a> tag ExampleIn this
Support for Cascading Style SheetsIssue 1 April 2005 191 <do> tag ExampleCSS2 properties for a <do> tag are inherited from its parent <
Web Browser for the 4625SW IP Telephone192 4600 Series IP Telephones Application Programmer Interface (API) Guide CSS2 Color Image Support ExamplesIn
Support for Cascading Style SheetsIssue 1 April 2005 193 <do> tag image support for softkeysTo render JPEG or WBMP images in the softkey area,
Web Browser for the 4625SW IP Telephone194 4600 Series IP Telephones Application Programmer Interface (API) Guide The code example that follows embed
Colors SpecificationIssue 1 April 2005 195 Colors SpecificationProperties that set colors accept the standard 16 HTML 4.0 color keywords (color=”yell
Web Browser for the 4625SW IP Telephone196 4600 Series IP Telephones Application Programmer Interface (API) Guide Table 19: Supported Colors and Corr
Colors SpecificationIssue 1 April 2005 197 Table 19: Supported Colors and Corresponding Hexadecimal Coding (continued)2 of 2
Web Browser for the 4625SW IP Telephone198 4600 Series IP Telephones Application Programmer Interface (API) Guide Table 20: Supported Colors by Name
Colors SpecificationIssue 1 April 2005 199 Table 20: Supported Colors by Name and Hex Coding (continued)2 of 4
Copyright 2005, Avaya Inc.All Rights ReservedNoticeEvery effort was made to ensure that the information in this document was complete and accurate at
IP Telephone Interfaces20 4600 Series IP Telephones Application Programmer Interface (API) Guide
Web Browser for the 4625SW IP Telephone200 4600 Series IP Telephones Application Programmer Interface (API) Guide Table 20: Supported Colors by Name
Colors SpecificationIssue 1 April 2005 201 Table 20: Supported Colors by Name and Hex Coding (continued)4 of 4
Web Browser for the 4625SW IP Telephone202 4600 Series IP Telephones Application Programmer Interface (API) Guide
Issue 1 April 2005 203 IndexIndexNumerical4610SW, 4620/4620SW, 4621SW, and 4622SW IP TelephonesAnchor Elements . . . . . . . . . . . . .
204 4600 Series IP Telephones Application Programmer Interface (API) Guide IndexDisplay PushBarge Priority. . . . . . . . . . . . . . .
Issue 1 April 2005 205 IndexPush Feature Description. . . . . . . . . . . . . . 22Push Flow Process . . . . . . . . . . .
206 4600 Series IP Telephones Application Programmer Interface (API) Guide IndexUURI Examples, for Push Interface Validation. . . . . 61VValida
Issue 1 April 2005 21 Chapter 2: Push Interface OverviewIntroductionPush is the ability for an application to send content to the Web browser, to the
Push Interface Overview22 4600 Series IP Telephones Application Programmer Interface (API) Guide Push Feature DescriptionThe Push interface offers se
Push ArchitectureIssue 1 April 2005 23 The Push/Pull Process – A Two-Step View The Push framework is a two-step process - a “push” operation followed
Push Interface Overview24 4600 Series IP Telephones Application Programmer Interface (API) Guide Push Message FlowThis section describes the step-by-
Push ArchitectureIssue 1 April 2005 25 Figure 4: Push FlowStep 4 – Request LaunchedOnce the URL is verified as a Trusted Push Server, the Push Agent
Push Interface Overview26 4600 Series IP Telephones Application Programmer Interface (API) Guide About the Push Agent The 4600 Series IP Telephones (
Push Agent - HTTP POST AddressIssue 1 April 2005 27 Push Agent - HTTP POST AddressThe HTTP POST address (URL) for the IP telephone where a Push reque
Push Interface Overview28 4600 Series IP Telephones Application Programmer Interface (API) Guide Topline push type - Text can be pushed to the toplin
Issue 1 April 2005 29 Chapter 3: Creating Push MessagesIntroductionThis chapter covers the details involved in setting up Push Messages for each type
Issue 1 April 2005 3 About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9About this Document
Creating Push Messages30 4600 Series IP Telephones Application Programmer Interface (API) Guide AlertsA Display Push Message can be sent using alerts.
The Display Push TypeIssue 1 April 2005 31 Successful Push ResponseIf the phone is in a pushable state, the Push Agent sends the Push Initiator the fo
Creating Push Messages32 4600 Series IP Telephones Application Programmer Interface (API) Guide If the Web is in “text edit mode” a subsequent normal
The Display Push TypeIssue 1 April 2005 33 Display Push XML MessagesThis section describes how to send a Display push using XML messages. Display Push
Creating Push Messages34 4600 Series IP Telephones Application Programmer Interface (API) Guide Using the <postfield> TagThe IP telephones’ Web
The Display Push TypeIssue 1 April 2005 35 Display Push Example 2:Using our previous hotel example, the hotel is ready to serve lunch and wants to sen
Creating Push Messages36 4600 Series IP Telephones Application Programmer Interface (API) Guide Push Content (PC)The Display push type’s Push Content
The Topline Push TypeIssue 1 April 2005 37 The IP telephone’s XML parser parses the WML file. Depending on the priorities and state of the telephone,
Creating Push Messages38 4600 Series IP Telephones Application Programmer Interface (API) Guide AlertsA Topline Push Message can be sent with alerts.
The Topline Push TypeIssue 1 April 2005 39 Priorities and StatesTopline Push Content is sent with one of two priorities: normal or barge. Normal prior
Contents4 4600 Series IP Telephones Application Programmer Interface (API) Guide Push Agent - HTTP POST Address. . . . . . . . . . . . .
Creating Push Messages40 4600 Series IP Telephones Application Programmer Interface (API) Guide Normal PriorityWhen the mode attribute in the <Push
The Topline Push TypeIssue 1 April 2005 41 Topline Push XML MessagesThis section describes how to send a Topline push with XML messages. Use the Stock
Creating Push Messages42 4600 Series IP Telephones Application Programmer Interface (API) Guide Using the <postfield> TagThe IP telephones’ Web
The Topline Push TypeIssue 1 April 2005 43 Topline Push Example 2:Using our previous stock alert example, the price of the AV is reaching the $15 pric
Creating Push Messages44 4600 Series IP Telephones Application Programmer Interface (API) Guide Push AgentOnce a Push Message is received from the Pus
The Topline Push TypeIssue 1 April 2005 45 Using the <Topline> tagThe <Topline> tag consists of the actual text message to display on the
Creating Push Messages46 4600 Series IP Telephones Application Programmer Interface (API) Guide The Audio Push TypeUse an Audio push when you need to
The Audio Push TypeIssue 1 April 2005 47 Audio Push Example:An Audio push example could be a hotel wake-up message a guest schedules from the room. Th
Creating Push Messages48 4600 Series IP Telephones Application Programmer Interface (API) Guide Normal PriorityWhen the mode attribute in the <Push
The Audio Push TypeIssue 1 April 2005 49 Audio Push XML MessagesThis section describes how to send an Audio push with XML messages.Audio Push Message
ContentsIssue 1 April 2005 5 Audio Push Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Prior
Creating Push Messages50 4600 Series IP Telephones Application Programmer Interface (API) Guide RTP PortAn RTP port is needed to stream audio to the t
The Audio Push TypeIssue 1 April 2005 51 The code excerpt associated with Audio Push Example: (the hotel wake-up message), which will be sent as part
Creating Push Messages52 4600 Series IP Telephones Application Programmer Interface (API) Guide Each <Response> can contain only one <Audio&g
The Audio Push TypeIssue 1 April 2005 53 Note:Note: For example, if an audio stream originator wanted to explicitly stop an audio stream the following
Creating Push Messages54 4600 Series IP Telephones Application Programmer Interface (API) Guide The Subscribe Push TypeThe Subscribe push is used as a
The Subscribe Push TypeIssue 1 April 2005 55 Priorities and StatesNormal and barge priorities are not applicable to the Subscribe push type.The Subscr
Creating Push Messages56 4600 Series IP Telephones Application Programmer Interface (API) Guide Using the <postfield> TagThe IP telephone’s Web
The Subscribe Push TypeIssue 1 April 2005 57 Subscribe Push Content (PC)The Push Content for the Subscribe push type must be an XML file. This XML fil
Creating Push Messages58 4600 Series IP Telephones Application Programmer Interface (API) Guide
Issue 1 April 2005 59 Chapter 4: Push AdministrationIntroductionThis chapter covers the administrative actions required for the Push interface to wor
Contents6 4600 Series IP Telephones Application Programmer Interface (API) Guide Chapter 5: Troubleshooting the Push Interface . . . . . . . .
Push Administration60 4600 Series IP Telephones Application Programmer Interface (API) Guide Trusted Push Server List (TPSLIST)Depending upon the TPS
Validation ScenariosIssue 1 April 2005 61 Validation ScenariosTable 5: URI Examples Validation String(Validation string Interpreted as)Pushed URI stri
Push Administration62 4600 Series IP Telephones Application Programmer Interface (API) Guide Recommendations: If the domain from Table 5: URI Example
Subscription ServiceIssue 1 April 2005 63 Subscriber ServiceUsing the Push Subscription Service, the phone makes the following values known to the tru
Push Administration64 4600 Series IP Telephones Application Programmer Interface (API) Guide Subscription List (SUBSCRIBELIST)This list specifies the
Subscription List (SUBSCRIBELIST)Issue 1 April 2005 65 Subscription UpdateUse the Subscribe push type to make an asynchronous request to a phone to re
Push Administration66 4600 Series IP Telephones Application Programmer Interface (API) Guide
Issue 1 April 2005 67 Chapter 5: Troubleshooting the Push InterfaceAvaya HTTP Header Extensions (x-Push-Status Codes)The Push Agent sends a response
Troubleshooting the Push Interface68 4600 Series IP Telephones Application Programmer Interface (API) Guide 205 “Not In Push State: Push Aborted”The P
HTTP Error MessagesIssue 1 April 2005 69 HTTP Error MessagesThe following standard HTTP Error Messages will be supported. Status codes starting with
ContentsIssue 1 April 2005 7 Chapter 7: Web Browser for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP Telephones . . . . . . . . . . . . . .
Troubleshooting the Push Interface70 4600 Series IP Telephones Application Programmer Interface (API) Guide 415 Unsupported Media TypeThe server refus
Issue 1 April 2005 71 Chapter 6: About The Web BrowserIntroductionThis chapter provides general information about and requirements for developing Web
About The Web Browser72 4600 Series IP Telephones Application Programmer Interface (API) Guide Figure 12: Schematic View of the Standard Web Browser
Web Browser NavigationIssue 1 April 2005 73 The Web browser renders pages with spaces before the XML prolog. The strict rules of XML specify that pag
About The Web Browser74 4600 Series IP Telephones Application Programmer Interface (API) Guide Icons for Navigation ControlIcons associated with (def
Web Browser NavigationIssue 1 April 2005 75 Table 8: Navigation Control Icons4625SWAll Other Phones ExplanationPage Up. If more text exists than can
About The Web Browser76 4600 Series IP Telephones Application Programmer Interface (API) Guide Use the Focus Up and Focus Down Feature buttons (singl
Web Browser NavigationIssue 1 April 2005 77 Users can move up and down, bringing displayed text into focus as they choose. This is a unique WML featu
About The Web Browser78 4600 Series IP Telephones Application Programmer Interface (API) Guide Tags with Titles and Corresponding Top Line Defaults:A
Enabling Text EntryIssue 1 April 2005 79 LinksRules for links within a page are simplified for development purposes:● A maximum of one link can be di
Contents8 4600 Series IP Telephones Application Programmer Interface (API) Guide Configuring the Directory Application Details Administration Screen.
About The Web Browser80 4600 Series IP Telephones Application Programmer Interface (API) Guide 8. On-hook keypad dialing to make a phone call is not
Text Editing ModesIssue 1 April 2005 81 Text Editing ModesWhen a text entry area is enabled, these softkey labels display centered above the actual s
About The Web Browser82 4600 Series IP Telephones Application Programmer Interface (API) Guide Input ModesThe default entry mode is alpha (lower case
Text Editing ModesIssue 1 April 2005 83 Figure 15: Text Editing Symbol Screen TwoFigure 16: Text Editing Symbol Screen ThreeUse the Feature button as
About The Web Browser84 4600 Series IP Telephones Application Programmer Interface (API) Guide Character Set SupportCharacter set support differs dep
Call InteractionIssue 1 April 2005 85 Call InteractionThe user can make and receive calls when in a Web browser session. When users re-enter the Web
About The Web Browser86 4600 Series IP Telephones Application Programmer Interface (API) Guide The attributes xml:lang, class, and id are universal a
Wireless Telephony Applications (WTA)Issue 1 April 2005 87 Syntax ImplementationClick to Dial FunctionalityTo enable the click to dial functionality,
About The Web Browser88 4600 Series IP Telephones Application Programmer Interface (API) Guide Click-to-dial using <a> tag: <?xml version=”1
Wireless Telephony Applications (WTA)Issue 1 April 2005 89 Click-to-dial using <anchor> tag:<?xml version=”1.0”?> <!DOCTYPE wml PUBLI
Issue 1 April 2005 9 About This GuideAbout this DocumentThis document describes how to set up two optional Avaya application interfaces, the Web brow
About The Web Browser90 4600 Series IP Telephones Application Programmer Interface (API) Guide The code shows a hyperlink as Call Us on the Web page.
Wireless Telephony Applications (WTA)Issue 1 April 2005 91 Click-to-dial using <do> tag (softkey):<?xml version=”1.0”?> <!DOCTYPE wml
About The Web Browser92 4600 Series IP Telephones Application Programmer Interface (API) Guide Add to Speed Dial FunctionalityAdd to Speed Dial is re
Wireless Telephony Applications (WTA)Issue 1 April 2005 93 The generated code is rendered as the following diagram:The code adds the entry to the spe
About The Web Browser94 4600 Series IP Telephones Application Programmer Interface (API) Guide Support for HTTP AuthenticationAn authentication input
Error TonesIssue 1 April 2005 95 Error TonesError tones are consistent with other applications. When a labeled button is pressed but the button’s fun
About The Web Browser96 4600 Series IP Telephones Application Programmer Interface (API) Guide User-Agent Header String (4610SW IP Telephones)Identif
Error MessagesIssue 1 April 2005 97 User-Agent Header String (4625SW IP Telephones)Identify the 4625SW Web browser using the following User-Agent str
About The Web Browser98 4600 Series IP Telephones Application Programmer Interface (API) Guide When the client server receives a Status Code 431, it
Summary Of WML Tags and AttributesIssue 1 April 2005 99 Summary Of WML Tags and AttributesTable 11: Summary Of WML Tags And Attributes Tag Attribute
Related products and manuals for Software Avaya 4600 Series
(90 pages)
(252 pages)
(168 pages)
(218 pages)
(180 pages)
© 2020, manymanuals.com. All rights reserved. | 0.068 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals