[jperry22]

I got up early this morning to run some tests on BV in the wee hours. Here is what I saw and what has been progessing through the day. I invite anyone to add or dispute the findings with you own tests. All input is welcome.

I'm in the 281-984 exchange

05:00 CDT:

Outgoing:
calling withing my own call center worked.
calling adjacent call centers worked.
calling my own BV 800 number worked.
calling my BV UK number worked.
calling outside of my call center (out of state) worked.
did not call any international numbers at this time.

Inbound:
primary BV number worked from internal and external numbers.
all "special" number worked (800, UK, etc.)

Tests were performed both within BV as well as from an outside PSTN line. I was homed through my asterisk server with DCA at the time.

11:00 CDT
have lost inbound audio on incoming calls to primary number
have lost ability to call adjacent call centers. I can still call within my own call center and "distant" (non-adjacent call center) calls work.

I'm still homed on DCA.

It's just my opinion and I may be wrong but it appears that as the call load picks up during the normal course of the morning, we seem to start having spotty problems.

Anyone have any ideas?

[jperry22]

I also have another BV number that is directly provisioned by BV on a SPA-2000. BV is currently provisioning it for LAX. I'll point the asterisk server at LAX also and see what happens.

----------------------------

UPDATE: Further tests show that the BV-provisioned Sipura has the same problems as the asterisk server. The asterisk server cannot register with LAX but can still register with DCA.

[cayman]

MY BV is still basically unreliable, up sometimes for incoming/out but not all things work even in the best of times. Mostly its basically down and NOT reliable at any time. If/when SimulRing works, the caller-ID is some strange unknown out-of-area #. Sometimes I can't call out at all. I just had LAX totally fail and refuse to re-register a few minutes ago. I've now moved back to DCA, but my GLBX primary doesn't work for incoming although my alternate does ring [only] the SimulRing (strange caller-ID).

Bottm-line: BV ist still broken.

I sent in an email request for a credit to billing for the $9.95 charge when I dropped my GLBX alternate and picked up a non-GLBX alternate a few days back in an attempt to get some incoming. No response whatsoever.

I was told mid-day yesterday that there would be a posting on the portal later in the day. I didn't post anything here as it didn't help anyone and the last time I was told that there would be a press release, nothing happened and I got yelled at for leaking.

So imagine my surprise when they did post something, and imagine my further surprise when I went to look at it and got a 404. I IM'd my contact and they got it fixed later. Not too damn impressive and the letter, IMO, just didn't go far enough.

I've taken away the number I had RCF to BV, and Ive re-mapped my other non-BV-tollfree#s away from BV, and I've told folks to call me on my SR#. But with all that said, for the moment I'm still keeping my BV so I guess I'll end up paying for another month of service in a couple days in the next billing cycle. But it sure would be nice if they fix it soon. This boggles the mind.

BV had such great promise. At least I've learned a bunch more now with my Sipura 2100 and I'm looking forward to making the big leap into asterisk.

With great dissapointment,
- Don