ducsg / siphon

Automatically exported from code.google.com/p/siphon
0 stars 0 forks source link

Can't connect to vitelity #392

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1. Configure for vitelity with same settings as my HT488:

Username: <user>
Password: <passwd>
Server: sip23.vitelity.net

Advanced/Proxy: sip23.vitelity.net
Advanced/Enable NAT: ON
Advanced/Auth. Username: <user>

Phone Settings/Codec: uLaw, ALaw, GSM, G.729

Network/Local Port: 5060
Network/Keep Alive Interval: 15
Network/Enable ICE: ON

(not mentioned = blank/default)

2. Try to connect (over WiFi)

What is the expected output? What do you see instead?

Always get "Service Unavailable" followed by "Request Timeout"
(Tried many combinations of Codecs, NAT on/off, ICE on/off: same results)

My HT488 connects just fine from the same network.

What version of the product are you using? On what operating system?

OS 3.1.2
Siphon 2.2.0-1

Please provide any additional information below.

By looking at the log all I see is that it keeps trying to retransmit
REGISTER messages (and that's all it does until it decides to timeout).

Original issue reported on code.google.com by cesar.cr...@gmail.com on 4 May 2010 at 6:50

GoogleCodeExporter commented 9 years ago
Vitelity using siphon has worked fine for me for months, the correct server 
should be: sip2.vitelity.net NOT sip23.vitelity.net

Original comment by max...@gmail.com on 29 Nov 2010 at 9:51

GoogleCodeExporter commented 9 years ago
Could you please share your detailed settings? sip23 is what vitelity tells me 
to use. I tried sip2 but it doesn't work either.

Original comment by cesar.cr...@gmail.com on 1 Dec 2010 at 6:52

GoogleCodeExporter commented 9 years ago
I made it work by opening up the firewall to UDP connections from Vitelity's 
server. My HT488 does not need this firewall setting (the router keeps track of 
SIP connections) so there is something else going on with Siphon's way of 
connecting...

Original comment by cesar.cr...@gmail.com on 1 Dec 2010 at 7:47