thanks Ivan, i was just told that its not that we CANT do it on the bworks, but we don't b/c currently can't bill for it if the clid is a TFN. On Mon, Apr 20, 2015 at 11:36 AM, Ivan Kovacevic < ivan.kovacevic at startelecom.ca> wrote:

Hi Shri,

In Canada it is mandated by the CRTC and most carriers pass it through when we send it. Most of our US-bound traffic uses TF CLI which seems to come across. So as far as we are aware, using TF as CLI is not an issue.

Best Regards,

Ivan Kovacevic

Vice President, Client Services

Star Telecom | www.startelecom.ca | SIP Based Services for Contact Centers

*From:* VoiceOps [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Shripal Daphtary *Sent:* Monday, April 20, 2015 11:13 AM *To:* VoiceOps at voiceops.org *Subject:* [VoiceOps] Toll Free as Outbound CLID

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

Thanks! I'll work on it with billing over here Shripal

On Apr 20, 2015, at 12:11 PM, Glen Gerhard <ggerhard at sansay.com> wrote:

Hi Shripal,

normally calls with TF CLIDs are just billed as Indeterminant Jurisdiction. If your rate sheets don't specify IJ calls then it is generally the higher of the two rates.

~Glen

...

On 4/20/2015 8:38 AM, Shripal Daphtary wrote: thanks Ivan,

i was just told that its not that we CANT do it on the bworks, but we don't b/c currently can't bill for it if the clid is a TFN.

...

On Mon, Apr 20, 2015 at 11:36 AM, Ivan Kovacevic <ivan.kovacevic at startelecom.ca> wrote: Hi Shri,

In Canada it is mandated by the CRTC and most carriers pass it through when we send it. Most of our US-bound traffic uses TF CLI which seems to come across. So as far as we are aware, using TF as CLI is not an issue.

Best Regards,

Ivan Kovacevic

Vice President, Client Services

Star Telecom | www.startelecom.ca | SIP Based Services for Contact Centers

From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Shripal Daphtary Sent: Monday, April 20, 2015 11:13 AM To: VoiceOps at voiceops.org Subject: [VoiceOps] Toll Free as Outbound CLID

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

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: 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<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops

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