Enabling Sip Rfc Privacy, Asserted-Identity, & Preferred-Identity Headers (Rfc 3323/3325); Updating Caller Address Parameters - Patton electronics SmartNode Series Software Configuration Manual

Software for smartnode series
Hide thumbs Also See for SmartNode Series:
Table of Contents

Advertisement

SmartWare Software Configuration Guide
Mode: Interface SIP
Step
1
[node](if-sip)[if-name]# address-transla-
tion outgoing-call request-uri target-
param call redir
2
[node](if-sip)[if-name]# address-transla-
tion incoming-call calling-redir
requesturi-target-param
Enabling SIP RFC Privacy, Asserted-Identity, & Preferred-Identity headers (RFC 3323/3325)
The following command sequence enables support for the SIP Privacy and Asserted-Identity headers, sending
and receiving of the Privacy as well as the Asserted-Identity headers of RFCs 3323 & 3325. This provides the
required identity to SIP entities. The privacy header suppresses the forwarding of the identity to the final sta-
tion. Handling of the Asserted-Identity header can be configured in the same way as for any other SIP header
using the address-translation command in the SIP interface configuration mode. The privacy header is mapped
to the call-control's presentation indicator property field.
The type of header sent depends on the screening-indicator property of the call-control. When receiving one of
these privacy headers the screening-indicator is also set depending on the received header type.
Mode: Interface SIP
Step
1
[node](if-sip)[if-name]#[no] privacy

Updating caller address parameters

A SIP User Agent Client (UAC) can use the sip update method for modifying caller-name and caller-number.
These parameters must be included in the P-Asserted-Identity header of the sip update message. This feature is
often required if sip has to interwork with an analog telephone network where the Caller-Id cannot be deliv-
ered together with the call offering. If SmartWare is working as SIP to FXS Gateway, the UAC can send the
update at any time between the initial invite and the final response. The delivered parameters will be presented
to the FXS subscriber during the current or the next ring pause.
SIP interface configuration task list
Command
Command
39 • SIP interface configuration
Purpose
Enables Redirecting Party Number Tunneling
ISDN ‡ SIP: Enables transmission of the target
and cause parameters in the Request-URI for
outgoing SIP calls. Whenever the (incoming
ISDN) call has a redirecting party number
information element, the Request-URI is
extended by the target and cause parame-
ters.
Default: disabled
Enables Redirecting Party Number Tunneling
SIP ‡ ISDN: Enables reception of the target
and cause parameters in the Request-URI for
incoming SIP calls. Sets the redirecting party
number information element for (outgoing
ISDN) calls where the target parameter is
present in the Request-URI.
Default: disabled
Purpose
Enables/Disables privacy.
Default: disabled
443

Advertisement

Table of Contents
loading

This manual is also suitable for:

Smartware release 5.1

Table of Contents