Sip Enhancement - Alcatel-Lucent OmniPCX Enterprise Manual

Hide thumbs Also See for OmniPCX Enterprise:
Table of Contents

Advertisement

INSTALLATION PROCEDURE FOR VERSION
J1.410.34.c – RELEASE 10.0
2.2.4.

SIP Enhancement

2.2.4.1. New SIP improvement for interworking with Open Touch Solution
As of Release 10.0, new SIP improvements allow the interworking of OmniPCX Enterprise in the new
Open Touch Solution.
2.2.4.2. SIP Trunk enhancement: CLI display with From header, even if P-Asserted-ID
header is available (Incoming call)
Up to R9.1, Call Presentation mechanism does not scope with all situations because all carriers do
not use the headers in the same way.
For example, some carriers give the user number in the From header and the installation number in
the P-Asserted-ID header. This means, that in some cases, the From header should be used to
provide the calling number even if the P-Asserted-ID header is present.
As of Release 10.0, three parameters allow to manage the way the headers are used for calling
presentation.
The three parameters, configured for each external gateway, are:
• P-Asserted-ID in Calling Number
• Trusted P-Asserted-ID header
• Trusted From header
2.2.4.3. SIP Trunk enhancement: Service route header (RFC 3608) and Path header (RFC
3327)
When an external gateway registers, the Supported header of the REGISTER message includes the
path header in the list of the supported headers.
The 200 OK responses sent by the remote proxy may contain a Service Route header containing a
list of URLs.
As of Release 10.0, OmniPCX Enterprise stores the list of URLs received.
The list of URLs stored for an external gateway is used for outbound calls: each INVITE or OPTIONS
method includes one Route header for each URL stored.
2.2.4.4. SIP Trunk enhancement: Faster overflow on no answer to INVITE, REGISTER and
OPTIONS method
Up to Release 10.0, the classical re-transmission procedure defined in the RFC 3261 applies when
SIP requests sent by OmniPCX Enterprise are not answered by remote party.
As a consequence, it takes 32s before OmniPCX Enterprise considers that no response has been
received.
When REGISTER/OPTIONS methods are used to supervise the availability of an external gateway,
this re-transmission time leads to a slow overflow to a backup/alternate gateway for outgoing calls.
Another situation is slow overflow from one ARS route to another when an outgoing INVITE to a SIP
external gateway is not answered.
Ed. 02 / 22 June 2011
OmniPCX Enterprise
5
NEW HARDWARE AND FEATURES
APPENDIX 1
TC1449

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents

Save PDF