Re: [Ekiga-list] Ekiga 3.2.7 Windows XP

[Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr>]

On 26/05/10 16:10, Jānis Rukšāns wrote:
> On Tue, May 25, 2010 at 9:54 PM, Eugen Dedu
> <Eugen Dedu pu-pm univ-fcomte fr>  wrote:
> > On 25/05/10 19:09, Nigel Brown wrote:
> > > Hi All,
> > >
> > >
> > >
> > > Re: 'Could not register (Method not allowed)'
> > >
> > >
> > >
> > > Herewith latest dump after double checking all necessary posts opened
> >
> > There is something wrong with your firewall:
> >
> > 2010/05/25 17:35:23.165   0:54.351            StunDetector:4780 STUN    No
> > response to STUN server 75.101.138.128:3478
> > 2010/05/25 17:35:23.165   0:54.351            StunDetector:4780 OPAL    STUN
> > server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1
>
> Apart from STUN problems I also noticed that for some reason the top
> route is set to the local IP, which is why he is getting Method Not
> Allowed - Ekiga sends the REGISTER to itself!!
>
> 2010/05/25 17:35:24.056	  0:55.247	        subscriber:7304	SIP	Sending
> PDU (561 bytes) to:
> rem=udp$192.168.10.27:5060,local=udp$192.168.10.27:5060,if=192.168.10.27%Intel(R)
> 82567LM-3 Gigabit Network Connection - Miniport d'ordonnancement de
> paquets
>
> REGISTER sip:ekiga.net SIP/2.0
>
>
> Route:<sip:192.168.10.27:5060;lr>
>
> 2010/05/25 17:35:24.056	  0:55.249	     Opal Listener:7044	SIP	PDU
> received: rem=udp$192.168.10.27:5060,local=udp$192.168.10.27:5060,if=192.168.10.27%Intel(R)
> 82567LM-3 Gigabit Network Connection - Miniport d'ordonnancement de
> paquets
>
> REGISTER sip:ekiga.net SIP/2.0
>
> Route:<sip:192.168.10.27:5060;lr>
>
> 2010/05/25 17:35:24.056	  0:55.250	     Opal Listener:7044	SIP	Sending
> PDU (463 bytes) to:
> rem=udp$192.168.10.27:5060,local=udp$192.168.10.27:5060,if=192.168.10.27%Intel(R)
> 82567LM-3 Gigabit Network Connection - Miniport d'ordonnancement de
> paquets
>
> SIP/2.0 405 Method Not Allowed
>
>
> CSeq: 1 REGISTER

This could be because Blocked returns 127.0.0.1 as address.

> Nigel, do you have set something as outbound proxy? Or is the
> erroneous route added by Ekiga?

Nigel, there is something wrong with your firewall or router.  Tell your 
technician to capture your packets (by starting wireshark for ex.) on 
your NAT machine and see where packets are lost.  This is the surest 
method to see what happens.

--
Eugen