Avaya IPO R9 IP500 T1 ADD 2CH ADI LIC 275639 Manuel D’Utilisation
Codes de produits
275639
Product Description
IP Office 9.0
IP Office 9.0
© 2014 AVAYA All rights reserved.
Page 276
Issue 27.02.0 (Monday, January 06, 2014)
SIP Trunks
SIP Trunk enhancements have been included that allow service providers to continue to broaden their SIP
trunk offerings.
trunk offerings.
SME customers are increasingly evaluating and adopting SIP trunks. IP Office responds to these market
trends, with several new SIP trunk capabilities, designed to simplify and address a wider set of implementation
scenarios.
trends, with several new SIP trunk capabilities, designed to simplify and address a wider set of implementation
scenarios.
The IP Office architecture brings the benefits of Session Initiated Protocol (SIP) to the enterprise customer
through SIP Service Providers. To help enable the SIP Service Provider, Avaya offers a SIP Compliance
Testing Program (GSSCP) that will validate the operation of the IP Office solution with the Service Provider’s
SIP trunk offering.
through SIP Service Providers. To help enable the SIP Service Provider, Avaya offers a SIP Compliance
Testing Program (GSSCP) that will validate the operation of the IP Office solution with the Service Provider’s
SIP trunk offering.
For more information about Avaya’s SIP Compliance Testing Program (GSSCP), please refer to the following
link:
link:
SIP Trunk Capabilities
SIP From in Clear when privacy is requested
Many SIP Service Providers require that the From field contain account information for outbound calls. SIP
Lines will now support the Send From in Clear field. IP Office will send the caller ID in the clear in the SIP
From header for outbound anonymous calls. The default of Send From in Clear is disabled. This new
capability is configurable on a per line basis.
Lines will now support the Send From in Clear field. IP Office will send the caller ID in the clear in the SIP
From header for outbound anonymous calls. The default of Send From in Clear is disabled. This new
capability is configurable on a per line basis.
SIP User-Agent header included to identify IPO in SIP trunk calls
IP Office identifier will now be included in the SIP header. This addition will enhance troubleshooting
capabilities when additional identification is required. The identifier will be configurable as the system
administrator is permitted to enter identifying (User-Agent) information into the SIP messages. User-Agent
headers are generated for IP Office initiative messages such as INVITE, OPTIONS, CANCEL, etc. This feature
will also support enhanced SIP Server header information in all 18x response messages such as Trying,
Ringing, etc.
capabilities when additional identification is required. The identifier will be configurable as the system
administrator is permitted to enter identifying (User-Agent) information into the SIP messages. User-Agent
headers are generated for IP Office initiative messages such as INVITE, OPTIONS, CANCEL, etc. This feature
will also support enhanced SIP Server header information in all 18x response messages such as Trying,
Ringing, etc.
IP Office can send UPDATE without SDP for session refresh over SIP trunks
The addition of this new audit mechanism will validate that the connection is in place. If not, the IP Office will
free the trunk, thereby improving network resource utilization.
free the trunk, thereby improving network resource utilization.
IP Office can now negotiate RFC 4028 for session refresh over SIP Trunks. It can either be the refresher or will
expect UPDATE messages from remote party, depending on negotiation. The session will be terminated if IP
Office doesn’t receive an UPDATE/200 OK message for session refresh. In earlier IP Office releases, RE-INVITE
messages were used as the refresher. IP Office is now RFC 4028-compliant. By default, UPDATE Supported is
not enabled and IP Office will send RE-INVITE messages for session refresh. If UPDATE Supported is Allow or
Auto and the other party supports UPDATE (specified in the "Allow" header), IP Office will send UPDATE
messages for session refresh.
expect UPDATE messages from remote party, depending on negotiation. The session will be terminated if IP
Office doesn’t receive an UPDATE/200 OK message for session refresh. In earlier IP Office releases, RE-INVITE
messages were used as the refresher. IP Office is now RFC 4028-compliant. By default, UPDATE Supported is
not enabled and IP Office will send RE-INVITE messages for session refresh. If UPDATE Supported is Allow or
Auto and the other party supports UPDATE (specified in the "Allow" header), IP Office will send UPDATE
messages for session refresh.
From header shall be used by IPO as calling identity whatever presence of P-Asserted-
Identity (PAI)
Identity (PAI)
Although service providers typically use PAI for Caller ID delivery, additional flexibility is sometimes required.
IP Office answers this requirement by providing an option to use the From header. The administrator will have
the option of selecting which Caller ID information to use for displaying on the user equipment. By default, IP
Office will display PAI caller ID present in the SIP/Tel URI consistent with the behaviour of previous releases. If
the checkbox is set, the caller ID present in the From SIP URI will be used instead.
IP Office answers this requirement by providing an option to use the From header. The administrator will have
the option of selecting which Caller ID information to use for displaying on the user equipment. By default, IP
Office will display PAI caller ID present in the SIP/Tel URI consistent with the behaviour of previous releases. If
the checkbox is set, the caller ID present in the From SIP URI will be used instead.
Turn off OPTIONS if registration can do keep-alive
Some service provider implementations utilize registration to maintain the status of lines instead of OPTIONS.
OPTIONS requests are sent to regularly check if the SIP Line is in service. It is possible to send frequent
REGISTER requests to keep the line in service rather than using OPTIONS.
OPTIONS requests are sent to regularly check if the SIP Line is in service. It is possible to send frequent
REGISTER requests to keep the line in service rather than using OPTIONS.
Fax G711 pass through mode including SG3
Super G3 fax machines utilize higher speeds than normal G3 or earlier fax machines. In order to broaden IP
Office fax support, IP Office now supports Super G3 fax transmission.
Office fax support, IP Office now supports Super G3 fax transmission.
This includes Fax Transport support for sending and receiving of faxes over G.711. IP Office will detect fax
tones in G.711 calls between Super G3 fax machines.
tones in G.711 calls between Super G3 fax machines.
IP Office should support nonce-caching for proactive inserting SIP credentials in
outgoing SIP requests
outgoing SIP requests
Traditionally, IP Office sends the Authorization/Proxy-Authorization only if the network specifically requests this
for one IP Office request. Now, IP Office will cache the nonce received with the challenge or with the
Authentication-Info header. IP Office will use the information for proactively inserting the SIP credentials in all
the outgoing SIP messages.
for one IP Office request. Now, IP Office will cache the nonce received with the challenge or with the
Authentication-Info header. IP Office will use the information for proactively inserting the SIP credentials in all
the outgoing SIP messages.