[SIPForum-discussion] SIP Proxy stripping responsible maddr

Eugene Mednikov em at HERMONLABS.com
Sun Jun 17 08:52:28 UTC 2007


Greetings!
 
RFC 3261. 16.4 Route Information Preprocessing
 
If the Request-URI contains a maddr parameter, the proxy MUST check to see
if its value is in the set of addresses or domains the proxy is configured
to be responsible for.  If the Request-URI has a maddr parameter with a
value the proxy is responsible for, and the request was received using the
port and transport indicated (explicitly or by default) in the Request-URI,
the proxy MUST strip the maddr and any non-default port or transport
parameter and continue processing as if those values had not been present in
the request.

 
    In the last message of log you may see that maddr isn't stripped from
Request-URI of ACK message. 192.168.0.57 is the address of telephone
simulator so it seems reasonable that proxy (192.168.0.4) would be
responsible for phones registered on it. Please advise whether proxy
behaviour is correct in this case.
 
 
Sending from UDP1:5060 to IUT (192.168.0.4:5060) at 11:37:39.478
>>>
INVITE sip:202 at 192.168.0.4 SIP/2.0
Call-ID: 2ccfecb4d94c5b4b at 192.168.0.57
<mailto:2ccfecb4d94c5b4b at 192.168.0.57> 
Contact: sip:201 at 192.168.0.57:5060
Content-Disposition: session
Content-Length: 155
Content-Type: application/sdp
CSeq: 4 INVITE
From: TCA <sip:201 at 192.168.0.4>;tag=3007da786ea6e2b5
Max-Forwards: 70
Proxy-Authorization: Digest
username="201",realm="192.168.0.4",nonce="4674f3fffda70808b84a7ce8e5c447527d
50f53e",uri="sip:192.168.0.4:5060",response="f0451a10b57307839829d9016f64f8f
b",algorithm=MD5,cnonce="01234567890abcdef01234567890abcdef",qop=auth,opaque
="",nc=00000001
To: TCA 2 <sip:202 at 192.168.0.4>
Via: SIP/2.0/UDP 192.168.0.57:5060;branch=z9hG4bK7f2c16c3f8636d92
 
v=0 
 o=voicesession 12345 12345 IN IP4 193.174.154.20 
 s=Voice Session
 c=IN IP4 195.174.154.20 
 t=0 0 
 m=audio 8500 RTP/AVP 0 
 a=rtpmap:0 PCMU/8000
 
>>>
 
Received from IUT (192.168.0.4:5060) to UDP1:5060 at 11:37:39.524
<<<
SIP/2.0 100 trying -- your call is important to us
Call-Id: 2ccfecb4d94c5b4b at 192.168.0.57
<mailto:2ccfecb4d94c5b4b at 192.168.0.57> 
Cseq: 4 INVITE
From: TCA <sip:201 at 192.168.0.4>;tag=3007da786ea6e2b5
To: TCA 2 <sip:202 at 192.168.0.4>
Via: SIP/2.0/UDP 192.168.0.57:5060;branch=z9hG4bK7f2c16c3f8636d92
Server: Sip EXpress router (0.9.6 (i386/linux))
Content-Length: 0
Warning: 392 192.168.0.4:5060 "Noisy feedback tells:  pid=4969
req_src_ip=192.168.0.57 req_src_port=3057 in_uri=sip:202 at 192.168.0.4
out_uri=sip:202 at 192.168.0.57:5061;transport=UDP via_cnt==1"
Date: Sun, 17 Jun 2007 08:37:39 GMT
 

<<<
 
Received from IUT (192.168.0.4:5060) to UDP2:5061 at 11:37:39.571
<<<
INVITE sip:202 at 192.168.0.57:5061;transport=UDP SIP/2.0
Record-Route: <sip:192.168.0.4;ftag=3007da786ea6e2b5;lr=on>
Call-Id: 2ccfecb4d94c5b4b at 192.168.0.57
<mailto:2ccfecb4d94c5b4b at 192.168.0.57> 
Contact: sip:201 at 192.168.0.57:5060
Content-Disposition: session
Content-Length: 161
Content-Type: application/sdp
Cseq: 4 INVITE
From: TCA <sip:201 at 192.168.0.4>;tag=3007da786ea6e2b5
Max-Forwards: 16
To: TCA 2 <sip:202 at 192.168.0.4>
Via: SIP/2.0/UDP 192.168.0.4;branch=z9hG4bKdcb2.89fe0652.0
Via: SIP/2.0/UDP 192.168.0.57:5060;branch=z9hG4bK7f2c16c3f8636d92
Date: Sun, 17 Jun 2007 08:37:39 GMT
 
v=0 
 o=voicesession 12345 12345 IN IP4 193.174.154.20 
 s=Voice Session
 c=IN IP4 195.174.154.20 
 t=0 0 
 m=audio 8500 RTP/AVP 0 
 a=rtpmap:0 PCMU/8000
 
