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

nikolas at networkmakers.com nikolas at networkmakers.com
Fri Jul 23 12:20:44 EDT 2010


Thank you Jason - pulling the cable is exactly what we ended up doing. The
length ended up being 210 ft., and it tested fine - so we should be OK. 

I still cannot believe that switching DIDs between two already-provisioned
and operational PRIs with the same vendor requires 25 days of lead time,
though! On the other hand, it looks like par for the course for AT&T.

 

Many thanks to everyone who responded - it was instructive, to say the
least! 

 

Nikola

 

 

 

 

 

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

Nikola Stojsin

PhD CCIE #12888

nikola at att.net

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

 

From: Jason Aarons (US) [mailto:jason.aarons at us.didata.com] 
Sent: Friday, July 23, 2010 9:52 AM
To: nikola at att.net; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] OT: AT&T circuit in Florida

 

Yeah it's normal for the last mile provider to require 21 business days,
I've seen other countries require 6 months (Asia, Central America). In the
case of AT&T you can request a "Expedite" for which they charge you more
even if they complete it in 20 days vs 21 days.  I recently had a AT&T PRI
in Houston, TX completed in about 14 days which surprised me.

 

You are better off having it moved, then having a wiring vendor run a
shielded T1 cable back to your floor for temp fix.

 

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

 

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

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

 

  _____  

Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee, you
are hereby notified that you have received this communication in error and
that any use or reproduction of this email or its contents is strictly
prohibited and may be unlawful. If you have received this communication in
error, please notify us immediately by replying to this message and deleting
it from your computer. Thank you. 

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


More information about the cisco-voip mailing list