[VoiceOps] Toll Free as Outbound CLID
d at d-man.org
Mon Apr 20 13:08:14 EDT 2015
I believe the proper solution here is the toll-free number goes in the Caller-ID header (P-Asserted or otherwise) and your From: field should carry the ANI (or the optional but rarely used ANI field). This works with most of our providers.
The issue is as Calvin has listed. You need to have knowledge of how to bill, and that’s especially important when the remote party is the one doing the billing. So ultimately, you need to send a non-TF number in the ANI header and the Caller-ID would have the Toll-Free number. This is allowed behavior with most carriers.
From: "Calvin E." <calvine at gmail.com<mailto:calvine at gmail.com>>
Date: Monday, April 20, 2015 at 10:06 AM
To: Shripal Daphtary <shripald at gmail.com<mailto:shripald at gmail.com>>
Cc: "VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>" <VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>>
Subject: Re: [VoiceOps] Toll Free as Outbound CLID
>From the perspective of a wholesale VoIP provider, we do see Toll Free ANI causing some problems:
Routing - some carriers will reject these calls, which can result in traffic connecting at a higher LCR position and therefore less margin.
Rating - TF ANI may result in calls being billed under "indeterminate jurisdiction", which is typically the higher of the interstate and intrastate rates or some 3rd penalty rate.
On Mon, Apr 20, 2015 at 5:13 AM, Shripal Daphtary <shripald at gmail.com<mailto:shripald at gmail.com>> wrote:
i'm just wondering if there is a legal/regulatory issue with having a TFN as the outbound CLID for a customer on our hosted platform(s).
On the broadworks, the system won't even allow for it. However, on our M6, it doesn't really care.
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the VoiceOps