Stefan Sayer writes:
> are you sure it is not the URI from the Contact of the ACK rather than
> the From uri? I think its correct to update remote uri from ACK Contact
> uri.
stefan,
there is no contact header in the ack (see below). to me this looks
like a severe bug.
-- juha
--------------------------------------------------------------------
No. Time Source Destination Protocol
Info
1 16:47:29.216459 192.98.101.10 127.0.0.1 SIP/SDP
Request: INVITE sip:[email protected], with session description
Frame 1 (1039 bytes on wire, 1039 bytes captured)
Linux cooked capture
Internet Protocol, Src: 192.98.101.10 (192.98.101.10), Dst: 127.0.0.1
(127.0.0.1)
User Datagram Protocol, Src Port: sip (5060), Dst Port: 5090 (5090)
Session Initiation Protocol
Request-Line: INVITE sip:[email protected] SIP/2.0
Message Header
Record-Route: <sip:192.98.101.10;lr;ftag=mqbpn>
Via: SIP/2.0/UDP 192.98.101.10;branch=z9hG4bKaca8.537d1577.0
Via: SIP/2.0/UDP 192.98.101.10:5074;rport=5074;branch=z9hG4bKxuqqlfsx
Max-Forwards: 69
To: <sip:[email protected]>
From: "Test" <sip:[email protected]>;tag=mqbpn
Call-ID: mynutthblsnt...@localhost
CSeq: 164 INVITE
Contact: <sip:[email protected]:5074;transport=udp>
Content-Type: application/sdp
Allow:
INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE
Supported: replaces,norefersub,100rel
User-Agent: Twinkle/1.3.2
Content-Length: 336
P-App-Param: Language=en
P-App-Name: announcement
Message Body
No. Time Source Destination Protocol
Info
2 16:47:29.240631 127.0.0.1 192.98.101.10 SIP/SDP
Status: 200 OK, with session description
Frame 2 (760 bytes on wire, 760 bytes captured)
Linux cooked capture
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 192.98.101.10
(192.98.101.10)
User Datagram Protocol, Src Port: 5090 (5090), Dst Port: sip (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Message Header
Record-Route: <sip:192.98.101.10;lr;ftag=mqbpn>
Via: SIP/2.0/UDP 192.98.101.10;branch=z9hG4bKaca8.537d1577.0
Via: SIP/2.0/UDP 192.98.101.10:5074;rport=5074;branch=z9hG4bKxuqqlfsx
To: <sip:[email protected]>;tag=4F6EF1BA-4AD727F100034EE8-B6A62B90
From: "Test" <sip:[email protected]>;tag=mqbpn
Call-ID: mynutthblsnt...@localhost
CSeq: 164 INVITE
Server: Sip Express Media Server (1.1.0-dev-r1543M (i386/linux))
Contact: <sip:[email protected]:5090>
Content-Type: application/sdp
Content-Length: 203
Message Body
No. Time Source Destination Protocol
Info
3 16:47:29.582381 192.98.101.10 127.0.0.1 SIP
Request: ACK sip:[email protected]:5090
Frame 3 (415 bytes on wire, 415 bytes captured)
Linux cooked capture
Internet Protocol, Src: 192.98.101.10 (192.98.101.10), Dst: 127.0.0.1
(127.0.0.1)
User Datagram Protocol, Src Port: sip (5060), Dst Port: 5090 (5090)
Session Initiation Protocol
Request-Line: ACK sip:[email protected]:5090 SIP/2.0
Message Header
Via: SIP/2.0/UDP 192.98.101.10;branch=0
Via: SIP/2.0/UDP 192.98.101.10:5074;rport=5074;branch=z9hG4bKpljcpjxb
Max-Forwards: 69
To: <sip:[email protected]>;tag=4F6EF1BA-4AD727F100034EE8-B6A62B90
From: "Test" <sip:[email protected]>;tag=mqbpn
Call-ID: mynutthblsnt...@localhost
CSeq: 164 ACK
User-Agent: Twinkle/1.3.2
Content-Length: 0
No. Time Source Destination Protocol
Info
4 16:47:32.369514 127.0.0.1 127.0.0.1 SIP
Request: BYE sip:[email protected]
Frame 4 (438 bytes on wire, 438 bytes captured)
Linux cooked capture
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
User Datagram Protocol, Src Port: 5090 (5090), Dst Port: onscreen (5080)
Session Initiation Protocol
Request-Line: BYE sip:[email protected] SIP/2.0
Message Header
Via: SIP/2.0/UDP 127.0.0.1:5090;branch=z9hG4bKfFHFgaSY
Route: <sip:192.98.101.10;lr;ftag=mqbpn>
From: <sip:[email protected]>;tag=4F6EF1BA-4AD727F100034EE8-B6A62B90
To: "Test" <sip:[email protected]>;tag=mqbpn
CSeq: 10 BYE
Call-ID: mynutthblsnt...@localhost
User-Agent: Sip Express Media Server (1.1.0-dev-r1543M (i386/linux))
Max-Forwards: 70
Content-Length: 0
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
