AudioCodes E-SBC - Page 1213

CHAPTER68 Configuration Parameters Reference
Mediant 1000 Gateway & E-SBC | User's Manual
Parameter Description
[IPAlertTimeout]
'Remote Party ID'
configure voip >
sip-definition
settings > remote-
party-id
[EnableRPIheader]
Enables Remote-Party-Identity headers for calling and called
numbers for Tel-to-IP calls.
■ [0] Disable (default).
■ [1] Enable = Remote-Party-Identity headers are generated in
SIP INVITE messages for both called and calling numbers.
'History-Info Header'
configure voip >
sip-definition
settings > hist-
info-hdr
[EnableHistoryInfo]
Enables usage of the SIP History-Info header.
■ [0] Disable (default)
■ [1] 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:
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.
- 1175 -