Hello,
I am attempting to connect to any one one the many phone numbers used by the Atlanta VA medical system. When I attempt a call them, it rings, and then I get silence. I mainly try their main IVR hospital number in Atlanta. They have a listing of all their group office numbers on line. I tried most off them and get the same issue. I can dial many of the other VA numbers to other clinics outside of their coverage.
I have tried creating new sub-accounts, with various settings, but it is all the same. I tried setting up a soft phone, connecting it directly to the VOIP.ms POP servers using the Atlanta1 and 2 servers, and using my cell phones wireless connection, bypassing my home network all together.
I attempted to get online support but so far they tested their connectivity and they can get through with no problem. All they keep doing as asking me to try again. From what I can tell, they have not gone through any logs on their end to address this.
I am using the Zoiper soft phone, and am calling 404-321-6111 to troubleshoot this.
Thank you for any help,
HM
I’m at opposite end of continent, but my service stopped working about a week ago (using an ATA). I tried several reconfigurations, made improvements, but what finally worked was to mark (within subaccount) ‘use xyz-DID for CallerID’ explicitly. (My previous setting was wrong: using the ATA to assert CID.) I think VoIP.ms suddenly started to tighten-up conformance to FCC guidelines re CID, as part of its anti-robocallling campaign; but they did so without warning me. If your softphone can do encrypted calls, try turning that off until you get it working without the feature. In my ATA the chosen servers are in ‘servernameCITY3’ format with the number at the end; but I use the list of acceptable IPv4 server addresses as POP restriction in both subaccount screen and in the ATA as well. See if that helps!-SipDriver
Hello,
I have already set the CallerID Number in my sub-account to use one of mi DID numbers for the ID. Is this what you mean by suggesting an explicit CallerID? When you suggest trying a IPV4 address for the POP server, where are you suggesting I change it? On the soft-phone?
Thanks,
BTW: This worked until a few weeks ago. Perhaps your suggestion that Voip.ms changed something is more likely my issue too.
Hello @gmichie,
This is not easy to debug things like that.
CallerID setting: Yes, what @SipDriver means is explicitly selecting one of your DIDs in the sub-account settings under “Use this DID for CallerID” (instead of letting the ATA/softphone assert it). If you already have that set, good. If you have other DID, this could be a good idea to try that other one—sometimes a particular DID get flagged or treated differently on the destination side.
Also, here are other thoughts but I am not sure they will help in this case. But who knows.
- Try another softphone (to rule out a Zoiper-specific quirk).
- Do you have any error message or log on Zoiper when it disconnects, or any clue on your CDR?
- Are you using TLS with SRTP? If no, try it.
It might be a STIR/SHAKEN/Robocall filtering on the other side. Trying another validated DID can be useful in that case to see if this is robocall filtering, or an issue with the DID validity. Do not let Zoiper send out the phone number to use. This should be provided by your sub account, a DID from your account.
It might also be an (S)RTP negotiation failure. In that case, the phone rings, but then the audio connection fails, and the call is dropped. A RTP issue can be caused by a NAT issue (this is why TLS+SRTP is best because it avoids all kinds of network issues) but probably not the case here, or due to a codec mismatch or encryption issue.
Kind regards.
It now seems to be a hit or miss issue. Mostly, miss. I have not tried SRPT. It looks to be a bit difficult to configure. I see that once set up, you cannot undo it. If it does not solve my issue, am I stuck with it?
Hello @gmichie,
One setup you can go back at any time. This is not complicated, but required attention to every details. If you do not use TLS/SRTP, I would recommand to try that. It might just solve your problem, or at least, it cannot make it worst.
If you are using sub accounts, just activate it for the one you want to try it:
https://wiki.voip.ms/article/Call_Encryption_-_TLS/SRTP#Activate_This_Option_on_Your_Sub_Account
Then configure your SIP client. Make sure to setup the SIP ports properly, and the RTP/SRTP port too.
To recap, there are 3 things to do:
- Activate on account (or sub account).
- Activate SIP-TLS on device (and make sure the port is right: 5061).
- Set SRTP on device as mendatory.
You should then be good to go. If you want to stop using TLS, simply deactivate on sub account, then reconfigure the client to not use TLS and no SRTP as mendatory.
Kind regards!