Re: [Ekiga-list] Security Check Failed
Hi, Yes, we do not have Attended Transfer yet (only Blind Transfer). Le vendredi 09 décembre 2016 à 11:17 +, Chris @ Willows Consulting Ltd. a écrit : > Hi Damien, > > > > > > Oh I see: I should have used sip.blueface.ie instead of > sip.blueface.com ! Sorry~. > > > > I have just changed to Linphone and it works like a charm~ (with > sip.blueface.com). It is actually better for handling calls' > transfers: > > * Ekiga: transfer to call roughly to another extension: the caller is > pushed away to the extension ; > > * Linphone: you first call the other extension and you can talk, then > transfer the call on hold there! > > > > Thanks for your time. I will now use sip.blueface.ie at all time. > > > > > > Regards, > > Chris. > > > ___ > ekiga-list mailing list > ekiga-list@gnome.org > https://mail.gnome.org/mailman/listinfo/ekiga-list -- Damien SANDRAS Ekiga Project http://www.ekiga.org ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Security Check Failed
Hi Damien, Oh I see: I should have used sip.blueface.ie instead of sip.blueface.com ! Sorry~. I have just changed to Linphone and it works like a charm~ (with sip.blueface.com). It is actually better for handling calls' transfers: * Ekiga: transfer to call roughly to another extension: the caller is pushed away to the extension ; * Linphone: you first call the other extension and you can talk, then transfer the call on hold there! Thanks for your time. I will now use sip.blueface.ie at all time. Regards, Chris. ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Security Check Failed
Hi, Your provider is buggy. Actually, Ekiga is able to handle several accounts at the same time.To do so, it relies on the "realm". The "realm" is supposed to be unique: both worldwide (not two providers can have the same realm), and from the point of view of the provider (you should have one and only one realm corresponding to the provider SIP "domain"). You can see in the REGISTER response:SIP/2.0 401 UnauthorizedCSeq: 1 REGISTERWWW-Authenticate: Digest realm="sip.blueface.com", nonce="WEqHgFhKhlQ42SeHns8yNIV4kvU7BP6j" And in the INVITE response:SIP/2.0 401 UnauthorizedCSeq: 1 INVITEWWW- Authenticate: Digest algorithm=MD5, realm="sip.blueface.ie", nonce="16ed6ca7" The realm is changing, just like if you had 2 different providers. Tell them to read the SIP RFCs. Le vendredi 09 décembre 2016 à 10:27 +, Chris @ Willows Consulting Ltd. a écrit : > I have waited to see the "Registered" status on the window. See log > attached. I have added the SIP proxy of the provider too. I can > still > see the "SIP/2.0 401 Unauthorized" on line 1025 despite the REGISTER > @ > line 527 :'(. > > > Regards, > Chris.___ > ekiga-list mailing list > ekiga-list@gnome.org > https://mail.gnome.org/mailman/listinfo/ekiga-list -- Damien SANDRAS Ekiga Project http://www.ekiga.org ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Security Check Failed
On 08/12/16 18:30, Chris @ Willows Consulting Ltd. wrote: Where are the logs located in Windows ?... I can also take a screenshot of the message but I doubt it will be of any help. Here it is: http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_debug_output_2 -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Security Check Failed
Where are the logs located in Windows ?... I can also take a screenshot of the message but I doubt it will be of any help. Regards, Chris. ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Security Check Failed
On 08/12/16 18:04, Chris @ Willows Consulting Ltd. wrote: Hi again Eugen, I tried without the "Enable network detection" and restarted EKIGA : same problem :(. I am connected using LAN. It was working correctly with another Softphone, so I do not think it is the network. Incoming calls are fine, only outgoing calls are affected. I am sorry, I do not know what happens. You could try sending me the -d 4 log, perhaps I see semething, see the wiki for sensibel information inside. -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Security Check Failed
Hi again Eugen, I tried without the "Enable network detection" and restarted EKIGA : same problem :(. I am connected using LAN. It was working correctly with another Softphone, so I do not think it is the network. Incoming calls are fine, only outgoing calls are affected. Regards, Chris. ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Security Check Failed
On 08/12/16 17:53, Chris @ Willows Consulting Ltd. wrote: Hi Eugen, Thanks for the fast follow-up. Unfortunately: * the checkbox "Enable network detection" is checked * I am properly registered in the SIP account: I have the green icon status for it. Try also with the checkbox disabled, and restart Ekiga. I am using version 4.0.2 on Windows 10. It should be fine. -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Security Check Failed
Hi again, In regards to the SIP call string I have tried everything: sip:00COUNTRY_CODE_NUMBER sip:COUNTRY_CODE_NUMBER sip:NUMBER sip:00country_code_num...@sip.hostname.com sip:country_code_num...@sip.hostname.com sip:num...@sip.hostname.com Regards, Chris. ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Security Check Failed
Hi Eugen, Thanks for the fast follow-up. Unfortunately: * the checkbox "Enable network detection" is checked * I am properly registered in the SIP account: I have the green icon status for it. I am using version 4.0.2 on Windows 10. Regards, Chris. ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Security Check Failed
On 08/12/16 17:05, Chris @ Willows Consulting Ltd. wrote: Hi Guys, I am using Windows, but I am getting "Security Check Failed" when I am trying to call out from PC to phone with sip:$number. Can somebody help?? It means you have not registered, or you have disabled Network Detection in Preferences. We have had several cases like this on the mailing list. Cheers, -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Security Check Failed
Hi Guys, I am using Windows, but I am getting "Security Check Failed" when I am trying to call out from PC to phone with sip:$number. Can somebody help?? Regards, Chris.___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Security Check Failed error message when calling: solution?
On 22/10/14 04:11, user wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have installed ekiga on my gnu/linux and got a free account. when I try to send a call back call, like sip:5...@ekiga.net I get a "security check failed" message and cannot complete the call. You need to be registered to an ekiga.net account to call 5...@ekiga.net account. Is that your case? -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Security Check Failed error message when calling: solution?
I encountered the same problem with Knoppix, but ekiga works fine with the latest ubuntu distribution. Max Gesendet: Mittwoch, 22. Oktober 2014 um 04:11 Uhr Von: user An: ekiga-list@gnome.org Betreff: [Ekiga-list] Security Check Failed error message when calling: solution? -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have installed ekiga on my gnu/linux and got a free account. when I try to send a call back call, like sip:5...@ekiga.net I get a "security check failed" message and cannot complete the call. Does anyone here know of a solution? Thanks C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJURxIzAAoJEKgziVG5mu+2jWEP/RxtpZt9+I01Hko5Ov5nqGgF NW9nXU4uf7unYHFgdGZZGVWp4Pv6MJ0yEu/9G0gKtDuLgyVDW2Q/ZdSIffGoYwFv D0seYjAGNWRWdj0eUMSYEIqkD8Us6rUn2VvDTsx7BAUm9ZU5COFQUgjD0VteodyS 8Yn2MyiCP9aqPr5B/tG+hTLw3K0JKd0uelqfRnF02oQafuJNIC7FyEDWeBvbLq6U EfEBQhcIDSx7Sy7Zsp6O56UpCdBSq4myuC0WVNi/DCZzz6LKd2iOsyHLkmvVAt98 NoLLh5X6G28aFXb/k+PZuKW/bR3MPK4nni6emmZ4TEJR9LLVQFHbnaTDS/zBRblG QPMzd/2QZvYjgQnsSTq1oHgrm6VNeJvlJpXI0V0xIBAu3nQkBrr8e8SkxlEzwzoF GeTiYcBn25zNaEahpqY9eR3mA5GzxnPHzj6sJAIoABXP0q1gePhKK8A5jbeVrnwD eNoUbWxNr9TdCRav9f50DcKAdxBehL7U1V9mI67qhV9y+h4/Dnne/jUsjEWQcu1K epd7yZhoqH4CRBLWn+8itidFSrJ070/zlOP0nMm5CgS1fb9cZ1D/s/axrwiRkQI/ sbr4eTNYOyKmLKCtz56TbGMjJHpUKLWHNzm3dkMGlny374I0ik7k6eDi0tjdrIjy zrag66DlzavwYf9f/SLs =n8Lm -END PGP SIGNATURE- ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Security Check Failed error message when calling: solution?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have installed ekiga on my gnu/linux and got a free account. when I try to send a call back call, like sip:5...@ekiga.net I get a "security check failed" message and cannot complete the call. Does anyone here know of a solution? Thanks C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJURxIzAAoJEKgziVG5mu+2jWEP/RxtpZt9+I01Hko5Ov5nqGgF NW9nXU4uf7unYHFgdGZZGVWp4Pv6MJ0yEu/9G0gKtDuLgyVDW2Q/ZdSIffGoYwFv D0seYjAGNWRWdj0eUMSYEIqkD8Us6rUn2VvDTsx7BAUm9ZU5COFQUgjD0VteodyS 8Yn2MyiCP9aqPr5B/tG+hTLw3K0JKd0uelqfRnF02oQafuJNIC7FyEDWeBvbLq6U EfEBQhcIDSx7Sy7Zsp6O56UpCdBSq4myuC0WVNi/DCZzz6LKd2iOsyHLkmvVAt98 NoLLh5X6G28aFXb/k+PZuKW/bR3MPK4nni6emmZ4TEJR9LLVQFHbnaTDS/zBRblG QPMzd/2QZvYjgQnsSTq1oHgrm6VNeJvlJpXI0V0xIBAu3nQkBrr8e8SkxlEzwzoF GeTiYcBn25zNaEahpqY9eR3mA5GzxnPHzj6sJAIoABXP0q1gePhKK8A5jbeVrnwD eNoUbWxNr9TdCRav9f50DcKAdxBehL7U1V9mI67qhV9y+h4/Dnne/jUsjEWQcu1K epd7yZhoqH4CRBLWn+8itidFSrJ070/zlOP0nMm5CgS1fb9cZ1D/s/axrwiRkQI/ sbr4eTNYOyKmLKCtz56TbGMjJHpUKLWHNzm3dkMGlny374I0ik7k6eDi0tjdrIjy zrag66DlzavwYf9f/SLs =n8Lm -END PGP SIGNATURE- ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] security check failed
On 18/05/12 18:11, Ólafur Jens Sigurðsson wrote: On Fri, May 18, 2012 at 05:48:38PM +0200, Eugen Dedu wrote: On 17/05/12 03:59, Ólafur Jens Sigurðsson wrote: Hi When trying to phone echo (5...@ekiga.net) then I don't get connected, just the Security check failed I have pasted the output of ekiga -d 4 2> ekiga.txt here: http://paste.debian.net/169187/ You should check off Disable network detection, in the preferences dialog box, and restart ekiga. Have you ticked it on by purpose? Hi Eugen Yes I ticked it off on purpose, I was getting messages saying that Ekiga couldn't configure the network automatically, I searched the net a bit and found that I had to disable this network detection. Well, disabling net detection hides that message but also makes registration with some registrars (ekiga.net included) fail. I think I have forwarded the ports on my router correctly (could it be that they are not correctly forwarded and therefore Ekiga is not authenticating correctly?). Yes, it could be. Is there any way I can check for correct port forwarding? The only thing is to look in the -d 4 output (or send it to us), which allows to see what kind of network you are connected to and what packets (if any) arrive to your computer. -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] security check failed
On Fri, May 18, 2012 at 05:48:38PM +0200, Eugen Dedu wrote: > On 17/05/12 03:59, Ólafur Jens Sigurðsson wrote: > >Hi > > > >When trying to phone echo (5...@ekiga.net) then I don't get connected, > >just the Security check failed > > > >I have pasted the output of ekiga -d 4 2> ekiga.txt here: > >http://paste.debian.net/169187/ > > You should check off Disable network detection, in the preferences > dialog box, and restart ekiga. Have you ticked it on by purpose? Hi Eugen Yes I ticked it off on purpose, I was getting messages saying that Ekiga couldn't configure the network automatically, I searched the net a bit and found that I had to disable this network detection. I think I have forwarded the ports on my router correctly (could it be that they are not correctly forwarded and therefore Ekiga is not authenticating correctly?). Is there any way I can check for correct port forwarding? Cheers, Oli ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] security check failed
On 17/05/12 03:59, Ólafur Jens Sigurðsson wrote: Hi When trying to phone echo (5...@ekiga.net) then I don't get connected, just the Security check failed I have pasted the output of ekiga -d 4 2> ekiga.txt here: http://paste.debian.net/169187/ You should check off Disable network detection, in the preferences dialog box, and restart ekiga. Have you ticked it on by purpose? -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] security check failed
Hi When trying to phone echo (5...@ekiga.net) then I don't get connected, just the Security check failed I have pasted the output of ekiga -d 4 2> ekiga.txt here: http://paste.debian.net/169187/ Any idea on what is wrong here? TIA Oli ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] security check failed
On Wed, Feb 2, 2011 at 5:14 PM, Jan Teichmann wrote: > I have a problem using Ekiga. I set-up an ekiga.net account and calling > the echo service works fine. > > When I try to call a SIP uri I get the message "security check failed" > > From the log I get: > > SIP/2.0 403 No relaying > CSeq: 1 INVITE > Via: SIP/2.0/UDP > 10.62.***.***:5060;branch=z9hG4bKe284eb70-4b2d-e011-9824-***;rport=5060 > Server: Sip EXpress router (0.9.7 (i386/linux)) > From: "Jan Teichmann" > ;tag=0e40d770-4b2d-e011-9824-*** > Call-ID: 4c48d770-4b2d-e011-9824-001cbf3d1cf3@fedora14 > To: ;tag=0354a2e1b960c9cc2279eca4e5f84e20.7c75 > Warning: 392 217.74.***.***:5060 "Noisy feedback tells: pid=28716 > req_src_ip=80.71.***.*** req_src_port=5060 in_uri=sip:***@bluesip.de > out_uri=sip:***@bluesip.de via_cnt==1" > Content-Length: 0 > > > what does that mean and how can I fix that? It depends on who are you calling and what is your setup. Do you have a bluesip.de account configured? Are you using an outbound proxy (doesn't seem so - no Route headers)? Is the number you are trying to call a PSTN number or a SIP address? Did the server asked to authenticate before giving that 403 (given the CSeq value of 1 I guess no)? 403 Forbidden is usually returned when the call fails to meet security restrictions on the other end (hence "security check failed" in the GUI), eg, you are trying to call a PSTN number but your account doesn't allow PC to phone calls. Also, many test numbers (echo test etc) are usually restricted to the customers of the SIP provider in question, regardless of whether it's free VoIP only, or offers PC to phone calls. "No relaying" instead of the usual "Forbidden" in the response kind-of implies that the server giving you the 403 thinks that you are trying to use it as a relay, that is, the callee is outside of it's administrative domain. This is forbidden by some SIP providers. One thing of notice in the above log snippet is that there is an IP address in the From: address. Some SIP providers use the From: address in addition to authentication for access checks. Which is a bit silly as From is not required to contain a SIP address at all and is trivial to fake. In your case, it could be that the proxy expects from to contain something like sip:j...@bluesip.de as the From address, that is, for you to have a bluesip.de account. So, in short, there are many options of what's the problem. If you're just trying to call someone who has a bluesip.de account, I suggest you to ask that person to complain to bluesip.de that he/she is not reachable for users using other SIP providers. Heck, it should work with no provider at all. Cheers, --- Ian ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] security check failed
On 02/02/11 16:14, Jan Teichmann wrote: Ekiga 3.2.7 Fedora 14 i686 Dear Ekiga list, I have a problem using Ekiga. I set-up an ekiga.net account and calling the echo service works fine. When I try to call a SIP uri I get the message "security check failed" From the log I get: SIP/2.0 403 No relaying CSeq: 1 INVITE Via: SIP/2.0/UDP 10.62.***.***:5060;branch=z9hG4bKe284eb70-4b2d-e011-9824-***;rport=5060 Server: Sip EXpress router (0.9.7 (i386/linux)) From: "Jan Teichmann" ;tag=0e40d770-4b2d-e011-9824-*** Call-ID: 4c48d770-4b2d-e011-9824-001cbf3d1cf3@fedora14 To:;tag=0354a2e1b960c9cc2279eca4e5f84e20.7c75 Warning: 392 217.74.***.***:5060 "Noisy feedback tells: pid=28716 req_src_ip=80.71.***.*** req_src_port=5060 in_uri=sip:***@bluesip.de out_uri=sip:***@bluesip.de via_cnt==1" Content-Length: 0 what does that mean and how can I fix that? Well, I am not SIP expert, but it seems to me that 403 Forbidden is sent by server when something is wrong, see page 186 of http://www.ietf.org/rfc/rfc3261.txt. Why the server answers like this I do not know. Maybe you need to disable or enable Disable/Enable Network Detection in Preferences? Maybe you need to look at the INVITE request too, to see if there is not something wrong with it. -- Eugen Dedu http://eugen.dedu.free.fr ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] security check failed
Ekiga 3.2.7 Fedora 14 i686 Dear Ekiga list, I have a problem using Ekiga. I set-up an ekiga.net account and calling the echo service works fine. When I try to call a SIP uri I get the message "security check failed" From the log I get: SIP/2.0 403 No relaying CSeq: 1 INVITE Via: SIP/2.0/UDP 10.62.***.***:5060;branch=z9hG4bKe284eb70-4b2d-e011-9824-***;rport=5060 Server: Sip EXpress router (0.9.7 (i386/linux)) From: "Jan Teichmann" ;tag=0e40d770-4b2d-e011-9824-*** Call-ID: 4c48d770-4b2d-e011-9824-001cbf3d1cf3@fedora14 To: ;tag=0354a2e1b960c9cc2279eca4e5f84e20.7c75 Warning: 392 217.74.***.***:5060 "Noisy feedback tells: pid=28716 req_src_ip=80.71.***.*** req_src_port=5060 in_uri=sip:***@bluesip.de out_uri=sip:***@bluesip.de via_cnt==1" Content-Length: 0 what does that mean and how can I fix that? Cheers, Jan smime.p7s Description: S/MIME cryptographic signature ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Security check failed
peasth...@shaw.ca wrote: Folk, An attempt to reach a number in Pacifica via sip.diamondcard.us fails with the message "Security check failed" or "Security Check Failed". Can anyone tell me what this means? One of the reasons is (in my opinion) a mismatch login/password. Could you attach the -d 4 output? -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Security check failed
Folk, An attempt to reach a number in Pacifica via sip.diamondcard.us fails with the message "Security check failed" or "Security Check Failed". Can anyone tell me what this means? Thanks, ... Peter E. -- http://members.shaw.ca/peasthope/ http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Security Check Failed
Hi There - can anyone help with this please. #Am unable to connect to Ekiga.net as I keep getting the following messages - "Registration Failed" also in calls history "Security Check Failed" #My hardware is working fine - I am registered with Diamond which is working Not up to speed with Ekiga yet, so would appreciate any advice on how to solve the above. Thanks for your time and attention Regards AM ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] security check failed
Le mercredi 18 avril 2007 à 23:16 +0200, Thomas Schiex a écrit : > I tried to reuse Ekiga SIP after a period of quietness in this area > (Ekiga worked fine one year ago). I used my SIP account (provided by my > ISP, free.fr). This is the only account I have configured. > > The call is not initiated and I instead get a "Security check failed" > message. This was using EKiga 2.0.3. > > 1) I cross checked (retyped) the Registrar, user, password and > authentication id. > > Still fails > > 2) I tested the SIP account using Twinkle and XLite > > Both worked fine > > 3) I rechecked the SIP account configuration in Ekiga for safety: > > Failed again > > 4) I upgraded Ekiga to 2.0.9 (using saillard ubuntu repository) > > Still fails with the same message (appears more shortly) > > 5) I stopped my (iptable) firewall for a moment (DMZ machine), retried: > failure (STUN NAT with restricted port). Tried redoing NAT detection in > Ekiga, shifted to Cone NAT: > > Still fails with the same message > > 4) I restarted my firewall and redid NAT detection (went back to > restricted port). I tried an ekiga -d4. Ekiga seems to register the SIP > account fine but the call itself fails... again I put part of it below. > > Any idea ? I'd rather use Ekiga than Twinkle. The bad news is that Freephonie recently changed the way they are working. They reject calls if the PDUs come from different ports (which is what Ekiga is doing). We plan to find a workaround, but it will take time. Unfortunately, this is very silly from them. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] security check failed
I tried to reuse Ekiga SIP after a period of quietness in this area (Ekiga worked fine one year ago). I used my SIP account (provided by my ISP, free.fr). This is the only account I have configured. The call is not initiated and I instead get a "Security check failed" message. This was using EKiga 2.0.3. 1) I cross checked (retyped) the Registrar, user, password and authentication id. Still fails 2) I tested the SIP account using Twinkle and XLite Both worked fine 3) I rechecked the SIP account configuration in Ekiga for safety: Failed again 4) I upgraded Ekiga to 2.0.9 (using saillard ubuntu repository) Still fails with the same message (appears more shortly) 5) I stopped my (iptable) firewall for a moment (DMZ machine), retried: failure (STUN NAT with restricted port). Tried redoing NAT detection in Ekiga, shifted to Cone NAT: Still fails with the same message 4) I restarted my firewall and redid NAT detection (went back to restricted port). I tried an ekiga -d4. Ekiga seems to register the SIP account fine but the call itself fails... again I put part of it below. Any idea ? I'd rather use Ekiga than Twinkle. Thomas 2007/04/18 23:02:22.387 0:36.636SIP Transport:89fa3d0 SIP Transaction 3 SUBSCRIBE completed. [...] 2007/04/18 23:03:18.871 1:33.120GMURLHandler:08a97260 PCSS Outgoing call routed to sip:[EMAIL PROTECTED] for Call[1]-EP[Default] 2007/04/18 23:03:18.872 1:33.121GMURLHandler:08a97260 Call OnSetUp Call[1]-EP[Default] 2007/04/18 23:03:18.872 1:33.121GMURLHandler:08a97260 SIP SetUpConnection: 2007/04/18 23:03:18.998 1:33.247GMURLHandler:08a97260 OpalUDP Binding to interface: 192.168.0.1:32819 2007/04/18 23:03:18.998 1:33.247GMURLHandler:08a97260 SIP Created transport udp$0.0.0.0 2007/04/18 23:03:18.999 1:33.248GMURLHandler:08a97260 OpalUDP Started connect to 212.27.52.5:5060 2007/04/18 23:03:19.079 1:33.328GMURLHandler:08a97260 OpalUDP STUN created socket: 82.254.75.27:5065 2007/04/18 23:03:19.081 1:33.330GMURLHandler:08a97260 SIP Transaction 1 INVITE created. 2007/04/18 23:03:19.081 1:33.330GMURLHandler:08a97260 Call CanDoMediaBypass Call[1]-EP[EMAIL PROTECTED] session 1 2007/04/18 23:03:19.082 1:33.331GMURLHandler:08a97260 OpalMan IsMediaBypassPossible: session 1 2007/04/18 23:03:19.082 1:33.331GMURLHandler:08a97260 SIP IsMediaBypassPossible: session 1 2007/04/18 23:03:19.082 1:33.331GMURLHandler:08a97260 OpalCon IsMediaBypassPossible: default returns FALSE 2007/04/18 23:03:19.083 1:33.332SIP Transport:8ad95f8 SIP Read thread started. 2007/04/18 23:03:19.083 1:33.332SIP Transport:8ad95f8 SIP Waiting for PDU on udp$212.27.52.5:5060 2007/04/18 23:03:20.089 1:34.338Opal Listener:86c4248 SIP Unknown method name Cirpack received on udp$212.27.52.5:5060 2007/04/18 23:03:20.089 1:34.338Opal Listener:86c4248 Opal Transport clean up on termination 2007/04/18 23:03:20.089 1:34.339Opal Listener:86c4248 OpalUDP Close 2007/04/18 23:03:20.090 1:34.339Opal Listener:86c4248 Listen Waiting on UDP packet on udp$192.168.0.1:5060 2007/04/18 23:03:24.306 1:38.555GMURLHandler:08a97260 RTP STUN could not create RTP/RTCP socket pair; trying to create RTP socket anyway. 2007/04/18 23:03:24.465 1:38.714GMURLHandler:08a97260 RTP_UDP Session 1 created: 82.254.75.27:5066-5067 ssrc=805738867 2007/04/18 23:03:24.465 1:38.714GMURLHandler:08a97260 RTP Adding session RTP_UDP 2007/04/18 23:03:24.469 1:38.718GMURLHandler:08a97260 Call GetMediaFormats for Call[1]-EP[EMAIL PROTECTED] SpeexWide-20.6k GSM-06.10 MS-GSM SpeexNarrow-8k G.711-uLaw-64k G.711-ALaw-64k G.726-16k G.726-32k LPC-10 H.261(QCIF) H.261(CIF) YUV420P RGB32 RGB24 2007/04/18 23:03:24.470 1:38.719GMURLHandler:08a97260 SIP Using RTP payload [pt=101] for NTE 2007/04/18 23:03:24.470 1:38.719GMURLHandler:08a97260 Call CanDoMediaBypass Call[1]-EP[EMAIL PROTECTED] session 2 2007/04/18 23:03:24.470 1:38.719GMURLHandler:08a97260 OpalMan IsMediaBypassPossible: session 2 2007/04/18 23:03:24.470 1:38.719GMURLHandler:08a97260 SIP IsMediaBypassPossible: session 2 2007/04/18 23:03:24.470 1:38.719GMURLHandler:08a97260 OpalCon IsMediaBypassPossible: default returns FALSE 2007/04/18 23:03:24.787 1:39.036GMURLHandler:08a97260 RTP_UDP Session 2 created: 82.254.75.27:5006-5007 ssrc=1883152657 2007/04/18 23:03:24.787 1:39.037GMURLHandler:08a97260 RTP Adding session RTP_UDP 2007/04/18 23:03:24.792 1:39.041GMURLHandler:08a97260 Call GetMediaFormats for Call[1]-EP[EMAIL PROTECTED] SpeexWide-20.6k GSM-06.10 MS-GSM SpeexNarrow-8k G.711-uLaw-64k G.711-ALaw-64k G.726-16k G.726-32k LPC-10 H.261(QCIF) H.261(CIF) YUV420P RGB32 RGB24 2007/04/18 23:03:24.792 1:39.041GMURLHandler:08a97260 SIP No authentication
Re: [Ekiga-list] Security check failed
On Sun, Dec 17, 2006 at 11:39:50AM +0100, Damien Sandras wrote: > Hi, > > can you post the output of ekiga -d 4 when the problem occurs somewhere? No, because I just tried and Ekiga worked without a hitch. :-) Sound was a bit shaky, but the connection is there. Sorry to bother you and thanks for the reply! Cheers, Martin -- \u270C ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Security check failed
Hi, can you post the output of ekiga -d 4 when the problem occurs somewhere? Thanks, Le samedi 16 décembre 2006 à 21:09 +, Martin Swift a écrit : > Dear Ekiga community, > > Today, I have been trying to get Ekiga to work on my machine (Gentoo > Linux x86). It took a little while to get an understanding of how some > of the pieces fit together, but with the help of a few resources I > think I've got it down. > > Still, one problem eludes me which I'm hoping someone here might be > able to help me with. When trying to make a call, I get the error > Security check failed > in the status line at the bottom of the main GUI window. The "General > History" ( Tools > General History ) tool logs > 20:36:18 Calling sip:[EMAIL PROTECTED] > 20:36:19 Security check failed > [x-es inserted for privacy]. > > This actually happened before when I hadn't learnt how to properly > register my PC-to-Phone Account properly. Currently, I have the > following settings: > > In "PC-To-Phone Settings" ( Tools > PC-To-Phone Account ) I have > "Account number" and "Password" set to the "Account ID" and "PIN > code", respectively, as listed on my Diamondcard (diamondcard.us) > account "Home" page. After registering with Diamondcard and charging > the account, applying these settings seemed to connect me properly to > Diamondcard according to the "General History": > 19:28:36 Registered to eugw.ast.diamondcard.us > > I have two accounts registered in the "Accounts" ( Edit > Accounts ) > dialog, > * ekiga.net SIP Service: set according to my ekiga.net account > * Ekiga PC-To-Phone: set according to my diamondcard.us account as >described in the previous paragraph. > The latter I set to default. > > Everything seems to be set up correctly according to the Documentation > and FAQ, but connecting still results in the "Security check" failure. > Does anyone have any suggestions as to where my problem may lie? > > Just in case the error might be misleading me, I've tried connecting > to all of > sip:004989 > sip:4989 > 004989 > 4989 > sip:[EMAIL PROTECTED] > without any difference. > > Sincerely, > Martin Swift > -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Security check failed
Dear Ekiga community, Today, I have been trying to get Ekiga to work on my machine (Gentoo Linux x86). It took a little while to get an understanding of how some of the pieces fit together, but with the help of a few resources I think I've got it down. Still, one problem eludes me which I'm hoping someone here might be able to help me with. When trying to make a call, I get the error Security check failed in the status line at the bottom of the main GUI window. The "General History" ( Tools > General History ) tool logs 20:36:18 Calling sip:[EMAIL PROTECTED] 20:36:19 Security check failed [x-es inserted for privacy]. This actually happened before when I hadn't learnt how to properly register my PC-to-Phone Account properly. Currently, I have the following settings: In "PC-To-Phone Settings" ( Tools > PC-To-Phone Account ) I have "Account number" and "Password" set to the "Account ID" and "PIN code", respectively, as listed on my Diamondcard (diamondcard.us) account "Home" page. After registering with Diamondcard and charging the account, applying these settings seemed to connect me properly to Diamondcard according to the "General History": 19:28:36 Registered to eugw.ast.diamondcard.us I have two accounts registered in the "Accounts" ( Edit > Accounts ) dialog, * ekiga.net SIP Service: set according to my ekiga.net account * Ekiga PC-To-Phone: set according to my diamondcard.us account as described in the previous paragraph. The latter I set to default. Everything seems to be set up correctly according to the Documentation and FAQ, but connecting still results in the "Security check" failure. Does anyone have any suggestions as to where my problem may lie? Just in case the error might be misleading me, I've tried connecting to all of sip:004989 sip:4989 004989 4989 sip:[EMAIL PROTECTED] without any difference. Sincerely, Martin Swift -- \u270C ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
