From jt at dpets.co.uk Fri Apr 3 14:14:17 2015 From: jt at dpets.co.uk (John Talbut) Date: Fri, 03 Apr 2015 15:14:17 +0100 Subject: [Ekiga-list] STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 Message-ID: <551EA039.5030205@dpets.co.uk> I am getting the "Ekiga did not manage to configure your network settings automatically" message. I have followed the instructions and checked my router settings, which seem correct (I think I have used Ekiga before without this problem). Using the command: ekiga -d 4 2>&1 | grep STUN I get: 2015/04/03 15:02:04.701 0:02.756 Ekiga Started STUN detector 2015/04/03 15:02:07.171 0:05.226 StunDetector:0xad47db40 STUN No response to STUN server 77.72.174.167:3478 2015/04/03 15:02:07.172 0:05.226 StunDetector:0xad47db40 OPAL STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 2015/04/03 15:02:08.556 0:06.610 Housekeeper:0xad8dab40 Ekiga Stopped STUN detector 2015/04/03 15:02:11.091 0:09.146 subscriber:0xaac14b40 STUN STUN server 77.72.174.167:3478 unexpectedly went offline getting external address. If the STUN server is replying to 127.0.0.1 then I imagine that the router would block it since this is just a loopback address. Any suggestions about what is wrong. John From eugen.dedu at univ-fcomte.fr Fri Apr 3 14:38:01 2015 From: eugen.dedu at univ-fcomte.fr (Eugen Dedu) Date: Fri, 03 Apr 2015 16:38:01 +0200 Subject: [Ekiga-list] STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 In-Reply-To: <551EA039.5030205@dpets.co.uk> References: <551EA039.5030205@dpets.co.uk> Message-ID: <551EA5C9.2030109@univ-fcomte.fr> On 03/04/15 16:14, John Talbut wrote: > I am getting the "Ekiga did not manage to configure your network > settings automatically" message. I have followed the instructions and > checked my router settings, which seem correct (I think I have used > Ekiga before without this problem). > > Using the command: ekiga -d 4 2>&1 | grep STUN > I get: > > 2015/04/03 15:02:04.701 0:02.756 > Ekiga Started STUN detector > 2015/04/03 15:02:07.171 0:05.226 StunDetector:0xad47db40 > STUN No response to STUN server 77.72.174.167:3478 > 2015/04/03 15:02:07.172 0:05.226 StunDetector:0xad47db40 > OPAL STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 > 2015/04/03 15:02:08.556 0:06.610 Housekeeper:0xad8dab40 > Ekiga Stopped STUN detector > 2015/04/03 15:02:11.091 0:09.146 subscriber:0xaac14b40 > STUN STUN server 77.72.174.167:3478 unexpectedly went offline getting > external address. > > If the STUN server is replying to 127.0.0.1 then I imagine that the > router would block it since this is just a loopback address. Right. The problem is "No response to STUN server". This means it cannot contact it. Why? Possible answers: - you are not connected to Internet (I suppose this is not your case, right?) - there is a firewall which blocks those packets STUN uses ports 3478 to 3479 (perhaps the following ones too), does a machine block these ports? -- Eugen From jt at dpets.co.uk Fri Apr 3 15:10:35 2015 From: jt at dpets.co.uk (John Talbut) Date: Fri, 03 Apr 2015 16:10:35 +0100 Subject: [Ekiga-list] STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 In-Reply-To: <551EA5C9.2030109@univ-fcomte.fr> References: <551EA039.5030205@dpets.co.uk> <551EA5C9.2030109@univ-fcomte.fr> Message-ID: <551EAD6B.5020109@dpets.co.uk> On 03/04/15 15:38, Eugen Dedu wrote: > On 03/04/15 16:14, John Talbut wrote: >> I am getting the "Ekiga did not manage to configure your network >> settings automatically" message. I have followed the instructions and >> checked my router settings, which seem correct (I think I have used >> Ekiga before without this problem). >> >> Using the command: ekiga -d 4 2>&1 | grep STUN >> I get: >> >> 2015/04/03 15:02:04.701 0:02.756 >> Ekiga Started STUN detector >> 2015/04/03 15:02:07.171 0:05.226 StunDetector:0xad47db40 >> STUN No response to STUN server 77.72.174.167:3478 >> 2015/04/03 15:02:07.172 0:05.226 StunDetector:0xad47db40 >> OPAL STUN server "stun.ekiga.net" replies Blocked, external IP >> 127.0.0.1 >> 2015/04/03 15:02:08.556 0:06.610 Housekeeper:0xad8dab40 >> Ekiga Stopped STUN detector >> 2015/04/03 15:02:11.091 0:09.146 subscriber:0xaac14b40 >> STUN STUN server 77.72.174.167:3478 unexpectedly went offline getting >> external address. >> >> If the STUN server is replying to 127.0.0.1 then I imagine that the >> router would block it since this is just a loopback address. > > Right. > > The problem is "No response to STUN server". This means it cannot > contact it. Why? Possible answers: > - you are not connected to Internet (I suppose this is not your case, > right?) > - there is a firewall which blocks those packets > > STUN uses ports 3478 to 3479 (perhaps the following ones too), does a > machine block these ports? > Thanks Eugen I had checked and have rechecked my router and ports 3478 - 3479 are allowed. Also I can successfully ping and run traceroute to 77.72.174.167. John From law_ence.dev at ntlworld.com Fri Apr 3 16:02:04 2015 From: law_ence.dev at ntlworld.com (ael) Date: Fri, 3 Apr 2015 17:02:04 +0100 Subject: [Ekiga-list] STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 In-Reply-To: <551EA039.5030205@dpets.co.uk> References: <551EA039.5030205@dpets.co.uk> Message-ID: <20150403160204.GB3067@shelf.conquest> On Fri, Apr 03, 2015 at 03:14:17PM +0100, John Talbut wrote: > I am getting the "Ekiga did not manage to configure your network settings > automatically" message. I have followed the instructions and checked my I too have *suddenly* started getting those messages from ekiga, which seems to work properly with 2 sip servers notwithstanding, but not with ekiga-net. So far I have not investigated. I am on debian-testing (for now) and regularly update. I assume that one of the recent updates probably to a library is responsible. Unless I missed it, ekiga itself has not been updated recently. Likewise my router configuration has not changed. Checking with gconf-editor, the stun server is set to stun.ekiga.net. The failure message from ekiga-net is "Globally not acceptable". This may, or may not, be useful information, at least to Eugen. ael From bittwister2 at gmail.com Fri Apr 3 16:08:45 2015 From: bittwister2 at gmail.com (mdbug) Date: Fri, 03 Apr 2015 11:08:45 -0500 Subject: [Ekiga-list] STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 In-Reply-To: <551EAD6B.5020109@dpets.co.uk> References: <551EA039.5030205@dpets.co.uk> <551EA5C9.2030109@univ-fcomte.fr> <551EAD6B.5020109@dpets.co.uk> Message-ID: <551EBB0D.4030703@gmail.com> On 04/03/2015 10:10 AM, John Talbut wrote: > I had checked and have rechecked my router and ports 3478 - 3479 are > allowed. Also I can successfully ping and run traceroute to 77.72.174.167. > I would suggest running a VOIP port check. Change _registar to your sip provider in the attached script and see what happens. Do read third paragraph of header for needed applications. -------------- next part -------------- #!/bin/bash #*********************************************************************** #* #* ck_voip - check voip ports version 2.1 #* #* Verify ports used by ekiga are open on pc and accessible #* through pc firewall and modem. #* Verify DiamondCard SIP servers have not blacklisted your WAN ip. #* #* Uses nc from netcat-openbsd rpm to test port connections #* wget from wget rpm, #* pkill from procps rpm, #* netstat from net-tools rpm, and #* dig from bind-utils rpm to check sip.diamondcard.us servers. #* #* If you are not going to be using the ports, and it is not marked required #* free to remove the line from the port_ary. #* #* Do change _registar="sip.diamondcard.us" to your VOIP carrier #* #* #* If behind NAT router, read #* http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router #* #* #* Required /etc/shorewall/rules snippet follows: #* #* # ekiga UDP Through NAT (STUN) ports #* ACCEPT $FW net udp 3478:3479 #* ACCEPT net $FW udp 3478:3479 #* #* # ekiga incomming SIP VoIP, Windows Messenger ports #* ACCEPT $FW net udp 5000:5100 #* ACCEPT net $FW udp 5000:5100 #* #* # ekiga RTP #* ACCEPT net $FW udp 7070 #* ACCEPT net $FW udp 16382 #* #* # ekiga incomming H.323, Netmeeting ports #* ACCEPT net $FW tcp 1720 #* ACCEPT $FW net tcp 1720 #* ACCEPT $FW net tcp 30000:30010 #* ACCEPT net $fw tcp 30000:30010 #* #* #*********************************************************************** set -u export LC_ALL=C _exe=$0 _app=$(basename $_exe) _dport=0 declare -a _errors=("") _fault_flg=0 _fault_msg="" _ipv_mode="-4" ix=0 _lan_ip="" _msg="" _nc_app="nc" _pkt_sw="" _pkt="-u" _registar="sip.diamondcard.us" _required="" _rpm="" _servers="" _servers_ip="" _sport=38564 _svr_fn=$HOME/tmp/$_app.log _target="$_lan_ip" _test="" _test_msg="" _test_type="" _wan_ip="" declare -a port_ary=( "3478 udp mandatory Outgoing STUN for SIP (phone calls) and RTP (video)." "3479 udp mandatory Outgoing STUN for calls and video." "5060 udp required SIP listen port for incoming SIP signaling." "5000 udp required SIP SIP signaling range 5000-5100." "5100 udp required SIP end of SIP 5000-5100 and H.323 gatekeepers range." "5004 udp required RTP Incoming traffic from the other end. Often 5004, 7070, 16382." "7070 udp optional RTP Incoming traffic from the other end. Often 5004, 7070, 16382." "16382 udp required RTP is the IETF standard used to transport audio and video. " "1720 tcp optional H.323 Listening port for H.323 gatekeepers (Netmeeting)." "30000 tcp optional H.245 channel for old H.323 implementations (Netmeeting). " "30010 tcp optional H.245 end of 30000-30010 range (Netmeeting)." ) function port_test () { _fault_flg=0 _errors=("") if [ "$_test_type" = "LAN" ] ; then _test_msg="pc firewall" _target="$_lan_ip" else _test_msg="router firewall" _target="$_wan_ip" fi echo " " echo "Testing $_test_type $_target ports" i=0 while [ $i -ne ${#port_ary[@]} ] ; do set -- $(echo ${port_ary[$i]}) _dport=$1 _pkt=$2 _required=$3 shift 3 _test="$@" if [ "$_pkt" = "udp" ] ; then _pkt_sw="-u" else _pkt_sw="" fi _test_args="$_ipv_mode -s $_sport $_pkt_sw -w 3 $_target" rm -f $_svr_fn /bin/echo -n "$_required $_pkt port $_dport " _msg="$_test_type $_test_msg port ${port_ary[$i]}" $_nc_app $_ipv_mode -l $_pkt_sw $_dport > $_svr_fn 2>&1 & /bin/echo "$_msg" |$_nc_app $_test_args $_dport _count=$(grep -c "$_msg" $_svr_fn) if [ $_count -eq 0 ] ; then /bin/echo " FAILED" (( _fault_flg++ )) _errors+=("") _errors+=("$_required $_test_type $_pkt $_dport FAILED") _errors+=("$_test") _errors+=("") _errors+=("Sent: $_msg ") _errors+=("Received: $(cat $_svr_fn )") _errors+=("") _errors+=("Run netstat | grep $_dport") _errors+=("if you have port in use errors.") else /bin/echo " passed" fi (( i++ )) done /bin/echo " " } # end function port_test #********************************** #* main code start here #********************************** pgrep -f ekiga > /dev/null 2>&1 if [ $? -eq 0 ] ; then echo " ekiga is running somewhere. You need to stop it " exit 1 fi #********************************** #* Verify needed apps are installed #********************************** _apps="pkill nc wget dig hostname netstat /bin/echo" for _app in $_apps ; do type $_app > /dev/null 2>&1 if [ $? -ne 0 ] ; then _errors+=("unable to find $_app") (( _fault_flg++ )) fi done if [ $_fault_flg -gt 0 ] ; then echo " $_exe fatal error:" for ix in ${!_errors[*]} ; do printf " %s\n" "${_errors[$ix]}" done echo "Please install missing application " exit 1 fi _lan_ip=$(hostname --ip-address) _wan_ip=$(wget -qO - http://myip.dnsomatic.com/) mkdir -p $HOME/tmp _nc_app=$(type -p nc) pkill -u $USER -f $_nc_app > /dev/null 2>&1 #************************************************** #* check LAN pc firewall then WAN router ports #************************************************** echo " Testing LAN PC firewall, WAN Router ports and Registar sip server connectivity " for _test_type in LAN WAN ; do port_test if [ $_fault_flg -ne 0 ] ; then break fi done pkill -u $USER -f $_nc_app > /dev/null 2>&1 sleep 1 echo "ignore any Terminated \$_nc_app \$_ipv_mode .... messages " if [ $_fault_flg -gt 0 ] ; then if [ ${#_errors[*]} -gt 0 ] ; then echo "$_exe fatal error:" for ix in ${!_errors[*]} ; do printf " %s\n" "${_errors[$ix]}" done echo " Solution:" if [ "$_test_type" = "LAN" ] ; then echo "Open FAILED port in $_test_type's firewall" echo "Allow ip/app in $_target's /etc/hosts.allow or" echo "Remove ip/app in $_target's /etc/hosts.deny" echo "if you are using tcpwrappers and modified those files" else echo "Open and forward FAILED port to LAN $_lan_ip" echo "in the $_test_type's router" fi fi echo " Clear all port FAILED failures to finish $_exe testing. Assuming you did not get any nc: errors; LAN port failures are a PC firewall problem. Maybe /etc/hosts.(allow | deny) if you are using them. WAN failures are a ROUTER firewall problem and you need to open/forward ports to your LAN pc For any questions about ports/router, refer to http://wiki.ekiga.org/index.php/Manual#Using_Ekiga_with_routers_and_firewalls If you get $_nc_app argument error, then you do not have a compatible netcat-openbsd $_nc_app application. " exit 1 fi echo " Testing sip servers by ip then by name. " #************************************************* #* get registar's sip udp server and ip address #************************************************* while read -r line; do set -- $line _servers="$_servers $4" set -- $(host $4) _servers_ip="$_servers_ip $4" done < <((dig +short _sip._udp.$_registar SRV)) #********************************************* #* ping by ip then by name #********************************************* for _serv in $_servers_ip $_servers ; do _cmd="ping -c1 -w2 $_serv" /bin/echo -n "$_cmd" $_cmd > /dev/null 2>&1 if [ $? -ne 0 ] ; then /bin/echo " FAILED" (( _fault_flg++ )) else /bin/echo " passed" fi done /bin/rm $_svr_fn if [ $_fault_flg -ne 0 ] ; then echo " If one sip server FAILED and the other passed, then I am betting your WAN ip ($_wan_ip) has been blacklisted. You get blacklisted after X number of failed connection attempts. You will need to contact diamond to clear it from their blacklist. http://wiki.diamondcard.us/BlockdIp Repeated server pings can also get you blacklisted. :( " else echo " Yay, if all tests passed, that indicates echo test should work. You may want to consider running something like audacity to check microphone input and on what device before setting it in Ekiga preferences. Assuming you have the account configured correctly. I had to remove the Ekiga account, on one ekiga release, to get my diamond account working. My Account settings: Name: sip.diamondcard.us Registrar: sip.diamondcard.us User and Authentication user are both the same value. My Audio-> codec preference order had to be PCMU PCMA Speex All others not selected. I have not done any video call testing. " fi #****************** end ck_voip ********************************************* From jt at dpets.co.uk Sat Apr 4 05:15:47 2015 From: jt at dpets.co.uk (John Talbut) Date: Sat, 04 Apr 2015 06:15:47 +0100 Subject: [Ekiga-list] STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 In-Reply-To: <551EBB0D.4030703@gmail.com> References: <551EA039.5030205@dpets.co.uk> <551EA5C9.2030109@univ-fcomte.fr> <551EAD6B.5020109@dpets.co.uk> <551EBB0D.4030703@gmail.com> Message-ID: <551F7383.9040507@dpets.co.uk> On 03/04/15 17:08, mdbug wrote: > > > On 04/03/2015 10:10 AM, John Talbut wrote: > >> I had checked and have rechecked my router and ports 3478 - 3479 are >> allowed. Also I can successfully ping and run traceroute to >> 77.72.174.167. >> > > I would suggest running a VOIP port check. > Change _registar to your sip provider in the attached script and see > what happens. > > Do read third paragraph of header for needed applications. > Thanks for that suggestion. I changed _registar to "sip.ekiga.net" and I have run the test with various results. The first time I tried it this morning all the LAN ports passed and all the WAN ports failed. Subsequently when I run the test I get one or more of the LAN ports failing, but different ones each time. My /etc/hosts.(allow | deny) files have no entries, everything in them is commented out. I do not have iptables installed. My router appears to be set up in accordance with wiki.ekiga.org/index.php/Enable_port_forwarding_manually and has not been changed since Ekiga was working for me. Like ael I am on debian-testing and regularly update. John From bittwister2 at gmail.com Sat Apr 4 14:23:24 2015 From: bittwister2 at gmail.com (mdbug) Date: Sat, 04 Apr 2015 09:23:24 -0500 Subject: [Ekiga-list] STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 In-Reply-To: <551F7383.9040507@dpets.co.uk> References: <551EA039.5030205@dpets.co.uk> <551EA5C9.2030109@univ-fcomte.fr> <551EAD6B.5020109@dpets.co.uk> <551EBB0D.4030703@gmail.com> <551F7383.9040507@dpets.co.uk> Message-ID: <551FF3DC.7050000@gmail.com> On 04/04/2015 12:15 AM, John Talbut wrote: > On 03/04/15 17:08, mdbug wrote: >> >> >> On 04/03/2015 10:10 AM, John Talbut wrote: >> >>> I had checked and have rechecked my router and ports 3478 - 3479 are >>> allowed. Also I can successfully ping and run traceroute to >>> 77.72.174.167. >>> >> >> I would suggest running a VOIP port check. >> Change _registar to your sip provider in the attached script and see >> what happens. >> >> Do read third paragraph of header for needed applications. >> > Thanks for that suggestion. I changed _registar to "sip.ekiga.net" and > I have run the test with various results. The first time I tried it > this morning all the LAN ports passed and all the WAN ports failed. Which would suggest router was blocking. > Subsequently when I run the test I get one or more of the LAN ports > failing, but different ones each time. That is odd. There is a "-w 3" argument which indicates netcat (nc) should wait 3 seconds before timing out causing the error message. you could change -w 3 to -w 5 to see if the port test start working. If it runs more reliably, I have no idea why it takes more than three seconds to get a connection established. I have no clue as to how long ekiga waits before timing out. There can be no DNS issues because script gets the ip addresses prior to starting test. See for yourself, paste these in a terminal. _lan_ip=$(hostname --ip-address) _wan_ip=$(wget -qO - http://myip.dnsomatic.com/) echo "lan ip $_lan_ip" echo "wan ip $_wan_ip" Test does assume ipv4 addressing. > My /etc/hosts.(allow | deny) files have no entries, everything in them > is commented out. I do not have iptables installed. My router appears > to be set up in accordance with > wiki.ekiga.org/index.php/Enable_port_forwarding_manually and has not > been changed since Ekiga was working for me. The only other variable is your ISP could have updated your router's firmware or router has been cracked and port forwarding is different. The port tests are dead simple. nc uses source port _sport=38564, opens LAN_ip_addy:destination_port and sends message. At end of run, uses pkill to close all ports, then runs test again for WAN ip address if there were no LAN failures. From jt at dpets.co.uk Sat Apr 4 19:26:42 2015 From: jt at dpets.co.uk (John Talbut) Date: Sat, 04 Apr 2015 20:26:42 +0100 Subject: [Ekiga-list] STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 In-Reply-To: <551FF3DC.7050000@gmail.com> References: <551EA039.5030205@dpets.co.uk> <551EA5C9.2030109@univ-fcomte.fr> <551EAD6B.5020109@dpets.co.uk> <551EBB0D.4030703@gmail.com> <551F7383.9040507@dpets.co.uk> <551FF3DC.7050000@gmail.com> Message-ID: <55203AF2.8000104@dpets.co.uk> On 04/04/15 15:23, mdbug wrote: > > > On 04/04/2015 12:15 AM, John Talbut wrote: >> On 03/04/15 17:08, mdbug wrote: >>> >>> >>> On 04/03/2015 10:10 AM, John Talbut wrote: >>> >>>> I had checked and have rechecked my router and ports 3478 - 3479 are >>>> allowed. Also I can successfully ping and run traceroute to >>>> 77.72.174.167. >>>> >>> >>> I would suggest running a VOIP port check. >>> Change _registar to your sip provider in the attached script and see >>> what happens. >>> >>> Do read third paragraph of header for needed applications. >>> >> Thanks for that suggestion. I changed _registar to "sip.ekiga.net" and >> I have run the test with various results. The first time I tried it >> this morning all the LAN ports passed and all the WAN ports failed. > > Which would suggest router was blocking. > >> Subsequently when I run the test I get one or more of the LAN ports >> failing, but different ones each time. > > That is odd. There is a "-w 3" argument which indicates netcat (nc) > should wait 3 seconds before timing out causing the error message. > > you could change -w 3 to -w 5 to see if the port test start working. > If it runs more reliably, I have no idea why it takes more than three > seconds to get a connection established. > > I have no clue as to how long ekiga waits before timing out. > > There can be no DNS issues because script gets the ip addresses prior to > starting test. See for yourself, paste these in a terminal. > > _lan_ip=$(hostname --ip-address) > _wan_ip=$(wget -qO - http://myip.dnsomatic.com/) > > echo "lan ip $_lan_ip" > echo "wan ip $_wan_ip" > > Test does assume ipv4 addressing. > > >> My /etc/hosts.(allow | deny) files have no entries, everything in them >> is commented out. I do not have iptables installed. My router appears >> to be set up in accordance with >> wiki.ekiga.org/index.php/Enable_port_forwarding_manually and has not >> been changed since Ekiga was working for me. > > The only other variable is your ISP could have updated your router's > firmware or router has been cracked and port forwarding is different. > > The port tests are dead simple. nc uses source port _sport=38564, opens > LAN_ip_addy:destination_port and sends message. > > At end of run, uses pkill to close all ports, then runs test again for > WAN ip address if there were no LAN failures. > I am not getting much further. I have tried -w 5, -w 7 and even -w 10 but I still get one or more ports failing, different each time. I notice that when the ports pass there is a time delay but the fails come up almost immediately. My router is under my control (my ISP does not have access to it) and there is no sign of it being hacked (it has a decent password). I have been having a go with stun and I have got: ~$ stun stun.ekiga.net 0 STUN client version 0.96 running test number 0 Primary: Blocked or could not reach STUN server Return value is 0x00001c ~$ stun stun.sipgate.net STUN client version 0.96 Primary: Indepndent Mapping, Port Dependent Filter, preserves ports, no hairpin Return value is 0x000017 In other words it seems to work with stun.sipgate.net but not with stun.ekiga.net. Is the problem with the ekiga stun server? From law_ence.dev at ntlworld.com Mon Apr 6 09:29:44 2015 From: law_ence.dev at ntlworld.com (ael) Date: Mon, 6 Apr 2015 10:29:44 +0100 Subject: [Ekiga-list] STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 In-Reply-To: <55203AF2.8000104@dpets.co.uk> References: <551EA039.5030205@dpets.co.uk> <551EA5C9.2030109@univ-fcomte.fr> <551EAD6B.5020109@dpets.co.uk> <551EBB0D.4030703@gmail.com> <551F7383.9040507@dpets.co.uk> <551FF3DC.7050000@gmail.com> <55203AF2.8000104@dpets.co.uk> Message-ID: <20150406092944.GA3611@shelf.conquest> On Sat, Apr 04, 2015 at 08:26:42PM +0100, John Talbut wrote: > In other words it seems to work with stun.sipgate.net but not with > stun.ekiga.net. > > Is the problem with the ekiga stun server? I can confirm this. If I change from the ekiga stun server (I also have an account on sipgate, so also used the sipgate stun server) the problem goes away. No time to look further just now... ael From dsandras at seconix.com Mon Apr 6 19:14:01 2015 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 06 Apr 2015 21:14:01 +0200 Subject: [Ekiga-list] STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 In-Reply-To: <20150403160204.GB3067@shelf.conquest> References: <551EA039.5030205@dpets.co.uk> <20150403160204.GB3067@shelf.conquest> Message-ID: <1428347641.27964.1.camel@seconix.com> stun.ekiga.net is an alias to stun.voipbuster.com Perhaps they are down ? If that's the case, I can change the alias to stun.sipgate.de We used to have our own STUN server, but that's not the case anymore... Le vendredi 03 avril 2015 ? 17:02 +0100, ael a ?crit : > On Fri, Apr 03, 2015 at 03:14:17PM +0100, John Talbut wrote: > > I am getting the "Ekiga did not manage to configure your network settings > > automatically" message. I have followed the instructions and checked my > > I too have *suddenly* started getting those messages from ekiga, which > seems to work properly with 2 sip servers notwithstanding, but not with ekiga-net. > > So far I have not investigated. I am on debian-testing (for now) and > regularly update. I assume that one of the recent updates probably to a > library is responsible. Unless I missed it, ekiga itself has not been > updated recently. Likewise my router configuration has not changed. > > Checking with gconf-editor, the stun server is set to stun.ekiga.net. > > The failure message from ekiga-net is "Globally not acceptable". > > This may, or may not, be useful information, at least to Eugen. > > ael > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > https://mail.gnome.org/mailman/listinfo/ekiga-list -- Damien SANDRAS Ekiga Project http://www.ekiga.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From jt at dpets.co.uk Mon Apr 6 19:25:12 2015 From: jt at dpets.co.uk (John Talbut) Date: Mon, 06 Apr 2015 20:25:12 +0100 Subject: [Ekiga-list] STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 In-Reply-To: <1428347641.27964.1.camel@seconix.com> References: <551EA039.5030205@dpets.co.uk> <20150403160204.GB3067@shelf.conquest> <1428347641.27964.1.camel@seconix.com> Message-ID: <5522DD98.4080304@dpets.co.uk> It looks as if stun.sipgate.net might be a possibility from trying with the stun command: ~$ stun stun.voipbuster.com STUN client version 0.96 Primary: Blocked or could not reach STUN server Return value is 0x00001c ~$ stun stun.sipgate.de STUN client version 0.96 error was 110 stun.sipgate.de is not a valid host name john at johnwtwind:~$ stun stun.sipgate.net STUN client version 0.96 Primary: Indepndent Mapping, Port Dependent Filter, preserves ports, no hairpin Return value is 0x000017 On 06/04/15 20:14, Damien Sandras wrote: > stun.ekiga.net is an alias to stun.voipbuster.com > > Perhaps they are down ? > > If that's the case, I can change the alias to stun.sipgate.de > > We used to have our own STUN server, but that's not the case anymore... > > Le vendredi 03 avril 2015 ? 17:02 +0100, ael a ?crit : > >> On Fri, Apr 03, 2015 at 03:14:17PM +0100, John Talbut wrote: >>> I am getting the "Ekiga did not manage to configure your network settings >>> automatically" message. I have followed the instructions and checked my >> >> I too have *suddenly* started getting those messages from ekiga, which >> seems to work properly with 2 sip servers notwithstanding, but not with ekiga-net. >> >> So far I have not investigated. I am on debian-testing (for now) and >> regularly update. I assume that one of the recent updates probably to a >> library is responsible. Unless I missed it, ekiga itself has not been >> updated recently. Likewise my router configuration has not changed. >> >> Checking with gconf-editor, the stun server is set to stun.ekiga.net. >> >> The failure message from ekiga-net is "Globally not acceptable". >> >> This may, or may not, be useful information, at least to Eugen. >> >> ael >> >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> https://mail.gnome.org/mailman/listinfo/ekiga-list > > > > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > https://mail.gnome.org/mailman/listinfo/ekiga-list > From eugen.dedu at univ-fcomte.fr Mon Apr 6 20:13:54 2015 From: eugen.dedu at univ-fcomte.fr (Eugen Dedu) Date: Mon, 06 Apr 2015 22:13:54 +0200 Subject: [Ekiga-list] STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 In-Reply-To: <1428347641.27964.1.camel@seconix.com> References: <551EA039.5030205@dpets.co.uk> <20150403160204.GB3067@shelf.conquest> <1428347641.27964.1.camel@seconix.com> Message-ID: <5522E902.8060807@univ-fcomte.fr> Damien, stun.ekiga.net is down... On 06/04/15 21:14, Damien Sandras wrote: > stun.ekiga.net is an alias to stun.voipbuster.com > > Perhaps they are down ? > > If that's the case, I can change the alias to stun.sipgate.de > > We used to have our own STUN server, but that's not the case anymore... > > Le vendredi 03 avril 2015 ? 17:02 +0100, ael a ?crit : > >> On Fri, Apr 03, 2015 at 03:14:17PM +0100, John Talbut wrote: >>> I am getting the "Ekiga did not manage to configure your network settings >>> automatically" message. I have followed the instructions and checked my >> >> I too have *suddenly* started getting those messages from ekiga, which >> seems to work properly with 2 sip servers notwithstanding, but not with ekiga-net. >> >> So far I have not investigated. I am on debian-testing (for now) and >> regularly update. I assume that one of the recent updates probably to a >> library is responsible. Unless I missed it, ekiga itself has not been >> updated recently. Likewise my router configuration has not changed. >> >> Checking with gconf-editor, the stun server is set to stun.ekiga.net. >> >> The failure message from ekiga-net is "Globally not acceptable". >> >> This may, or may not, be useful information, at least to Eugen. >> >> ael >> >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> https://mail.gnome.org/mailman/listinfo/ekiga-list > > > > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > https://mail.gnome.org/mailman/listinfo/ekiga-list > From dsandras at seconix.com Tue Apr 7 07:04:46 2015 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 07 Apr 2015 09:04:46 +0200 Subject: [Ekiga-list] STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 In-Reply-To: <5522E902.8060807@univ-fcomte.fr> References: <551EA039.5030205@dpets.co.uk> <20150403160204.GB3067@shelf.conquest> <1428347641.27964.1.camel@seconix.com> <5522E902.8060807@univ-fcomte.fr> Message-ID: <1428390286.29204.0.camel@seconix.com> I updated the DNS Zone to stun.sipgate.net... Le lundi 06 avril 2015 ? 22:13 +0200, Eugen Dedu a ?crit : > Damien, stun.ekiga.net is down... > > On 06/04/15 21:14, Damien Sandras wrote: > > stun.ekiga.net is an alias to stun.voipbuster.com > > > > Perhaps they are down ? > > > > If that's the case, I can change the alias to stun.sipgate.de > > > > We used to have our own STUN server, but that's not the case anymore... > > > > Le vendredi 03 avril 2015 ? 17:02 +0100, ael a ?crit : > > > >> On Fri, Apr 03, 2015 at 03:14:17PM +0100, John Talbut wrote: > >>> I am getting the "Ekiga did not manage to configure your network settings > >>> automatically" message. I have followed the instructions and checked my > >> > >> I too have *suddenly* started getting those messages from ekiga, which > >> seems to work properly with 2 sip servers notwithstanding, but not with ekiga-net. > >> > >> So far I have not investigated. I am on debian-testing (for now) and > >> regularly update. I assume that one of the recent updates probably to a > >> library is responsible. Unless I missed it, ekiga itself has not been > >> updated recently. Likewise my router configuration has not changed. > >> > >> Checking with gconf-editor, the stun server is set to stun.ekiga.net. > >> > >> The failure message from ekiga-net is "Globally not acceptable". > >> > >> This may, or may not, be useful information, at least to Eugen. > >> > >> ael > >> > >> _______________________________________________ > >> ekiga-list mailing list > >> ekiga-list at gnome.org > >> https://mail.gnome.org/mailman/listinfo/ekiga-list > > > > > > > > > > > > _______________________________________________ > > ekiga-list mailing list > > ekiga-list at gnome.org > > https://mail.gnome.org/mailman/listinfo/ekiga-list > > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > https://mail.gnome.org/mailman/listinfo/ekiga-list -- Damien SANDRAS Ekiga Project http://www.ekiga.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From kezhawe28 at gmail.com Sun Apr 19 12:06:09 2015 From: kezhawe28 at gmail.com (Kezhawe) Date: Sun, 19 Apr 2015 16:36:09 +0430 Subject: [Ekiga-list] Getting webcam work in ekiga Message-ID: <20150419163609.38d816e3@ceylan.homenetwork> Hi My webcam is working properly using Camorama , Guvcview and WebBrowsers[firefox,chrome] here in gentoo , ekiga recognizes my webcam too and it even turns on its indicator light but there is nothing but a empty window http://pasteboard.co/2DL9UBwI.png I played with camera setting in ekiga but no luck also tried ekiga's debug option nothing related showed up. ---- while opening camera with ekiga dmesg gives me the this [Apr18 00:52] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -110 (exp. 2). --- P.S. --- I just find out webcam/ekiga problem are not related to the dmesg message just tested ekiga on debian and it worked great with the same message from dmesg I think its related to ekiga or some other packages but I don't know how to figure out what is the problem. # lsusb -v -d 5986:02d2 Bus 004 Device 003: ID 5986:02d2 Acer, Inc Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 bDeviceProtocol 1 Interface Association bMaxPacketSize0 64 idVendor 0x5986 Acer, Inc idProduct 0x02d2 bcdDevice 0.07 iManufacturer 1 Ricoh Company Ltd. iProduct 2 Integrated Camera iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 794 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 200mA Interface Association: bLength 8 bDescriptorType 11 bFirstInterface 0 bInterfaceCount 2 bFunctionClass 14 Video bFunctionSubClass 3 Video Interface Collection bFunctionProtocol 0 iFunction 4 Integrated Camera Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 14 Video bInterfaceSubClass 1 Video Control bInterfaceProtocol 0 iInterface 4 Integrated Camera VideoControl Interface Descriptor: bLength 13 bDescriptorType 36 bDescriptorSubtype 1 (HEADER) bcdUVC 1.00 wTotalLength 104 dwClockFrequency 30.000000MHz bInCollection 1 baInterfaceNr( 0) 1 VideoControl Interface Descriptor: bLength 18 bDescriptorType 36 bDescriptorSubtype 2 (INPUT_TERMINAL) bTerminalID 1 wTerminalType 0x0201 Camera Sensor bAssocTerminal 5 iTerminal 0 wObjectiveFocalLengthMin 0 wObjectiveFocalLengthMax 0 wOcularFocalLength 0 bControlSize 3 bmControls 0x00040a0e Auto-Exposure Mode Auto-Exposure Priority Exposure Time (Absolute) Zoom (Absolute) PanTilt (Absolute) Privacy VideoControl Interface Descriptor: bLength 11 bDescriptorType 36 bDescriptorSubtype 5 (PROCESSING_UNIT) Warning: Descriptor too short bUnitID 2 bSourceID 1 wMaxMultiplier 0 bControlSize 2 bmControls 0x0000157f Brightness Contrast Hue Saturation Sharpness Gamma White Balance Temperature Backlight Compensation Power Line Frequency White Balance Temperature, Auto iProcessing 0 bmVideoStandards 0x1b None NTSC - 525/60 SECAM - 625/50 NTSC - 625/50 VideoControl Interface Descriptor: bLength 27 bDescriptorType 36 bDescriptorSubtype 6 (EXTENSION_UNIT) bUnitID 3 guidExtensionCode {0a3e1874-8254-1a48-b402-48b8b8c49cc8} bNumControl 12 bNrPins 1 baSourceID( 0) 2 bControlSize 2 bmControls( 0) 0xff bmControls( 1) 0x0f iExtension 0 VideoControl Interface Descriptor: bLength 26 bDescriptorType 36 bDescriptorSubtype 6 (EXTENSION_UNIT) bUnitID 4 guidExtensionCode {ed2a1c0b-f739-d145-8100-fbcfac7ace06} bNumControl 6 bNrPins 1 baSourceID( 0) 3 bControlSize 1 bmControls( 0) 0x3f iExtension 0 VideoControl Interface Descriptor: bLength 9 bDescriptorType 36 bDescriptorSubtype 3 (OUTPUT_TERMINAL) bTerminalID 5 wTerminalType 0x0101 USB Streaming bAssocTerminal 0 bSourceID 4 iTerminal 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 8 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 14 Video bInterfaceSubClass 2 Video Streaming bInterfaceProtocol 0 iInterface 0 VideoStreaming Interface Descriptor: bLength 15 bDescriptorType 36 bDescriptorSubtype 1 (INPUT_HEADER) bNumFormats 2 wTotalLength 563 bEndPointAddress 130 bmInfo 1 bTerminalLink 5 bStillCaptureMethod 1 bTriggerSupport 0 bTriggerUsage 0 bControlSize 1 bmaControls( 0) 27 bmaControls( 1) 27 VideoStreaming Interface Descriptor: bLength 27 bDescriptorType 36 bDescriptorSubtype 4 (FORMAT_UNCOMPRESSED) bFormatIndex 1 bNumFrameDescriptors 8 guidFormat {59555932-0000-1000-8000-00aa00389b71} bBitsPerPixel 16 bDefaultFrameIndex 1 bAspectRatioX 0 bAspectRatioY 0 bmInterlaceFlags 0x02 Interlaced stream or variable: No Fields per frame: 1 fields Field 1 first: No Field pattern: Field 1 only bCopyProtect 0 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 1 bmCapabilities 0x01 Still image supported wWidth 640 wHeight 480 dwMinBitRate 73728000 dwMaxBitRate 147456000 dwMaxVideoFrameBufferSize 614400 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666666 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 2 bmCapabilities 0x01 Still image supported wWidth 640 wHeight 360 dwMinBitRate 55296000 dwMaxBitRate 110592000 dwMaxVideoFrameBufferSize 460800 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666666 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 3 bmCapabilities 0x01 Still image supported wWidth 352 wHeight 288 dwMinBitRate 24330240 dwMaxBitRate 48660480 dwMaxVideoFrameBufferSize 202752 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666666 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 4 bmCapabilities 0x01 Still image supported wWidth 320 wHeight 240 dwMinBitRate 18432000 dwMaxBitRate 36864000 dwMaxVideoFrameBufferSize 153600 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666666 VideoStreaming Interface Descriptor: bLength 30 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 5 bmCapabilities 0x01 Still image supported wWidth 800 wHeight 448 dwMinBitRate 86016000 dwMaxBitRate 86016000 dwMaxVideoFrameBufferSize 716800 dwDefaultFrameInterval 666666 bFrameIntervalType 1 dwFrameInterval( 0) 666666 VideoStreaming Interface Descriptor: bLength 30 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 6 bmCapabilities 0x01 Still image supported wWidth 960 wHeight 540 dwMinBitRate 82944000 dwMaxBitRate 82944000 dwMaxVideoFrameBufferSize 1036800 dwDefaultFrameInterval 1000000 bFrameIntervalType 1 dwFrameInterval( 0) 1000000 VideoStreaming Interface Descriptor: bLength 30 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 7 bmCapabilities 0x01 Still image supported wWidth 1280 wHeight 720 dwMinBitRate 147456000 dwMaxBitRate 147456000 dwMaxVideoFrameBufferSize 1843200 dwDefaultFrameInterval 1000000 bFrameIntervalType 1 dwFrameInterval( 0) 1000000 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 8 bmCapabilities 0x01 Still image supported wWidth 424 wHeight 240 dwMinBitRate 24422400 dwMaxBitRate 48844800 dwMaxVideoFrameBufferSize 203520 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666666 VideoStreaming Interface Descriptor: bLength 6 bDescriptorType 36 bDescriptorSubtype 13 (COLORFORMAT) bColorPrimaries 1 (BT.709,sRGB) bTransferCharacteristics 1 (BT.709) bMatrixCoefficients 4 (SMPTE 170M (BT.601)) VideoStreaming Interface Descriptor: bLength 11 bDescriptorType 36 bDescriptorSubtype 6 (FORMAT_MJPEG) bFormatIndex 2 bNumFrameDescriptors 7 bFlags 0 Fixed-size samples: No bDefaultFrameIndex 1 bAspectRatioX 0 bAspectRatioY 0 bmInterlaceFlags 0x02 Interlaced stream or variable: No Fields per frame: 2 fields Field 1 first: No Field pattern: Field 1 only bCopyProtect 0 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 7 (FRAME_MJPEG) bFrameIndex 1 bmCapabilities 0x01 Still image supported wWidth 640 wHeight 480 dwMinBitRate 110592000 dwMaxBitRate 221184000 dwMaxVideoFrameBufferSize 921600 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666666 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 7 (FRAME_MJPEG) bFrameIndex 2 bmCapabilities 0x01 Still image supported wWidth 640 wHeight 360 dwMinBitRate 82944000 dwMaxBitRate 165888000 dwMaxVideoFrameBufferSize 691200 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666666 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 7 (FRAME_MJPEG) bFrameIndex 3 bmCapabilities 0x01 Still image supported wWidth 352 wHeight 288 dwMinBitRate 36495360 dwMaxBitRate 72990720 dwMaxVideoFrameBufferSize 304128 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666666 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 7 (FRAME_MJPEG) bFrameIndex 4 bmCapabilities 0x01 Still image supported wWidth 320 wHeight 240 dwMinBitRate 27648000 dwMaxBitRate 55296000 dwMaxVideoFrameBufferSize 230400 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666666 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 7 (FRAME_MJPEG) bFrameIndex 5 bmCapabilities 0x01 Still image supported wWidth 800 wHeight 448 dwMinBitRate 129024000 dwMaxBitRate 258048000 dwMaxVideoFrameBufferSize 1075200 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666666 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 7 (FRAME_MJPEG) bFrameIndex 6 bmCapabilities 0x01 Still image supported wWidth 960 wHeight 540 dwMinBitRate 186624000 dwMaxBitRate 373248000 dwMaxVideoFrameBufferSize 1555200 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666666 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 7 (FRAME_MJPEG) bFrameIndex 7 bmCapabilities 0x01 Still image supported wWidth 1280 wHeight 720 dwMinBitRate 331776000 dwMaxBitRate 663552000 dwMaxVideoFrameBufferSize 2764800 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666666 VideoStreaming Interface Descriptor: bLength 6 bDescriptorType 36 bDescriptorSubtype 13 (COLORFORMAT) bColorPrimaries 1 (BT.709,sRGB) bTransferCharacteristics 1 (BT.709) bMatrixCoefficients 4 (SMPTE 170M (BT.601)) Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 1 bNumEndpoints 1 bInterfaceClass 14 Video bInterfaceSubClass 2 Video Streaming bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x0b5c 2x 860 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 2 bNumEndpoints 1 bInterfaceClass 14 Video bInterfaceSubClass 2 Video Streaming bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x135c 3x 860 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 3 bNumEndpoints 1 bInterfaceClass 14 Video bInterfaceSubClass 2 Video Streaming bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x13c0 3x 960 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 4 bNumEndpoints 1 bInterfaceClass 14 Video bInterfaceSubClass 2 Video Streaming bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x13fc 3x 1020 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 5 bNumEndpoints 1 bInterfaceClass 14 Video bInterfaceSubClass 2 Video Streaming bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x1400 3x 1024 bytes bInterval 1 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 bDeviceProtocol 1 Interface Association bMaxPacketSize0 64 bNumConfigurations 1 can't get debug descriptor: Resource temporarily unavailable Device Status: 0x0000 (Bus Powered) From eugen.dedu at univ-fcomte.fr Sun Apr 19 15:23:38 2015 From: eugen.dedu at univ-fcomte.fr (Eugen Dedu) Date: Sun, 19 Apr 2015 17:23:38 +0200 Subject: [Ekiga-list] Getting webcam work in ekiga In-Reply-To: <20150419163609.38d816e3@ceylan.homenetwork> References: <20150419163609.38d816e3@ceylan.homenetwork> Message-ID: <5533C87A.2000804@univ-fcomte.fr> On 19/04/15 14:06, Kezhawe wrote: > My webcam is working properly using Camorama , Guvcview and > WebBrowsers[firefox,chrome] here in gentoo , ekiga recognizes my webcam > too and it > even turns on its indicator light but there is nothing but a empty > windowhttp://pasteboard.co/2DL9UBwI.png I played with camera setting > in ekiga but no luck also tried ekiga's debug option nothing related > showed up. Hi, We need the -d 4 output, could you give it to us/me? See http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_debug_output -- Eugen From kezhawe28 at gmail.com Sun Apr 19 15:43:02 2015 From: kezhawe28 at gmail.com (Kezhawe) Date: Sun, 19 Apr 2015 20:13:02 +0430 Subject: [Ekiga-list] Getting webcam work in ekiga In-Reply-To: <5533C87A.2000804@univ-fcomte.fr> References: <20150419163609.38d816e3@ceylan.homenetwork> <5533C87A.2000804@univ-fcomte.fr> Message-ID: <20150419201302.02e47f43@ceylan.homenetwork> On Sun, 19 Apr 2015 17:23:38 +0200 Eugen Dedu wrote: > On 19/04/15 14:06, Kezhawe wrote: > > My webcam is working properly using Camorama , Guvcview and > > WebBrowsers[firefox,chrome] here in gentoo , ekiga recognizes my > > webcam too and it > > even turns on its indicator light but there is nothing but a empty > > windowhttp://pasteboard.co/2DL9UBwI.png I played with camera > > setting in ekiga but no luck also tried ekiga's debug option > > nothing related showed up. > > Hi, > > We need the -d 4 output, could you give it to us/me? See > http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_debug_output > Hi Eugen Sure , Here you are https://bpaste.net/raw/97d0ecce6e80