“if the incoming caller is hiding their phone number this call will fail due to the new regulations for CID, on where sending a valid caller ID number is mandatory.”
At the moment this is correct, due regulations over the callerid for hidden or anonymous callerID the only work around is to manage a call forwarding with CallerID override set, now when using the callerID filtering tool, you can set this up ONLY for those calls that reach you out with the callerid information in this form.
We understand this might not be optimal, however this is a workaround to be able to receive those calls for now.
Incoming calls with valid callerID information would not be affected and won’t require any special configuration.
Back in 2022 new regulations over callerID information was applied for our service, also following the guideliness from our carriers, where valid information is required for incoming and outgoing calls to ensure connectivity.
This appears to be impossible due to the fact that I can’t create multiple call forwardings targeting the same destination number.
This is not correct, you can create multiple call forwardings using the same number , one of the purposes is specifically to use the callerid filtering, this way you can setup the filter for anonymous callers into the modified call forwarding and use the regular call forwarding in a different way.
The fact that calls with anonymous/hidden caller-ID go straight to voicemail by default seems extremely sub-optimal to me.
With proper configuration this should not occur and should take path the route set in the callerId filtering instead of just going into VM
In this sense what you aim to is, to have the anonymous callers forwarded and reaching the route set correctly , the only difference would be that they will have the callerID override set instead of displaying anonymous
Anything you can point to in terms of public information on these regulations?
I tried to do exactly that, but when I attempt to add a second call forwarding to the same (target) number, I get the error that “The number you provided is already in use”.
Given that the form in question contains at least 2 different phone numbers, I’m unsure which one “the number you provided” refers to, but I’m pretty sure that it’s saying I can’t create multiple forwardings to the same (target) number since it happens with multiple different options for caller-ID override:
I was able to duplicate the record this way, one record with 1 in front, and the second record without 1 in front, this might only work for US/CAN as long as you have dialing mode NANPA on the account settings. In addition this is only a workaround.
As I verified there is a limitation with the call forwarding entries as you confirmed, in this moment.
I would think any provider of medical would not use Anonymous as caller ID. I would confirm with the provider. I have a Poly 402 ATA and have setup VOIP.MS to play a message to users who “block” caller ID (Enter *67) so those calls are received but tells caller to not block their number. I tested it with my cell. Is it possible you have a filter enabled?
I love the Anonymous is blocked and not routed as that has stopped 99% of the SPAM calls I was receiving on our number.
Quick suggestion to solve your problem, instead of forwarding to a phone number, you could route to a sub-account, and then use a softphone to receive calls on your cellphone for this sub-account.
We are pleased to announce that the feature allowing the creation of multiple call forwardings with the same number has been reinstated.
This will enable you to effectively implement the following workaround:
Create a call forwarding with CallerID override set, now when using the callerID filtering tool, you can set this record (the one with the callerid override) up ONLY for those calls that reach you out with the callerid information in this form in order to receive anonymous calls.
While you have a regular call forwarding with the same number, without callerID override for regular routing
