27 Mar
2007
27 Mar
'07
6:02 p.m.
Hello List.
I have a problem with an ACK message for a CANCEL. I'm just wondering if anyone
knows what could be happening here. It seems that SER can't route or
"understand" this ACK
ACK sip:0299005622408196@sipvoiss.desa.redvoiss.net SIP/2.0.
v: SIP/2.0/UDP 192.168.1.100:5060;branch=z9hG4bK2861608023.
f: "5502203289"
<sip:5502203289@sipvoiss.desa.redvoiss.net>;tag=1349608987.
t: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=f146818fa4.
i: 5c83a04822964085e07aabd210e9d72f(a)192.168.1.100.
CSeq: 4 ACK.
l: 0.
Could be something with the COMPACT form ???
This is the log from the debug :
Mar 23 12:18:10 sipvoiss ser[5430]: t_lookup_request: start searching: hash=52251, isACK=1
Mar 23 12:18:10 sipvoiss ser[5430]: DEBUG: RFC3261 transaction matching failed
Mar 23 12:18:10 sipvoiss ser[5430]: DEBUG: t_lookup_request: no transaction found
Mar 23 12:18:10 sipvoiss ser[5430]: SER: forwarding ACK statelessly
Mar 23 12:18:10 sipvoiss ser[5430]: DEBUG: mk_proxy: doing DNS lookup...
Mar 23 12:18:10 sipvoiss ser[5430]: get_record:
lookup(_sip._udp.sipvoiss.desa.redvoiss.net, 33) failed
Mar 23 12:18:10 sipvoiss ser[5430]: sip_resolvehost: no SRV record found for
sipvoiss.desa.redvoiss.net, trying 'normal' lookup...
Mar 23 12:18:10 sipvoiss ser[5430]: check_via_address(10.0.0.248, 192.168.1.100, 0)
Mar 23 12:18:10 sipvoiss ser[5430]: Sending: ACK
sip:0299005622408196@sipvoiss.desa.redvoiss.net SIP/2.0^M Max-Forwards: 10^M Record-Route:
<sip:10.0.0.246;ftag=2639303304;lr=on>^M Via: SIP/2.0/UDP 10.0.0.246;branch=0^M v:
SIP/2.0/UDP 192.168.1.100:5060;received=10.0.0.248;branch=z9hG4bK365542204^M f:
"5502203289" <sip:5502203289@sipvoiss.desa.redvoiss.net>;tag=2639303304^M
t: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=2746a580a4^M i:
81983e61d980fd3ef0046dafe9518284(a)192.168.1.100^M CSeq: 10 ACK^M l: 0^M ^M .
Mar 23 12:18:10 sipvoiss ser[5430]: orig. len=338, new_len=477, proto=1
Mar 23 12:18:10 sipvoiss ser[5430]: DEBUG:destroy_avp_list: destroying list (nil)
Mar 23 12:18:10 sipvoiss ser[5430]: receive_msg: cleaning up
What does it means : "RFC3261 transaction matching failed" and why ???
The weird situation happend when almost the same message arrives without the Compact Form
:
V102
ACK sip:0299005622408196@sipvoiss.desa.redvoiss.net SIP/2.0.
Via: SIP/2.0/UDP 10.0.0.237:5060;branch=z9hG4bK2364391837.
From: "5502203289"
<sip:5502203289@sipvoiss.desa.redvoiss.net>;tag=827237367.
To: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=6b466391a4.
Call-ID: 43b2cc325b7fbe9f8790e4cee01dc4b3(a)10.0.0.237.
CSeq: 2 ACK.
Content-Length: 0.
This message works ok!.
....
...
Mar 23 16:30:06 sipvoiss ser[5974]: DEBUG: RFC3261 transaction matched, tid=424819551
Mar 23 16:30:06 sipvoiss ser[5974]: DEBUG: t_lookup_request: transaction found
(T=0x404ce3e8)
Mar 23 16:30:06 sipvoiss ser[5974]: DEBUG: cleanup_uac_timers: RETR/FR timers reset
Mar 23 16:30:06 sipvoiss ser[5974]: DEBUG: add_to_tail_of_timer[2]: 0x404ce430
Mar 23 16:30:06 sipvoiss ser[5974]: DEBUG:destroy_avp_list: destroying list (nil)
Mar 23 16:30:06 sipvoiss ser[5974]: receive_msg: cleaning up
Can someone give me a hand here?
Thanks in advance
Regards,
Ricardo Martinez-
27 Mar
27 Mar
6:18 p.m.
It means that ser cannot find the transaction that this ACK should
belong to and it thus tries to relay it to the request uri.
The matching is done using from tag, to tag and call-id, so you should
check that these values match the CANCEL.
g-)
Ricardo Martinez wrote:
Hello List.
I have a problem with an ACK message for a CANCEL. I'm just
wondering if anyone knows what could be happening here. It seems that
SER can't route or "understand" this ACK
ACK sip:0299005622408196@sipvoiss.desa.redvoiss.net SIP/2.0.
v: SIP/2.0/UDP 192.168.1.100:5060;branch=z9hG4bK2861608023.
f: "5502203289"
<sip:5502203289@sipvoiss.desa.redvoiss.net>;tag=1349608987.
t: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=f146818fa4.
i: 5c83a04822964085e07aabd210e9d72f(a)192.168.1.100.
CSeq: 4 ACK.
l: 0.
Could be something with the COMPACT form ???
This is the log from the debug :
Mar 23 12:18:10 sipvoiss ser[5430]: t_lookup_request: start searching:
hash=52251, isACK=1
*Mar 23 12:18:10 sipvoiss ser[5430]: DEBUG: RFC3261 transaction
matching failed *
*Mar 23 12:18:10 sipvoiss ser[5430]: DEBUG: t_lookup_request: no
transaction found*
Mar 23 12:18:10 sipvoiss ser[5430]: SER: forwarding ACK statelessly
Mar 23 12:18:10 sipvoiss ser[5430]: DEBUG: mk_proxy: doing DNS lookup...
Mar 23 12:18:10 sipvoiss ser[5430]: get_record:
lookup(_sip._udp.sipvoiss.desa.redvoiss.net, 33) failed
Mar 23 12:18:10 sipvoiss ser[5430]: sip_resolvehost: no SRV record
found for sipvoiss.desa.redvoiss.net, trying 'normal' lookup...
Mar 23 12:18:10 sipvoiss ser[5430]: check_via_address(10.0.0.248,
192.168.1.100, 0)
Mar 23 12:18:10 sipvoiss ser[5430]: Sending: ACK
sip:0299005622408196@sipvoiss.desa.redvoiss.net SIP/2.0^M
Max-Forwards: 10^M Record-Route:
<sip:10.0.0.246;ftag=2639303304;lr=on>^M Via: SIP/2.0/UDP
10.0.0.246;branch=0^M v: SIP/2.0/UDP
192.168.1.100:5060;received=10.0.0.248;branch=z9hG4bK365542204^M f:
"5502203289"
<sip:5502203289@sipvoiss.desa.redvoiss.net>;tag=2639303304^M t:
<sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=2746a580a4^M i:
81983e61d980fd3ef0046dafe9518284(a)192.168.1.100^M CSeq: 10 ACK^M l: 0^M
^M .
Mar 23 12:18:10 sipvoiss ser[5430]: orig. len=338, new_len=477, proto=1
Mar 23 12:18:10 sipvoiss ser[5430]: DEBUG:destroy_avp_list: destroying
list (nil)
Mar 23 12:18:10 sipvoiss ser[5430]: receive_msg: cleaning up
What does it means : "RFC3261 transaction matching failed" and why ???
The weird situation happend when almost the same message arrives
without the Compact Form :
V102
ACK sip:0299005622408196@sipvoiss.desa.redvoiss.net SIP/2.0.
Via: SIP/2.0/UDP 10.0.0.237:5060;branch=z9hG4bK2364391837.
From: "5502203289"
<sip:5502203289@sipvoiss.desa.redvoiss.net>;tag=827237367.
To: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=6b466391a4.
Call-ID: 43b2cc325b7fbe9f8790e4cee01dc4b3(a)10.0.0.237.
CSeq: 2 ACK.
Content-Length: 0.
This message works ok!.
....
...
*Mar 23 16:30:06 sipvoiss ser[5974]: DEBUG: RFC3261 transaction
matched, tid=424819551*
Mar 23 16:30:06 sipvoiss ser[5974]: DEBUG: t_lookup_request:
transaction found (T=0x404ce3e8)
Mar 23 16:30:06 sipvoiss ser[5974]: DEBUG: cleanup_uac_timers: RETR/FR
timers reset
Mar 23 16:30:06 sipvoiss ser[5974]: DEBUG: add_to_tail_of_timer[2]:
0x404ce430
Mar 23 16:30:06 sipvoiss ser[5974]: DEBUG:destroy_avp_list: destroying
list (nil)
Mar 23 16:30:06 sipvoiss ser[5974]: receive_msg: cleaning up
Can someone give me a hand here?
Thanks in advance
Regards,
Ricardo Martinez-
------------------------------------------------------------------------
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
7:50 p.m.
Thanks Greger
I'm still unable to find any mismatch. Can you help me here?. If there is no
mismatch is maybe a bug in SER?
Here are more details:
No. Time Source Destination Protocol Info
6 0.363947 100.100.100.246 100.100.100.239 SIP/SDP Request:
INVITE sip:005622408196@100.100.100.239, with session description
Session Initiation Protocol
Request-Line: INVITE sip:005622408196@100.100.100.239 SIP/2.0
Method: INVITE
Resent Packet: False
Message Header
Record-Route:
<sip:0299005622408196@100.100.100.246:5060;nat=yes;ftag=1587516403;lr=on>
Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0
v: SIP/2.0/UDP
192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087
f: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
t: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
i: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 INVITE
m: sip:cl@100.100.100.248:46127
Contact Binding: sip:cl@100.100.100.248:46127
URI: sip:cl@100.100.100.248:46127\r
SIP contact address: sip:cl@100.100.100.248:46127\r
Max-Forwards: 16
User-Agent: endpoint-type1
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, REFER
Supported: timer, replaces
c: application/sdp
Accept: application/sdp
Content-Length: 294
Message body
Session Description Protocol
No. Time Source Destination Protocol Info
7 0.438768 100.100.100.239 100.100.100.246 SIP Status: 100
Trying
Session Initiation Protocol
Status-Line: SIP/2.0 100 Trying
[...]
No. Time Source Destination Protocol Info
8 1.263245 100.100.100.239 100.100.100.246 SIP/SDP Status: 183
Session Progress, with session description
Session Initiation Protocol
Status-Line: SIP/2.0 183 Session Progress
Status-Code: 183
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0
Via: SIP/2.0/UDP
192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087
From: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
To: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=9146c297a4
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
SIP tag: 9146c297a4
<sip:0299005622408196@sipvoiss.desa.redvoiss.net>
Call-ID: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 INVITE
Supported: timer, replaces, early-session
User-Agent: AddPac SIP Gateway
Contact: sip:005622408196@100.100.100.239
Contact Binding: sip:005622408196@100.100.100.239
URI: sip:005622408196@100.100.100.239\r
SIP contact address: sip:005622408196@100.100.100.239\r
Content-Type: application/sdp
Content-Length: 247
Record-Route:
<sip:0299005622408196@100.100.100.246:5060;nat=yes;ftag=1587516403;lr=on>
Message body
Session Description Protocol
No. Time Source Destination Protocol Info
9 1.265778 100.100.100.246 100.100.100.248 SIP/SDP Status: 183
Session Progress, with session description
Session Initiation Protocol
Status-Line: SIP/2.0 183 Session Progress
Status-Code: 183
Resent Packet: False
Message Header
Via: SIP/2.0/UDP
192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087
From: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
To: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=9146c297a4
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
SIP tag: 9146c297a4
<sip:0299005622408196@sipvoiss.desa.redvoiss.net>
Call-ID: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 INVITE
Supported: timer, replaces, early-session
User-Agent: AddPac SIP Gateway
Contact: sip:005622408196@100.100.100.239
Contact Binding: sip:005622408196@100.100.100.239
URI: sip:005622408196@100.100.100.239\r
SIP contact address: sip:005622408196@100.100.100.239\r
Content-Type: application/sdp
Content-Length: 247
Record-Route:
<sip:0299005622408196@100.100.100.246:5060;nat=yes;ftag=1587516403;lr=on>
Message body
Session Description Protocol
No. Time Source Destination Protocol Info
10 6.039661 100.100.100.248 100.100.100.246 SIP Request:
CANCEL sip:0299005622408196@sipvoiss.desa.redvoiss.net
Session Initiation Protocol
Request-Line: CANCEL sip:0299005622408196@sipvoiss.desa.redvoiss.net SIP/2.0
Method: CANCEL
Resent Packet: False
Message Header
v: SIP/2.0/UDP 192.168.1.100:5060;branch=z9hG4bK2893084087
f: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
t: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
i: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 CANCEL
Max-Forwards: 70
User-Agent: endpoint-type1
l: 0
No. Time Source Destination Protocol Info
11 6.042124 100.100.100.246 100.100.100.239 SIP Request:
CANCEL sip:005622408196@100.100.100.239
Session Initiation Protocol
Request-Line: CANCEL sip:005622408196@100.100.100.239 SIP/2.0
Method: CANCEL
Resent Packet: False
Message Header
Record-Route: <sip:100.100.100.246;ftag=1587516403;lr=on>
Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0
v: SIP/2.0/UDP
192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087
f: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
t: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
i: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 CANCEL
Max-Forwards: 16
User-Agent: endpoint-type1
l: 0
No. Time Source Destination Protocol Info
12 6.042182 100.100.100.246 100.100.100.248 SIP Status: 200
canceling
Session Initiation Protocol
Status-Line: SIP/2.0 200 canceling
Status-Code: 200
Resent Packet: False
Message Header
v: SIP/2.0/UDP
192.168.1.100:5060;branch=z9hG4bK2893084087;rport=46127;received=100.100.100.248
f: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
t:
<sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=91e558155f4f8a61296d9268e8f451e8-57f4
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
SIP tag: 91e558155f4f8a61296d9268e8f451e8-57f4
i: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 CANCEL
Server: Sip EXpress router (0.9.3 (i386/linux))
Content-Length: 0
Warning: 392 100.100.100.246:5060 "Noisy feedback tells: pid=5532
req_src_ip=100.100.100.248 req_src_port=46127
in_uri=sip:0299005622408196@sipvoiss.desa.redvoiss.net
out_uri=sip:0299005622408196@sipvoiss.desa.redvoiss.net via_cnt==1"
No. Time Source Destination Protocol Info
13 6.092090 100.100.100.239 100.100.100.246 SIP Status: 200
OK
Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Status-Code: 200
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0
Via: SIP/2.0/UDP
192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087
From: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
To: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
Call-ID: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 CANCEL
User-Agent: AddPac SIP Gateway
Content-Length: 0
Record-Route: <sip:100.100.100.246;ftag=1587516403;lr=on>
No. Time Source Destination Protocol Info
14 6.102719 100.100.100.239 100.100.100.246 SIP Status: 487
Request Terminated
Session Initiation Protocol
Status-Line: SIP/2.0 487 Request Terminated
Status-Code: 487
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0
Via: SIP/2.0/UDP
192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087
From: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
To: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=9146c297a4
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
SIP tag: 9146c297a4
<sip:0299005622408196@sipvoiss.desa.redvoiss.net>
Call-ID: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 INVITE
User-Agent: AddPac SIP Gateway
Content-Length: 0
No. Time Source Destination Protocol Info
15 6.103011 100.100.100.246 100.100.100.239 SIP Request: ACK
sip:005622408196@100.100.100.239
Session Initiation Protocol
Request-Line: ACK sip:005622408196@100.100.100.239 SIP/2.0
Method: ACK
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0
f: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
i: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
To: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=9146c297a4
Thanks
Ricardo.-
28 Mar
28 Mar
12:59 a.m.
Hello again.
So, could this posible be a bug in SER?. Even if the last ACK has the To-Tag,
From-Tag and Call-id correct, SER is not matching the transaction.
Thanks
Ricardo.-
-----Mensaje original-----
De: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org]En nombre de
Ricardo Martinez
Enviado el: martes, 27 de marzo de 2007 11:51
Para: serusers(a)iptel.org
Asunto: RE: [Serusers] Problems with ACK
1:54 a.m.
On Mar 27, 2007 at 11:50, Ricardo Martinez <rmartinez(a)magenta.cl> wrote:
Thanks Greger
I'm still unable to find any mismatch. Can you help me here?. If there is no
mismatch is maybe a bug in SER?
It might be a bug, but we need more info.
First of all small correction: the 3261 transaction matching works by looking
at the via branch. If the branch starts with the magic z9hG4bK, 3261 style
transaction matching is performed: only the via branch is compared.
The callid and cseq number should also be the same (ser uses them to
generate a hashtable key).
Your last dump doesn't include the reply sent by ser to the UA and the
ACK sent by the UA to ser. I assume you have an UA with public address
100.100.100.248 which looks to be behind a nat, ser with address
100.100.100.246 and a gateway with address 100.100.100.239. The ACK
included in this dump is the ser generated ACK to the gateway's 487.
Could you send me a binary dump (e.g. tcpdump pcap file) including all the
messages?
Thanks,
Andrei
Here are more details:
No. Time Source Destination Protocol Info
6 0.363947 100.100.100.246 100.100.100.239 SIP/SDP Request:
INVITE sip:005622408196@100.100.100.239, with session description
Session Initiation Protocol
Request-Line: INVITE sip:005622408196@100.100.100.239 SIP/2.0
Method: INVITE
Resent Packet: False
Message Header
Record-Route:
<sip:0299005622408196@100.100.100.246:5060;nat=yes;ftag=1587516403;lr=on>
Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0
v: SIP/2.0/UDP
192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087
f: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
t: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
i: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 INVITE
m: sip:cl@100.100.100.248:46127
Contact Binding: sip:cl@100.100.100.248:46127
URI: sip:cl@100.100.100.248:46127\r
SIP contact address: sip:cl@100.100.100.248:46127\r
Max-Forwards: 16
User-Agent: endpoint-type1
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, REFER
Supported: timer, replaces
c: application/sdp
Accept: application/sdp
Content-Length: 294
Message body
Session Description Protocol
No. Time Source Destination Protocol Info
7 0.438768 100.100.100.239 100.100.100.246 SIP Status: 100
Trying
Session Initiation Protocol
Status-Line: SIP/2.0 100 Trying
[...]
No. Time Source Destination Protocol Info
8 1.263245 100.100.100.239 100.100.100.246 SIP/SDP Status: 183
Session Progress, with session description
Session Initiation Protocol
Status-Line: SIP/2.0 183 Session Progress
Status-Code: 183
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0
Via: SIP/2.0/UDP
192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087
From: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
To: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=9146c297a4
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
SIP tag: 9146c297a4
<sip:0299005622408196@sipvoiss.desa.redvoiss.net>
Call-ID: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 INVITE
Supported: timer, replaces, early-session
User-Agent: AddPac SIP Gateway
Contact: sip:005622408196@100.100.100.239
Contact Binding: sip:005622408196@100.100.100.239
URI: sip:005622408196@100.100.100.239\r
SIP contact address: sip:005622408196@100.100.100.239\r
Content-Type: application/sdp
Content-Length: 247
Record-Route:
<sip:0299005622408196@100.100.100.246:5060;nat=yes;ftag=1587516403;lr=on>
Message body
Session Description Protocol
No. Time Source Destination Protocol Info
9 1.265778 100.100.100.246 100.100.100.248 SIP/SDP Status: 183
Session Progress, with session description
Session Initiation Protocol
Status-Line: SIP/2.0 183 Session Progress
Status-Code: 183
Resent Packet: False
Message Header
Via: SIP/2.0/UDP
192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087
From: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
To: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=9146c297a4
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
SIP tag: 9146c297a4
<sip:0299005622408196@sipvoiss.desa.redvoiss.net>
Call-ID: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 INVITE
Supported: timer, replaces, early-session
User-Agent: AddPac SIP Gateway
Contact: sip:005622408196@100.100.100.239
Contact Binding: sip:005622408196@100.100.100.239
URI: sip:005622408196@100.100.100.239\r
SIP contact address: sip:005622408196@100.100.100.239\r
Content-Type: application/sdp
Content-Length: 247
Record-Route:
<sip:0299005622408196@100.100.100.246:5060;nat=yes;ftag=1587516403;lr=on>
Message body
Session Description Protocol
No. Time Source Destination Protocol Info
10 6.039661 100.100.100.248 100.100.100.246 SIP Request:
CANCEL sip:0299005622408196@sipvoiss.desa.redvoiss.net
Session Initiation Protocol
Request-Line: CANCEL sip:0299005622408196@sipvoiss.desa.redvoiss.net SIP/2.0
Method: CANCEL
Resent Packet: False
Message Header
v: SIP/2.0/UDP 192.168.1.100:5060;branch=z9hG4bK2893084087
f: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
t: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
i: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 CANCEL
Max-Forwards: 70
User-Agent: endpoint-type1
l: 0
No. Time Source Destination Protocol Info
11 6.042124 100.100.100.246 100.100.100.239 SIP Request:
CANCEL sip:005622408196@100.100.100.239
Session Initiation Protocol
Request-Line: CANCEL sip:005622408196@100.100.100.239 SIP/2.0
Method: CANCEL
Resent Packet: False
Message Header
Record-Route: <sip:100.100.100.246;ftag=1587516403;lr=on>
Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0
v: SIP/2.0/UDP
192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087
f: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
t: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
i: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 CANCEL
Max-Forwards: 16
User-Agent: endpoint-type1
l: 0
No. Time Source Destination Protocol Info
12 6.042182 100.100.100.246 100.100.100.248 SIP Status: 200
canceling
Session Initiation Protocol
Status-Line: SIP/2.0 200 canceling
Status-Code: 200
Resent Packet: False
Message Header
v: SIP/2.0/UDP
192.168.1.100:5060;branch=z9hG4bK2893084087;rport=46127;received=100.100.100.248
f: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
t:
<sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=91e558155f4f8a61296d9268e8f451e8-57f4
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
SIP tag: 91e558155f4f8a61296d9268e8f451e8-57f4
i: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 CANCEL
Server: Sip EXpress router (0.9.3 (i386/linux))
Content-Length: 0
Warning: 392 100.100.100.246:5060 "Noisy feedback tells: pid=5532
req_src_ip=100.100.100.248 req_src_port=46127
in_uri=sip:0299005622408196@sipvoiss.desa.redvoiss.net
out_uri=sip:0299005622408196@sipvoiss.desa.redvoiss.net via_cnt==1"
No. Time Source Destination Protocol Info
13 6.092090 100.100.100.239 100.100.100.246 SIP Status: 200
OK
Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Status-Code: 200
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0
Via: SIP/2.0/UDP
192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087
From: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
To: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
Call-ID: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 CANCEL
User-Agent: AddPac SIP Gateway
Content-Length: 0
Record-Route: <sip:100.100.100.246;ftag=1587516403;lr=on>
No. Time Source Destination Protocol Info
14 6.102719 100.100.100.239 100.100.100.246 SIP Status: 487
Request Terminated
Session Initiation Protocol
Status-Line: SIP/2.0 487 Request Terminated
Status-Code: 487
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0
Via: SIP/2.0/UDP
192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087
From: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
To: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=9146c297a4
SIP to address: sip:0299005622408196@sipvoiss.desa.redvoiss.net
SIP tag: 9146c297a4
<sip:0299005622408196@sipvoiss.desa.redvoiss.net>
Call-ID: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
CSeq: 6 INVITE
User-Agent: AddPac SIP Gateway
Content-Length: 0
No. Time Source Destination Protocol Info
15 6.103011 100.100.100.246 100.100.100.239 SIP Request: ACK
sip:005622408196@100.100.100.239
Session Initiation Protocol
Request-Line: ACK sip:005622408196@100.100.100.239 SIP/2.0
Method: ACK
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0
f: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403
SIP Display info: "cl"
SIP from address: sip:cl@sipvoiss.desa.redvoiss.net
SIP tag: 1587516403
i: e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100
To: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=9146c297a4
Thanks
Ricardo.-
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
6432
days inactive
6432
days old
4 comments
3 participants
participants (3)
-
Andrei Pelinescu-Onciul -
Greger V. Teigre -
Ricardo Martinez