<<<
 
Sending from UDP2:5061 to IUT (192.168.0.4:5060) at 11:37:39.618
>>>
SIP/2.0 200 OK
Call-ID: 2ccfecb4d94c5b4b at 192.168.0.57
<mailto:2ccfecb4d94c5b4b at 192.168.0.57> 
Contact: TCA 2 <sip:202 at 192.168.0.57:5061>;transport=UDP
Content-Length: 155
Content-Type: application/sdp
CSeq: 4 INVITE
From: TCA <sip:201 at 192.168.0.4>;tag=3007da786ea6e2b5
Record-Route: <sip:192.168.0.4;ftag=3007da786ea6e2b5;lr=on>
To: TCA 2 <sip:202 at 192.168.0.4>;tag=c13796d553bffe3e
Via: SIP/2.0/UDP 192.168.0.4;branch=z9hG4bKdcb2.89fe0652.0, SIP/2.0/UDP
192.168.0.57:5060;branch=z9hG4bK7f2c16c3f8636d92
 
v=0 
 o=voicesession 12345 12345 IN IP4 193.174.154.20 
 s=Voice Session
 c=IN IP4 195.174.154.20 
 t=0 0 
 m=audio 8500 RTP/AVP 0 
 a=rtpmap:0 PCMU/8000
 
>>>
 
Received from IUT (192.168.0.4:5060) to UDP1:5060 at 11:37:39.649
<<<
SIP/2.0 200 OK
Call-Id: 2ccfecb4d94c5b4b at 192.168.0.57
<mailto:2ccfecb4d94c5b4b at 192.168.0.57> 
Contact: TCA 2 <sip:202 at 192.168.0.57:5061>;transport=UDP
Content-Length: 161
Content-Type: application/sdp
Cseq: 4 INVITE
From: TCA <sip:201 at 192.168.0.4>;tag=3007da786ea6e2b5
Record-Route: <sip:192.168.0.4;ftag=3007da786ea6e2b5;lr=on>
To: TCA 2 <sip:202 at 192.168.0.4>;tag=c13796d553bffe3e
Via: SIP/2.0/UDP 192.168.0.57:5060;branch=z9hG4bK7f2c16c3f8636d92
Date: Sun, 17 Jun 2007 08:37:39 GMT
 
v=0 
 o=voicesession 12345 12345 IN IP4 193.174.154.20 
 s=Voice Session
 c=IN IP4 195.174.154.20 
 t=0 0 
 m=audio 8500 RTP/AVP 0 
 a=rtpmap:0 PCMU/8000
 
<<<
 
Sending from UDP1:5060 to IUT (192.168.0.4:5060) at 11:37:39.681
>>>
ACK sip:202 at 192.168.0.57:5061;maddr=192.168.0.57 SIP/2.0
Call-ID: 2ccfecb4d94c5b4b at 192.168.0.57
<mailto:2ccfecb4d94c5b4b at 192.168.0.57> 
Content-Length: 0
CSeq: 4 ACK
From: TCA <sip:201 at 192.168.0.4>;tag=3007da786ea6e2b5
Max-Forwards: 70
To: TCA 2 <sip:202 at 192.168.0.4>;tag=c13796d553bffe3e
Via: SIP/2.0/UDP 192.168.0.57:5060;branch=z9hG4bK273c333a96014488
 
#
>>>
 
Received from IUT (192.168.0.4:5060) to UDP2:5061 at 11:37:39.728
<<<
ACK sip:202 at 192.168.0.57:5061;maddr=192.168.0.57 SIP/2.0
Record-Route: <sip:192.168.0.4;ftag=3007da786ea6e2b5;lr=on>
Call-Id: 2ccfecb4d94c5b4b at 192.168.0.57
<mailto:2ccfecb4d94c5b4b at 192.168.0.57> 
Content-Length: 4
Cseq: 4 ACK
From: TCA <sip:201 at 192.168.0.4>;tag=3007da786ea6e2b5
Max-Forwards: 16
To: TCA 2 <sip:202 at 192.168.0.4>;tag=c13796d553bffe3e
Via: SIP/2.0/UDP 192.168.0.4;branch=0
Via: SIP/2.0/UDP 192.168.0.57:5060;branch=z9hG4bK273c333a96014488
Date: Sun, 17 Jun 2007 08:37:39 GMT
 
#
 
Respectfully yours, Eugene Mednikov.
 
Software Engineer
Hermon Labs
972-4-6288001, 207
972-54-4520187
em at hermonlabs.com <blocked::mailto:em at hermonlabs.com> 
www.hermonlabs.com <blocked::http://www.hermonlabs.com> 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20070617/63906b21/attachment-0002.html>


More information about the discussion mailing list