Re: [VoiceOps] TF number ported out/re-assigned without authorization

lear path of >>>>> ownership. If your docs supersede the one after the fact and you didn't >>>>> release the number or lose it due to non payment with notice etc.. >>>>> >>>>> >>>>> >>>>> -Original Message--

Re: [VoiceOps] TF number ported out/re-assigned without authorization

;>> release the number or lose it due to non payment with notice etc.. >>>> >>>> >>>> >>>> -Original Message- >>>> From: VoiceOps On Behalf Of Peter Beckman >>>> via VoiceOps >>>> Sent: Tuesday, March 14, 2

Re: [VoiceOps] TF number ported out/re-assigned without authorization

;>> -Original Message----- >>> From: VoiceOps On Behalf Of Peter Beckman >>> via VoiceOps >>> Sent: Tuesday, March 14, 2023 9:30 PM >>> To: Carlos Alvarez >>> Cc: VoiceOps >>> Subject: Re: [VoiceOps] TF number ported out/re-assi

Re: [VoiceOps] TF number ported out/re-assigned without authorization

e one after the fact and you didn't release the number or lose it due to non payment with notice etc.. -Original Message- From: VoiceOps On Behalf Of Peter Beckman via VoiceOps Sent: Tuesday, March 14, 2023 9:30 PM To: Carlos Alvarez Cc: VoiceOps Subject: Re: [VoiceOps] TF number por

Re: [VoiceOps] TF number ported out/re-assigned without authorization

fact and you didn't > release the number or lose it due to non payment with notice etc.. > > > > -Original Message- > From: VoiceOps On Behalf Of Peter Beckman > via VoiceOps > Sent: Tuesday, March 14, 2023 9:30 PM > To: Carlos Alvarez > Cc: VoiceOps &g

Re: [VoiceOps] TF number ported out/re-assigned without authorization

ceOps Sent: Tuesday, March 14, 2023 9:30 PM To: Carlos Alvarez Cc: VoiceOps Subject: Re: [VoiceOps] TF number ported out/re-assigned without authorization On Tue, 14 Mar 2023, Carlos Alvarez via VoiceOps wrote: > On Mar 14, 2023 at 2:03:17 PM, Peter Beckman wrote: > >> >> We&#

Re: [VoiceOps] TF number ported out/re-assigned without authorization

On Tue, 14 Mar 2023, Carlos Alvarez via VoiceOps wrote: On Mar 14, 2023 at 2:03:17 PM, Peter Beckman wrote: We've also put numbers into production that our carrier provided, only to find out they should not have been in their inventory at all. I’ve learned this lesson, hence the test call

Re: [VoiceOps] TF number ported out/re-assigned without authorization

I'm fighting one now for a local number. The number was with BW and used rarely. It disappeared from our account and no one was aware for 12 months. It's now with T-Mobile and we've been told to basically piss off. That nothing will happen.. On Tue, Mar 14, 2023 at 5:11 PM Carlos Alvarez via Voice

Re: [VoiceOps] TF number ported out/re-assigned without authorization

On Mar 14, 2023 at 2:03:17 PM, Peter Beckman wrote: > > We've also put numbers into production that our carrier provided, only to > find out they should not have been in their inventory at all. > I’ve learned this lesson, hence the test calls. But this is a new one on me; how often should we ha

Re: [VoiceOps] TF number ported out/re-assigned without authorization

You're not alone. We've had numbers ported out without authorization or even the correct information before, and we get billed for it for months until someone notices. We've also put numbers into production that our carrier provided, only to find out they should not have been in their inventory

Re: [VoiceOps] TF number ported out/re-assigned without authorization

NASC is a name for a process where your RespOrg takes ownership of the TFN without the cooperation of the losing carrier. So you can expect it to be bumpier than the usual give and take. If you are not your own RespOrg - then thinQ is likely not going to cooperate - since it would create liability.

Re: [VoiceOps] TF number ported out/re-assigned without authorization

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. I don’t know w

Re: [VoiceOps] TF number ported out/re-assigned without authorization

Do you have a <30 day invoice with the number on it? 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. [image: Star Telecom - Cloud Communications and Customer Experience Solutions]

[VoiceOps] TF number ported out/re-assigned without authorization

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 w