Avaya IPO R9 TELEWORKER 1 PLDS LIC 273947 Manuel D’Utilisation
Codes de produits
273947
Product Description
IP Office 9.0
IP Office 9.0
© 2014 AVAYA All rights reserved.
Page 21
Issue 27.02.0 (Monday, January 06, 2014)
RFC2833 Default Payload Configuration Option
It is now possible to configure the default RFC2833 payload to be used when initiating SIP calls. The
enhancement addresses the situation where some devices and networks cannot negotiate the dynamic payload
type for RFC2833, and insist on a value different from the IP Office default of 101.
enhancement addresses the situation where some devices and networks cannot negotiate the dynamic payload
type for RFC2833, and insist on a value different from the IP Office default of 101.
Session Refresh Enhancements
IP Office will now have the ability to initiate the use of SIP Session Timers on SIP/SM Trunks, whether the
other end , supports it or not. SIP Calls between IP Office endpoints can now make use of this mechanism to
detect the loss of SIP sessions caused by failure in the network path or remote endpoint, freeing up resources
appropriately.
other end , supports it or not. SIP Calls between IP Office endpoints can now make use of this mechanism to
detect the loss of SIP sessions caused by failure in the network path or remote endpoint, freeing up resources
appropriately.
Enhancements supported on the France2 locale
Direct Early Media Support plus UPDATE with SDP
Early Media includes audio (e.g. ring back, remote tones or announcements) heard before the far end answers.
Early Media is considered to be Direct when the media is sent directly from one IP endpoint to the other rather
than being anchored by the IP Office. In some call scenarios (e.g. blind transfer) a SIP UPDATE must be sent
to the far end to inform it of a new destination for the media stream. Using Direct Early Media can reduce
network bandwidth consumption and VCM utilization on the IP Office network.
Early Media is considered to be Direct when the media is sent directly from one IP endpoint to the other rather
than being anchored by the IP Office. In some call scenarios (e.g. blind transfer) a SIP UPDATE must be sent
to the far end to inform it of a new destination for the media stream. Using Direct Early Media can reduce
network bandwidth consumption and VCM utilization on the IP Office network.
P-Early-Media Header for Remote/Local Progress Tones
The P-Early-Media Header is used by some SIP trunk providers when there may be multiple early media
sources. SIP calls may be forked, resulting in multiple early sessions to be established, but it is not clear to
the originating party which session should take precedence. This feature allows the network to indicate which
early media to play to the caller.
sources. SIP calls may be forked, resulting in multiple early sessions to be established, but it is not clear to
the originating party which session should take precedence. This feature allows the network to indicate which
early media to play to the caller.
SIP Trunks Empty INVITE support
IP Office can now allow incoming SIP trunk calls to the IP Office without SDP in the INVITE. These (slow starts)
were formerly rejected with a 503 Service Unavailable response. The Offer/Answer model allows for an INVITE
with no SDP, but then the OFFER must present in the 200 OK, and the answer is then provided in the ACK. The
Offer/Answer model allows for an INVITE with no SDP, but then the OFFER must present in the 200 OK, and
the answer is then provided in the ACK.
were formerly rejected with a 503 Service Unavailable response. The Offer/Answer model allows for an INVITE
with no SDP, but then the OFFER must present in the 200 OK, and the answer is then provided in the ACK. The
Offer/Answer model allows for an INVITE with no SDP, but then the OFFER must present in the 200 OK, and
the answer is then provided in the ACK.
Automated On-Boarding and SSL VPN Enhancements
IP Office R8.1included the successful introduction of the new IP Office Support Services maintenance offer. To
support the offer, automated on-boarding and SSL VPN functionality was introduced in release 8.1.
support the offer, automated on-boarding and SSL VPN functionality was introduced in release 8.1.
IP Office release 9.0 builds upon the initial introduction by expanding the IP Office elements that can use the
automated on-boarding and SSL VPN connection, providing release over release updates to the inventory file
to represent new hardware elements and additional material codes required to support the evolution of the
IPOSS offering.
automated on-boarding and SSL VPN connection, providing release over release updates to the inventory file
to represent new hardware elements and additional material codes required to support the evolution of the
IPOSS offering.
Key enhancements include:
· SSL VPN manual configuration for Basic Edition through Web Manager so as to facilitate the use of SSL VPN
by Business Partners who are establishing their own SSL VPN infrastructure. In R8.1 manually configuring
SSL VPN was limited to using IP Office Manager and therefore one could not configure SSL VPN tunnels to
systems running Basic Edition.
SSL VPN was limited to using IP Office Manager and therefore one could not configure SSL VPN tunnels to
systems running Basic Edition.
· SSL/VPN Automated On-Boarding for the external Linux applications server used with IP Office. In release
8.1 these servers required manual registration which added an extra step when completing the processes
associated with establishing an IPOSS contract.
associated with establishing an IPOSS contract.
· Expanded use of the Network Address and Port Translation (NAPT) feature, introduced in release 8.1 FP1, to
work with the Linux servers thereby completing the solution coverage. With NAPT support, the SSL VPN
tunnel can be enabled to remotely access LAN devices on the private side of the IP500 v2 or the Linux
servers. An SSL VPN tunnel configured to the IP Office can now be used to remotely manage devices such
as the IP Office Unified Communication Module (UCM), the IP Office external UC applications server running
Preferred Edition or Advanced Edition, the Avaya Session Border Controller for Enterprise (ASBCE) and other
LAN devices.
tunnel can be enabled to remotely access LAN devices on the private side of the IP500 v2 or the Linux
servers. An SSL VPN tunnel configured to the IP Office can now be used to remotely manage devices such
as the IP Office Unified Communication Module (UCM), the IP Office external UC applications server running
Preferred Edition or Advanced Edition, the Avaya Session Border Controller for Enterprise (ASBCE) and other
LAN devices.
· Updates to the automated the inventory file created as part of the Automated On-Boarding to include new
hardware material codes introduced in this release. This ensures the most accurate installed base
information can be extracted from the IP Office.
information can be extracted from the IP Office.
Phone and Hardware Enhancements
96x1 H.323 Release 6.3 Phone Firmware
IP Office Release 9.0 packages the 96x1 H.323 Release 6.3 phone firmware. The following functionality is
supported with IP Office.
supported with IP Office.