Re: [reSIProcate] why different between send 200 OK message and refer message in the Via header
The refer request is logged before it goes through the transport
selector. The sent-by field will be populated based on which
transport (even which interface if you have more than one) the
message is actually sent on based on 3263 resolution.
RjS
On Feb 6, 2007, at 12:11 AM, maodonghu wrote:
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@xxxxxxxxxxxx:37000;user=phone>
To: <sip:63471111@xxxxxxxxxxxx:37000>;tag=8b03dd2c
From: "6591000508"<sip:
6591000508@xxxxxxxxxxxxx:5060>;tag=t1170741648-co861
Call-ID: 1170741648885806400-0@xxxxxxxxxxx
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@xxxxxxxxxxxxx:5060 SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-d8754z-ce36cf488e13cd26-1---
d8754z-;rport
Max-Forwards: 70
Contact: <sip:63471111@xxxxxxxxxxxx:37000;user=phone>
To: "6591000508"<sip:6591000508@xxxxxxxxxxxxx:5060>;tag=t1170741648-
co861
From: <sip:63471111@xxxxxxxxxxxx:37000>;tag=8b03dd2c
Call-ID: 1170741648885806400-0@xxxxxxxxxxx
CSeq: 2 REFER
Subject: callinfo=01103480026010656324137701016NWRK050000002924
Refer-To: <sip:6563241377@xxxxxxxxxxxxx?
Replaces=NTcyNDBhZjA1NDIyZWE3OWY5NWM0NGFlNDI0YTY5MGY.!3Bto-tag!
3Dt1170741663-co863!3Bfrom-tag!3D04639a52>
Referred-By: <sip:63471111@xxxxxxxxxxxx:37000;user=phone>
Content-Length: 0
can you see? the Via in refer lack of "/UDP 192.168.2.143:5060"
maodonghu
hhmmdd@xxxxxxx
2007-02-06
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel