Chris,
RPID is a concept which really doesn't support SIP-to-SIP calls. It's meant for SIP-to-PSTN calls only. A PSTN gatway [should] honor the RPID header.
To get similiar functionality on SIP-to-SIP calls you may have to look at the UAC module, which is in the CVS unstable branch, but has also been backported to SER-0.9.x
The UAC module will allow to you safely alter the FROM header at your SIP router.
Regards, Paul
On 9/25/05, Chris Tsai christsai@draytek.com wrote:
hi, I have a question about blocking caller id at SER (public proxy) if I want to blocking my caller id to invite other user at IPtel.org How do I do ? How about the INVITE message format needs? I try it the messae as follows: but it's fail.........><
Request-Line: INVITE sip:8201@iptel.org SIP/2.0 Message Header Via: SIP/2.0/UDP 61.216.39.201:5060;branch=z9hG4bK-hrs-21193 From: Anonymous sip:anonymous@iptel.org;tag=DBb-18789 To: sip:8201@iptel.org Call-ID: gnA-11414@61.216.39.201 CSeq: 8 INVITE Contact: sip:christsai12@61.216.39.201 Max-Forwards: 70 Remote-Party-ID: Chris sip:christsai12@iptel.org;privacy=full;party=calling supported: replaces User-Agent: DrayTek UA-1.2.1 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, INFO, REFER, NOTIFY, SUBSCRIBE Content-Type: application/sdp Content-Length: 270 Message body
Session Initiation Protocol Status-Line: SIP/2.0 407 Proxy Authentication Required Message Header Via: SIP/2.0/UDP 61.216.39.201:5060;branch=z9hG4bK-hrs-21193;rport=5060;received=61.216.35.30 From: Anonymous sip:anonymous@iptel.org;tag=DBb-18789 To: sip:8201@iptel.org;tag=b51ece8fd8c195776737473dd6552d43.8aa7 Call-ID: gnA-11414@61.216.39.201 CSeq: 8 INVITE P-Behind-NAT: Yes Proxy-Authenticate: Digest realm="iptel.org", nonce="42bf93c8d6bc77f7ef3e6e8f24513796fda5bccc" Server: Sip EXpress router (0.9.0udpfifo (i386/linux)) Content-Length: 0 Warning: 392 195.37.77.99:5060 "Noisy feedback tells: pid=30610 req_src_ip=61.216.35.30 req_src_port=5060 in_uri=sip:8201@iptel.org out_uri=sip:8201@iptel.org via_cnt==1"
Session Initiation Protocol Request-Line: ACK sip:8201@iptel.org SIP/2.0 Message Header Via: SIP/2.0/UDP 61.216.39.201:5060;branch=z9hG4bK-hrs-21193 From: Anonymous sip:anonymous@iptel.org;tag=DBb-18789 To: sip:8201@iptel.org;tag=b51ece8fd8c195776737473dd6552d43.8aa7 Call-ID: gnA-11414@61.216.39.201 CSeq: 8 ACK Content-Length: 0
Session Initiation Protocol Request-Line: INVITE sip:8201@iptel.org SIP/2.0 Message Header Via: SIP/2.0/UDP 61.216.39.201:5060;branch=z9hG4bK-mWf-3372 From: Anonymous sip:anonymous@iptel.org;tag=DBb-18789 To: sip:8201@iptel.org Call-ID: gnA-11414@61.216.39.201 CSeq: 9 INVITE Contact: sip:christsai12@61.216.39.201 Proxy-Authorization: Digest username="christsai12", realm="iptel.org", nonce="42bf93c8d6bc77f7ef3e6e8f24513796fda5bccc", uri="sip:8201@iptel.org", response="d1cb74bf6a92df9edf18e565ee2eac79", algorithm=MD5 Max-Forwards: 70 Remote-Party-ID: Chris sip:christsai12@iptel.org;privacy=full;party=calling supported: replaces User-Agent: DrayTek UA-1.2.1 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, INFO, REFER, NOTIFY, SUBSCRIBE Content-Type: application/sdp Content-Length: 270 Message body
Session Initiation Protocol Status-Line: SIP/2.0 403 That is ugly -- use From=id next time (OB) Message Header Via: SIP/2.0/UDP 61.216.39.201:5060;branch=z9hG4bK-mWf-3372;rport=5060;received=61.216.35.30 From: Anonymous sip:anonymous@iptel.org;tag=DBb-18789 To: sip:8201@iptel.org;tag=b51ece8fd8c195776737473dd6552d43.b29b Call-ID: gnA-11414@61.216.39.201 CSeq: 9 INVITE P-Behind-NAT: Yes Server: Sip EXpress router (0.9.0udpfifo (i386/linux)) Content-Length: 0 Warning: 392 195.37.77.99:5060 "Noisy feedback tells: pid=30606 req_src_ip=61.216.35.30 req_src_port=5060 in_uri=sip:8201@iptel.org out_uri=sip:8201@iptel.org via_cnt==1" _______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers