AudioCodes Mediant 600 User Manual page 284

Media gateways
Hide thumbs Also See for Mediant 600:
Table of Contents

Advertisement

Parameter
Web: Enable History-Info
Header
EMS: Enable History Info
[EnableHistoryInfo]
Web/EMS: Enable Contact
Restriction
[EnableContactRestriction]
Web: Use Tgrp Information
EMS: Use SIP Tgrp
[UseSIPTgrp]
SIP User's Manual
Enables usage of the History-Info header.
[0] Disable = Disable (default)
[1] Enable = Enable
User Agent Client (UAC) Behavior:
Initial request: The History-Info header is equal to the Request
URI. If a PSTN Redirect number is received, it is added as an
additional History-Info header with an appropriate reason.
Upon receiving the final failure response, the device copies the
History-Info as is, adds the reason of the failure response to the
last entry, and concatenates a new destination to it (if an
additional request is sent).
The order of the reasons is as follows:
1. Q.850 Reason
2. SIP Reason
3. SIP Response code
Upon receiving the final response (success or failure), the device
searches for a Redirect reason in the History-Info (i.e., 3xx/4xx
SIP reason). If found, it is passed to ISDN according to the
following table:
SIP Reason Code
302 - Moved Temporarily
408 - Request Timeout
480 - Temporarily Unavailable
487 - Request Terminated
486 - Busy Here
600 - Busy Everywhere
If history reason is a Q.850 reason, it is translated to the SIP
reason (according to the SIP-ISDN tables) and then to ISDN
Redirect reason according to the table above.
User Agent Server (UAS) Behavior:
The History-Info header is sent only in the final response.
Upon receiving a request with History-Info, the UAS checks the
policy in the request. If 'session', 'header', or 'history' policy tag is
found, the (final) response is sent without History-Info; otherwise,
it is copied from the request.
Determines whether the device sets the Contact header of outgoing
INVITE requests to 'anonymous' for restricted calls.
[0] = Disabled (default)
[1] = Enabled
Determines whether the SIP 'tgrp' parameter is used, which specifies
the Trunk Group to which the call belongs, according to RFC 4904.
For example:
INVITE sip::+16305550100;tgrp=1;trunk-
context=example.com@10.1.0.3;user=phone SIP/2.0
[0] Disable = The 'tgrp' parameter isn't used (default).
[1] Send Only = The Trunk Group number is added to the 'tgrp'
parameter value in the Contact header of outgoing SIP
messages. If a Trunk Group number is not associated with the
284
Mediant 600 & Mediant 1000
Description
ISDN Redirecting Reason
Call Forward Universal (CFU)
Call Forward No Answer (CFNA)
Call Forward Busy (CFB)
Document #: LTRT-83305

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Mediant 1000

Table of Contents