Activation Timing
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
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
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
No. At least in our case, there are so many things that can go wrong both with the installation (fiber you were certain was spliced actually isn't, machinery breaking down, etc.) that it's easier to just make it a 2-step process. There are times when we'll just go ahead and do all of it in one trip, but I prefer to do it in 2. Less stress on everyone involved. Shawn On Mon, May 2, 2022 at 3:10 PM Mike Hammett <voiceops at ics-il.net> wrote:
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
------------------------------ *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
When we are installing a new fiber connection, we do not schedule until the customer drop (not the ONT) is in and spliced to the mainline fiber. ONT installation and running a copper ethernet data run is done on the day of install/activation. On Fri, Apr 29, 2022 at 12:50 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
-- Jeff Shultz Central Office Technician SCTC (503) 769-2125 Go Big Ask for Gig -- Like us on Social Media for News, Promotions, and other information!! ?? <https://www.facebook.com/SCTCWEB/>? ? ? <https://www.instagram.com/sctc_sctc/>? ? ? <https://www.yelp.com/biz/sctc-stayton-3>? ? ? <https://www.youtube.com/c/sctcvideos> _**** This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ****_
participants (3)
-
jeffshultz＠sctcweb.com -
shawn＠rmrf.us -
voiceops＠ics-il.net