<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>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.<br><br>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:<br><ul><li>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</li><li>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</li></ul>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.<br><br>*sigh*<br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><br><br>----- Original Message -----<br>From: "Mac GroupStudy" <mac.groupstudy@gmail.com><br>To: "Neal Haas" <nhaas@co.fresno.ca.us><br>Cc: cisco-voip@puck.nether.net<br>Sent: Thursday, July 22, 2010 5:14:16 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] OT: AT&T circuit in Florida<br><br>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.<br>
<br><div class="gmail_quote">On Thu, Jul 22, 2010 at 3:21 PM, Haas, Neal <span dir="ltr"><<a href="mailto:nhaas@co.fresno.ca.us" target="_blank">nhaas@co.fresno.ca.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div lang="EN-US"><div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">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.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p><div><div style="border-right: medium none; border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> Fuermann, Jason [mailto:<a href="mailto:JBF005@shsu.edu" target="_blank">JBF005@shsu.edu</a>] <br><b>Sent:</b> Thursday, July 22, 2010 11:49 AM<br>
<b>To:</b> 'Edward Beheler'; Haas, Neal; '<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>'<br><b>Subject:</b> RE: [cisco-voip] OT: AT&T circuit in Florida</span></p>
</div></div><p class="MsoNormal"> </p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">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. </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">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.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p><div><div style="border-right: medium none; border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; padding: 3pt 0in 0in;"><p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Edward Beheler<br>
<b>Sent:</b> Thursday, July 22, 2010 1:30 PM<br><b>To:</b> 'Haas, Neal'; '<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>'<br><b>Subject:</b> Re: [cisco-voip] OT: AT&T circuit in Florida</span></p>
</div></div><p class="MsoNormal"> </p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">AHAHAHAHAHAHAHAHAHAHAHAHAHAHA AAAGHAHAH SO DID I!</span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<div><div style="border-right: medium none; border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; padding: 3pt 0in 0in;"><p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> Haas, Neal [mailto:<a href="mailto:nhaas@co.fresno.ca.us" target="_blank">nhaas@co.fresno.ca.us</a>] <br>
<b>Sent:</b> Thursday, July 22, 2010 12:10 PM<br><b>To:</b> Edward Beheler; '<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>'<br><b>Subject:</b> RE: [cisco-voip] OT: AT&T circuit in Florida</span></p>
</div></div><p class="MsoNormal"> </p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">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.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p><div><p class="MsoNormal" style=""><span style="font-size: 10pt; font-family: "Courier New"; color: rgb(31, 73, 125);">Neal Haas</span></p>
</div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p><div><div style="border-right: medium none; border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; padding: 3pt 0in 0in;"><p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Edward Beheler<br>
<b>Sent:</b> Thursday, July 22, 2010 9:02 AM<br><b>To:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><b>Subject:</b> Re: [cisco-voip] OT: AT&T circuit in Florida</span></p>
</div></div><p class="MsoNormal"> </p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">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.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">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.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">“Can you hear me now?”</span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">“We’re sorry, you have reached a number that is disconnected or no longer in service.”</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">/rant</span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p><div><div style="border-right: medium none; border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; padding: 3pt 0in 0in;"><p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Bill<br>
<b>Sent:</b> Thursday, July 22, 2010 11:43 AM<br><b>To:</b> 'Ted Nugent'; <a href="mailto:nikola@att.net" target="_blank">nikola@att.net</a></span></p><div class="im"><br><b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
</div><b>Subject:</b> Re: [cisco-voip] OT: AT&T circuit in Florida<p></p></div></div><p class="MsoNormal"> </p><p class="MsoNormal"><span style="font-size: 10pt; color: navy;">Second the motion on porting early. I have had them do that to me multiple times. </span></p>
<p class="MsoNormal"><span style="font-size: 10pt; color: navy;"> </span></p><div><div class="MsoNormal" style="text-align: center;" align="center"><hr align="center" width="100%" size="2"></div><p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Ted Nugent<br>
<b>Sent:</b> Thursday, July 22, 2010 10:35 AM<br><b>To:</b> <a href="mailto:nikola@att.net" target="_blank">nikola@att.net</a></span></p><div class="im"><br><b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
</div><b>Subject:</b> Re: [cisco-voip] OT: AT&T circuit in Florida<p></p></div><p class="MsoNormal"> </p><p class="MsoNormal">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. </p>
<div><p class="MsoNormal">Your only option really is to raise holy hell with their AM and see if they can get it escalated.</p></div><div><p class="MsoNormal" style="margin-bottom: 12pt;"> </p><div><p class="MsoNormal">On Thu, Jul 22, 2010 at 11:25 AM, Nikola Stojsin <<a href="mailto:nikolas@networkmakers.com" target="_blank">nikolas@networkmakers.com</a>> wrote:</p>
<div><div><p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Hello guys –</span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);">First of all, my apologies – this is quite OT; I just want to make sure that the information we are getting is correct.</span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);">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. </span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);">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. </span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);">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?</span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Needless to say, all help/input/suggestions will be greatly appreciated!</span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Thank you,</span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Nikola</span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">-------------------------------------------</span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Nikola Stojsin</span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);">PhD CCIE #12888</span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">President</span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><a href="mailto:nikola@att.net" target="_blank">nikola@att.net</a></span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);">-------------------------------------------</span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p></div></div><div class="im"><p class="MsoNormal" style="margin-bottom: 12pt;"><br>_______________________________________________<br>cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></p>
</div></div><p class="MsoNormal"> </p></div></div></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>
<br>_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
</div></body></html>