<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">oops, didn't finish my though. <div><br></div><div>i'm assuming there is no way to differentiate between a US TFN and CANADIAN TFN right? </div><div><br></div><div>thanks </div><div><br></div><div>srhi<br><div><div>On Oct 19, 2012, at 11:28 AM, Shripal Daphtary <<a href="mailto:shripald@gmail.com">shripald@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">there's no way to differ<br><br><div class="gmail_quote">On Fri, Oct 19, 2012 at 10:25 AM, Shripal Daphtary <span dir="ltr"><<a href="mailto:shripald@gmail.com" target="_blank">shripald@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks. I'm actually working with Primus Canada and I have inbound trunks with them now.<br>
<br>
<br>
<br>
Sent from my mobile device.<br>
<div class="HOEnZb"><div class="h5"><br>
On Oct 19, 2012, at 10:05 AM, Jared Geiger <<a href="mailto:jared@compuwizz.net">jared@compuwizz.net</a>> wrote:<br>
<br>
> On Fri, Oct 19, 2012 at 9:23 AM, Shripal Daphtary <<a href="mailto:shripald@gmail.com">shripald@gmail.com</a>> wrote:<br>
>> Hi all, I have an issue that seems to have arisen (perhaps recently), that<br>
>> i'm unsure of how to resolve. We have a few customers in the Toronto, ON<br>
>> area where the outgoing CLID set as a Toronto TN (sourced from <a href="http://bandwidth.com/" target="_blank">bandwidth.com</a><br>
>> i believe). when these customers dial canadian Toll Free numbers, the TFN<br>
>> provider rejects the call. we send these calls our our level3 EVT trunk.<br>
>> Level 3 states that they only support canadian TN's calling Canadian TFN's<br>
>> as "best effort".<br>
>><br>
>> we have the same issue sending the calls out Bandwidth, where they might<br>
>> likely send the call out Level3 as well.<br>
>> we have the same issue sending the calls out windstream.<br>
>><br>
>> has anyone seen this issue as well? i'm going to try a few more carriers.<br>
>><br>
>> thanks,<br>
>><br>
>> shri<br>
>><br>
>> _______________________________________________<br>
>> VoiceOps mailing list<br>
>> <a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br>
>> <a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
><br>
> Hi Shri,<br>
><br>
> Yes we see this a lot. The frustrating part is when the carrier<br>
> doesn't give a 503 but instead plays a recording. We usually have good<br>
> luck by first sending the call to our Peerless Networks trunks and<br>
> then if they can't terminate it, they do 503 it and then we try 360<br>
> Networks (Onvoy Voip360). This has given us the best results.<br>
><br>
> Carriers that we've tested that tend to play a message are O1<br>
> Communications and Hypercube,<br>
><br>
> I've been told in Canada many carriers have to pay to terminate the<br>
> Toll Free traffic reliably. I would suggest talking to Primus Canada<br>
> to see if they can help you out.<br>
><br>
> ~Jared<br>
> _______________________________________________<br>
> VoiceOps mailing list<br>
> <a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</div></div></blockquote></div><br>
</blockquote></div><br></div></body></html>