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

Thu Jul 22 18:04:53 EDT 2010

When I was migrating from one carrier to another (physically different PRIs), I specifically asked for as much technical detail as possible so I could communicate the project to others. 

Well, one thing they neglected to tell me (and something I didn't know) is that when they port numbers from one carrier to another, it's done in two steps: 

    • first, the numbers are entered in the new carriers switch and broadcast to the other switches so people who call one of the ported numbers are directed to the correct switch 
    • second, the switch which had the numbers in the first place has to be told to stop using the local route and using the off-net routing tables to send to the new carrier 

Well, here I am telling everyone things are complete and when we go to test (of course, using lines on the local switch) nothing is working. 

*sigh* 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 

----- Original Message ----- 
From: "Mac GroupStudy" <mac.groupstudy at gmail.com> 
To: "Neal Haas" <nhaas at co.fresno.ca.us> 
Cc: cisco-voip at puck.nether.net 
Sent: Thursday, July 22, 2010 5:14:16 PM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] OT: AT&T circuit in Florida 

Maybe sometime through new technologies such as SIP and other IP based solutions we will finally get away from that holier than thou mentality that seems to follow providers. When I did deployments out of all of the things that could go wrong you could almost always expect something would go wrong when numbers were ported or connections were swapped around. Even when you are troubleshooting with them you know about what to expect. In fact, I teach some low level IP/Voice classes and when a student has a problem and suspects it is on my side (simulated provider) I jokingly say "it looks good on my end" and everyone in the class always "gets it". They too have dealt with that level of support far too long. 

On Thu, Jul 22, 2010 at 3:21 PM, Haas, Neal < nhaas at co.fresno.ca.us > wrote: 

I like that I know more than the ATT people I have two sites each on a separate CO’s (other side of town) and I wanted our new Prefix to failover to the alternate site (Which we were told that we could do without going to SIP). They setup and tested, yea all 10,000 DID’s fail over to the main BTN of the trunk group. Their solution was to have that BTN on a phone and that person could transfer the calls. My reply was “10,000 phone numbers, 1 person answering them, AT&T will provide the1 person to do so right???” No reply, they THINK they have resolved the issue I still need to test it. I am not sure if AT&T can do a 1 to 1 failover on a trunk outage. They said they can, I’ll not hold my breath, it’s only been 7 months of trying and failing. 

From: Fuermann, Jason [mailto: JBF005 at shsu.edu ] 
Sent: Thursday, July 22, 2010 11:49 AM 
To: 'Edward Beheler'; Haas, Neal; ' cisco-voip at puck.nether.net ' 
Subject: RE: [cisco-voip] OT: AT&T circuit in Florida 

That’s nothing, we went 2 weeks without 911 because after our port AT&T swore we never had PSALI. Supposedly they had somebody investigating it 24/7 for those 2 weeks. 

The only thing I can suggest is demand to be on the patch with the technician who is doing the port. I think AT&T, Verizon, ect. have like 12 people who actually know what they’re doing in the SS7 switches. Learn the lingo so that you sound like a field tech and can get transferred to one of them. 

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 1:30 PM 
To: 'Haas, Neal'; ' cisco-voip at puck.nether.net ' 
Subject: Re: [cisco-voip] OT: AT&T circuit in Florida 

AHAHAHAHAHAHAHAHAHAHAHAHAHAHA AAAGHAHAH SO DID I! 

From: Haas, Neal [mailto: nhaas at co.fresno.ca.us ] 
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 

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

_______________________________________________ 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/a3936e07/attachment.html>