Cisco Cisco IOS Software Release 12.4(4)T

Page de 30
 
SIP: CLI for Caller ID When Privacy Exists
  Prerequisites for SIP: CLI for Caller ID When Privacy Exists
2
Cisco IOS Release 12.4(4)T
Prerequisites for SIP: CLI for Caller ID When Privacy Exists
Establish a working IP network.
Configure VoIP.
Ensure that the gateway has voice functionality configured for SIP.
Note
Cisco IOS Voice Configuration Library.
Information About SIP: CLI for Caller ID When Privacy Exists
The SIP: CLI for Caller ID When Privacy Exists feature is comprised of three main components, as follows: 
SIP: Caller ID Removable to Improve Privacy
The caller ID information is passed through from the ISDN-to-SIP by copying the number in the Calling 
Party Number information element (IE) in an ISDN Setup message into the Calling Number field of the 
SIP Remote-Party-ID and From headers.
The Calling Name from the ISDN Display IE is copied into the SIP Display Name field in the SIP 
Remote-Party-ID and From headers. The Calling Party Number IE contains a Presentation Indicator field 
that is set to presentation allowed, presentation restricted, number not available due to interworking, or 
reserved. Presentation allowed and presentation restricted are translated into privacy set to off or privacy 
set to null, respectively, in the SIP Remote-Party-ID header field. 
However, for added privacy, the SIP: CLI for Caller ID When Privacy Exists feature introduces CLI to 
completely remove the Calling Number and Display Name from an outgoing message’s From header if 
presentation is prohibited. This prohibits sending the SIP Remote Party ID header, because the Cisco 
gateway does not send SIP Remote-Party ID headers without both a Display Name and Calling Number. 
Note
The SIP: Caller ID Removable to Improve Privacy option is available both globally and at the dial-peer 
level. 
See 
 for call flows and 
 and 
 for additional presentation mapping.