[VoiceOps] Code opening miseries

Mary Lou Carey marylou at backuptelecom.com
Tue May 1 10:52:38 EDT 2012

I don't know of any new industry requirements but it definitely is a
problem. I know you can put in a suggestion with the NANC group that creates
all the guidelines, but don't expect anything to happen soon on that if you
do because they discuss everything to death before they do anything.

It would at least be nice if you could get ahold of the right department so
you could put a trouble ticket in easily because when you make it to the
right department, they know what they need to do and can fix it right away.
My experience has been that you waste a lot of time locating the right
department because they don't publish their internal numbers so you have to
start with their customer care number and work in from there.  

If anyone is interested in consolidating resources, I would be happy to
volunteer my website as a resource to store it on. If you are interested and
have information you would like to share, please forward me the Carrier's
name and phone number so I can put together a contact list and get it posted
on my website. 

Mary Lou Carey
BackUP Telecom Consulting


-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Matthew S. Crocker
Sent: Tuesday, May 01, 2012 8:38 AM
To: Paul Timmins
Cc: VoiceOps
Subject: Re: [VoiceOps] Code opening miseries


  Both worked for me from my Broadsoft switch (bandwidth.com LD).

  Both worked from my iPhone (AT&T).

  I have an ear ache after dialing the first one. 
  I'd like to have my special dialing wand,  I mashed my keypad but your
system just hung up on me ;)

----- Original Message -----
> From: "Paul Timmins" <paul at timmins.net>
> To: "VoiceOps" <voiceops at voiceops.org>
> Sent: Tuesday, May 1, 2012 2:06:39 AM
> Subject: [VoiceOps] Code opening miseries
> Has the industry come up with a better way of dealing with the 
> drudgery of calling every carrier in an area and cajoling, begging, 
> and pleading with them to get their new prefix loaded in everyone's 
> switches other than the traditional "buy a pile of paygo phones and 
> open tickets with each carrier" method?
> (half frustrated, half serious. If I had spare time these days, it 
> seems this sort of contact information would be a perfect fit for my 
> database, but alas, I can barely keep up with eating 3 meals a day 
> these days, let alone work on more neat stuff like this)
> -Paul
> PS: If you can't call 708-666-7999 (and more humorously,
> 708-666-7565) please fix your stuff. If you have any unreachable 
> codes, I'll happily check my systems to return the favor.
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
VoiceOps mailing list
VoiceOps at voiceops.org

More information about the VoiceOps mailing list