Works fine for me. Now we need a user-friendly implementation of that
workaround.
--
Some SIP providers return 403 Forbidden (No RFC 1918 IP allowed)
https://bugs.launchpad.net/bugs/362891
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Hey,
you have to add %limit to account name, not registrar:
https://bugzilla.gnome.org/show_bug.cgi?id=592012
After doing so restart Ekiga (!) and you should be done. At least it worked for
me with 1und1 ;)
--
Some SIP providers return 403 Forbidden (No RFC 1918 IP allowed)
Yannick,
what do you mean with %limit?
I have tried:
before: sip.1und1.de
after: sip.1und1.de%limit
does not change anything.
% aptitude show ekiga | grep Version
Version: 3.2.6~ppa~jaunty1
--
Some SIP providers return 403 Forbidden (No RFC 1918 IP allowed)
Hi,
Ekiga 3.2.6 was released yesterday. It fix numerous issues. Could you
please give it a try to check if it solves your issue?
https://launchpad.net/~sevmek/+archive/ekiga-released
(instructions and packages)
In your case add the string %limit to the registrar field in the
account window and
** Bug watch added: GNOME Bug Tracker #592012
http://bugzilla.gnome.org/show_bug.cgi?id=592012
** Also affects: ekiga via
http://bugzilla.gnome.org/show_bug.cgi?id=592012
Importance: Unknown
Status: Unknown
--
Some SIP providers return 403 Forbidden (No RFC 1918 IP allowed)
** Changed in: ekiga
Status: Unknown = New
--
Some SIP providers return 403 Forbidden (No RFC 1918 IP allowed)
https://bugs.launchpad.net/bugs/362891
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to ekiga in ubuntu.
--
** Changed in: ekiga (Ubuntu)
Status: New = In Progress
--
Some SIP providers return 403 Forbidden (No RFC 1918 IP allowed)
https://bugs.launchpad.net/bugs/362891
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to ekiga in ubuntu.
Hi,
This has been fixed in OPAL:
2009-07-13 06:33 rjongbloed
* [r23102] :
Added special case of m_contactAddress *= %LIMITED for SIP
registration which will only fill the Contact field of the
REGISTER command with addresses that are on the same interface as
Funatiker,
there is a fix in the new upstream versions. Did not try so far, but
changelogs say, they fixed this issue.
The usage of the internal IPs _can_ be what you want, if you want to
talk to people in you internal network. If your sip provider allows,
this is a nice feature. But the current
Is there any chance to get the upstream fix into ubuntu?
--
Some SIP providers return 403 Forbidden (No RFC 1918 IP allowed)
https://bugs.launchpad.net/bugs/362891
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to ekiga in ubuntu.
--
Hi,
Ekiga 3.2.5 was released yesterday. I do not recommend any version
between 3.2.0 and this last one because of a nasty bug in video in them.
3.2.5 seems to compile quite easily on Jaunty as one user reported on
the ekiga mailling list using this procedure:
(If you're not familiar with
I don't know if this is new to you: I think I found the reason for this
ugly bug: Some servers require that the client reports a valid IP but
Ekiga 3 reports sometimes the internal IP if you're behind a NAT.
--
Some SIP providers return 403 Forbidden (No RFC 1918 IP allowed)
Funatiker,
In this particular case, ekiga provide several IPs for contact with
priority order:
Contact: sip:49941...@79.209.54.40:61224;q=1,
sip:49941...@79.209.54.40;q=0.667,
sip:49941...@192.168.2.101;q=0.334
The first one to be tried (q=1) is a public one. There is indeed also a
What would be if ekiga didn't use the internal IPs at all?!
--
Some SIP providers return 403 Forbidden (No RFC 1918 IP allowed)
https://bugs.launchpad.net/bugs/362891
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to ekiga in ubuntu.
--
Ekiga released 3.2.1 with fixes regarding sip registration. Just did not
manage to get it build to try if it resolves the problem.
--
Some SIP providers return 403 Forbidden (No RFC 1918 IP allowed)
https://bugs.launchpad.net/bugs/362891
You received this bug notification because you are a
15 matches
Mail list logo
