fareedf
join:2008-01-25
Portland, OR
| reply to nitzan
Re: Future Nine and IPKall
In my experience IPKall works fine with sip.future-nine.com but fails every times the ATA connected to sip2.future-nine.com. It doesn't matter if you have setup your proxy server for sip.future-nine.com or even IP address of the server at Future Nine still logs to one of 2 servers, I am not sure about the rules. If connected to sip.future-nine.com the calls come through without any issues but if it is connected to sip2 then based on amount the time that you setup your IPKall the person who called hears no ring tone on his or her end until it goes to VM. I hope this help Nitzan and his crew to figure out sip2 server. |
|
nitzan
Premium,VIP
join:2008-02-27
 ·ViaTalk
 ·Comcast
| reply to pandora
It depends on your router and ATA. sip may load balance between servers, while incoming goes to one server only. Some routers & ATA combo are OK with ATA being registered to server A, call coming from server B - but some reject those calls.
incoming.future-nine.com has DNS failover, so if the server goes down it will switch to a backup server within a few minutes.
Overall, for best reliability, I'd recommend using incoming.future-nine.com instead of sip if you have an incoming DID with us or use IpKall. If you use FN for outgoing only, it doesn't matter. |
|
pandora
Premium
join:2001-06-01
Outland
·ooma
·Future Nine Corpor..
·Comcast
|  reply to nitzan
I just checked, my IPKALL account is still pointing to sip.future-nine.com and seems to work fine. Is there an advantage / difference between sip.future-nine.com and incoming.future-nine.com?
--
"People demand freedom of speech as a compensation for the freedom of thought which they seldom use." |
|
