We touched on this topic a couple years ago however we see a slight increase in “anonymous caller ID connectivity issues” so thought to re-vist in a quick post here.
One of the ways you can use your FlyNumber is to forward the FlyNumber to a regular phone number. Any regular phone number in the world. When this happens the call is routed via what’s called the PSTN network, which is basically the network involved in connecting phone calls to and from regular phone numbers.
Generally you have 2 options as far as where to send the FlyNumber calls, a regular phone number or VoIP (PBX would fall in this category).
When the person calling your FlyNumber calls from a blocked or anonymous caller-ID and you have your FlyNumber set to forward to a regular phone number, the involved provider could choose not to connect the call.
This can happen with the following caller-ID types:
- Without a CLI
- Invalid CLI
- Manipulated CLI
- CLI originating from unidentified, closed, or unallocated prefix ranges
- CLI not in E.164 format
- CLI not matching ITU standards
- Anonymous, Blocked, Private CLI
The way around this is to also set your FlyNumber to go to VoIP, either directly or as a backup to your “standard phone number” forwarding.
Our cloud phone system can help because you can set the FlyNumber to go to a regular phone number and if there is no answer there, to go to a VoIP solution.