[VoiceOps] Toll Free as Outbound CLID

[Calvin E.]

Also, those carrier rejects can add up to PDD and overall deflated stats
(lower ASR, higher FCR). When our customers complain about poor
connectivity, this is often the culprit.

On Mon, Apr 20, 2015 at 7:11 AM Colin Brown <zavoid at gmail.com> wrote:

> I have also seen numerous carriers reject the calls as well, I've also
> seen carriers change that after re-negotiating with them so your milage may
> vary.
>
> On Mon, Apr 20, 2015 at 1:06 PM, Calvin E. <calvine at gmail.com> wrote:
>
>> 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>
>> wrote:
>>
>>> Hello everyone,
>>>
>>> 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.
>>>
>>> thanks
>>>
>>> Shri
>>>
>>>
>>>
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>
>>>
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20150420/1e773dd7/attachment-0001.html>