|
alien registrar problem
I can not convince recent git revisions of ekiga to register with my
phone provider (1und1.de). I get an "could not register (Forbidden,
please check that username and password are correct)" answer, same error
on Linux and Windows. I tested from behind a FritzBox as a NAT router:
git-Linux no, git-WinXP no, git-Win7RC no, 3.02-WinXP yes. On a
different computer with an official IP: git-Linux no. For attached d4
log I started up Ekiga which was registering to ekiga.net. Then I
manually enabled my other account sip.1und1.de resulting in above error.
Then I shut down again. This behaviour seems not related to the number
of accounts but to, ekiga.net or not.
Additionally, Ekiga crashes on Windows only, when I delete an account.
There may be a connection between the two errors and the difference in
crashing may be caused by the difference in gmconf storing.
The registering problem may be related to what thomas schorp reported in
http://mail.gnome.org/archives/ekiga-devel-list/2009-June/msg00036.html .
At that time I was still happy with my Windows version connecting to
ekiga.net. Does ekiga.net not require a password? Can I register with
any string? That seems to be the case.
Regards
Michael
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Le mardi 23 juin 2009 à 14:39 +0200, Michael Rickmann a écrit :
> I can not convince recent git revisions of ekiga to register with my
> phone provider (1und1.de). I get an "could not register (Forbidden,
> please check that username and password are correct)" answer, same error
> on Linux and Windows. I tested from behind a FritzBox as a NAT router:
> git-Linux no, git-WinXP no, git-Win7RC no, 3.02-WinXP yes. On a
> different computer with an official IP: git-Linux no. For attached d4
> log I started up Ekiga which was registering to ekiga.net. Then I
> manually enabled my other account sip.1und1.de resulting in above error.
> Then I shut down again. This behaviour seems not related to the number
> of accounts but to, ekiga.net or not.
> Additionally, Ekiga crashes on Windows only, when I delete an account.
> There may be a connection between the two errors and the difference in
> crashing may be caused by the difference in gmconf storing.
> The registering problem may be related to what thomas schorp reported in
> http://mail.gnome.org/archives/ekiga-devel-list/2009-June/msg00036.html .
> At that time I was still happy with my Windows version connecting to
> ekiga.net. Does ekiga.net not require a password? Can I register with
> any string? That seems to be the case.
It tells:
SIP/2.0 403 Keine RFC1918-IPs erlaubt
That seems to be the reason. Not sure why. You should try a capture with
only that account active, for clarity.
--
_ Damien Sandras
(o-
//\ Ekiga Softphone : http://www.ekiga.org/v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip: dsandras@...
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Damien Sandras wrote:
> Le mardi 23 juin 2009 à 14:39 +0200, Michael Rickmann a écrit :
>> I can not convince recent git revisions of ekiga to register with my
>> phone provider (1und1.de). I get an "could not register (Forbidden,
>> please check that username and password are correct)" answer, same error
>> on Linux and Windows. I tested from behind a FritzBox as a NAT router:
>> git-Linux no, git-WinXP no, git-Win7RC no, 3.02-WinXP yes. On a
>> different computer with an official IP: git-Linux no. For attached d4
>> log I started up Ekiga which was registering to ekiga.net. Then I
>> manually enabled my other account sip.1und1.de resulting in above error.
>> Then I shut down again. This behaviour seems not related to the number
>> of accounts but to, ekiga.net or not.
>> Additionally, Ekiga crashes on Windows only, when I delete an account.
>> There may be a connection between the two errors and the difference in
>> crashing may be caused by the difference in gmconf storing.
>> The registering problem may be related to what thomas schorp reported in
>> http://mail.gnome.org/archives/ekiga-devel-list/2009-June/msg00036.html .
>> At that time I was still happy with my Windows version connecting to
>> ekiga.net. Does ekiga.net not require a password? Can I register with
>> any string? That seems to be the case.
>
> It tells:
> SIP/2.0 403 Keine RFC1918-IPs erlaubt
>
> That seems to be the reason. Not sure why. You should try a capture with
> only that account active, for clarity.
You could also compare or send us the -d 4 output on current git version
and on 2-weeks-old version, to see what has changed...
--
Eugen
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Am Dienstag, den 23.06.2009, 15:02 +0200 schrieb Damien Sandras:
> Le mardi 23 juin 2009 à 14:39 +0200, Michael Rickmann a écrit :
> > I can not convince recent git revisions of ekiga to register with my
> > phone provider (1und1.de). I get an "could not register (Forbidden,
> > please check that username and password are correct)" answer, same error
> > on Linux and Windows. I tested from behind a FritzBox as a NAT router:
> > git-Linux no, git-WinXP no, git-Win7RC no, 3.02-WinXP yes. On a
> > different computer with an official IP: git-Linux no. For attached d4
> > log I started up Ekiga which was registering to ekiga.net. Then I
> > manually enabled my other account sip.1und1.de resulting in above error.
> > Then I shut down again. This behaviour seems not related to the number
> > of accounts but to, ekiga.net or not.
> > Additionally, Ekiga crashes on Windows only, when I delete an account.
> > There may be a connection between the two errors and the difference in
> > crashing may be caused by the difference in gmconf storing.
> > The registering problem may be related to what thomas schorp reported in
> > http://mail.gnome.org/archives/ekiga-devel-list/2009-June/msg00036.html .
> > At that time I was still happy with my Windows version connecting to
> > ekiga.net. Does ekiga.net not require a password? Can I register with
> > any string? That seems to be the case.
>
> It tells:
> SIP/2.0 403 Keine RFC1918-IPs erlaubt
>
> That seems to be the reason. Not sure why. You should try a capture with
> only that account active, for clarity.
> --
snip
Yes that is the only German string in there saying no RFC1918-IPs
allowed. I attach the 1und1only log. Admittedly network setup of my
computer here is a bit complicated. It has two interfaces, one to the
free internet and one to our lab network where also the nameservers
are.
Kernel-IP-Routentabelle
Ziel Router Genmask Flags Metric Ref Use
Iface
192.168.21.0 * 255.255.255.0 U 0 0 0
eth1
link-local * 255.255.0.0 U 1000 0 0
eth1
localnet * 255.255.0.0 U 0 0 0
eth0
default gr-physio1-145. 0.0.0.0 UG 100 0 0
eth0
I checked ekiga.net requires a password. However, Ekiga seems to pick up
a password change only the next time it is started.
I will report the d4 log from home this evening.
Regards
Michael
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Am Dienstag, den 23.06.2009, 16:11 +0200 schrieb Eugen Dedu:
> Damien Sandras wrote:
> > Le mardi 23 juin 2009 à 14:39 +0200, Michael Rickmann a écrit :
> >> I can not convince recent git revisions of ekiga to register with my
> >> phone provider (1und1.de). I get an "could not register (Forbidden,
> >> please check that username and password are correct)" answer, same error
snip
> >
> > It tells:
> > SIP/2.0 403 Keine RFC1918-IPs erlaubt
> >
> > That seems to be the reason. Not sure why. You should try a capture with
> > only that account active, for clarity.
>
> You could also compare or send us the -d 4 output on current git version
> and on 2-weeks-old version, to see what has changed...
>
> --
> Eugen
Well, after an upgrade to Jaunty this computer has been ill, avahi was
talking nonsense of a .local net, gave up and Ekiga did not work at all.
Reason for that was that I had an eth0 and eth0:1 on the same interface
card. It started to work a few days ago when I put in an extra eth1. So
I have no real recent comparison. And at home I never tried 1und1.de
from Ekiga as we have it on our regular phones. I will try standard
Jaunty ekiga first and then jump somewhere into git / SVN, perhaps
before the overhaul of the account window.
Regards
Michael
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Le mardi 23 juin 2009 à 16:15 +0200, Michael Rickmann a écrit :
> Am Dienstag, den 23.06.2009, 15:02 +0200 schrieb Damien Sandras:
> > Le mardi 23 juin 2009 à 14:39 +0200, Michael Rickmann a écrit :
> > > I can not convince recent git revisions of ekiga to register with my
> > > phone provider (1und1.de). I get an "could not register (Forbidden,
> > > please check that username and password are correct)" answer, same error
> > > on Linux and Windows. I tested from behind a FritzBox as a NAT router:
> > > git-Linux no, git-WinXP no, git-Win7RC no, 3.02-WinXP yes. On a
> > > different computer with an official IP: git-Linux no. For attached d4
> > > log I started up Ekiga which was registering to ekiga.net. Then I
> > > manually enabled my other account sip.1und1.de resulting in above error.
> > > Then I shut down again. This behaviour seems not related to the number
> > > of accounts but to, ekiga.net or not.
> > > Additionally, Ekiga crashes on Windows only, when I delete an account.
> > > There may be a connection between the two errors and the difference in
> > > crashing may be caused by the difference in gmconf storing.
> > > The registering problem may be related to what thomas schorp reported in
> > > http://mail.gnome.org/archives/ekiga-devel-list/2009-June/msg00036.html .
> > > At that time I was still happy with my Windows version connecting to
> > > ekiga.net. Does ekiga.net not require a password? Can I register with
> > > any string? That seems to be the case.
> >
> > It tells:
> > SIP/2.0 403 Keine RFC1918-IPs erlaubt
> >
> > That seems to be the reason. Not sure why. You should try a capture with
> > only that account active, for clarity.
> > --
> snip
>
> Yes that is the only German string in there saying no RFC1918-IPs
> allowed. I attach the 1und1only log. Admittedly network setup of my
> computer here is a bit complicated. It has two interfaces, one to the
> free internet and one to our lab network where also the nameservers
> are.
>
> Kernel-IP-Routentabelle
> Ziel Router Genmask Flags Metric Ref Use
> Iface
> 192.168.21.0 * 255.255.255.0 U 0 0 0
> eth1
> link-local * 255.255.0.0 U 1000 0 0
> eth1
> localnet * 255.255.0.0 U 0 0 0
> eth0
> default gr-physio1-145. 0.0.0.0 UG 100 0 0
> eth0
>
> I checked ekiga.net requires a password. However, Ekiga seems to pick up
> a password change only the next time it is started.
> I will report the d4 log from home this evening.
What happens is that your contact field has 2 IP addresses :
- 1 public IP
- 1 private IP (with lower priority)
The remote SER is misconfigured and rejects the packets because one of
the IPs is private while the public one is reachable. You should contact
them.
Btw, is that a recent trunk ? Something else seems to be broken (without
affecting the failure you see or being related to it).
--
_ Damien Sandras
(o-
//\ Ekiga Softphone : http://www.ekiga.org/v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip: dsandras@...
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
|
|
Re: alien registrar problem
Michael Rickmann schrieb:
> Am Dienstag, den 23.06.2009, 16:11 +0200 schrieb Eugen Dedu:
>> Damien Sandras wrote:
>>> Le mardi 23 juin 2009 à 14:39 +0200, Michael Rickmann a écrit :
>>>> I can not convince recent git revisions of ekiga to register with my
>>>> phone provider (1und1.de). I get an "could not register (Forbidden,
>>>> please check that username and password are correct)" answer, same error
> snip
>>> It tells:
>>> SIP/2.0 403 Keine RFC1918-IPs erlaubt
>>>
>>> That seems to be the reason. Not sure why. You should try a capture with
>>> only that account active, for clarity.
>> You could also compare or send us the -d 4 output on current git version
>> and on 2-weeks-old version, to see what has changed...
>>
>> --
>> Eugen
>
> Well, after an upgrade to Jaunty this computer has been ill, avahi was
> talking nonsense of a .local net, gave up and Ekiga did not work at all.
> Reason for that was that I had an eth0 and eth0:1 on the same interface
> card. It started to work a few days ago when I put in an extra eth1. So
> I have no real recent comparison. And at home I never tried 1und1.de
> from Ekiga as we have it on our regular phones. I will try standard
> Jaunty ekiga first and then jump somewhere into git / SVN, perhaps
> before the overhaul of the account window.
> Regards
> Michael
>
Sorry, for the uproar. I found the answer myself. I should have googled
before: http://bugzilla.gnome.org/show_bug.cgi?id=579832A provider bug from Ekiga#s point of view? Also when I google for Keine
erlaubt "RFC1918 IPs " its mainly 1und1 who show up here in Germany.
Regards
Michael
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Damien Sandras schrieb:
> Le mardi 23 juin 2009 à 16:15 +0200, Michael Rickmann a écrit :
>> Am Dienstag, den 23.06.2009, 15:02 +0200 schrieb Damien Sandras:
>>> Le mardi 23 juin 2009 à 14:39 +0200, Michael Rickmann a écrit :
snip
>
> What happens is that your contact field has 2 IP addresses :
> - 1 public IP
> - 1 private IP (with lower priority)
>
> The remote SER is misconfigured and rejects the packets because one of
> the IPs is private while the public one is reachable. You should contact
> them.
>
> Btw, is that a recent trunk ? Something else seems to be broken (without
> affecting the failure you see or being related to it).
It is 2009-06-22 18:45:38 83b71c1b57b0cb15 Made the SIP
endpoint cache the default address of record, at the moment 21 hrs old.
Regards
Michael
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Le mardi 23 juin 2009 à 18:09 +0200, Michael Rickmann a écrit :
> Damien Sandras schrieb:
> > Le mardi 23 juin 2009 à 16:15 +0200, Michael Rickmann a écrit :
> >> Am Dienstag, den 23.06.2009, 15:02 +0200 schrieb Damien Sandras:
> >>> Le mardi 23 juin 2009 à 14:39 +0200, Michael Rickmann a écrit :
>
> snip
>
> >
> > What happens is that your contact field has 2 IP addresses :
> > - 1 public IP
> > - 1 private IP (with lower priority)
> >
> > The remote SER is misconfigured and rejects the packets because one of
> > the IPs is private while the public one is reachable. You should contact
> > them.
> >
> > Btw, is that a recent trunk ? Something else seems to be broken (without
> > affecting the failure you see or being related to it).
>
> It is 2009-06-22 18:45:38 83b71c1b57b0cb15 Made the SIP
> endpoint cache the default address of record, at the moment 21 hrs old.
And for opal ?
--
_ Damien Sandras
(o-
//\ Ekiga Softphone : http://www.ekiga.org/v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip: dsandras@...
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Am Dienstag, den 23.06.2009, 18:16 +0200 schrieb Damien Sandras:
> Le mardi 23 juin 2009 à 18:09 +0200, Michael Rickmann a écrit :
> > Damien Sandras schrieb:
> > > Le mardi 23 juin 2009 à 16:15 +0200, Michael Rickmann a écrit :
> > >> Am Dienstag, den 23.06.2009, 15:02 +0200 schrieb Damien Sandras:
> > >>> Le mardi 23 juin 2009 à 14:39 +0200, Michael Rickmann a écrit :
> >
> > snip
> >
> > >
> > > What happens is that your contact field has 2 IP addresses :
> > > - 1 public IP
> > > - 1 private IP (with lower priority)
> > >
> > > The remote SER is misconfigured and rejects the packets because one of
> > > the IPs is private while the public one is reachable. You should contact
> > > them.
> > >
> > > Btw, is that a recent trunk ? Something else seems to be broken (without
> > > affecting the failure you see or being related to it).
> >
> > It is 2009-06-22 18:45:38 83b71c1b57b0cb15 Made the SIP
> > endpoint cache the default address of record, at the moment 21 hrs old.
>
> And for opal ?
> --
I am back at the computer now on which I compiled. Its opal SVN 22948
(2009-06-22T03:02:20.998594Z) and ptlib SVN 22945
(2009-06-22T01:49:54.035585Z) with which I had linked Ekiga, so approx.
two days old.
Regards
Michael
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Damien Sandras wrote:
[...]
>>> It tells:
>>> SIP/2.0 403 Keine RFC1918-IPs erlaubt
[...]
> What happens is that your contact field has 2 IP addresses :
> - 1 public IP
> - 1 private IP (with lower priority)
>
> The remote SER is misconfigured and rejects the packets because one of
> the IPs is private while the public one is reachable. You should contact
> them.
I'm having the same problem, however with another provider
(bluesip.net). The relevant debug output is:
rem=udp$217.74.179.29:5060,local=udp$96.232.27.238:5060,if=192.168.1.36%wlan0
SIP/2.0 479 Please don't use private IP addresses
Concerning to another voip forum, the responsibilty of this issue is on
the client site, i.e. ekiga in this case. It seems that ekiga's behavior
isn't sip-standard conform here (I'm no expert, though). The only
unsatisfactory solution for me rigth now is to use twinkle with this
specific provider. Is there a chance that ekiga switches it's behavior?
Chris
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Le lundi 29 juin 2009 à 11:02 -0400, Christian Schäfer a écrit :
> Damien Sandras wrote:
>
> [...]
>
> >>> It tells:
> >>> SIP/2.0 403 Keine RFC1918-IPs erlaubt
>
> [...]
>
> > What happens is that your contact field has 2 IP addresses :
> > - 1 public IP
> > - 1 private IP (with lower priority)
> >
> > The remote SER is misconfigured and rejects the packets because one of
> > the IPs is private while the public one is reachable. You should contact
> > them.
>
> I'm having the same problem, however with another provider
> (bluesip.net). The relevant debug output is:
>
> rem=udp$217.74.179.29:5060,local=udp$96.232.27.238:5060,if=192.168.1.36%wlan0
> SIP/2.0 479 Please don't use private IP addresses
>
> Concerning to another voip forum, the responsibilty of this issue is on
> the client site, i.e. ekiga in this case. It seems that ekiga's behavior
> isn't sip-standard conform here (I'm no expert, though). The only
> unsatisfactory solution for me rigth now is to use twinkle with this
> specific provider. Is there a chance that ekiga switches it's behavior?
I would be happy to change the behavior if Ekiga was not sip conform,
but I have no idea what to change. I also have some doubts.
Wouldn't it be STUN? Have you tried disabling it?
--
_ Damien Sandras
(o-
//\ Ekiga Softphone : http://www.ekiga.org/v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip: dsandras@...
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Damien Sandras wrote:
> Le lundi 29 juin 2009 à 11:02 -0400, Christian Schäfer a écrit :
>> Damien Sandras wrote:
>>
>> [...]
>>
>> >>> It tells:
>> >>> SIP/2.0 403 Keine RFC1918-IPs erlaubt
>>
>> [...]
>>
>> > What happens is that your contact field has 2 IP addresses :
>> > - 1 public IP
>> > - 1 private IP (with lower priority)
>> >
>> > The remote SER is misconfigured and rejects the packets because one of
>> > the IPs is private while the public one is reachable. You should contact
>> > them.
>>
>> I'm having the same problem, however with another provider
>> (bluesip.net). The relevant debug output is:
>>
>> rem=udp$217.74.179.29:5060,local=udp$96.232.27.238:5060,if=192.168.1.36%wlan0
>> SIP/2.0 479 Please don't use private IP addresses
>>
>> Concerning to another voip forum, the responsibilty of this issue is on
>> the client site, i.e. ekiga in this case. It seems that ekiga's behavior
>> isn't sip-standard conform here (I'm no expert, though). The only
>> unsatisfactory solution for me rigth now is to use twinkle with this
>> specific provider. Is there a chance that ekiga switches it's behavior?
>
> I would be happy to change the behavior if Ekiga was not sip conform,
> but I have no idea what to change. I also have some doubts.
>
> Wouldn't it be STUN? Have you tried disabling it?
The problem is independent from whether using STUN or not, and it only
appears when I am behind a NAT. As a result, the local IP address
(192.168.1.36 in my case) somehow gets through to the provider. To my
understanding the IP needs to be replaced with the WAN address by ekiga.
Most providers seem to ignore this non-sip-standard behavior, however
bluesip (and some others) seem to be more strict.
(google for "Please don't use private IP addresses")
Chris
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Le lundi 29 juin 2009 à 11:33 -0400, Christian Schäfer a écrit :
> Damien Sandras wrote:
> > Le lundi 29 juin 2009 à 11:02 -0400, Christian Schäfer a écrit :
> >> Damien Sandras wrote:
> >>
> >> [...]
> >>
> >> >>> It tells:
> >> >>> SIP/2.0 403 Keine RFC1918-IPs erlaubt
> >>
> >> [...]
> >>
> >> > What happens is that your contact field has 2 IP addresses :
> >> > - 1 public IP
> >> > - 1 private IP (with lower priority)
> >> >
> >> > The remote SER is misconfigured and rejects the packets because one of
> >> > the IPs is private while the public one is reachable. You should contact
> >> > them.
> >>
> >> I'm having the same problem, however with another provider
> >> (bluesip.net). The relevant debug output is:
> >>
> >> rem=udp$217.74.179.29:5060,local=udp$96.232.27.238:5060,if=192.168.1.36%wlan0
> >> SIP/2.0 479 Please don't use private IP addresses
> >>
> >> Concerning to another voip forum, the responsibilty of this issue is on
> >> the client site, i.e. ekiga in this case. It seems that ekiga's behavior
> >> isn't sip-standard conform here (I'm no expert, though). The only
> >> unsatisfactory solution for me rigth now is to use twinkle with this
> >> specific provider. Is there a chance that ekiga switches it's behavior?
> >
> > I would be happy to change the behavior if Ekiga was not sip conform,
> > but I have no idea what to change. I also have some doubts.
> >
> > Wouldn't it be STUN? Have you tried disabling it?
>
> The problem is independent from whether using STUN or not, and it only
> appears when I am behind a NAT. As a result, the local IP address
> (192.168.1.36 in my case) somehow gets through to the provider. To my
> understanding the IP needs to be replaced with the WAN address by ekiga.
> Most providers seem to ignore this non-sip-standard behavior, however
> bluesip (and some others) seem to be more strict.
> (google for "Please don't use private IP addresses")
Ekiga.net also rejects private IP addresses and all Ekiga clients behave
fine.
The problem is that your router replaces the public IP address Ekiga
puts in by a private one due to a bug in the router itself, you can see
the Ekiga PDUs in the log, they are correct.
If you disable STUN, perhaps your router will put the public IP address
in the packets.
What happens is that some dummy routers replace public ip's by private
ones. That's your case.
--
_ Damien Sandras
(o-
//\ Ekiga Softphone : http://www.ekiga.org/v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip: dsandras@...
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Christian Schäfer wrote:
> Damien Sandras wrote:
>> Le lundi 29 juin 2009 à 11:02 -0400, Christian Schäfer a écrit :
>>> Damien Sandras wrote:
>>>
>>> [...]
>>>
>>> >>> It tells:
>>> >>> SIP/2.0 403 Keine RFC1918-IPs erlaubt
>>>
>>> [...]
>>>
>>> > What happens is that your contact field has 2 IP addresses :
>>> > - 1 public IP
>>> > - 1 private IP (with lower priority)
>>> >
>>> > The remote SER is misconfigured and rejects the packets because
>>> one of
>>> > the IPs is private while the public one is reachable. You should
>>> contact
>>> > them.
>>>
>>> I'm having the same problem, however with another provider
>>> (bluesip.net). The relevant debug output is:
>>>
>>> rem=udp$217.74.179.29:5060,local=udp$96.232.27.238:5060,if=192.168.1.36%wlan0
>>>
>>> SIP/2.0 479 Please don't use private IP addresses
>>>
>>> Concerning to another voip forum, the responsibilty of this issue is
>>> on the client site, i.e. ekiga in this case. It seems that ekiga's
>>> behavior isn't sip-standard conform here (I'm no expert, though). The
>>> only unsatisfactory solution for me rigth now is to use twinkle with
>>> this specific provider. Is there a chance that ekiga switches it's
>>> behavior?
>>
>> I would be happy to change the behavior if Ekiga was not sip conform,
>> but I have no idea what to change. I also have some doubts.
>>
>> Wouldn't it be STUN? Have you tried disabling it?
>
> The problem is independent from whether using STUN or not, and it only
> appears when I am behind a NAT. As a result, the local IP address
> (192.168.1.36 in my case) somehow gets through to the provider. To my
> understanding the IP needs to be replaced with the WAN address by ekiga.
> Most providers seem to ignore this non-sip-standard behavior, however
> bluesip (and some others) seem to be more strict.
> (google for "Please don't use private IP addresses")
Just out of curiousity, can anybody point me to the section of the SIP
spec that covers this behavior? I looked for it briefly but could not
find any mention of 479 as a valid response code.
>
> Chris
> _______________________________________________
> Ekiga-devel-list mailing list
> Ekiga-devel-list@...
> http://mail.gnome.org/mailman/listinfo/ekiga-devel-list_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Damien Sandras wrote:
>>> Wouldn't it be STUN? Have you tried disabling it?
>> The problem is independent from whether using STUN or not, and it only
>> appears when I am behind a NAT. As a result, the local IP address
>> (192.168.1.36 in my case) somehow gets through to the provider. To my
>> understanding the IP needs to be replaced with the WAN address by ekiga.
>> Most providers seem to ignore this non-sip-standard behavior, however
>> bluesip (and some others) seem to be more strict.
>> (google for "Please don't use private IP addresses")
>
> Ekiga.net also rejects private IP addresses and all Ekiga clients behave
> fine.
>
> The problem is that your router replaces the public IP address Ekiga
> puts in by a private one due to a bug in the router itself, you can see
> the Ekiga PDUs in the log, they are correct.
> If you disable STUN, perhaps your router will put the public IP address
> in the packets.
>
> What happens is that some dummy routers replace public ip's by private
> ones. That's your case.
Don't think that's true. As I said, using twinkle behind the NAT with
the same router works perfectly with that provider. So the router
couldn't be the problem here and it seems that it's indeed a software
issue.
Chris
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Le lundi 29 juin 2009 à 11:50 -0400, Christian Schäfer a écrit :
> Damien Sandras wrote:
> >>> Wouldn't it be STUN? Have you tried disabling it?
> >> The problem is independent from whether using STUN or not, and it only
> >> appears when I am behind a NAT. As a result, the local IP address
> >> (192.168.1.36 in my case) somehow gets through to the provider. To my
> >> understanding the IP needs to be replaced with the WAN address by ekiga.
> >> Most providers seem to ignore this non-sip-standard behavior, however
> >> bluesip (and some others) seem to be more strict.
> >> (google for "Please don't use private IP addresses")
> >
> > Ekiga.net also rejects private IP addresses and all Ekiga clients behave
> > fine.
> >
> > The problem is that your router replaces the public IP address Ekiga
> > puts in by a private one due to a bug in the router itself, you can see
> > the Ekiga PDUs in the log, they are correct.
> > If you disable STUN, perhaps your router will put the public IP address
> > in the packets.
> >
> > What happens is that some dummy routers replace public ip's by private
> > ones. That's your case.
>
> Don't think that's true. As I said, using twinkle behind the NAT with
> the same router works perfectly with that provider. So the router
> couldn't be the problem here and it seems that it's indeed a software
> issue.
Please show me a trace of Ekiga with stun disabled and a trace of
twinkle so that we can compare both.
Btw, I don't understand your reasoning which consists to say that Ekiga
puts deliberately private IP addresses in PDUs when the log says no.
--
_ Damien Sandras
(o-
//\ Ekiga Softphone : http://www.ekiga.org/v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip: dsandras@...
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
Damien Sandras wrote:
>>> The problem is that your router replaces the public IP address Ekiga
>>> puts in by a private one due to a bug in the router itself, you can see
>>> the Ekiga PDUs in the log, they are correct.
>>> If you disable STUN, perhaps your router will put the public IP address
>>> in the packets.
>>>
>>> What happens is that some dummy routers replace public ip's by private
>>> ones. That's your case.
>> Don't think that's true. As I said, using twinkle behind the NAT with
>> the same router works perfectly with that provider. So the router
>> couldn't be the problem here and it seems that it's indeed a software
>> issue.
>
> Please show me a trace of Ekiga with stun disabled and a trace of
> twinkle so that we can compare both.
>
> Btw, I don't understand your reasoning which consists to say that Ekiga
> puts deliberately private IP addresses in PDUs when the log says no.
Again, to clearify my reasoning, these are the relevant observations:
Firstly:
Relevant -d 4 output of ekiga says the following when trying to connect
to bluesip.net:
rem=udp$217.74.179.29:5060,local=udp$96.232.27.238:5060,if=192.168.1.36%wlan0
SIP/2.0 479 Please don't use private IP addresses
This suggests that there's a problem with the private IP address
(192.168.1.36). Whether this is sip conform or not I dodn't know.
Concerning to some people in some voip forums, it isn't.
Secondly:
This behavior is independent of using a STUN server or not and only
appears when I am behind a NAT router.
And thirdly:
The fact that twinkle is able to connect to bluesip successfully from
behind this specific router, suggests that this is no router-issue.
Detailed traces of both ekiga and twinkle will follow.
Chris
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
|
Re: alien registrar problem
>>>> The problem is that your router replaces the public IP address Ekiga
>>>> puts in by a private one due to a bug in the router itself, you can see
>>>> the Ekiga PDUs in the log, they are correct.
>>>> If you disable STUN, perhaps your router will put the public IP address
>>>> in the packets.
>>>>
>>>> What happens is that some dummy routers replace public ip's by private
>>>> ones. That's your case.
>>>
>>> Don't think that's true. As I said, using twinkle behind the NAT with the
>>> same router works perfectly with that provider. So the router couldn't be
>>> the problem here and it seems that it's indeed a software issue.
>>
>> Please show me a trace of Ekiga with stun disabled and a trace of
>> twinkle so that we can compare both.
>>
>> Btw, I don't understand your reasoning which consists to say that Ekiga
>> puts deliberately private IP addresses in PDUs when the log says no.
>
> Again, to clearify my reasoning, these are the relevant observations:
>
> Firstly:
> Relevant -d 4 output of ekiga says the following when trying to connect to
> bluesip.net:
>
> rem=udp$217.74.179.29:5060,local=udp$96.232.27.238:5060,if=192.168.1.36%wlan0
> SIP/2.0 479 Please don't use private IP addresses
>
> This suggests that there's a problem with the private IP address
> (192.168.1.36). Whether this is sip conform or not I dodn't know. Concerning
> to some people in some voip forums, it isn't.
>
> Secondly:
> This behavior is independent of using a STUN server or not and only appears
> when I am behind a NAT router.
>
> And thirdly:
> The fact that twinkle is able to connect to bluesip successfully from behind
> this specific router, suggests that this is no router-issue.
This issue sounds quite familiar to a couple of bugs I've had reported
on F-11 where they are unable to connect to a SIP server where with
previous versions of ekiga they were (in some cases they even went as
far as recompiling ekiga 2 themselves.
Peter
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
|
1und1-d4.log.gz (17K) 