I have multiple numbers with voip.ms and am decent with computer settings.
I am using linphone and I put in the exact same settings for my first subaccount, XXXXXX_YYY1 as for my second account XXXXXX_YYY2.
My subaccount settings are identical except the subaccounts are on different servers.
I can place calls fine with the first account, I can’t get make any outgoing calls on the second account and get a network error every time.
I really need to use this line and am very frustrated because it feels like this is an issue with the line itself or a backend problem, not a configuration problem. When I contacted voip.ms, they said they checked some things and it should be fine, but it’s not working.
I have tried multiple servers to see if this was a server issue and the server just choosing to block my incoming IP and I get the same error. I deleted the account and re-added it in case it was due to a typo, I get the same error. I just don’t know what to do anymore.
I mostly love voip.ms because of their great prices and features but I don’t know what to do. Does anyone have any ideas?
Are you trying to use a secure connection (SSL?) if not, I would suggest you start there. It is a little bit trickier to setup, but it avoids lots of networks and settings hurdles down the road. It works flawlessly anywhere* after. (Any public places, airports, etc., of course, with a VPN or not.)
There might be geo-related security limitations, like if you go to Europe, you will have to use a European server.
Have you set any POP server security on your subaccount? If so, it must match the server you are connecting to. FYI, the “Canada” POP server does not mean “any server in Canada”, it means the new distributed POP cluster currently in Beta testing.
I use TLS for all connections because I connect to VPNs sometimes and don’t want the packets unencrypted in transit, which would seem not a good idea to me.
Is this the same as SSL?
I just use TLS
it’s just servernameforvoipms:5061 with tls as the option
I use the exact same configuration for other TLS lines and they work fine.
Yes, this is the same. Sorry for the confusion. This is a very good place to start. If this is not working with these settings, properly set, there is a serious issue.
But usually I found that my problem was always with a forgotten setting. Just this little detail here and there. So every time I got an issue I took the time to systematically read the documentation for TLS and double-make sure that all the settings were set properly. Most of the time there was “this” or “that” that I forgot, and then everything was working.
You probably already did that, but:
Check on the server side for the TLS settings for the sub account. (Encrypted SIP traffic.)
Check on the device every setting. TLS, SRTP as mandatory (this is the one I usually forget, the mandatory part), using port 5061.
If you do that, it should work right away. (SRTP mandatory is the one I forgot; now I remember it all the time.)
voip.ms blocked my outgoing calls, didn’t tell me when i contacted customer support, then sent me an email (but didn’t respond to the support inquiries) because the configuration was “suspicious,” telling me i had to click some link buried in the email to enable the call.
I can’t believe their technical support didn’t know this and didn’t tell me to just check my email.
i do not want AI or cloudflare or whoever monitoring my connections for voip.ms to randomly flag if they are “suspicious” and randomly halt my calls.
i had an urgent matter that was highly important, this delayed me for 6 hours and their support staff never told me the calls were being halted because i didn’t authorize it in the email. this was really not acceptable. someone i knew had a personal emergency and I needed this number available.
If voip.ms intends to randomly block calls and call configurations and email users, they should warn them
is there a way to turn this “feature” off? if there isn’t, i’m going to consider going to a different company, because this sort of paternalism and blocking calls doesn’t help in urgent situations
this was an incredibly frustrating experience, despite how much i normally like voip.ms
i also do not have foreign IP guard enabled or any advanced security enabled. It’s just randomly flagging my IPs and then blocking any calls for that number.
This is really annoying and awful.
Is there a reason this can’t be opt-in?
And for technical support to not tell me that I might need to me to check emails, leading me to some wild goose chase configuration check on a day that was absolute h*ck for me after finding out something horrible happened with someone i knew who needed to contact me… that really takes the cake. I wasted 6 hours because support couldn’t say “we randomly block outgoing calls on new configurations if our AI system thinks it’s suspicious unless you click on a random email we send you” - great stuff. (I did not provide this number to that person because I thought it wasn’t getting inbound calls since I couldn’t place outbound calls.)
well, i hope this feature and technical support not telling me to check my emails was somehow a useful security feature to someone, it certainly wasn’t me
i’m sorry, but this was really frustrating, i’m usually a very happy and loyal voip.ms customer, but i feel treated poorly
Happened to me twice, with sufficient time between the incidents that I had forgotten about the first block when I encountered the second one - so in both cases I spent more than an hour trying to figure thinhgs out.
I don’t think that email is the appropriate communication channel when someone tries to use the phone system. Insterd, the system should provide an error message that gives the user enough of a hint about where to look for a solution
I previously have complained here about misleading or uninformative error messages:
My challenge to the good folks at VOIP.MS is this: you are communication specialists - can you please ensure your technology communicates well with us users?
Following up:
As an aside, here are the official SIP response codes:
it would be a good idea to put this list into the VOIP.MS’s wiki, as well.
ALso, code 580 (“Precondition Failure)”, could be used, for example, for those “suspicious” calls (among other things), with an explanation in VOIP.MS’s own wiki of what this code could mean and what users need to look for or do.
