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

[Matthew Loraditch]

What I might suggest for something like this and I will admit I don't know the costs for all carriers or the implications for anything beyond a simple setup, but we had a similar situation and what we did was have our carrier set it up as a trunk group between the old and new pris, we could turn up the new one, test outbound calling, during a maintenance interval disable the original one and test inbound to the new one as with the Trunk group they automatically overflowed to the new one, and then at the move permanently disable the old one and schedule it for disconnect.


Matthew Loraditch, CCVP, CCNA, CCDA
1965 Greenspring Drive
Timonium, MD 21093
support at heliontechnologies.com<mailto:support at heliontechnologies.com>
(p) (410) 252-8830
(F) (443) 541-1593

Visit us at www.heliontechnologies.com<http://www.heliontechnologies.com/>
Support Issue? Email support at heliontechnologies.com<mailto:support at heliontechnologies.com> for fast assistance!

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

Hello,

This has been my normal experience with AT&T for about the last three years.

Thanks,

James Buchanan | Senior Network Engineer | South Region | Presidio Networked Solutions
12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | jbuchanan at presidio.com<mailto:jbuchanan at ctiusa.com>
D: 615-866-5729 | F: 615-866-5781 | www.presidio.com<http://www.presidio.com> <http://www.presidio.com>
CCIE #25863, Voice

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 10: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<mailto:nikola at att.net>
-------------------------------------------

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