No announcement yet.
  • Filter
  • Time
  • Show
Clear All
new posts

  • Simple and easy to follow directions

    I have kinda asked this question before: Has anyone come up with a simple procedure to install and get running a [I]single site like a Small Business Edition?[I]

    When I went to I&M training I came back knowing a little less than I did before I went. Too much time on the whiz-bang and too little on how to set up a single system.

    We keep making stupid choices in how things are supposed to work. How to get the right phones to ring, how to log in and out of a group. Simple things.

    Has any one come up with a clear cut "this is the minimum to make a ShoreTel work?" I'd love to see ShoreTel devote the 5 days to this instead of touching on many other things.

    We took the admin course a couple of weeks ago and that helped.

    Any thoughts?

  • #2
    I guess you start with really good data collection. Find out Exactly how the system is suppose to work for the customer.
    Figure out a workable dial plan (I like 50X for Hunt groups and 55x for WG. For multi sites I precedethese with a Site number (4 digit numbering)
    Next Build the site,
    Then trunks,
    Then Trunkgroups
    Build Class of services next, assigning pertinent trunk groups.
    Build all your users,
    Then you can start assigning people to groups,
    Finally Set up any Auto Attendants.

    Somewhere in there decide on schedules and start assigning them.

    Every install is different, and I have yet to do a square install. The last one I did I had to build a complete different schedule, AA, and Hunt groups Just for tax season. then throw in some error messages just because customers where use to dialing 2 digits.

    Hope this hel-s with some "what if questions" posted here and some practice you will be able to throw these together without too much effort.

    As far as phone systems go this is the 2nd most limited large phone system I have ever dealt with (ESI being the most limited). That being said, limited is not always a bad thing. The manual for the NEC Aspire is over 1500 pages, has several 10000 entries. And has supplememnt manuals for VOIP, ACD, Networking. But you can change pretty much Anything.

    All systems follow the same flow as above.


    • #3
      Don't forget to get detailed maps/information about their network. I understand you said one site, but we have one site, with roaming profiles, two data vlans and the voice vlan ALL OF WHICH weren't asked about. We got the "here are all the bells and whistles when do we start the install?" Then, as they discovered our details, they scurried to find work you can see from my trail of posts on this site.

      If I were running an install company, I would spend one day with an engineer on site just to have our own idea of what is happening. Some smaller companies don't even know what is happening if they have outsourced most of their IT.


      • #4
        Here's how I do it:
        1. I spend an hour or 2 going over the features of the system. I then start to hammer out some call flow basics. This is done weeks before the install.
        2. Once the equipment arrives, I make sure I have Static IP addresses assigned, and I load 2003 server, and configure the switches with there IP information. Obviously, by this point, I have discussed VLANS, and IP Requirements.
        3. After I load the ST software, I begin with the basics: I add the licenses. Set up the Contact info, etc.
        4. Next, Sites, trunks, trunk groups, and then switches.
        5. Now is a good time to set up schedules
        6. Class of Service, Users, then Hunt groups and workgroups.
        7. Auto-attendants
        8. Other misc items.

        Personally, if you get the chance, you should take the system engineer class in Cali. I loved it. It really gets into the meat and potatoes of teh system.