Announcement

Collapse

Welcome to ShoreTelForums.com

Welcome to ShoreTelForums.com!

This site was created as a place to share stories, tips, and troubleshooting help with ShoreTel/Mitel systems. ShoreTel/Mitel is obviously the MOST exciting VoiP platform on the market right now, and we realized there was no centralized place to discuss this platform, but now there is. Please feel free to join and share your experiences.

Please Note: This site IS NOT owned, funded, or managed by ShoreTel/Mitel, Inc. although you may find ShoreTel/Mitel employees sharing there experiences and expertise. If you would like more information on ShoreTel/Mitel systems, contact BTX at [email protected]

As always please support the advertisers that help support our site.

Thank You,
BTX
See more
See less
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Installation Checklist

    Has anyone came up with an installation checklist? I am looking for something that shows a logical order for programming and installation.

  • #2
    Hey Smith, have you seen Control Point? It is a good starting point, a really good one.

    Comment


    • #3
      What type of 'Installation' Checklist?
      Complete system project management (Hardware planning, etc)? or just Shoreware Director (cheat sheet on quickest way to program a system)?

      Charles

      Comment


      • #4
        I would like a cheat sheet on quickest and best way to program a system. Thanks

        Comment


        • #5
          Installation Checklist

          Another thought about this. It might save a lot of grief if, for every installation where we are replacing a legacy system, we created a feature map that showed the customer how the legacy system features map to the ShoreTel system.

          Of course, this is primarily important were features are different or operate differently, like transferring a call.

          Also, just replicating the legacy system architecture and functionality will not always take advantage of the ShoreTel system's best functions.

          Comment


          • #6
            Originally posted by BenTDM
            Another thought about this. It might save a lot of grief if, for every installation where we are replacing a legacy system, we created a feature map that showed the customer how the legacy system features map to the ShoreTel system.

            Of course, this is primarily important were features are different or operate differently, like transferring a call.

            Also, just replicating the legacy system architecture and functionality will not always take advantage of the ShoreTel system's best functions.
            I'm a Network Engineer, not a traditional PBX person...so this would be of no use to me (I don't know a thing about legacy PBX's). I usually ask my customers in a Project Planning meeting, 'what they would like', rather then 'what do you currently have'. Then I try and find a way to make the Shoretel system do what they want (or as close as possible).

            Comment


            • #7
              Originally posted by Charles
              I'm a Network Engineer, not a traditional PBX person...so this would be of no use to me (I don't know a thing about legacy PBX's). I usually ask my customers in a Project Planning meeting, 'what they would like', rather then 'what do you currently have'. Then I try and find a way to make the Shoretel system do what they want (or as close as possible).
              Same here but my experience is mostly project management and applications. I recently took the cert course and a few days later was installing my first system. A basic pre-install checklist would have come in handy, so now I'm developing one of my own.

              Comment

              Working...
              X
              😀
              🥰
              🤢
              😎
              😡
              👍
              👎