advertisement
The Push Feature
●
Audio Messages (RTP) can be pushed. Pushed audio messages can drive the telephone off-hook, if necessary and play the pushed message through the telephone’s Speaker. If the audio push has barge-in priority, the audio message is presented to the user, even if the user is on a call. In this latter case, the far-end is automatically placed on Hold and does not hear the pushed audio message.
A given push can include any or all of the three content forms, but can have only one priority.
You can optionally accompany each push with notification tones to draw the user’s attention to the phone and to the pushed content.
Push Priorities
Barge-in pushes, as the name implies, are meant for information important to get to the user. An example of a barge-in push might be an audio message alerting users that the building is closing because of inclement weather. You can accompany that message with a Web page detailing weather conditions. There are very few circumstances that can prevent barge-in pushes from being presented to the user. Of course, network conditions can prevent actual delivery of the pushed content.
Use normal pushes for less-essential or less time-critical information. An example might be
“Mary has birthday cake in her office.” A normal push might or might not be presented to the user. For example, a normal audio push is not presented to a user already on a call. Or, a normal text message would not display until a higher priority message completes.
For More Information on Push
The specifications and interactions of pushed content are beyond the scope of this document.
The 4600 Series IP Telephones Application Programmer Interface (API) Guide provides detailed information about developing Push content and administering the Push feature. Find the API on the Avaya support Web site, http://www.avaya.com/support . Further information, including sample applications, is also available in a Software Developer Toolkit on the Avaya support Web site.
For more detailed assistance in developing applications, also visit the Solutions Directory on
Avaya’s Developer Connect Web page ( www.devconnectprogram.com
) and follow the Find a
Solution link. The Directory has a list of companies you can work with to develop applications.
The Solutions Directory lists all current Developer Connection Program Members, with whom you can work to develop applications, and their innovative solutions. The members in this directory have all been approved in the program and are compliance-tested to assure customer satisfaction.
146 4600 Series IP Telephone Release 2.2 LAN Administrator Guide
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 9 About This Guide
- 9 Intended Audience
- 10 Document Organization
- 11 Change History
- 12 What’s New in Release 2.2
- 12 Terms Used in This Guide
- 14 Conventions Used in This Guide
- 14 Symbolic Conventions
- 14 Typographic Conventions
- 15 Online Documentation
- 15 Related Documents
- 18 IETF Documents
- 19 ITU Documents
- 20 ISO/IEC, ANSI/IEEE Documents
- 20 Customer Support
- 21 Introduction
- 21 Overview of Voice over IP (VoIP)
- 21 Data and Voice Network Similarities
- 22 Delay and Jitter
- 22 Tandem Coding
- 23 Voice Coding Standards
- 23 H.323 Standard
- 23 DHCP
- 23 TFTP
- 24 HTTP
- 24 DNS
- 24 NAT
- 25 QoS
- 25 SNMP
- 26 Network Assessment
- 27 TCP/UDP Port Utilization
- 31 Suggestions for Installation and Configuration
- 31 Reliability and Performance
- 32 IP Address Lists and Station Number Portability
- 33 Security
- 34 4600 Series IP Telephones
- 34 Dual Connection Architecture
- 34 Single Connection Architecture
- 34 Registration and Authentication
- 34 Software
- 35 WAN Considerations
- 35 DHCP and File Servers
- 36 Initialization Process
- 36 Step 1: Telephone to Network
- 36 Step 2: DHCP Server to Telephone
- 36 Step 3: Telephone and File Server
- 37 Step 4: Telephone and the Avaya Media Server
- 39 Introduction
- 39 Hardware Requirements
- 40 Additional Hardware Requirements
- 41 Software Requirements
- 43 Introduction
- 46 Administering 4600 Series IP Telephones on Avaya Media Servers
- 46 DEFINITY Releases 9, 9.5, 10, and Avaya Communication Manager Software Release 1.1+
- 47 DEFINITY Release 8.4
- 47 DHCP and File Servers
- 47 Software Checklist
- 48 Required Network Information
- 49 DHCP
- 49 Choosing a DHCP Configuration
- 49 DHCP Software Alternatives
- 50 DHCP Generic Setup
- 53 Windows NT 4.0 DHCP Server
- 53 Verifying the Installation of the DHCP Server
- 54 Initial Configuration
- 54 Creating a DHCP Scope for the IP Telephones
- 55 Editing Custom Options
- 56 Adding the DHCP Option
- 56 Activating the Leases
- 57 Verifying Your Configuration
- 58 Windows 2000 DHCP Server
- 58 Verifying the Installation of the DHCP Server
- 60 Adding DHCP Options
- 61 Activating the New Scope
- 62 TFTP
- 62 TFTP Generic Setup
- 63 Avaya TFTP (Suite Pro)
- 63 TFTP Server on S8300 Media Server
- 66 HTTP
- 66 HTTP Generic Setup
- 67 4600 Series IP Telephone Scripts and Application Files
- 69 Choosing the Right Application File and Upgrade Script File
- 71 Contents of the Upgrade Script
- 73 Contents of the Settings File
- 73 The GROUP System Value
- 74 QoS
- 74 IEEE 802.1D and 802.1Q
- 75 DIFFSERV
- 76 UDP Port Selection
- 77 Network Audio Quality Display on 4600 Series IP Telephones
- 78 RSVP and RTCP
- 79 VLAN Considerations
- 80 Administering Options for the 4600 Series IP Telephones
- 84 DNS Addressing
- 84 Customizing the Site-Specific Option Number (SSON)
- 84 Entering Options Using the Telephone Dialpad
- 85 Enhanced Local Dialing
- 87 Customizing the 4630/4630SW IP Telephone
- 90 4630/4630SW Backup/Restore
- 91 Call Log Archive
- 92 Customizing 4610SW, 4620/4620SW, 4621SW, 4622SW, and 4625SW IP Telephones
- 95 The Application Status Flag (APPSTAT)
- 97 Backup/Restore for 4610SW, 4620/4620SW, 4621SW, 4622SW and 4625SW IP Telephones
- 99 Introduction
- 99 Error Conditions
- 106 The Clear Administrative Option
- 108 The Reset Administrative Option
- 108 Reset System Values
- 110 Restart the Telephone
- 111 The View Administration Option
- 113 Error Messages
- 118 Troubleshooting the 4601 IP Telephone
- 123 Downloading the Avaya - 46xx IP Telephone MIB
- 125 Introduction
- 126 General Background
- 126 Browser Features and Behavior
- 127 Document Skeleton
- 127 Content-Based Style
- 128 Logical Style
- 129 Physical Style
- 129 Physical Spacing and Layout
- 130 Lists and Tables
- 130 Lists
- 130 Tables
- 131 Images
- 132 Links
- 132 Frames
- 133 Forms
- 134 Character Entities
- 134 Colors
- 134 Fonts
- 135 Cookies
- 135 Design Guidelines
- 135 Fixed-Width Objects
- 136 Images
- 136 Frames
- 137 Fonts
- 137 Maintaining Context
- 138 User Interaction
- 138 Click-to-Dial Functionality
- 141 Introduction
- 143 Introduction
- 145 Introduction
- 145 Push Content
- 146 Push Priorities
- 146 For More Information on Push
- 147 Numerical
- 147 A
- 147 B
- 147 C
- 148 D
- 148 E
- 148 F
- 148 G
- 148 H
- 148 I
- 148 M
- 148 N
- 148 O
- 148 P
- 148 Q
- 148 R
- 149 S
- 149 T
- 149 U
- 149 V
- 149 W