Hi Paul!
I think the only way to get real privacy is by use of a B2BUA. Even if the From: header will be changed, there is information about the origin in the SIP message - e.g. Call-Id, Contact, SDP, Via ...
You can also make the Caller-Id-Block in the originating client. I think there are some SIP UA which will put a From: Anonymous into the INVITE if you enable Caller-ID-Block. You may configure your proxy to route this message although the AuthUser!=FromUser.
regards, klaus
Java Rockx wrote:
Klaus,
I realize that RFC3261 says do not modify the From header, however, my question is this;
When making SIP-to-SIP calls between two subscribers on the same SIP proxy, how can one implement Caller ID Block when RPID is not usually honored by SIP UAs - since this is really for PSTN gateways?
It seems that altering the From header in this case is the only option. Have I missed something?
Regards, Paul
On Wed, 23 Feb 2005 12:00:14 +0100, Klaus Darilion klaus.mailinglists@pernau.at wrote:
Hi Mik!
Do not modify the From: or To: URI - this is not allowed (RFC 3261) and will cause problems.
regards, klaus
Mik Cheez wrote:
Since I'm able to modify the URI for relaying, I would assume there would be a way to modify the FROM_URI as well. Has anyone managed to do this with SER acting as a proxy? Any other possible avenues to modify the CALLID?
Best regards
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers