Restricting calling name on SIP Trunk in CUCM

[Vivek Batra]

Friends,

To restrict sending calling name on SIP trunk, "Calling Name Presentation" on SIP trunk should be set to Restricted. Seems if I set this parameter to Restricted, CUCM is sending From field as <anonymous@anonymous.invalid> and in result, called party can't see even the calling number. How to correct it while CUCM should send calling number in From field and restrict only calling name?

Precisely, if either of the parameter "Calling Name Presentation" or "Calling Line ID Presentation" is set to Restricted, From field is sent as anonymous.

Same is working as expected on H.323 by disabling only "Display IE Dilevery" parameter in H.323 configuration.

Thanks

Vivek 
 

[Aaron Harrison]

Hi

If you are using CUBE you may be able to use SIP Profiles to strip out the info.

With CUCM you may be best to write a lua script.

Aaron

[Vivek Batra]

Hi Aaron,

Thanks...

Just to get your point, what is the purpose of then "Calling Name Presentation" and "Calling Line ID Presentation" parameters on SIP trunk?

Are both parameters doing the same job of replacing From field with anonymous (when either one is set to on)?

Thanks

Vivek

[Suresh Subramanian]

alling Line ID Presentation - Default Calling Name Presentation - Restricted

with the above settings, if Privacy is set to None, then Calling number displayed & 

if Privacy is set to Default, then no name & no number displayed.

You can keep both the asserted id & remote party id Checked & asserted type be Default. just change the privacy to None.

Let the Calling Line ID Presentation - Default  & Calling Name Presentation - Restricted

Pls try that and let us know how it works

[Vivek Batra · Accepted solution]

Hi Suresh,

Thank you very much for the hint.... then I realized the interactions between RPID, Asserted, Privacy, Calling Line ID and Calling Name Presentation parameter and tried to cover all combinations. Seems all combinations are possible and it's now depends on remote end configuration how to fetch the ANI to display on phone. Results are mentioned below.

Case1	Asserted - Off
	RPID - Off
	Calling Line-ID Presentation	Calling Name Presentation	Result1 (SIP From)	Conclusion
	Allow	Allow	name <number@localhost>	"CLI" and "Name" presentation parameter can be used to control sending name and number in From field of INVITE message.
	Allow	Restrict	anonymous <number@localhost>
	Restrict	Allow	name <anonymous@localhost>
	Restrict	Restrict	anonymous <anonymous@localhost>
Case2	Asserted - Off
	RPID - On
	Calling Line-ID Presentation	Calling Name Presentation	Result1 (From field in INVITE)	Result2 (RPID privacy header)	Conclusion
	Allow	Allow	name <number@localhost>	off	When RPID is being used, "CLI" and "Name" presentation parameter can be used to control sending name and number in From field along with marking required privacy in RPID header.
	Allow	Restrict	anonymous <number@localhost>	uri
	Restrict	Allow	name <anonymous@localhost>	name
	Restrict	Restrict	anonymous <anonymous@localhost>	full
Case3	Asserted - On & Privacy - None
	RPID - Off
	Calling Line-ID Presentation	Calling Name Presentation	Result1 (From field in INVITE)	Conclusion
	Allow	Allow	name <number@localhost>	When RPID is off and Asserted Privacy is None, From field is always populated with name and number. "CLI" and "Name" presentation parameter can not be used to control sending name and number in FROM field of INVITE message.
	Allow	Restrict	name <number@localhost>
	Restrict	Allow	name <number@localhost>
	Restrict	Restrict	name <number@localhost>
Case4	Asserted - On & Privacy - Id
	RPID - Off
	Calling Line-ID Presentation	Calling Name Presentation	Result1 (From field in INVITE)	Conclusion
	Allow	Allow	anonymous <anonymous@localhost>	When Asserted Privacy is Id, From field is always populated as Anonymous. "CLI" and "Name" presentation parameter can not be used to control sending name and number in FROM field of INVITE message.
	Allow	Restrict	anonymous <anonymous@localhost>
	Restrict	Allow	anonymous <anonymous@localhost>
	Restrict	Restrict	anonymous <anonymous@localhost>
Case5	Asserted - On & Privacy - None
	RPID - On
	Calling Line-ID Presentation	Calling Name Presentation	Result1 (From field in INVITE)	Result2 (RPID privacy header)	Conclusion
	Allow	Allow	name <number@localhost>	off	When asserted is on with privacy none and RPID is also on, From field is always populated with name/number.  "CLI" and "Name" presentation parameter can not be used to control sending name and number in FROM field of INVITE message.
	Allow	Restrict	name <number@localhost>	name
	Restrict	Allow	name <number@localhost>	uri
	Restrict	Restrict	name <number@localhost>	full
Case6	Asserted - On & Privacy - Id
	RPID - On
	Calling Line-ID Presentation	Calling Name Presentation	Result1 (From field in INVITE)	Result2 (RPID privacy header)	Conclusion
	Allow	Allow	anonymous <anonymous@localhost>	off	When Asserted Privacy is Id, From field is always populated as Anonymous. Since RPID is on,  "CLI" and "Name" presentation parameter can be used for marking required privacy in RPID header.
	Allow	Restrict	anonymous <anonymous@localhost>	name
	Restrict	Allow	anonymous <anonymous@localhost>	uri
	Restrict	Restrict	anonymous <anonymous@localhost>	full

Abstract:

1. When asserted and rpid is not used, "Calling Line ID" and "Calling Name" presentation parameter can be used to control sending name and number in From field of INVITE message.

2. When only rpid is on (and asserted is off), "Calling Line ID" and "Calling Name" presentation parameter can be used to control sending name and number in From field of INVITE message. In addition, privacy header shall be added to RPID as per "Calling Line ID" and "Calling Name" presentation parameter values configured.

3. When only asserted is on and privacy is none (and rpid is off), From field is always populated with desired name and number in From field of INVITE message. "Calling Line ID" and "Calling Name" parameter has no role in controlling name and number in From field of INVITE message.

4. When only asserted is on and privacy is id (and rpid is off), From field is always populated as Anonymous. "Calling Lline ID" and "Calling Name" parameter has no role in controlling name and number in From field of INVITE message.

5. When both asserted and rpid is on (and privacy is none), From field is always populated with desired name and number in From field of INVITE message. "Calling Line ID" and "Calling Name" parameter will mark the required privacy marking in rpid header in INVITE message depends on "Calling Line ID" and "Calling Name" values.

6. When both asserted and rpid is on (and privacy is id), From field is always populated as Anonymous. "Calling Line ID" and "Calling Name" parameter will mark the required privacy marking in ripid header in INVITE message depends on "Calling Line ID" and "Calling Name" values.

Thanks

Vivek

[Vivek Batra]

Seems table is not copied completely hence attaching the file here.

Thanks

Vivek

[Aaron Harrison]

If I could rate you 10 for thoroughness, I would :-)

[Vivek Batra]

Thanks Aaron for the feedback :)

[Dennis Fogler]

Vivek,

    Try the following steps:

1) Under SIP Trunk Configuration, Uncheck "Asserted-Identity"

2) Set Calling Name to restricted

3) Leave Calling Number as default

4) Save, Apply Config, Reset Trunk

Let me know if this helps.   -Dennis

[Vivek Batra]

Hi Dennis,

True. I have observed other cases as well and attached the same.

Thank you...

Vivek

[Vivek Batra]

Thanks Jaime for the feedback :)