Ha! Spoke too soon. Disclaimer: Old voice guy who maybe doesn't know what he doesn't know. In the past month, many problems have come out of the woodwork. The ShoreTel system itself seems pretty stable, admin is a breeze, users are happy with that part of it. However, other WAN 'shortcomings' become very apparent when voice is added to the stream, and to the users it looks like phone system problems. Tools to monitor are costly; Troubleshooting can be tricky due to the 'spiky' nature of WAN traffic; QoS might work, but doesn't appear to work too well in a busy environment (hence the phrase "no substitution for bandwidth"). We've (temporarily) put a traffic shaper into the loop to overcome QoS' limitations while we evaluate/discuss/decide. (I anticipate having to buy lots more bandwidth to support VoIP.) Sorry, this isn't meant to be a blog -- just don't go into VoIP without being ready to spend $$$ up front, during, after -- it's not the panacea of cost savings that VoIP marketing departments suggest it is. (We thought we were ready). More later, if you're interested......
