ok, I run ekiga with parameter -d 4 to capture the message and this is what i got (last lines)
just to note that i registered successfully my diamondcard account using twinkle and was able to call the echo test ([email protected]) to interface 0 - "192.168.1.67%eth0" 2008/12/13 18:50:40.580 0:12.010 subscriber:0xb357ab90 SIP Transaction created. 2008/12/13 18:50:40.583 0:12.013 subscriber:0xb357ab90 DNS SRV Lookup sip.diamondcard.us service _sip._udp 2008/12/13 18:50:41.602 0:13.032 Housekeeper:0xb5878b90 SIP Set state Terminated_Timeout for transaction 1 REGISTER 2008/12/13 18:50:41.602 0:13.032 Housekeeper:0xb5878b90 SIP Changing REGISTER handler from Subscribing to Unavailable, target= sip:[email protected] <sip%[email protected]>, id=0e35fd72-9bc7-dd11-8a6f-001cc0223...@khalfan-desktop 2008/12/13 18:50:41.602 0:13.032 Housekeeper:0xb5878b90 SIP Retrying REGISTER in 30 seconds. 2008/12/13 18:50:45.870 0:17.300 subscriber:0xb357ab90 SIP Transaction remote address is udp$62.4.81.186:5060 2008/12/13 18:50:45.871 0:17.301 subscriber:0xb357ab90 SIP Sending PDU (549 bytes) to: rem=udp$62.4.81.186:5060,local=udp$ 84.255.181.235:5060,if=192.168.1.67%eth0 REGISTER sip:sip.diamondcard.us SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 84.255.181.235:5060 ;branch=z9hG4bK724e1376-9bc7-dd11-8a6f-001cc0223352;rport User-Agent: Ekiga/3.0.0 From: <sip:[email protected] <sip%[email protected]> >;tag=5a481376-9bc7-dd11-8a6f-001cc0223352 Call-ID: c479fd72-9bc7-dd11-8a6f-001cc0223...@khalfan-desktop To: <sip:[email protected] <sip%[email protected]>> Contact: <sip:[email protected]:5060;transport=udp> Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2008/12/13 18:50:45.871 0:17.301 subscriber:0xb357ab90 SIP Transaction timers set: retry=0.500, completion=6.000 2008/12/13 18:50:45.871 0:17.301 ThreadID:0xb357ab90 PWLib Destroyed thread 0x83751e0 subscriber:0xb357ab90(id = 0) 2008/12/13 18:50:46.371 0:17.801 Housekeeper:0xb5878b90 SIP Transaction 2 REGISTER timeout, making retry 1 2008/12/13 18:50:46.371 0:17.801 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:46.372 0:17.802 Housekeeper:0xb5878b90 SIP Sending PDU (549 bytes) to: rem=udp$62.4.81.186:5060,local=udp$ 84.255.181.235:5060,if=192.168.1.67%eth0 REGISTER sip:sip.diamondcard.us SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 84.255.181.235:5060 ;branch=z9hG4bK724e1376-9bc7-dd11-8a6f-001cc0223352;rport User-Agent: Ekiga/3.0.0 From: <sip:[email protected] <sip%[email protected]> >;tag=5a481376-9bc7-dd11-8a6f-001cc0223352 Call-ID: c479fd72-9bc7-dd11-8a6f-001cc0223...@khalfan-desktop To: <sip:[email protected] <sip%[email protected]>> Contact: <sip:[email protected]:5060;transport=udp> Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2008/12/13 18:50:46.372 0:17.802 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:46.871 0:18.301 Opal Garbage:0xb58fab90 SIP Transaction 1 REGISTER destroyed. 2008/12/13 18:50:47.372 0:18.802 Housekeeper:0xb5878b90 SIP Transaction 2 REGISTER timeout, making retry 2 2008/12/13 18:50:47.372 0:18.802 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:47.372 0:18.802 Housekeeper:0xb5878b90 SIP Sending PDU (549 bytes) to: rem=udp$62.4.81.186:5060,local=udp$ 84.255.181.235:5060,if=192.168.1.67%eth0 REGISTER sip:sip.diamondcard.us SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 84.255.181.235:5060 ;branch=z9hG4bK724e1376-9bc7-dd11-8a6f-001cc0223352;rport User-Agent: Ekiga/3.0.0 From: <sip:[email protected] <sip%[email protected]> >;tag=5a481376-9bc7-dd11-8a6f-001cc0223352 Call-ID: c479fd72-9bc7-dd11-8a6f-001cc0223...@khalfan-desktop To: <sip:[email protected] <sip%[email protected]>> Contact: <sip:[email protected]:5060;transport=udp> Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2008/12/13 18:50:47.372 0:18.802 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:49.372 0:20.802 Housekeeper:0xb5878b90 SIP Transaction 2 REGISTER timeout, making retry 3 2008/12/13 18:50:49.372 0:20.802 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:49.372 0:20.802 Housekeeper:0xb5878b90 SIP Sending PDU (549 bytes) to: rem=udp$62.4.81.186:5060,local=udp$ 84.255.181.235:5060,if=192.168.1.67%eth0 REGISTER sip:sip.diamondcard.us SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 84.255.181.235:5060 ;branch=z9hG4bK724e1376-9bc7-dd11-8a6f-001cc0223352;rport User-Agent: Ekiga/3.0.0 From: <sip:[email protected] <sip%[email protected]> >;tag=5a481376-9bc7-dd11-8a6f-001cc0223352 Call-ID: c479fd72-9bc7-dd11-8a6f-001cc0223...@khalfan-desktop To: <sip:[email protected] <sip%[email protected]>> Contact: <sip:[email protected]:5060;transport=udp> Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2008/12/13 18:50:49.372 0:20.802 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:51.872 0:23.302 Housekeeper:0xb5878b90 SIP Set state Terminated_Timeout for transaction 2 REGISTER 2008/12/13 18:50:51.872 0:23.302 Housekeeper:0xb5878b90 SIP Changing REGISTER handler from Subscribing to Unavailable, target= sip:[email protected] <sip%[email protected]>, id=c479fd72-9bc7-dd11-8a6f-001cc0223...@khalfan-desktop 2008/12/13 18:50:51.872 0:23.302 Housekeeper:0xb5878b90 SIP Retrying REGISTER in 30 seconds. 2008/12/13 18:50:51.872 0:23.302 Opal Garbage:0xb58fab90 SIP Transaction 2 REGISTER destroyed. On Fri, Dec 12, 2008 at 9:17 PM, Fedor vonBock <[email protected]> wrote: > is ekiga expecting something on any incoming port when registering > that i need to enable on my router? That's the main problem now > > main message is > > "could not register [email protected]" (i check the account > status and it says timeout. > > > > > > On 12/11/08, michel memeteau <[email protected]> wrote: > > On Thu, Dec 11, 2008 at 5:12 AM, James Garvin <[email protected]> wrote: > >> I have tested Ekiga behind a router and it failed.. After going to > >> directly to the network it worked fine. Unfortinuatly, I have two > >> options now. Buy a second PC for my firewall and sanity (Virus) and one > >> for > >> a great phone service for linux which will be open to all prediators. > I > >> have tried to open ports and tested shorewall to no avil > >> > > > > James , your problem IS an issue and should be resolved. > > > > At least you should be able to register , even if after you have som > > problems with the audio streams. > > > > Can't you check the router configuraion ? > > _______________________________________________ > > 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
