2 Aug
2007
2 Aug
'07
4:40 p.m.
I think that the message the most important is: after_loose: No next URI found
It cannot find the next URI...
What should I change in my configuration..?
0(2091) SIP Request:
0(2091) method: <BYE>
0(2091) uri: <sip:103@82.127.0.79:1027>
0(2091) version: <SIP/2.0>
0(2091) parse_headers: flags=2
0(2091) Found param type 232, <branch> = <z9hG4bK5748026460769314710>;
state=16
0(2091) end of header reached, state=5
0(2091) parse_headers: Via found, flags=2
0(2091) parse_headers: this is the first via
0(2091) After parse_msg...
0(2091) preparing to run routing scripts...
0(2091) parse_headers: flags=100
0(2091) DEBUG: add_param: tag=c0a80101-22a2095
0(2091) DEBUG:parse_to:end of header reached, state=29
0(2091) DBUG:parse_to: display={}, ruri={sip:103@sd-7501.dedibox.fr:5060;user=phone}
0(2091) DEBUG: get_hdr_field: <To> [67];
uri=[sip:103@sd-7501.dedibox.fr:5060;user=phone]
0(2091) DEBUG: to body [<sip:103@sd-7501.dedibox.fr:5060;user=phone>]
0(2091) get_hdr_field: cseq <CSeq>: <2> <BYE>
0(2091) DEBUG:maxfwd:is_maxfwd_present: value = 70
0(2091) DBG:maxfwd:process_maxfwd_header: value 70 decreased to 10
0(2091) !!!!!!!!! NAT UAC TEST 19 SUCEDEED
0(2091) parse_headers: flags=80
0(2091) DEBUG: get_hdr_body : content_length=0
0(2091) found end of header
0(2091) DEBUG: add_param: tag=c0a80101-a5c455
0(2091) DEBUG:parse_to:end of header reached, state=29
0(2091) DBUG:parse_to: display={"101"},
ruri={sip:101@sd-7501.dedibox.fr:5060;user=phone}
0(2091) parse_headers: flags=200
0(2091) is_preloaded: No
0(2091) grep_sock_info - checking if host==us: 11==12 && [82.127.0.79] ==
[88.191.45.91]
0(2091) grep_sock_info - checking if port 5060 matches port 1027
0(2091) grep_sock_info - checking if host==us: 11==12 && [82.127.0.79] ==
[88.191.45.91]
0(2091) grep_sock_info - checking if port 5060 matches port 1027
0(2091) DEBUG:check_self: host != me
0(2091) grep_sock_info - checking if host==us: 12==12 && [88.191.45.91] ==
[88.191.45.91]
0(2091) grep_sock_info - checking if port 5060 matches port 5060
0(2091) after_loose: Topmost route URI:
'sip:88.191.45.91:5060;lr=on;ftag=c0a80101-a5c455' is me
0(2091) parse_headers: flags=200
0(2091) found end of header
0(2091) find_next_route: No next Route HF found
0(2091) after_loose: No next URI found
0(2091) DBG:rr:run_rr_callbacks: callback id 0 entered with
<lr=on;ftag=c0a80101-a5c455>
Dan-Cristian Bogos a écrit :
Hi Marc,
it will help more if u will post full dialog from INVITE to BYE coming
in and out from the server. It is important to check whether openser
forwards the BYEs and if the end party listens on that port.
Cheers,
DanB
On 8/2/07, Marc LEURENT <lftsy(a)free.fr> wrote:
> STUN seems to be working
>
> In openserctl ul show, I have:
> AOR:: 103 Contact:: sip:103@82.127.0.79:1028;user=phone Q=
> AOR:: 101 Contact:: sip:101@82.127.0.79:1313;user=phone Q=
>
>
> And tcpdump -i eth0 -n port 5060 returns:
> 13:47:44.375374 IP 88.191.45.91.5060 > 82.127.0.79.1027: SIP, length: 241
> 13:47:44.375396 IP 88.191.45.91.5060 > 82.127.0.79.1312: SIP, length: 241
> 13:47:44.422471 IP 82.127.0.79.1027 > 88.191.45.91.5060: SIP, length: 276
> 13:47:44.426415 IP 82.127.0.79.1312 > 88.191.45.91.5060: SIP, length: 275
>
>
> And my ngrep returns
>
>
> #
> U 88.191.45.91:5060 -> 82.127.0.79:1027
> OPTIONS sip:82.127.0.79:1027 SIP/2.0.
> Via: SIP/2.0/UDP 88.191.45.91:5060;branch=0.
> From: sip:pinger@sd-7501.dedibox.fr;tag=7ad21f92.
> To: sip:82.127.0.79:1027.
> Call-ID: 90f2eea1-5c41f342-a91(a)88.191.45.91.
> CSeq: 1 OPTIONS.
> Content-Length: 0.
> .
>
> #
> U 88.191.45.91:5060 -> 82.127.0.79:1312
> OPTIONS sip:82.127.0.79:1312 SIP/2.0.
> Via: SIP/2.0/UDP 88.191.45.91:5060;branch=0.
> From: sip:pinger@sd-7501.dedibox.fr;tag=8ad21f92.
> To: sip:82.127.0.79:1312.
> Call-ID: 90f2eea1-6c41f342-a91(a)88.191.45.91.
> CSeq: 1 OPTIONS.
> Content-Length: 0.
> .
>
> #
> U 82.127.0.79:1027 -> 88.191.45.91:5060
> SIP/2.0 481 CallLeg/Transaction Does Not Exist.
> Via: SIP/2.0/UDP 88.191.45.91:5060;branch=0.
> From: <sip:pinger@sd-7501.dedibox.fr>;tag=7ad21f92.
> To: <sip:82.127.0.79:1027>;tag=c0a80101-1db9be2.
> Call-ID: 90f2eea1-5c41f342-a91(a)88.191.45.91.
> CSeq: 1 OPTIONS.
> Content-Length: 0.
> .
>
> #
> U 82.127.0.79:1312 -> 88.191.45.91:5060
> SIP/2.0 481 CallLeg/Transaction Does Not Exist.
> Via: SIP/2.0/UDP 88.191.45.91:5060;branch=0.
> From: <sip:pinger@sd-7501.dedibox.fr>;tag=8ad21f92.
> To: <sip:82.127.0.79:1312>;tag=c0a80101-573ff0.
> Call-ID: 90f2eea1-6c41f342-a91(a)88.191.45.91.
> CSeq: 1 OPTIONS.
> Content-Length: 0.
>
>
>
>
>
>
> Iñaki Baz Castillo a écrit :
>> El Thursday 02 August 2007 12:25:07 Marc LEURENT escribió:
>>> #
>>> U 82.127.0.79:1312 -> 88.191.45.91:5060
>>> BYE sip:103@82.127.0.79:1027 SIP/2.0.
>>> Via: SIP/2.0/UDP 82.127.0.79:1313;branch=z9hG4bK8030359792092547043.
>>> From:
"101"<sip:101@sip.leurent.eu:5060;user=phone>;tag=c0a80101-4c5eed.
>>> To: <sip:103@sip.leurent.eu:5060;user=phone>;tag=c0a80101-1d0bb0d.
>>> Call-ID: 66464a0-c0a80101-0-1f(a)192.168.95.4.
>>> CSeq: 2 BYE.
>>> Max-Forwards: 70.
>>> Route: <sip:88.191.45.91:5060;lr=on;ftag=c0a80101-4c5eed>.
>>> User-Agent: THOMSON ST2030 hw0 fw1.50 00-0E-50-4E-AF-AE.
>>> Content-Length: 0.
>> What more is after this message?
>> Did you try tcpdump to monitorize to with IP:port are the messages sent?
>>
> _______________________________________________
> Users mailing list
> Users(a)openser.org
> http://openser.org/cgi-bin/mailman/listinfo/users
>