12, 2016 8:37 PM
To: "VoiceOps" <voiceops@voiceops.org>
Subject: Re: [VoiceOps] Test Call Request
O1 opened a ticket with the ULC also.
It wasn't working on Hypercube, Alcazar Conv, ANPI, or Bandwidth. Maybe if
a couple get it fixed, everyone will be all fixed.
On Fri, Feb 12,
Greetings all,
I come to you today with a request.
We've been getting a lot of complaints from customers about their number
not being able to be called. In our CDR, We show no record of the call
attempt.
We get two general reports. 1. The call rings and rings (We never get the
behalf of Nick Olsen
<n...@flhsi.com>
Sent: Friday, February 12, 2016 2:42 PM
To: voiceops@voiceops.org
Subject: [VoiceOps] Test Call Request
Greetings all,
I come to you today with a request.
We've been getting a lot of complaints from customers about their number not
being able to be called
gt; *From:* VoiceOps <voiceops-boun...@voiceops.org> on behalf of Nick Olsen <
> n...@flhsi.com>
> *Sent:* Friday, February 12, 2016 2:42 PM
> *To:* voiceops@voiceops.org
> *Subject:* [VoiceOps] Test Call Request
>
> Greetings all,
>
> I come to you today with
Called from 414-269-60xx via SIP Logic out of NYC.
The recording played right away, no problems here.
On Fri, Feb 12, 2016 at 1:42 PM, Nick Olsen wrote:
> Greetings all,
>
> I come to you today with a request.
>
> We've been getting a lot of complaints from customers about
>From ATT wireless it works fine (two calls).
On Fri, Feb 12, 2016 at 2:53 PM, John Levine wrote:
> > The number is 321-205-1234, It should immediately answer and play back
> our
> >"You've reached Florida High Speed Internet" sound file. No DTMF options
> >will work, Then
Oddly, tonight I also had a customer complaining of the same issue as Nick.
They called a number we service three times and it hung with silence with
no rings for 20 seconds and then hung up. Like Nick, we never got the calls.
All of our tests through Thinq, Bandwidth and Verizon Wireless were
O1 opened a ticket with the ULC also.
It wasn't working on Hypercube, Alcazar Conv, ANPI, or Bandwidth. Maybe if
a couple get it fixed, everyone will be all fixed.
On Fri, Feb 12, 2016 at 4:12 PM, Paul Timmins wrote:
> Level 3 routed away from an "underlying carrier" and now
Level 3 routed away from an "underlying carrier" and now i can call
through just fine. They opened a ticket with the "underlying carrier" so
hopefully that kicks this issue in the junk for you :D
On 02/12/2016 05:33 PM, Rafael Possamai wrote:
Called from 414-269-60xx via SIP Logic out of NYC.