Announcement

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

  • Huge list of enhancements...

    This is the list I sent to Shoretel...

    1. Have the Shoretel Director show the current build and version at the top of the page somewhere after you are logged in. Typical scenario when I call in is that I already have the director open and then have to exit and go back to the log on page in order to supply tech support my version and build info.

    2. Have a link inside Shoretel Director that launches a remote session. This would just streamline the process and would mean less time that your reps need to spend on the phone waiting for a remote session to be established

    3. Have preferences inside the Shoretel Director. Example would be, on the individual users section, I always want to display all users. I do not like it that it always defaults to 25 users at a time

    4. Have a spot somewhere in the trunk groups to store trunk provider information. This would be very beneficial to have the information right there when you are troubleshooting. This would include :
    a. Company Name
    b. Contact
    c. Phone number
    d. Circuit ID

    5. Integrate with Active Directory. You may have to extend the schema a bit, but most of the information you store in Shoretel, has a home also in Active Directory. With Exchange so tightly integrated with AD, I can see many ways it could benefit Shoretel down the line.

    6. Develop a tool that enables us to simulate call flow and different scenarios. The tool would basically collect all the information from your Shoretel system and create a demo environment on a server with “virtual” servers and switches simulating your production environment. It would be a huge help for us and I believe would reduce call volume in your TAC. It would be great for testing disaster recovery plans, testing new call flows and running “What if?” scenarios. Some scenarios that it would be useful for include:
    a. Call flow based on what hour of the day it is. The tool would let you plug in a fictional time of day. You could then select if a call comes in on this line, at this fictional time of day and is destined for this workgroup, show me how the call travels and where it ends up.
    b. What would happen if a call comes in destined for a workgroup and all agents are logged out? What greetings will the caller hear? Will the call eventually be transferred to someone outside of the workgroup?
    c. What happens if a call comes in destined for a remote location and a WAN link is down? Did PSTN failover work properly?
    d. We have 4 PRI’s. 2 come into our main branch and 2 come into a remote location. They are setup as 46 channels each. We are setup with our phone provider so that if both PRI’s are down at one location, the call is transferred to the other PRI at our remote location. What happens when calls come into that remote location? Are they directed to the correct auto attendant?
    e. What happens if the HQ server is down?
    f. What happens if a DVM is down?

    7. Develop a way for the IP phones to display some type of name on your DHCP server when they grab an IP address.. It could either be the MAC address of the phone or just “Shoretel IP Phone”. Currently, if we look at our DHCP server for leased addresses, Shoretel phones show up with no description.

    8. Develop a report or the ability to see how many calls a user on the system receives. You can run a report on how many calls a user receives or makes, but it does not include calls that went to voicemail. We have several users that receive a large number of calls. Most of them end up going to voicemail. When we run a report on user activity, we are not seeing how many calls were sent to that extension. We are seeing how many calls were answered or made by that user. There is no way to capture how many calls went to voicemail. This functionality is there at the workgroup level, but not for an individual user. In this scenario, IT was asked to show management how many calls and voicemails were going to user. We were unable to do that. Seems simple, but functionality is not there.

    9. We run in a Citrix environment. By default, the Personal Call Manager history is saved to %system root%\documents and settings\user\application data\shoretel client...... At any day, a user could be on a different Citrix server than they were the day before. This means that their history from the previous day will be on a different server. It would be nice to be able to specify on the PCM that history is to be stored at a specific location.. \\networkserver\directory

    10. The new mobile call manager is great. It should be expanded to run on Windows based devices. Not only select Blackberry devices.

    11. Give the ability to trace a call. There is no way for an administrator to see what happened to a call. I would like to be able to see that a call came in, got Auto Attendant A, the caller hit 3, went to this Q, sat there this long, pressed 0 and went to the operator and was then transferred to a supervisor and got the supervisors voicemail.

    12. Ability to install server and DVM’s on a virtual machine.

    13. Build new, or partner with a better ECC provider. Easy Run’s product is light years behind ShoreTel’s as far as manageability goes. Examples of issues we have include:



    a. Poor reporting. I will not go into detail here. I am sure you are aware of the shortcoming. Let me know if you need me to elaborate.
    b. The ability to tag a call as a certain type. We would like to have the ability for a call center rep to plug in a code after a call based on what type of call it was. This would be similar to a wrap code. This would allow us to generate a report that shows, typically, this type of call takes 5 minutes and this type of call take 2 minutes etc.
    c. If a call gets transferred to a Queue in the ECC and then back to the base Shoretel system, we have no way to trace that call as it flows through the system.
    d. Since we are a small call center (7 agents), the ECC is overkill for us. It is difficult to configure and we never feel confident making changes to it.
    e. The call scripting tool is difficult to use and not user friendly at all.

    14. Improve the “dashboard” available for supervisors to monitor workgroup activity. We purchased the ECC because we wanted to do some IVR functions and wanted call overflow and interflow for our Customer Service Queue. We would be perfectly happy moving our call flow back to a workgroup instead of using the ECC for call queuing. Before we can do that, we need improvements made in the monitoring or a workgroup status. We would like to have the ability to see the TSF of the workgroup. We are a small contact center (7 agents). We typically only have 4 reps on the phone at a time. This is because of breaks and offline processing that they do. When our TSF drops, we typically take reps off processing and put them back on the phone. The current workgroup monitor does not display TSF because there is no TSF setting for workgroups like there is in the ECC.

    15. Develop a user forum on the Shoretel website. This could be a place where end users could exchange ideas and help each other resolve issues. This has worked well for VMware, Citrix and most other companies.

    16. Host regional user group meetings. This could be a quarterly meeting where Shoretel Administrators and local Shoretel reps get together. Details of new releases could be presented. Third party vendors that have solutions that work with Shoretel could also do presentations – Callrex etc..

    17. Ability to sign up for build update notifications. It seem like Shoretel is releasing build updates almost monthly. It would be nice to get a brief e-mail explaining the highlights of the release.

    18. Slow down the release updates. Go to a quarterly release schedule. It would give Shoretel more time to perform thorough testing on your releases.

    19. Don’t charge us for additional workgroup call reports. These are simple Crystal Reports. It seems ridiculous to say “If you really want detailed information from your phone system that you invested over $100,000 into, buy these reports that took us 10 minutes to make”

    20. On call history on phone, show internal callers by name not extension #.

    21. Make a user friendly way to adjust the volume on a per user basis beyond what is available with the volume control on the phone. The only way I know how to is to edit some file that gets downloaded to the phone. This should be a feature that is available to end users through the PCM. If not, it should be an easy adjustment that can be made on a per phone basis through the Shoreware Director. We have several end users that have hearing difficulty where this has come into play.

    22. Make trunk line weighing an easier option to configure. Currently you need to go in to the Shoreware Director with some special key combination and then use -5 or -10. It is cryptic and should be easier to configure.


    23. Make a printable system directory. People still like paper list hanging from their cube for some reason.

    24. When creating a new user, if you copy a user, it would be nice if the e-mail address would not copy over.

    25. Provide a data dictionary of how the database fields link so customers can easily create their own custom reports.

  • #2
    Good grief that is a long list

    Comment


    • #3
      By the way, some of your items are already on the roadmap.


      Virtualization is not going to happen any time soon. This is not a Shoretel issue but rather an issue with the way virtualization can gaurantee timing for highly sensitive applications like voice.

      Shoretel has engaged VMWare to try to work around it on their ESX platform and VMWare said no go.

      Comment


      • #4
        1. Have the Shoretel Director show the current build and version at the top of the page somewhere after you are logged in. Typical scenario when I call in is that I already have the director open and then have to exit and go back to the log on page in order to supply tech support my version and build info.

        Not a bad idea, but it is also available if you goto QUICK LOOK, then select the HQ server on the right, it's at the bottom of the page.

        7. Develop a way for the IP phones to display some type of name on your DHCP server when they grab an IP address.. It could either be the MAC address of the phone or just “Shoretel IP Phone”. Currently, if we look at our DHCP server for leased addresses, Shoretel phones show up with no description.

        You are correct. Even knowing the MAC address 00-10-49-xx-xx-xx is Shoretel, it could be easier. I always thought it would be nice if they would add a vendor code for DHCP.

        8. Develop a report or the ability to see how many calls a user on the system receives. You can run a report on how many calls a user receives or makes, but it does not include calls that went to voicemail.

        I do believe you can write a report that includes 3 of voicemails. Don't quote me on that.

        11. Give the ability to trace a call.

        I believe this would be (or close to) a Cradle to grave report. We have one written for version 6.0, but in 7.0, teh DB changed to MySQL, so it broke.

        13. Build new, or partner with a better ECC provider.

        I believe they have approved other CC providers.

        15. Develop a user forum on the Shoretel website. This could be a place where end users could exchange ideas and help each other resolve issues. This has worked well for VMware, Citrix and most other companies.

        They could always buy this site...

        18. Slow down the release updates. Go to a quarterly release schedule. It would give Shoretel more time to perform thorough testing on your releases.

        Let's be clear here. There are release updates and Build updates. release updates would be 6.0, 6.1, 7.0, 7.5, 8.0, etc. These are about every 6-9 months. Build updates happen alot more frequently. It's not required for every customer to have every Build update. If the customer has no issues with the current Build, we do not update them till a new feature release. If its not broke, don't fix it.

        I didn't answer them all, but like Chris mentioned, some are already on the roadmap.

        good list though.

        Comment


        • #5
          Long list

          It is a long list. Don't get me wrong though. I / We love our Shoretel system!! Most of the items in my list would be nice to haves. I sent this list about 6 months ago to Shoretel. We run 6.1. We needed to get everything up to 2003 before we could upgrade to 7 or 7.5.

          I just saw an e-mail about field trials of 8.0. I am excited..

          Comment


          • #6
            I totally agree on numbers 8, 11 and 19 (Especially #19). I harped on the "Enhanced ShoreTel Reports" that ShoreTel up-sells about a year ago on the Yahoo group and everyone said I should just write my own reports. Well, as you can see from Charles' post, when you write your own reports, a version upgrade can break them...ShoreTel should write the reports and provide them at "no additional cost" with the base system.

            I agree with number 4 also, but to expand on that, I think there should be a comment text box on nearly every configuration page in director. This allows you to easily document the reasons for some strange configurations, such as why this PRI has priority over that PRI but does not allow local calls, or why this route point forwards to another route point before 8am, but to a workgroup after 8am...

            Comment


            • #7
              For the Phone ID supplied in DHCP - what spec should ST follow e.g. Option 61 as defined in the RFC for DHCP ?

              Let us know so we can look into this.

              Thanks

              Comment


              • #8
                Originally posted by DRencken
                For the Phone ID supplied in DHCP - what spec should ST follow e.g. Option 61 as defined in the RFC for DHCP ?

                Let us know so we can look into this.

                Thanks
                I do believe that is it.
                Example. Network is a Class B private scheme. All computers are in the 172.20.1.x/16 range. They want all the phones in the 172.20.2.x/16 range. Being that they are on the same subnet, there currently is no way to issues IP addresses via DHCP to accomplish this. If the phones issues a client ID, then DHCP could make a reservation based off of that, allowing the phones to be in the proper range.

                61 Client-identifier.RFC 1533, RFC 2132, RFC 4361

                Comment


                • #9
                  Originally posted by chadd39
                  9. We run in a Citrix environment. By default, the Personal Call Manager history is saved to %system root%\documents and settings\user\application data\shoretel client...... At any day, a user could be on a different Citrix server than they were the day before. This means that their history from the previous day will be on a different server. It would be nice to be able to specify on the PCM that history is to be stored at a specific location.. \\networkserver\directory

                  Use roaming TS profiles, they do work.

                  Comment


                  • #10
                    We azre using Roaming profiles.

                    Are you sating you use roaming profiles and this is not a problem for you in your Citrix enviroment?

                    Thanks

                    Comment


                    • #11
                      Originally posted by Charles
                      I do believe that is it.
                      Example. Network is a Class B private scheme. All computers are in the 172.20.1.x/16 range. They want all the phones in the 172.20.2.x/16 range. Being that they are on the same subnet, there currently is no way to issues IP addresses via DHCP to accomplish this. If the phones issues a client ID, then DHCP could make a reservation based off of that, allowing the phones to be in the proper range.

                      61 Client-identifier.RFC 1533, RFC 2132, RFC 4361
                      Option 60 would be nice as well which would allow a different set of DHCP options to be sent to the phones compared to other devices. This is useful where 2 different vendors use the same boot option (e.g. 156) but look for different data in it.

                      Comment


                      • #12
                        11. Give the ability to trace a call. There is no way for an administrator to see what happened to a call. I would like to be able to see that a call came in, got Auto Attendant A, the caller hit 3, went to this Q, sat there this long, pressed 0 and went to the operator and was then transferred to a supervisor and got the supervisors voicemail.

                        The AA Log is in the shoreline data\logs\vmail-{date}.log file for the aa see below.

                        use this query to trace calls if you using Version 7+ with mysql backend

                        select ct.CallTableID,ct.connecttime,ct.disconnecttime,ct .partyid,ct.partyidname,ct.ctrlpartyid,ct.ctrlpart yidname,
                        time(ct.talktime) as 'Talk Time',time(ct.holdtime) as 'Hold Time',time(ct.ringtime),ct.trunkdirection,ct.portn ame from connect as ct where ct.CallTableID
                        IN (select CallTableID from connect where partyid like '%put your caller id here')
                        order by ct.CallTableID,ct.connecttime,ct.disconnecttime

                        Look for:

                        16:42:04.581 [3920] PM: ***** Start new call 0x16abd VMTID 4012 Version 12.6.2405.0

                        16:42:04.581 [4844] PM: Call offering han 0x16abd
                        16:42:04.581 [3920] PM: Connecected ID flags 0xc
                        16:42:04.581 [3920] PM: Start answer call 0x16abd
                        16:42:04.581 [4844] PM: Call connected han 0x16abd
                        16:42:04.596 [3920] PM: OpenMediaChannels ID [0,0] Media Handle 015884B0 CallerID +1423xxxxxxx
                        16:42:04.596 [3920] PM: ID's Call 0x332c2b69 Caller +1423xxxxxxx Called 700 Conn +1423xxxxxxx
                        16:42:04.596 [3920] PM: Call GUID 00070000-4aa0-4816-6f69-00104903ad9c
                        16:42:04.596 [3920] PM: Call han 0x16abd, digits DID () DNIS (4121) DNIS mbx ()
                        16:42:05.424 [4844] PM: Digit detected han 0x16abd ------> 1
                        16:42:05.784 [4012] VM: Process auto attendant call, tapi handle 0x16abd, PMTID 3920
                        16:42:05.784 [4012] VM: Process DNIS digits 4121
                        16:42:05.784 [3920] PM: Set original menu 751
                        16:42:05.799 [4012] VM: Extension prefix saved
                        16:42:05.799 [ 424] MS: Mail server open mailbox 751
                        16:42:05.799 [4012] VM: Set call language to 1
                        16:42:05.799 [3920] PM: Playfile (st=0 m=0 h=0 l=0) D:\Shoreline Data\Vms\SHORETEL\751\Prompt60.wav
                        16:42:05.799 [4012] VM: Process menu steps
                        16:42:05.799 [3920] PM: Collect 1 digits using timeout 5000
                        16:42:05.799 [3920] PM: Collect 2 digits using timeout 1200
                        16:42:06.253 [4844] PM: Digit detected han 0x16abd ------> 2
                        16:42:06.737 [4844] PM: Digit detected han 0x16abd ------> 1
                        16:42:06.737 [4012] VM: Call transfer state extn 121 extn list ID 0
                        16:42:06.737 [4012] VM: Transfer call to 121
                        16:42:06.737 [3920] PM: Play phrase 320 lang 1
                        16:42:08.800 [3920] PM: Start line transfer to 121 User group 0 COSCPID 0
                        16:42:08.800 [4844] PM: Line call state 0x2000 han 0x16abd
                        16:42:08.878 [4844] PM: Call went idle han 0x16abd
                        16:42:08.878 [4012] VM: Enter wait for call
                        16:42:08.878 [3920] PM: Port Manager wait for call 1
                        16:42:08.878 [3920] PM: (MediaOpenClose) Close media handle 0x15884b0
                        16:42:08.878 [3920] PM: End call main 0x16abd
                        16:42:08.878 [3920] PM: 0 of 22 call threads are in use
                        16:42:11.644 [4844] PM: New call han 0x16107
                        Last edited by mutilities; 07-01-2008, 10:27 AM.

                        Comment


                        • #13
                          I believe #25 (the data dictionary) is available if you buy the developer subscription ($100/year).

                          I haven't coughed up the money yet to check it out.

                          I would add the following to your list: Provide a list of variable that can be accessed using the extremely useful, yet woefully underused "Invoke URL" feature of the call manager toolbar. Passing the caller id number (or other data) via URL makes integrating with a CRM easy, but ShoreTel won't reveal the instructions.

                          Comment


                          • #14
                            Originally posted by Charles View Post
                            1. Have the Shoretel Director show the current build and version at the top of the page somewhere after you are logged in. Typical scenario when I call in is that I already have the director open and then have to exit and go back to the log on page in order to supply tech support my version and build info.

                            Not a bad idea, but it is also available if you goto QUICK LOOK, then select the HQ server on the right, it's at the bottom of the page.

                            7. Develop a way for the IP phones to display some type of name on your DHCP server when they grab an IP address.. It could either be the MAC address of the phone or just “Shoretel IP Phone”. Currently, if we look at our DHCP server for leased addresses, Shoretel phones show up with no description.

                            You are correct. Even knowing the MAC address 00-10-49-xx-xx-xx is Shoretel, it could be easier. I always thought it would be nice if they would add a vendor code for DHCP.

                            8. Develop a report or the ability to see how many calls a user on the system receives. You can run a report on how many calls a user receives or makes, but it does not include calls that went to voicemail.

                            I do believe you can write a report that includes 3 of voicemails. Don't quote me on that.

                            11. Give the ability to trace a call.

                            I believe this would be (or close to) a Cradle to grave report. We have one written for version 6.0, but in 7.0, teh DB changed to MySQL, so it broke.

                            13. Build new, or partner with a better ECC provider.

                            I believe they have approved other CC providers.

                            15. Develop a user forum on the Shoretel website. This could be a place where end users could exchange ideas and help each other resolve issues. This has worked well for VMware, Citrix and most other companies.

                            They could always buy this site...

                            18. Slow down the release updates. Go to a quarterly release schedule. It would give Shoretel more time to perform thorough testing on your releases.

                            Let's be clear here. There are release updates and Build updates. release updates would be 6.0, 6.1, 7.0, 7.5, 8.0, etc. These are about every 6-9 months. Build updates happen alot more frequently. It's not required for every customer to have every Build update. If the customer has no issues with the current Build, we do not update them till a new feature release. If its not broke, don't fix it.

                            I didn't answer them all, but like Chris mentioned, some are already on the roadmap.

                            good list though.
                            Charles,

                            What about creating rules for incoming calls using PCM (kinda like in Outlook)? Certain caller IDs or Blocked numbers will go straight to a person's voice mail while others can ring through. Can also ring a different ring tone (if it is an emergency or "special" caller).

                            Comment


                            • #15
                              Originally posted by cburgy View Post
                              Shoretel has engaged VMWare to try to work around it on their ESX platform and VMWare said no go.

                              I'm confused here, since I've been able to get realtime applications to perform in Vmware almost without exception. And when using a VM more as a Robust platform to move guests around you are pretty much guaranteed you will get the ticks you need as long as you're 1:1 on your allocations and don't oversubscribe.

                              Keeping an eye on your ready wait counts and watching for thrashing (normal esx performance stuff) and you can get it to within 4-5% of a comparable non-virtual system. You've gotta really dedicate a physical connection to this, since nobody has really got layer 2/3 QoS down at the VM level. (unless you pay for a virtual switch/module) At that point you use the VM platform as a medium to move around your application between redundant systems. And any other mission critical, highly available, realtime applications you have can ride on the same infrastructure as long as you keep to your CPU assignments. Try to keep to optimized CPU counts for your systems. If you only use 2 CPU's at >50% give the system 1 processor, it performs better.

                              Of course all of the above is specific to VMware, and not at all supported by Shoretel. We did run it on VMware (Shoretel 8) for about a year, and did not experience performance related issues. (Dcom issues were a whole 'nother thing.)

                              Comment

                              Working...
                              X