GNOME Bugzilla – Bug 582713
Unable to register to my SIP provider (NodePhone)
Last modified: 2011-03-17 03:51:54 UTC
Hello, I am unable to register to my SIP provider, NodePhone (http://www.internode.on.net/residential/nodephone/features/). This is a high-quality SIP provider with fully redundant hardware (http://broadsoft.com/Newsroom/Press2007/Internode_NodePhone2_Launch.htm). All of my SIP hardware and other SIP phones register with my NodePhone account without any problems (Twinkle, Linphone, Linksys ATA, Billion Electric ATA, Open Networks ATA, Polycom IP phone, Linksys IP phone, Zoiper, Asterisk, X-Lite, KPhone and SJPhone). I'm not really sure what Ekiga's problem is. It just says: "Could not register(Request terminated)". I have attached a log from: "ekiga --debug=5". What else can I provide or try? I'm willing to help out as much as I can, as long as you're willing to help guide me with suggestions. I'm using Ubuntu 9.04 (Jaunty), which provides: Ekiga 3.2.0, PTLib 2.6.1, and Linux 2.6.28. Cheers! Kind Regards, An Australian VoIP user that wants to use Ekiga with NodePhone! :-)
Created attachment 134685 [details] ekiga --debug=5
*** This bug has been marked as a duplicate of 578883 ***
Hi, I'm sorry: Could you please provide more information? I don't understand bug 578883, it's talking about enabling STUN support. Here[1], my provider tells me that STUN is not necessary and that I'm not meant to use it. "NodePhone generally avoids any need to configure 'STUN' or other VoIP tunneling protocols". So how is this related, exactly? Are you 100% sure it is _exactly_ the same problem? In addition, I looked at bug 578883's register_sip.log, and he received a SIP error of "SIP/2.0 606 Not Acceptable", whereas I am receiving a SIP error of "SIP/2.0 404 Not Found". There appears to be other differences too, but I'm not sure which ones are important enough to mention. Please provide more detailed and exact information. Kind Regards. [1] http://www.internode.on.net/support/faq/nodephone/troubleshooting_nodephone/#Do_I_have_to_open_up_any_ports_i
Hi, Sorry for not giving details. I noticed in your log that you connect to the provider through a private address (see line starting with Via:). If you have a private address, STUN is mandatory, to my knowledge. Can someone with more experience comment on this? There was a bug when STUN was not used in any case, but it was fixed. That's why I marked it as duplicate. 3.2.1 has just been released, and it contains the fix, if you can test.
It seems that some providers ignore that field indeed, so you might have right.
Callcentric is another provider that absolutely requires STUN deactivated for NAT to work. When I do, it works correctly. Unfortunately, it can't register with Ekiga.net in such a case, though.
Forgot to mention: Callcentric works only with STUN disabled, _but_ then only if there is one interface with an address; see bug #587504.
Bug mentioned in previous comment is closed. Daniel, we need to know if your bug still appears with 3.2.7 (or the fresh 3.3.0) version of ekiga? Please try it.
Daniel, any updated regarding comment#8 ?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!