Bug#454115: on pc-to-pc twinkle sends INVITE to unknown IP 81.169.145.87:5060 (registrar not configured)
package twinkle severity 454115 wishlist retitle 454115 twinkle: Can't send INVITE to sip uri without user part thanks Tim Rühsen wrote: ... sorry for that. I didn't expect twinkle works like that. of course i tried 'host 81.169.145.87' which lead to 'w87.rzone.de' which is absolutely unknown to me (it must be from my provider 'Strato'). i think, this bug can be closed. Is there a way to dial an IP directly without name? Or should I open a wishlist 'bug'? You don't need to open another bug report, I'm downgrading and retitling this report instead. Mikael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454115: on pc-to-pc twinkle sends INVITE to unknown IP 81.169.145.87:5060 (registrar not configured)
Package: twinkle Version: 1:1.1-2+b1 Severity: normal am trying to connect pc-to-pc (as described on the twinkle homepage, but without using name - so i just enter the destination IP 192.168.0.101 for example). I just enter the desired IP an hit 'Dial' which results in '503 Service Unavailable'. In the log i find that twinkle contacts the IP 81.169.145.87:5060, no matter what IP i selected. UserProfile/SIPServer/Registrar is empty and 'Register at startup' is off. 'Use Outbound Proxy' is off. NAT: 'NAT traversal not needed' is on. Here is the extract from the log: +++ 30-11-2007 12:40:28.187366 INFO SIP ::send_sip_udp Send to: 81.169.145.87:5060 INVITE sip:[EMAIL PROTECTED] SIP/2.0 Via: SIP/2.0/UDP 192.1.11.218;rport;branch=z9hG4bKlztaveet Max-Forwards: 70 To: sip:[EMAIL PROTECTED] From: Tim Ruehsen sip:[EMAIL PROTECTED];tag=frctk Call-ID: [EMAIL PROTECTED] CSeq: 710 INVITE Contact: sip:[EMAIL PROTECTED] Content-Type: application/sdp Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE Supported: replaces,norefersub,100rel User-Agent: Twinkle/1.1 Content-Length: 203 v=0 o=tim 1628269059 1659689211 IN IP4 192.1.11.218 s=- c=IN IP4 192.1.11.218 t=0 0 m=audio 8002 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 --- +++ 30-11-2007 12:40:28.212792 INFO NORMAL ::listen_udp Received ICMP from: 81.169.145.87 ICMP type: 3 ICMP code: 3 Destination of packet causing ICMP: 81.169.145.87:5060 Socket error: 111 Connection refused --- +++ 30-11-2007 12:40:28.213057 INFO NORMAL t_tc_invite::process_icmp ICMP error received. Send internal: SIP/2.0 503 Service Unavailable Via: SIP/2.0/UDP 192.1.11.218;rport;branch=z9hG4bKlztaveet To: sip:[EMAIL PROTECTED];tag=npooi From: Tim Ruehsen sip:[EMAIL PROTECTED];tag=frctk Call-ID: [EMAIL PROTECTED] CSeq: 710 INVITE Server: Twinkle/1.1 Content-Length: 0 That unknown IP 81.169.145.87 must somewhere being hardcoded... I don't want Twinkle to connect an unknown IP which can't be switched off. Do you? -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages twinkle depends on: ii kdelibs4c2a 4:3.5.8.dfsg.1-4 core libraries and binaries for al ii libasound2 1.0.15-2 ALSA library ii libboost-regex1.34.11.34.1-2 regular expression library for C++ ii libc6 2.7-2GNU C Library: Shared libraries ii libccrtp1-1.5-1 1.5.2-1 Common C++ class framework for RTP ii libcommoncpp2-1.5.3-0 1.5.9-1 A GNU package for creating portabl ii libgcc1 1:4.2.2-4GCC support library ii libgsm1 1.0.12-1 Shared libraries for GSM speech co ii libqt3-mt 3:3.3.7-9Qt GUI Library (Threaded runtime v ii libsndfile1 1.0.17-4 Library for reading/writing audio ii libspeex1 1.1.12-3 The Speex Speech Codec ii libstdc++6 4.2.2-4 The GNU Standard C++ Library v3 ii libx11-62:1.0.3-7X11 client-side library ii libxext61:1.0.3-2X11 miscellaneous extension librar ii libxml2 2.6.30.dfsg-3GNOME XML library ii libzrtpcpp-0.9.2deb00.9.2-3 ccrtp extension for zrtp/Zfone sup ii zlib1g 1:1.2.3.3.dfsg-7 compression library - runtime twinkle recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454115: on pc-to-pc twinkle sends INVITE to unknown IP 81.169.145.87:5060 (registrar not configured)
Tim Rühsen wrote: Package: twinkle Version: 1:1.1-2+b1 Severity: normal am trying to connect pc-to-pc (as described on the twinkle homepage, but without using name - so i just enter the destination IP 192.168.0.101 for example). Why can't you add a name? I just enter the desired IP an hit 'Dial' which results in '503 Service Unavailable'. In the log i find that twinkle contacts the IP 81.169.145.87:5060, no matter what IP i selected. UserProfile/SIPServer/Registrar is empty and 'Register at startup' is off. 'Use Outbound Proxy' is off. NAT: 'NAT traversal not needed' is on. Here is the extract from the log: +++ 30-11-2007 12:40:28.187366 INFO SIP ::send_sip_udp Send to: 81.169.145.87:5060 INVITE sip:[EMAIL PROTECTED] SIP/2.0 Via: SIP/2.0/UDP 192.1.11.218;rport;branch=z9hG4bKlztaveet Max-Forwards: 70 To: sip:[EMAIL PROTECTED] From: Tim Ruehsen sip:[EMAIL PROTECTED];tag=frctk ... That unknown IP 81.169.145.87 must somewhere being hardcoded... I don't want Twinkle to connect an unknown IP which can't be switched off. Do you? Apparently twinkle thinks 192.168.0.101 is a telephone number, not an IP address, and it got translated to 1921680101 and your domain name is appended resulting in [EMAIL PROTECTED] When sending the INVITE request to [EMAIL PROTECTED], twinkle looks up the IP address of openmediasystem.de, which is 81.169.145.87. Mikael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454115: on pc-to-pc twinkle sends INVITE to unknown IP 81.169.145.87:5060 (registrar not configured)
Am Montag, 3. Dezember 2007 schrieb Mikael Magnusson: Tim Rühsen wrote: Package: twinkle Version: 1:1.1-2+b1 Severity: normal am trying to connect pc-to-pc (as described on the twinkle homepage, but without using name - so i just enter the destination IP 192.168.0.101 for example). Why can't you add a name? the snom300 phone is reachable only without a name. i can test that with e.g. ekiga or linphone (address is sip:192.1.11.92). a name leads to '404 not found' message from the phone. I just enter the desired IP an hit 'Dial' which results in '503 Service Unavailable'. In the log i find that twinkle contacts the IP 81.169.145.87:5060, no matter what IP i selected. UserProfile/SIPServer/Registrar is empty and 'Register at startup' is off. 'Use Outbound Proxy' is off. NAT: 'NAT traversal not needed' is on. Here is the extract from the log: +++ 30-11-2007 12:40:28.187366 INFO SIP ::send_sip_udp Send to: 81.169.145.87:5060 INVITE sip:[EMAIL PROTECTED] SIP/2.0 Via: SIP/2.0/UDP 192.1.11.218;rport;branch=z9hG4bKlztaveet Max-Forwards: 70 To: sip:[EMAIL PROTECTED] From: Tim Ruehsen sip:[EMAIL PROTECTED];tag=frctk ... That unknown IP 81.169.145.87 must somewhere being hardcoded... I don't want Twinkle to connect an unknown IP which can't be switched off. Do you? Apparently twinkle thinks 192.168.0.101 is a telephone number, not an IP address, and it got translated to 1921680101 and your domain name is appended resulting in [EMAIL PROTECTED] When sending the INVITE request to [EMAIL PROTECTED], twinkle looks up the IP address of openmediasystem.de, which is 81.169.145.87. sorry for that. I didn't expect twinkle works like that. of course i tried 'host 81.169.145.87' which lead to 'w87.rzone.de' which is absolutely unknown to me (it must be from my provider 'Strato'). i think, this bug can be closed. Is there a way to dial an IP directly without name? Or should I open a wishlist 'bug'? Mikael -- OMS Open Media System GmbH Holzdamm 40 20099 Hamburg Fon +49-40-238878-0 Fax +49-40-238878-99 Email [EMAIL PROTECTED] Sitz und Registergericht Hamburg HRB 57616
