[reSIProcate] why different between send 200 OK message and refer message in the Via header

Byron Campen bcampen at estacado.net
Tue Feb 6 08:17:59 CST 2007


	Like I noted earlier, when we are preparing to send the REFER, we  
decide what to put in the topmost Via by making a call to connect  
(which prompts a routing-table lookup). This will tell us what  
interface we should send on. Once we get this information, we can  
fill out the topmost Via. Since this lookup happens down in the  
TransportSelector, it may not have happened yet when the logging  
statement was written. Also, as I mentioned before, if the routing  
table gives us something crazy like 127.0.0.1, we may fail to find a  
transport bound to that interface, and fail to populate the topmost  
Via. Is the REFER making it out on the wire? What does it look like  
then?

Best regards,
Byron Campen

> resip
>
>
> why different between send 200 OK message and refer message in the  
> Via header
>
>
>
> [14:01:03]			onConnected
>
>
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP  
> 192.168.2.143:5060;branch=z9hG4bK1c0a8028f45c81990-35d-ac89
> Contact: <sip:63471111 at 192.168.2.22:37000;user=phone>
> To: <sip:63471111 at 192.168.2.22:37000>;tag=8b03dd2c
> From: "6591000508"<sip: 
> 6591000508 at 192.168.2.143:5060>;tag=t1170741648-co861
> Call-ID: 1170741648885806400-0 at 192.168.2.6
> CSeq: 6090 INVITE
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER
> Content-Type: application/sdp
> User-Agent: hmd/2.0
> Content-Length: 182
>
>
>
> [14:01:03]			Ready to send...
> REFER sip:6591000508 at 192.168.2.143:5060 SIP/2.0
> Via: SIP/2.0/ ;branch=z9hG4bK-d8754z-ce36cf488e13cd26-1--- 
> d8754z-;rport
> Max-Forwards: 70
> Contact: <sip:63471111 at 192.168.2.22:37000;user=phone>
> To: "6591000508"<sip:6591000508 at 192.168.2.143:5060>;tag=t1170741648- 
> co861
> From: <sip:63471111 at 192.168.2.22:37000>;tag=8b03dd2c
> Call-ID: 1170741648885806400-0 at 192.168.2.6
> CSeq: 2 REFER
> Subject: callinfo=01103480026010656324137701016NWRK050000002924
> Refer-To: <sip:6563241377 at 192.168.2.143? 
> Replaces=NTcyNDBhZjA1NDIyZWE3OWY5NWM0NGFlNDI0YTY5MGY.!3Bto-tag! 
> 3Dt1170741663-co863!3Bfrom-tag!3D04639a52>
> Referred-By: <sip:63471111 at 192.168.2.22:37000;user=phone>
> Content-Length: 0
>
>
>
> can you see? the Via in refer lack of    "/UDP 192.168.2.143:5060"
>  				
>
>         maodonghu
>         hhmmdd at tom.com
>           2007-02-06
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2423 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070206/f1836e6e/attachment.bin>


More information about the resiprocate-devel mailing list