Description of problem: Ekiga cannot log into any SIP accounts. Total of 3 tried - all working with ekiga-3.2.x Version-Release number of selected component (if applicable): ekiga-3.9.90-1.fc17.i686 How reproducible: always Steps to Reproduce: 1. connect to SIP account with 3.2 to verify working 2. upgrade to 3.9 3. try to connect again Actual results: Security check failed Expected results: Normal SIP account registration Additional info: Failed intermittently in F13, see bug#624145 I did not leave karma for the regression because there were many other things broken in ekiga since F14 (where it worked well), so that ekiga-3.2 was unusable in F17 anyway, and moving forward is good.
I forgot to mention, I *did* try reentering login info in case there was a config file change causing the problem. Didn't help.
Well, interesting. I tried it on another F17 machine, same SIP accounts, and it works. It must be something about the network environment of the first machine that 3.9 can no longer deal with. Both environments are natted.
(In reply to comment #2) > Well, interesting. I tried it on another F17 machine, same SIP accounts, > and it works. It must be something about the network environment of the > first machine that 3.9 can no longer deal with. Both environments are > natted. Ok, it doesn't really work. It *seems* to register when you start up, but when you actually try to make a call, it gets an "unauthorized" error. Remember, these are the same SIP accounts that worked in ekiga-3.2.x.
Stuart: please provide exact versions of working/non working ptlib/opal/ekiga. We never shipped 3.2 with Fedora 17 (last release to ship a 3.2.x release was Fedora 14) so did you custom compile it yourself?
Also, please send a -d 4 output for both when it works and when it does not, preferably on the same machine with two different versions of ekiga.
Sorry, the previous version on f17 was ekiga-3.3.2-7.fc17.i686. It was also working on f16, where I probably got the 3.2 version. Will try killing gconfd before removing config.
Ok, removing the previous config after rebooting works. So this was some sort of config conversion problem. We can probably close this, or I can try to reproduce the account conversion problem. I think I saved the old config. I found a new problem: touch tones don't work anymore! They work with twinkle on the same SIP account. That would be a new bug, however.
In case we keep working on this: ekiga-3.9.90-1.fc17.i686 ptlib-2.10.7-1.fc17.i686 opal-3.10.7-1.fc17.i686
Touch tones just need to use the rfc2833 option in setup - I lost it when deleting the config to start from scratch. So this and bug#859497 are just config compatibility problems, and deleting and reconfiguring is a reasonable workaround.
This could be the same as bug #859497. In fact, if you are not registered (bug #859497), when you call you can receive Security Check failed (this bug). Are you sure that when you receive Security Check Failed you are registered? If not, this bug should be closed.
I agree. This bug is probably really 859497. I hadn't tried all the combinations yet when reporting it, and was most almost certainly *not* registered due to the config reading bug. *** This bug has been marked as a duplicate of bug 859497 ***