Quote:
Originally Posted by emoci
|
Yes, the Toolio in that thread is me. That problem has resolved itself, after I registered voip.ms on Voxalot with server IPs instead of names.
But the Voxalot call forwarding problem continued (at least last night). And it isn't restricted only to Voip.ms, so that might provide additional clues.
Originally I thought the problem trying to forward Voip.ms as a "provider" was because I had a few subaccounts listed and Voxalot was not able to distinguish one from the other (even though they have separate account numbers). So I unregistered all but one, but the problem persisted. Then I recalled that a few days ago I was able to do all of this successfully no matter how many Voip.ms subaccounts were registered.
On that topic, do you know if Voxalot identifies providers only by their name or server name, or by actual accounts. In other words, for forwarding purposes should my Voxalot account be able to distinguish between Voip.ms account 111111_01 and 111111_02 when both are registered with the same Voxalot account?
When I have some time today I will try to replicate the problem (or forward successfully) from some of the same providers on my other Voxalot premium account. I'll let you know what happens. I'll also test all of this again in case it was a temporary glitch.
Thanks again for your help and advice. I appreciate it.