<html><body><div dir="ltr">
We don’t list DIDs on our invoices when customers have a large number (and they have close to 1k). We do have CDRs showing that we test called it last year, and thinQ has confirmed that a mistake caused it to be taken back by their resporg. So I think ownership evidence is solid.</div><div dir="ltr"><br></div><div dir="ltr">I don’t know what you mean by NASC it, that’s probably access we do not have, as an ultra-small ITSP. We just go through thinQ and Bandwidth for all number management and porting.</div><div dir="ltr"><br></div><div dir="ltr">They are trying to get it released back from Telnyx. If that is refused, we’re going to be headed into a storm, I think.</div><div dir="ltr"><br></div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mar 14, 2023 at 9:54:48 AM, Ivan Kovacevic <<a href="mailto:ivan.kovacevic@startelecom.ca">ivan.kovacevic@startelecom.ca</a>> wrote:<br></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" type="cite">
<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small"><div class="gmail_default">Do you have a <30 day invoice with the number on it? </div><div class="gmail_default"><br></div><div class="gmail_default">I would try to NASC it... it may set off a pissing match between you and the current user, but if you can show that you had it first... you may win it. </div><div class="gmail_default"><br></div><div class="gmail_default"></div></div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><table border="0" cellspacing="0" cellpadding="0"><tbody><tr><td width="10" valign="top" style="width:7.5pt;padding:7.5pt 22.5pt 0cm 7.5pt"><p><a href="http://www.startelecom.ca" target="_blank"><img src="https://www.startelecom.ca/wp-content/uploads/2022/09/Star-Telecom-Genesys-Partner-Signature-2022-small-6.5.png" alt="Star Telecom - Cloud Communications and Customer Experience Solutions"></a><br><br><span style="color:rgb(34,34,34)"> </span><a href="https://www.linkedin.com/company/star-telecom-www-startelecom-ca-/" style="color:rgb(17,85,204)" target="_blank"><img src="https://www.startelecom.ca/wp-content/uploads/2022/09/linkedin-18.png"></a><span style="color:rgb(34,34,34)"> </span><a href="https://www.facebook.com/startelecomcanada" style="color:rgb(17,85,204)" target="_blank"><img src="https://www.startelecom.ca/wp-content/uploads/2022/09/facebook-18.png"></a><span style="color:rgb(34,34,34)"> </span><a href="https://twitter.com/startelecom?lang=en" style="color:rgb(17,85,204)" target="_blank"><img src="https://www.startelecom.ca/wp-content/uploads/2022/09/twitter-19.png"></a><span style="color:rgb(34,34,34)"> </span><a href="https://www.youtube.com/channel/UC7Us9bsIx2_ua1-LSQ3FGhw" style="color:rgb(17,85,204)" target="_blank"><img src="https://www.startelecom.ca/wp-content/uploads/2022/09/youtube-19.png"></a><br></p></td><td valign="top" style="border-top:none;border-bottom:none;border-left:none;border-right:1pt solid rgb(177,177,177);padding:0cm"></td><td valign="top" style="padding:0cm 0cm 0cm 15pt"><p><font face="trebuchet ms, sans-serif"><b><span style="font-size:10.5pt;color:rgb(51,51,51)">Ivan Kovacevic</span></b></font><span style="color:rgb(0,0,0);font-family:"trebuchet ms",sans-serif;font-size:x-small"> </span><font face="trebuchet ms, sans-serif"><span style="font-size:9pt;color:rgb(173,173,173)"><br></span></font></p><p><a href="http://www.startelecom.ca/" style="font-size:x-small;font-family:"trebuchet ms",sans-serif" target="_blank">www.startelecom.ca</a><br></p></td></tr></tbody></table></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 14, 2023 at 12:45 PM Carlos Alvarez via VoiceOps <<a href="mailto:voiceops@voiceops.org">voiceops@voiceops.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="">This is a huge problem, so while I’m waiting for thinQ to tell me what they can do, I thought I’d check with my other resources. They gave us a small block of TF numbers some time back, and we assigned them to one customer. We tested them in March of 2022. One of them was not put into use as it was for a pre-planned project this year; the customer needed to physically publish the number on posters, via letters, and by email. Now it’s time to start the project, and we find out that the number has been given to Telnyx. We were told by thinQ that it was part of a bad inventory load, but that can’t be possible since it did work. And we also have working numbers from the same batch (for now…that’s worrisome too).<div><br></div><div dir="ltr">Currently the number goes to a fax tone, and we don’t know who owns it. I have not tried sending a fax. I’m not sure how I’d start that conversation.</div><div dir="ltr"><br></div><div dir="ltr">This seems like a massive failing on thinQ’s part. The end user is a regional government authority that has spread the number far and wide. In fact if you google the number, you get the government agency’s info. What can we force them to do? The project was to go live on Monday.</div><br></div></div>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div><img src="https://t.sidekickopen71.com/s3t/o/5/f18dQhb0V1-gm08fTz3ZW2rZD6K2B9gXrN7sKj6v4LCS0Vf6xNj7dSCJWW64Jplz1pctGFW2w-ydG1k1H6H0?si=6470560385859584&pi=cb688069-cc25-425b-f19d-ca5c2aacbb91" alt="" style="display:none!important" height="1" width="1"></div>
<br>
<p><span style="font-size:10.0pt">NOTE: This email message and
any attachments are for the sole use of the intended recipient(s) and may
contain confidential and/or privileged information. Any unauthorized review,
use, disclosure or distribution is prohibited. If you are not the intended recipient,
please contact the sender by replying to this email, and destroy all copies of
the original message.</span></p>
</blockquote>
</div></body></html>