Re: [Siproxd-users] Failure to receive ACK with Ekiga
Status: Beta
Brought to you by:
tries
Menu
▾
▴
Re: [Siproxd-users] Failure to receive ACK with Ekiga
|
From: Felix L. <fel...@am...> - 2010-12-01 01:47:40
|
Hello Thomas, The excerpt below is from the debug log. Server is Sipphone. Client is Ekiga. Network is complex. Nested NAT. Is it possible the user name mismatch has anything to do with it? Thank you, Felix Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: siproxd.c:526 received SIP type REQ:ACK Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: utils.c:349 fetching outbound IP by HOSTNAME Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: proxy.c:89 proxy_request Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: route_processing.c:63 route_preprocess: no Route header present Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: utils.c:130 DNS lookup - from cache: 192.168.11.177 -> 192.168.11.177 Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: sip_utils.c:1018 sip_find_direction: reghost:192.168.11.177 ip:198.65.166.131 Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: sip_utils.c:279 comparing urls: sip:7476686228@74.125.66.80 <sip%3A7476686228@74.125.66.80> -> sip:17476686228@72.254.95.107 <sip%3A17476686228@72.254.95.107> Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: sip_utils.c:294 compare_url: username mismatch Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: sip_utils.c:279 comparing urls: sip:7476686228@74.125.66.80 <sip%3A7476686228@74.125.66.80> -> sip:174...@pr...<sip%3A1...@pr...> Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: sip_utils.c:294 compare_url: username mismatch Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: sip_utils.c:279 comparing urls: sip:7476686228@72.254.95.107 <sip%3A7476686228@72.254.95.107> -> sip:17476686228@72.254.95.107 <sip%3A17476686228@72.254.95.107> Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: sip_utils.c:294 compare_url: username mismatch Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: sip_utils.c:279 comparing urls: sip:7476686228@72.254.95.107 <sip%3A7476686228@72.254.95.107> -> sip:174...@pr...<sip%3A1...@pr...> Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: sip_utils.c:294 compare_url: username mismatch Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: utils.c:382 fetching interface IP by INTERFACE [1] Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: utils.c:454 ifaddr lookup - from cache: eth0 -> 192.168.11.1 UP Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: utils.c:349 fetching outbound IP by HOSTNAME Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: utils.c:130 DNS lookup - from cache: 72.254.95.107 -> 72.254.95.107 Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: sip_utils.c:1179 sip_find_direction: unable to determine direction of SIP packet Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: plugin_logcall.c:120 INFO:ACK Call: +16172295005@10.218.1.144 -> 7476686228@74.125.66.80 Nov 30 17:15:01 buffalo-linkstation siproxd[6237]: proxy.c:242 request [ACK] from/to unregistered UA (RQ: +16172295005@10.218.1.144 -> 7476686228@72.254.95.107) On Mon, Nov 29, 2010 at 10:08 AM, Thomas Ries <tr...@gm...> wrote: > Can you provide a debug log of siproxd? > I'd like to see how the dropped ACK looks like. There is/was a know > issue with ekiga.net. In that articular case a wrong Content-Lenght did > cause the packet to be dropped by libosip2. > Are there any warnings/errors in the siproxd log file? > > Regards, > /Thomas > > On 29 Nov, Felix Lechner wrote: > > Hello, > > > > Is anyone aware of a situation when Siproxd would swallow the ACK in > > an INVITE handshake? > > > > Below are my logs. > > > > Ekiga terminates because of failure to receive ACK. > > > > Siproxd runs on gateway at 192.168.11.1. Client is 192.168.11.177. > > Call is an inbound Google Voice call via Sipphone/Gizmo5. > > > > Regards, > > Felix > > > > * * * Between Ekiga and my gateway running Siproxd: > > > > No. Time Source Destination > > Protocol Info > > 1 0.000000 192.168.11.1 192.168.11.177 > > SIP/SDP Request: INVITE > > sip:17476686228@192.168.11.177 <sip%3A17476686228@192.168.11.177>< > sip%3A17476686228@192.168.11.177 <sip%253A17476686228@192.168.11.177>>, > > with session description > > 2 0.004324 192.168.11.177 192.168.11.1 SIP > > Status: 100 Trying > > 3 0.011226 192.168.11.177 192.168.11.1 SIP > > Status: 180 Ringing > > 4 1.221986 192.168.11.177 192.168.11.1 SIP > > Request: REGISTER sip:proxy01.sipphone.com > > 5 1.668841 192.168.11.1 192.168.11.177 SIP > > Status: 200 OK (1 bindings) > > 6 1.676359 192.168.11.177 192.168.11.1 SIP > > Request: SUBSCRIBE > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > 7 2.116070 192.168.11.1 192.168.11.177 SIP > > Request: SUBSCRIBE > > sip:17476686228@192.168.11.177 <sip%3A17476686228@192.168.11.177>< > sip%3A17476686228@192.168.11.177 <sip%253A17476686228@192.168.11.177>> > > 8 2.119343 192.168.11.177 192.168.11.1 SIP > > Status: 405 Method Not Allowed > > 9 2.178203 192.168.11.177 192.168.11.1 SIP > > Request: SUBSCRIBE > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > 10 2.208363 192.168.11.177 198.65.166.131 > > SIP/XML Request: PUBLISH > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > 11 2.598451 192.168.11.1 192.168.11.177 SIP > > Status: 405 Method Not Allowed > > 12 2.638144 192.168.11.1 192.168.11.177 SIP > > Status: 405 Method Not Allowed > > 13 2.709676 192.168.11.177 198.65.166.131 > > SIP/XML Request: PUBLISH > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > 14 3.674083 192.168.11.177 192.168.11.1 > > SIP/SDP Status: 200 OK, with session description > > 15 3.710301 192.168.11.177 198.65.166.131 > > SIP/XML Request: PUBLISH > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > 16 4.174685 192.168.11.177 192.168.11.1 > > SIP/SDP Status: 200 OK, with session description > > 17 5.710938 192.168.11.177 198.65.166.131 > > SIP/XML Request: PUBLISH > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > 18 31.680208 192.168.11.177 192.168.11.1 SIP > > Request: REGISTER sip:proxy01.sipphone.com > > 19 32.181097 192.168.11.177 192.168.11.1 SIP > > Request: REGISTER sip:proxy01.sipphone.com > > 20 32.814627 192.168.11.1 192.168.11.177 SIP > > Status: 200 OK (1 bindings) > > 21 32.822995 192.168.11.177 192.168.11.1 SIP > > Request: SUBSCRIBE > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > 22 32.829732 192.168.11.1 192.168.11.177 SIP > > Status: 200 OK (1 bindings) > > 23 33.328976 192.168.11.1 192.168.11.177 SIP > > Request: SUBSCRIBE > > sip:17476686228@192.168.11.177 <sip%3A17476686228@192.168.11.177>< > sip%3A17476686228@192.168.11.177 <sip%253A17476686228@192.168.11.177>> > > 24 33.331561 192.168.11.177 192.168.11.1 SIP > > Request: SUBSCRIBE > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > 25 33.333971 192.168.11.177 192.168.11.1 SIP > > Status: 405 Method Not Allowed > > 26 33.448979 192.168.11.177 198.65.166.131 > > SIP/XML Request: PUBLISH > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > 27 33.733403 192.168.11.1 192.168.11.177 SIP > > Request: SUBSCRIBE > > sip:17476686228@192.168.11.177 <sip%3A17476686228@192.168.11.177>< > sip%3A17476686228@192.168.11.177 <sip%253A17476686228@192.168.11.177>> > > 28 33.738981 192.168.11.177 192.168.11.1 SIP > > Status: 405 Method Not Allowed > > 29 33.761589 192.168.11.1 192.168.11.177 SIP > > Status: 405 Method Not Allowed > > 30 33.950697 192.168.11.177 198.65.166.131 > > SIP/XML Request: PUBLISH > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > 31 34.951540 192.168.11.177 198.65.166.131 > > SIP/XML Request: PUBLISH > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > 32 35.745194 192.168.11.177 192.168.11.1 SIP > > Request: BYE sip:+16172295005@74.125.46.80:24000 > > 33 36.246353 192.168.11.177 192.168.11.1 SIP > > Request: BYE sip:+16172295005@74.125.46.80:24000 > > 34 36.266313 192.168.11.1 192.168.11.177 SIP > > Status: 404 Not here > > 35 36.715199 192.168.11.1 192.168.11.177 SIP > > Status: 404 Not here > > 36 36.951550 192.168.11.177 198.65.166.131 > > SIP/XML Request: PUBLISH > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > > > * * * Between Siproxd and the outside world: > > > > No. Time Source Destination > > Protocol Info > > 1 0.000000 198.65.166.131 10.11.39.174 > > SIP/SDP Request: INVITE > > sip:17476686228@72.254.95.107 <sip%3A17476686228@72.254.95.107>< > sip%3A17476686228@72.254.95.107 <sip%253A17476686228@72.254.95.107>>, > > with session description > > 2 0.017487 10.11.39.174 198.65.166.131 SIP > > Status: 100 Trying > > 3 0.024133 10.11.39.174 198.65.166.131 SIP > > Status: 180 Ringing > > 4 1.234185 10.11.39.174 198.65.166.131 SIP > > Request: REGISTER sip:proxy01.sipphone.com > > 5 1.673553 198.65.166.131 10.11.39.174 SIP > > Status: 200 OK (1 bindings) > > 6 1.688100 10.11.39.174 198.65.166.131 SIP > > Request: SUBSCRIBE > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > 7 2.120416 198.65.166.131 10.11.39.174 SIP > > Request: SUBSCRIBE > > sip:17476686228@72.254.95.107 <sip%3A17476686228@72.254.95.107>< > sip%3A17476686228@72.254.95.107 <sip%253A17476686228@72.254.95.107>> > > 8 2.131477 10.11.39.174 198.65.166.131 SIP > > Status: 405 Method Not Allowed > > 9 2.189953 10.11.39.174 198.65.166.131 SIP > > Request: SUBSCRIBE > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > 10 2.603282 198.65.166.131 10.11.39.174 SIP > > Status: 405 Method Not Allowed > > 11 2.643286 198.65.166.131 10.11.39.174 SIP > > Status: 405 Method Not Allowed > > 12 3.689478 10.11.39.174 198.65.166.131 > > SIP/SDP Status: 200 OK, with session description > > 13 4.188695 10.11.39.174 198.65.166.131 > > SIP/SDP Status: 200 OK, with session description > > 14 4.289813 198.65.166.131 10.11.39.174 SIP > > Request: ACK sip:7476686228@72.254.95.107:5060 > > 15 4.297488 10.11.39.174 198.65.166.131 SIP > > Status: 408 Request Timeout > > 16 4.797679 198.65.166.131 10.11.39.174 SIP > > Request: ACK sip:7476686228@72.254.95.107:5060 > > 17 4.804459 10.11.39.174 198.65.166.131 SIP > > Status: 408 Request Timeout > > 18 32.231665 10.11.39.174 198.65.166.131 SIP > > Request: REGISTER sip:proxy01.sipphone.com > > 19 32.236893 10.11.39.174 198.65.166.131 SIP > > Request: REGISTER sip:proxy01.sipphone.com > > 20 32.819967 198.65.166.131 10.11.39.174 SIP > > Status: 200 OK (1 bindings) > > 21 32.831952 198.65.166.131 10.11.39.174 SIP > > Status: 200 OK (1 bindings) > > 22 32.834899 10.11.39.174 198.65.166.131 SIP > > Request: SUBSCRIBE > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > 23 33.332820 198.65.166.131 10.11.39.174 SIP > > Request: SUBSCRIBE > > sip:17476686228@72.254.95.107 <sip%3A17476686228@72.254.95.107>< > sip%3A17476686228@72.254.95.107 <sip%253A17476686228@72.254.95.107>> > > 24 33.343388 10.11.39.174 198.65.166.131 SIP > > Request: SUBSCRIBE > > sip:174...@pr...<sip%3A1...@pr...> > <sip%3A1...@pr...<sip%253...@pr...> > > > > 25 33.347591 10.11.39.174 198.65.166.131 SIP > > Status: 405 Method Not Allowed > > 26 33.736708 198.65.166.131 10.11.39.174 SIP > > Request: SUBSCRIBE > > sip:17476686228@72.254.95.107 <sip%3A17476686228@72.254.95.107>< > sip%3A17476686228@72.254.95.107 <sip%253A17476686228@72.254.95.107>> > > 27 33.752125 10.11.39.174 198.65.166.131 SIP > > Status: 405 Method Not Allowed > > 28 33.765718 198.65.166.131 10.11.39.174 SIP > > Status: 405 Method Not Allowed > > 29 35.063947 10.11.39.174 198.65.166.165 STUN > > Message: Binding Request > > 30 35.543214 198.65.166.165 10.11.39.174 STUN > > Message: Binding Response > > 31 35.759343 10.11.39.174 74.125.46.80 SIP > > Request: BYE sip:+16172295005@74.125.46.80:24000 > > 32 36.257008 74.125.46.80 10.11.39.174 SIP > > Status: 404 Not here > > 33 36.271817 10.11.39.174 74.125.46.80 SIP > > Request: BYE sip:+16172295005@74.125.46.80:24000 > > 34 36.720896 74.125.46.80 10.11.39.174 SIP > > Status: 404 Not here > > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > Tap into the largest installed PC base & get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > _______________________________________________ > Siproxd-users mailing list > Sip...@li... > https://lists.sourceforge.net/lists/listinfo/siproxd-users > > |
