After I finally got it working (somehow), here are some thoughts. It seems that:
1) I shouldn't use proxy sip:sip.smartvoip.com or sip.smartvoip.com <--- this results in unconditional inability to connect to any host 2) having the number ending with @smartvoip.com results in security check failure ... this is the reliable reason this stupid message appears! It's not a problem with Ekiga. It's just that given provider will not route to the numbers which are not within its own network. 3) having sip: in the phone number also results in the inability to connect (unreliable?) 4) having just the number +xx... results in inability to connect (unreliable?) The number should be in the format of +xx...@sip.smartvoip.com or 00xx...@sip.smartvoip.com . Both work for me. It seems, that when a connection can not be established the best strategy is to re-register the account and try again. It might be that my testing was unreliable, because the provided has some kind on limits on the number of unsuccessful attempts and few failed attempts make the subsequent correct attempts to fail. Very strange. I had a similar kind of issues with ekiga 2.x, but after the first round of problems all subsequent starts very perfectly fine. Let's see if it gonna work tomorrow. -- "security check failed" https://bugs.launchpad.net/bugs/120251 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
