GNOME Bugzilla – Bug 563670
Registration fails (with tun interface enabled)
Last modified: 2009-07-11 09:19:29 UTC
Please describe the problem: Registration to my provider sip.1und1.de fails when an openvpn tunnel is active. Steps to reproduce: 1. Enable openvpn (set up a route with local interface having a local IP, eg. 10.0.0.1) 2. Start ekiga and try to register with sip.1und1.de Actual results: Registration fails with the following reason: 403 Forbidden ekiga -d 4 shows the server's response (Translated to english) : RFC1918 IP adresses are not allowed. Expected results: Registration to the SIP server Does this happen every time? Yes Other information: ekiga seems to transmit the local IP address together with the external adress which confuses the server. If I disable the openvpn, it works fine.
Please attach the -d 4 output.
Created attachment 124251 [details] -d 4 output while registering to SIP server For simplicity I just attached the part of the output while registering to the server. If you need the complete output, please ask.
Two possibilities: that this is one of the small set of registrars that point bank refuse to accept multiple contact fields in the REGISTER command. Or of the other subset of registrars that reject the REGISTER when there is an un-routable address in the Contact field (the 10.0.0 one). What it SHOULD do is take the un-routable address out in the 200 OK and leave the routable one in. Much more sensible, but some registrars don't do it. There is really nothing the stack can do about the first one. The second one I was pretty sure had been fixed, but requires STUN to be enabled so that the 10.x.x.x address gets translated. Perhaps you could try with pure TRUNK ?
I think this bug should be merged into bug #587504, since that's the very same issue, but in the 3.2.x rather than 3.0.x series.
Thanks, duplicating it then! *** This bug has been marked as a duplicate of 587504 ***