Re: [Ekiga-list] Ekiga timeout trying to register with hostedsip.net since upgrade to version 3



Andrew Swerlick wrote:
Hi,

I've had some trouble with ekiga ever since I upgraded to v3 last week. My
company has a sip account with the provider hostedsip.net. In v2 I set up
this account in ekiga's accounts section and everything worked fine, both
inbound and out. However, since my upgrade, ekiga can no longer connect with
the hostedsip.net account. Instead every time I get a time out error. Below
is the relevant debug output. Any recommendations?




Route: <sip:hostedsip.net:5060;lr>

CSeq: 1 REGISTER

Via: SIP/2.0/UDP 24.99.59.0:5060
;branch=z9hG4bK42e92df2-d23d-de11-9808-001fe11b6237;rport

User-Agent: Ekiga/3.2.0

From: <sip:254 hostedsip net <sip%3A254 hostedsip net>
;tag=ecee28f2-d23d-de11-9808-001fe11b6237

Call-ID: f4aa0af2-d23d-de11-9808-001fe11b6237 andrew-laptop

To: <sip:254 hostedsip net <sip%3A254 hostedsip net>>

Contact: <sip:254 24 99 59 0 <sip%3A254 24 99 59 0>>;q=1, <
sip:254 192 168 1 100 <sip%3A254 192 168 1 100>>;q=0.800, <
sip:254 192 168 122 1 <sip%3A254 192 168 122 1>>;q=0.600, <
sip:254 172 16 251 1 <sip%3A254 172 16 251 1>>;q=0.400, <
sip:254 172 16 192 1 <sip%3A254 172 16 192 1>>;q=0.200

Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING

Expires: 10000

Content-Length: 0

Max-Forwards: 70




2009/05/12 22:25:08.824 0:07.583 Housekeeper:0xb549cb90 OpalUDP Setting
interface to 172.16.192.1%vmnet1
2009/05/12 22:25:08.829 0:07.588 Housekeeper:0xb549cb90 SIP Transaction 1
REGISTER timeout, making retry 1
2009/05/12 22:25:08.829 0:07.588 Housekeeper:0xb549cb90 OpalUDP Setting
interface to 192.168.122.1%virbr0
2009/05/12 22:25:08.829 0:07.588 Housekeeper:0xb549cb90 SIP Set new
interface 192.168.122.1%virbr0 for transport udp$65.168.93.26:5060<if=udp$
192.168.122.1:5060>
2009/05/12 22:25:08.830 0:07.589 Housekeeper:0xb549cb90 SIP Sending PDU (667
bytes) to: rem=udp$65.168.93.26:5060,local=udp$192.168.122.1:5060
,if=192.168.122.1%virbr0
REGISTER sip:hostedsip.net SIP/2.0

Route: <sip:hostedsip.net:5060;lr>

CSeq: 1 REGISTER

Via: SIP/2.0/UDP 24.99.59.0:5060
;branch=z9hG4bK229f2ef2-d23d-de11-9808-001fe11b6237;rport

User-Agent: Ekiga/3.2.0

From: <sip:254 hostedsip net <sip%3A254 hostedsip net>
;tag=ecee28f2-d23d-de11-9808-001fe11b6237

Call-ID: f4aa0af2-d23d-de11-9808-001fe11b6237 andrew-laptop

To: <sip:254 hostedsip net <sip%3A254 hostedsip net>>

Contact: <sip:254 24 99 59 0 <sip%3A254 24 99 59 0>>;q=1, <
sip:254 192 168 1 100 <sip%3A254 192 168 1 100>>;q=0.800, <
sip:254 192 168 122 1 <sip%3A254 192 168 122 1>>;q=0.600, <
sip:254 172 16 251 1 <sip%3A254 172 16 251 1>>;q=0.400, <
sip:254 172 16 192 1 <sip%3A254 172 16 192 1>>;q=0.200

Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING

Expires: 10000

Content-Length: 0

Max-Forwards: 70




2009/05/12 22:25:08.830 0:07.589 Housekeeper:0xb549cb90 OpalUDP Setting
interface to 172.16.192.1%vmnet1
2009/05/12 22:25:08.833 0:07.592 Housekeeper:0xb549cb90 SIP Transaction 1
REGISTER timeout, making retry 1
2009/05/12 22:25:08.834 0:07.593 Housekeeper:0xb549cb90 OpalUDP Setting
interface to 172.16.251.1%vmnet8
2009/05/12 22:25:08.834 0:07.593 Housekeeper:0xb549cb90 SIP Set new
interface 172.16.251.1%vmnet8 for transport udp$65.168.93.26:5060<if=udp$
172.16.251.1:5060>
2009/05/12 22:25:08.834 0:07.593 Housekeeper:0xb549cb90 SIP Sending PDU (667
bytes) to: rem=udp$65.168.93.26:5060,local=udp$172.16.251.1:5060
,if=172.16.251.1%vmnet8

I am not sure, but I suppose it is because ekiga uses in the previous line your private address. This was a bug in 3.2.0 which got fixed in 3.2.1 (and subsequent). You see if you are hit by this bug if ekiga -d 4 2>&1 | grep STUN does not show smth like "Stun server... replied ... NAT".

Solution: Either you upgrade, or re-compile with the patch http://git.gnome.org/cgit/ekiga/commit/?h=gnome-2-26&id=886c7668d815955b046f4270004503bd4256d388 applied.

--
Eugen


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]