-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Eugen Dedu Sent: 26 May 2010 16:53 To: Ekiga mailing list Subject: Re: [Ekiga-list] Ekiga 3.2.7 Windows XP
On 26/05/10 16:10, Jānis Rukšāns wrote: > On Tue, May 25, 2010 at 9:54 PM, Eugen Dedu > <[email protected]> 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%Int el(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%Int el(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%Int el(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 Dear Eugen/Ekiga members, I have made some research into this situation, just to help myself as this is not an area with which I am familiar. Our IT Technicians will not assist further, they have opened the ports to my machine 192.168.10.27. SIP communication is not high on their list of priorities, they are willing to let me use Skype but here in Tunisia that’s a disaster. I can confirm all ports have been opened. I can confirm I am behind a SYMMETRIC NAT, (so STUN is not relevant?). From what I can see, my pc will send a request to the Ekiga.net or Iptel.org servers (I tried another account) but can not receive the response. I can confirm by looking at the dump, that my pc sends its own private IP address 192.168.10.27, not the public one, from our ISP, 193.95.76.165. I read on a VOLP user forum that the SIP server must send the response back using exactly the same IP address/port combination - could this be the problem? Local IP: 192.168.10.27 Public IP: 193.95.76.165 DHCP Server: 192.168.10.3 DNS Server: 192.168.10.3 Default Gateway: 192.168.10.254 Regards Nigel Brown _______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
_______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
