8 Aug
2006
8 Aug
'06
5:34 p.m.
Evan Borgström wrote:
Changing the From header is not really a good thing to
do, instead you
should look at implementing the Remote-Party-ID (RPID) headers using the
append_rpid_hf() function and if privacy is requested the privacy=full
tag should be applied. The auth modules can retrieve the RPID value from
a database or radius engine.
I agree although an exception is allowed for "anonymous" users. This is
what we currently use for caller ID blocking. My current replace
function call replaces the entire from address (display name and URI)
with the anonymous string recommended in RFC3323.
Any modern device (UAC, UAS, Gateway, etc) should
support the RPID
header and should honor the privacy tag.
I was just told by a consultant that RPID has been deprecated by the
IETF. I do not have any more information on this move but if true it
suggests that this is the wrong approach. Does anyone have any more
information about this? Does anyone have any additional suggestions?
Thanks,Steve
-Evan
Steve Blair wrote:
Is it possible to change just the display name
portion of the from
header? I'm trying to implement caller ID blocking but we cannot remove
the actual from URI because that breaks our gateway based CDR generation.
I'm hoping changing the from header to something like:
from="Anonymous" <sip:376826@myschool.edu>;tag=003094
Thanks,
Steve
______________________________________________________________________
This e-mail has been scanned by Verizon Managed Email Content Service, using Skeptic™
technology powered by MessageLabs. For more information on Verizon Managed Email Content
Service, visit http://www.verizonbusiness.com.
______________________________________________________________________