|reply to vikingisson |
Re: [Cable] Routing issues to toronto.voip.ms
said by vikingisson:That would work, but only if the user notices that the server he's currently on is down. Ideally, Voip.ms needs to implement some sort of automatic failover to switch users to another server if one is down. Especially important since the current failover rules are server based so if the user's server is down, no calls goes through at all.
Just use a different server. I gave up on the toronto server a while back. Montreal and Chicago have good latency and are more reliable.
I can't help if you don't know there's a problem. And I can't make service providers automate failover practices. Meanwhile I can only do the next best thing. My logs have long told me that toronto.voip isn't reliable so I switched servers and POP. I still keep a toronto trunk active as *my* failover and to see if they ever fix the problem, they haven't.
A number of servers have had periods of relative instability. In addition to the Toronto servers, the NY and Montreal POP have had issues. Even other like Seattle have the occasional fit.
As well, most users don't have the ability to continually monitor the registration status for their accounts. Most Voip.ms users just use it as a hosted solution and don't have an Asterisk server with status monitoring scripts. Also Voip.ms doesn't provide an option that notifies users an account is offline like a few other providers do. Consequently, expecting the average user to know when their DID is unreachable due to server issue is unreasonable.
Then they should use a different service. The OP question isn't about what is reasonable or what should happen or any of that nonsense. The user has a problem and did check the right things, I'm answering to that. I dare say that the "average" user shouldn't use a service such as TSI given all that logic.