_________________________________________________________________________________
_________________________________________________________________________________
Universal Network Terminal TAU-32M.IP 95
requests after subscriber registration, and will only process NOTIFY requests received from IMS,
which are used for service management;
Explicit subscription to IMS services
– in this subscription option, gateway will send SUBSCRIBE
requests after subscriber registration, and upon successful subscription, will process NOTIFY
requests received from IMS, which are used for service management.
When
'Enable IMS'
setting is enabled,
'Process flash'
,
'Call waiting'
and
'Hot line'
parameters will
not be processed in subscriber port settings, as these services are managed by IMS server.
–
XCAP name for three-party conference –
a name sent in XCAP attachment for '3-party conference' service
management;
–
XCAP name for hotline
– a name sent in XCAP attachment for 'Hotline' service management;
–
XCAP name for call waiting
– a name sent in XCAP attachment for 'Call waiting' service management;
–
XCAP name for call hold
– a name sent in XCAP attachment for 'Call hold' service management;
–
XCAP name for explicit call transfer –
a name sent in XCAP attachment for 'Explicit call transfer' service
management.
For forced registration renewal of subscriber ports with the current SIP profile, click the
Re-registration
button.
Use the
Defaults
button to set default parameters (the figure below shows default values).
To apply changes, click the
Submit Changes
button; to discard all changes
,
click the
Undo All Changes
button;
to save changes, click the
Save
button.
5.1.2.2.3.1
Provisional response setting operation
SIP protocol defines two types of responses for connection initiating request (INVITE) – provisional and final.
2хх, 3хх, 4хх, 5хх and 6хх-class responses are final and their transfer is reliable, with ACK message confirmation. 1хх-
class responses, except for '100 Trying' response, are provisional, without confirmation (rfc3261). These responses
contain information on the current INVITE request processing step, therefore loss of these responses is
unacceptable. Utilization of reliable provisional responses is also stated in SIP (rfc3262) protocol and defined by
'100rel' tag presence in the initiating request. In this case, provisional responses are confirmed with PRACK message.
Setting operation for outgoing communications:
–
supported
– send the following tag in 'INVITE' request–supported: 100rel. In this case, communicating
gateway may transfer provisional responses reliably or unreliably–as it deems fit;
–
required
– send the following tags in 'INVITE' request–supported: 100rel and required: 100rel. In this case,
communicating gateway should perform reliable transfer of provisional replies. If communicating gateway
does not support reliable provisional responses, it should reject the request with message 420 and provide
the following tag–unsupported: 100rel, In this case, the second INVITE request will be sent without the
following tag–required: 100rel;
–
off
– do not send any of the following tags in INVITE request–supported: 100rel and required: 100rel. In
this case, communicating gateway will perform unreliable transfer of provisional replies.
Setting operation for incoming communications:
–
supported, required
–when the following tag is received in 'INVITE' request–supported: 100rel, or required: