McDewey

from an endpoint with directory number, 69005, and a Caller ID, “sip line,” for an outbound call will have the following Remote-Party-ID and From headers: Remote-Party-ID: "sip line" sip:69005@10.10.10.2;party=calling;id-type=subscriber;privacy=off;screen=yes From: "sip line" sip:69005@10.10.10.2;tag=1234 Calling Line and Name Identification Restriction The system conveys the SIP Line (Number) and Name restrictions by using the privacy parameter. If neither is restricted, privacy gets specified as off. The details that follow provide other values of privacy (name, uri, and full) with their impact on the various values in the From and Remote-Party-ID headers: name Name Restrict only—When name is restricted, the display field (Calling Name) in “From” header gets set to “Anonymous.” The display field in the “Remote-Party-ID” header still includes the actual name, but the privacy field gets set to “name.” For example: Remote-Party-ID: "Anonymous" sip:69005@10.10.10.2;party=calling;id-type=subscriber;privacy=name;screen=yes From: "Anonymous" sip:69005@10.10.10.2;tag=1234 uri Number Restrict only—When number is restricted, the system sets the calling Line to “Anonymous” out in the “From” header; however, it still gets included in the “Remote-Party-ID” header with privacy=uri. For example: Remote-Party-ID: "sip line" sip:69005@10.10.10.2;party=calling;id-type=subscriber;privacy=uri;screen=yes From: "sip line" sip:Anonymous@10.10.10.2;tag=1234 full Both Name and Number Restrict—When both name and number are restricted, the same principle applies with privacy=full. For example: Remote-Party-ID: "sip line" sip:69005@10.10.10.2;party=calling;id-type=subscriber;privacy=full;screen=yes SIP Line Messaging Guide (Standard Edition) for Cisco Unified Communications Manager 13 SIP Standard Line Interface Calling Line and Name Identification Restriction