Huge list of enhancements...

[jlear]

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.

[mutilities]

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

[MiJaMu]

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.

[jcogorno]

Originally Posted by Charles

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).