I’ve had voip.ms accounts for probably 10 years so I know my way around the portal and various settings. But I can’t figure this one out.
I’ve got a DID, I have all routing options, including all fail-over, set to voice mail, the voicemail box / account exists. Yet when I call the DID, I get a busy signal. Not a fast busy.
In the CDR, the call disposition says busy. The CDR record lists a user agent and IP, not every record shows those. Is that the user-agent/IP of the calling device/ATA, or the receiving ATA?
I don’t think I have an ATA that is using that DID, but if I did, is that the reason for the busy? I’d have to track down which of several ATA’s I could have configured in the past to use that DID - is there some way to know this by looking at the DID (ie - manage DID’s) ?
Have you checked if you have any Call Filtering rules that would route the call to System/Busy for the CallerID you are calling from?
I’ve checked all possible call filtering, forwarding and parking rules, and I can’t figure this out.
I have multiple voip.ms accounts. Let’s say Account A and Account B.
Account A has several DIDs, the problem DID is one of them. Let’s call this DID-P. When I call DID-P from Account B, I always get a busy signal, even if the routing for DID-P is set to voicemail for all situations. The call logs for Account B show that a call was placed to DID-P, and that the disposition was Busy. The call logs for Account A do not show that a call was received for DID-P. If I call another DID belonging to Account A from Account B, everything is fine.
If I call DID-P from Account A, I also get busy signal.
If I call DID-P from the outside phone network (what I call the PSTN), it works! It follows the routing rules I have set up. If the rules say to go to voice mail, I get voice mail. If the rules say to route the call to a registered device or ATA, the call can be answered there.
DID-P is a DID that I’ve had for several years that I haven’t regularly used other than for recieving texts. I have the POP for this DID set to Toronto-07. Most or all of my other DID’s are set to Toronto-9 or Toronto-10.
I recall having a similar problem some months ago: one of my numbers was consistently unreachable from any of my other numbers I have with VOIP.MS, but it was reachable from the outside. I did not follow up on that matter, because except for testing I don’t really have to call my own numbers, and, anyway, it’s working now (just tried it). It might be worth exporting your set of filter rules, deleting all rules, making some test calls, and then importing the set again to enable filtering as needed. I seem to recall that at some time I solved some weird cconnection issues that way…
I think you should open a support ticket from your Portal. I suspect that there is something under the hood that only the VoIP.ms admin will be able to see.