EasyManua.ls Logo

AudioCodes Mediant 1000B - Page 1072

AudioCodes Mediant 1000B
1281 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
User's Manual 1072 Document #: LTRT-27055
Mediant 1000B Gateway & E-SBC
Parameter Description
[EnableHistoryInfo]
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:
a. Q.850 Reason
b. SIP Reason
c. 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
ISDN Redirecting Reason
302 - Moved Temporarily Call Forward Universal (CFU)
408 - Request Timeout Call Forward No Answer (CFNA)
480 - Temporarily Unavailable
487 - Request Terminated
486 - Busy Here Call Forward Busy (CFB)
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 a 'session', 'header', or 'history' policy tag is
found, the (final) response is sent without History-Info; otherwise, it
is copied from the request.
Note: The parameter is applicable only to digital interfaces.
Use Tgrp Information
configure voip > sip-
definition settings > use-
tgrp-inf
[UseSIPTgrp]
Enables the use of the SIP 'tgrp' parameter. This parameter specifies
the Trunk Group to which the call belongs (according to RFC 4904).
For example, the SIP message below indicates that the call belongs to
Trunk Group ID 1:
INVITE sip::+16305550100;tgrp=1;trunk-
context=example.com@10.1.0.3;user=phone SIP/2.0
[0] Disable = (Default) The 'tgrp' parameter isn't used.
[1] Send Only = The Trunk Group number or name (configured in
the Trunk Group Settings table) is added to the 'tgrp' parameter
value in the Contact header of outgoing SIP messages. If a Trunk
Group number / name is not associated with the call, the 'tgrp'
parameter isn't included. If a 'tgrp' value is specified in incoming
messages, it is ignored.
[2] Send and Receive = The functionality of outgoing SIP
messages is identical to the functionality described for option [1]. In
addition, for incoming SIP INVITEs (IP-to-Tel), if the Request-URI
includes a 'tgrp' parameter, the device routes the call according to
that value (if possible). The Contact header in the outgoing SIP

Table of Contents

Other manuals for AudioCodes Mediant 1000B

Related product manuals