You can take any of our local phone numbers and forward the calls to any regular phone number in the world. Some forward their FlyNumbers to a local number, for example – a Canada FlyNumber forwarded to a Canada mobile. Others go international – a UK FlyNumber forwarded to the US. (everyone has their reasons)
When you send FlyNumber calls to a regular phone number, we’ll pass along the caller-ID of the person calling the FlyNumber.
We do our best here but keep in mind there is a myriad of factors not in our control. The devices or software on both sides of the call, what countries they’re in, carriers used, etc.
Possible issue if you forward to a regular phone number and an anonymous/blocked call comes in
What happens when an anonymous call comes in on your FlyNumber and you have it set to forward to a regular phone number?
Or in other words – You have a FlyNumber, that forwards to regular phone number and a blocked/anonymous caller calls that FlyNumber.
Generally, we’ll send the “Anonymous” caller ID but not always. The call could be blocked or charged at the “highest rate”. Carriers and providers have started to block anonymous calls that are “terminating” to a regular phone number. This isn’t happening across the board but it’s something to be aware of.
Here’s the list from “corporate” where this applies. “CLI” being the “calling line identity” or in other words, the caller-id.
- 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 solution:
Anytime you forward the calls using VoIP ( ie SIP ) – we’ll always forward the call – with the anonymous or blocked caller-ID. You can do this directly from My account > My FlyNumbers – or with the phone system, where you can send the calls to multiple places. ( Smartphone, SIP desktop phone , Apps etc. )
