[VoiceOps] Activation Timing

[Mike Hammett]

So then for you, the risks aren't worth the rewards in rescheduling ports? 




----- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 



Midwest Internet Exchange 
http://www.midwest-ix.com 



----- Original Message -----

From: "Shawn L" <shawn at rmrf.us> 
To: "Mike Hammett" <voiceops at ics-il.net> 
Cc: "VoiceOps" <voiceops at voiceops.org> 
Sent: Friday, April 29, 2022 2:44:09 PM 
Subject: Re: [VoiceOps] Activation Timing 


Just my personal preference, but I like to wait until I can see our equipment at the far-end (verified connectivity) before doing the actual scheduling of the port. I know you can amend the port and re-schedule, but there's a lot of other things that can go wrong during the port -- provider not actually removing the number from their switch, etc. (I'm looking at you Spectrum) that I don't need to create additional complications. 


shawn 


On Fri, Apr 29, 2022 at 3:22 PM Mike Hammett < voiceops at ics-il.net > wrote: 




I'm trying to develop some new rules for dates we choose for porting. 


We have to build outside plant for most customers to accommodate their turn-up. The customers generally don't understand why the phone isn't alive when the tech is on-scene, but the tech has to go on-scene to build the infrastructure. 




Is it reasonable to choose a port date that seems like it would work, then bump the activation day by day if OSP has encountered any issues? 


I would like to think that by not *activating* the port and rescheduling it for the next day, everything would still work correctly, but I'd rather be right than lucky. 




----- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 



Midwest Internet Exchange 
http://www.midwest-ix.com 



_______________________________________________ 
VoiceOps mailing list 
VoiceOps at voiceops.org 
https://puck.nether.net/mailman/listinfo/voiceops 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20220502/d220b646/attachment.htm>