[cisco-voip] OT: AT&T circuit in Florida

Thu Jul 22 13:41:54 EDT 2010

Only 20,000 DIDs? Nah, I think listening threshold is at least 100,000! J

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

Nikola Stojsin

PhD CCIE #12888

nikola at att.net

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

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Haas, Neal
Sent: Thursday, July 22, 2010 12:10 PM
To: 'Edward Beheler'; 'cisco-voip at puck.nether.net'
Subject: Re: [cisco-voip] OT: AT&T circuit in Florida

I always put on my ports "Contact me before porting". And I make sure the AM
knows this. If they port early on me I would let them know I was looking to
move to another carrier! Hey almost 20,000 DID's, they might listen to me.

Neal Haas

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Edward Beheler
Sent: Thursday, July 22, 2010 9:02 AM
To: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] OT: AT&T circuit in Florida

AT&T isn't the only ones to do this, Verizon has done this to me multiple
times.  They ported over Emergency Management, Community Corrections, and
Work Release a week early on me.  Then the morning of instead of at the end
of the day.  Then at 2PM instead of the end of the day.

At another facility, they disconnected the old numbers and went home without
connecting them to the new PRI - at a facility that houses elderly and
handicapped people.  When I asked what would happen if they needed to call
911, A support person (I swear to God this actually happened) suggested that
I go out and buy some prepaid cellphones.

"Can you hear me now?"

"We're sorry, you have reached a number that is disconnected or no longer in
service."

/rant

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Bill
Sent: Thursday, July 22, 2010 11:43 AM
To: 'Ted Nugent'; nikola at att.net
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] OT: AT&T circuit in Florida

Second the motion on porting early. I have had them do that to me multiple
times. 

  _____  

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ted Nugent
Sent: Thursday, July 22, 2010 10:35 AM
To: nikola at att.net
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] OT: AT&T circuit in Florida

Not familiar with Florida but that doesn't seem excessive just knowing its
AT&T. We fight with them constantly about this in NC (formerly Bellsouth for
the most part) Just pray that they don't screw up anything in the port order
or 25 days might turn into 45. Also they are notorious for porting early
here especially if they had a port date pushed out for some reason, I've
seen it twice where half the number still ported even though they themselves
screwed up the order and pushed out the port date. 

Your only option really is to raise holy hell with their AM and see if they
can get it escalated.

On Thu, Jul 22, 2010 at 11:25 AM, Nikola Stojsin <nikolas at networkmakers.com>
wrote:

Hello guys -

First of all, my apologies - this is quite OT; I just want to make sure that
the information we are getting is correct.

We have a client that is moving their Florida office from one floor to
another (same building, bigger space) - and their phone system from one AT&T
PRI to another. The new circuit is tested and turned up; however, the client
elected not to port the DIDs (there are 20 of them) at the time of the test
and turn up, because they were not ready to physically move (they needed
another week to get the new space ready, furniture-wise etc.). So they
stayed in the old space (using the old PRI etc.) for another week or so. 

Now - less than a week later - they are being told by AT&T that it will take
25 days to re-schedule the port of the DIDs. I do not have much experience
with Florida ISPs (and the client chose to do their own circuit provisioning
- they have a national contract with AT&T - so I do not know all the
details), but 25 days sounds excessive; I have seen 5- and 7-day delays (one
of which was in in fact in Florida, though not with AT&T), but nothing even
coming close to 25 days, which makes me wonder whether the client is getting
the right information.  

Bottom line: if anyone on this list has any experience with AT&T PRIs in
Florida, and cares to chime in - is 25 days 'normal' lead time to schedule a
DID port?

Needless to say, all help/input/suggestions will be greatly appreciated!

Thank you,

Nikola

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

Nikola Stojsin

PhD CCIE #12888

President

nikola at att.net

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

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100722/ca048b4e/attachment.html>