Author: DrVoIP

Peter S. Buswell (aka DrVoIP) is a rare blend of C-level executive leadership and deep technical expertise in telecommunications and cloud infrastructure. With a career that began at AT&T in 1970, he has founded and led multiple industry-defining companies, including Dextr.Cloud—acquired by AWS Global Partner CloudHesive. Peter has held senior roles at firms like Exxon Enterprises, Intervoice/Brite, and Franklin Telecommunications, and has consistently driven innovation from traditional PBX to Amazon Connect cloud deployments. A hands-on architect with certifications from Cisco (CCNP/CCDP, UCCX/UCCE) and AWS (Solutions Architect, Developer, SysOps), he combines strategic vision with engineering precision. Known as DrVoIP, he continues to bridge the gap between enterprise goals and technical execution in today’s evolving cloud communications landscape.

QOS for ShoreTel VoIP Deployments!

Posted on March 23, 2010 by DrVoIP

Setting up QOS on your routers to support ShoreTel VoIP across a WAN connection requires that you employ some creativity in your configuration. Think of Class Marking as a way of “coloring” packets so that the routers no how to treat the packets when there is any kind of congestion. We want voice packets to have a priority over data packets, so we color them and tell the carrier or WAN router which color is voice. Generally, QOS strategies employ the use of Differential Service Control Points or DSCP values.

These values are established by convention and can be generally summarize as IP Precedence Level 5 (101xx000 = DSCP bits) or DSCP Values of 160-184 to representing “Express Forwarding” with a decimal value of 41. The TOS byte in the IP header allocates the high order 6 bits to the DSCP value, making Express Forwarding or EF equal to decimal 41 or 10111000 binary. Most carriers will comply with this class marking and will put IP packets marked with this value in the Low Latency or “go fast” queue. (See note below).

In the ShoreWare Director Portal you will find a link under Call Control to “options”. On this page, you will find a box for DiffServ/ToS Byte (0-255). This is where you will set your DSCP value, generally 184. This will mark all voice packets originating from ShoreTel Voice Switches and IP phones. A QOS configuration generally consists of three elements; The Class Map, the Policy Map and the Service Map. The Class Map tells us what it is we are looking for. The Policy Map tells us what do when we find what we are looking for and the Service Map applies this information to the proper interface, generally the WAN side of your router.

Here is an example of a simple QOS configuration:

class-map match-any VoIP
match ip dscp ef

policy-map QoS
class VoIP
set ip dscp ef
priority percent 50

Basically, we are telling the router to look for incoming IP packets that have a DSCP value equal to Express Forwarding. When we see these values we are going to know they are VoIP packets and move them to our LLC where we have reserved 50% of the available bandwidth for use by the voice application. It is important to note that queues in routers only take effect when we have contention for bandwidth. The QOS statements help the router make decisions as to what queue gets serviced first. Understand that, should queues fill up, the router will start “tail drop” and throw out packets no matter what the class mark! This is a key issue, as the queue is for outbound processing. What happens if some idiot is down loading Avatar from NetFlixs? The incoming data flow could drown out any attempt to service outbound queue handling.

Lets look at modifiying our ShoreTel QOS strategy to provide for some additional configuration options. One option is to set up an Access-List to capture information that might not be generated by a ShoreTel switch or IP phone. ShoreTel uses a specific set of TCP/DUP ports that we can easily identify. You also know the IP address of your ShoreTel server. Why not set up an access list to look for traffic originating from the ShoreTel server or traffic originating or terminating on specific ports? Here is an example, created by Brain Krail, of a configuration that establishes the access list and also sets up several classes of service for voice, mission critical data and best efforts data:

access-list 197 remark “All SHoreTel”
access-list 197 permit ip any any dscp ef
access-list 197 permit udp any any eq 2427
access-list 197 permit udp any any eq 2727
access-list 197 permit udp any any eq 5004
access-list 197 permit udp any any range 5440 5446
access-list 197 permit udp any any eq 5060
access-list 197 permit tcp any any eq 5060
access-list 197 permit udp any any eq 111
!
access-list 198 remark Mission Critical
access-list 198 permit tcp any any eq ftp
access-list 198 permit tcp any any eq telnet
access-list 198 permit tcp any any eq smtp
access-list 198 permit tcp any any eq 3389
access-list 198 permit udp any any eq 3389
!
access-list 198 remark VPN Traffic
access-list 198 permit esp any any

class-map match-any VoIP
match access-group 197
match ip dscp ef

class-map match-any mission
match access-group 198
!
policy-map QoS
class VoIP
set ip dscp ef
priority percent 50

class mission
set ip dscp af41
bandwidth percent 30

class class-default
set ip dscp default
fair-queue
random-detect

int ser 0/1/0
max-reserved-bandwidth 100
service-policy output QoS
!
In this configuration we use our Class Map to look for packets that match our Access-List. Clearly, we are scanning for matches and based on the match, we classify the traffic as voice or mission critical. The Policy map then assigns the proper value or class marking based on the Class Map matches. The Service-Policy at the end applies the Policy to the Serial Interface on this router, most likely going off to the Carrier. Your previously co-ordinate agreement with the carrier will result in them treating the packets as marketed an handling them accordingly. We find that QOS configurations that use Access-Lists to further search out traffic and host IP addresses that generate voice media streams, do a much better job than those that rely solely on the DSCP mark setup in the ShoreTel Director.

Now about that ugly issue of the user downloading NetFlix! How do we tell the carrier not to exceed a certain about of traffic inbound to our router? The following configuration is an example of “Policing” an inbound interface to throw away any traffic that exceeds the CIR rate we set up. This configuration increases the likely hood that QOS will be effective outbond, by making sure the inbound bandwidth is not over subscribed by a user downloading over your voice traffic!

access-list 199 permit ip any any dscp default

class-map match-all test
match access-group 199

policy-map testPolice
class test
set ip dscp default
police cir 1000000
conform-action transmit
exceed-action drop

QOS is an essential part of any VoIP deployment. ShoreTel Deployments can benefit measurably by getting creative with your Configurations and thinking outside the simplicity of DSCP! NOTE – you need to dig deep on circuits provided by carriers that are peering with another carrier to deliver a complete circuit solution. We have experienced situations in which the carrier taking the order adhered to our QOS markings and acted according to plan. However, when that carrier hands the packet off to another carrier for final delivery, you need to make sure that they are in fact, honoring the same QOS markings. In one situation, though our carrier was handling DSCP as agreed, the carrier that they handed off the packet to for final delivery, did not use DSCP on the MPLS circuit in question. Some carriers, by inter-carrier agreement, use the Experimental Bits to deal with QOS. Be Careful as the techs you are working with may not even know this, swearing all the time that QOS is setup per DSCP value!

Give us a call if you want assistance on QOS setup for Voice and Video!

ShoreTel Database Replication and Manipulation of MAXDBQUERIES!

Posted on March 4, 2010 by DrVoIP

It really doesn’t matter what VoIP system you installed they all generally have one architectural characteristic in common; the configuration database. Depending on the system, you might find a database engine that ranges in complexity from an Access Database to a full blown SQL database. The database will store configuration information, status information and often, call detail records that document phone system activities. The characteristic of the database that is consistent across all architectures is the fact that there can only be one “read/write” copy of that database!

Some phone systems distribute the database across multiple servers. ShoreTel, for example, distributes components of the database to application servers and distributed voice mail servers that characterize the single image architecture in a multi-site environment. We need to better how a change to the database effects the operation of the system, the bandwidth of the WAN links and the demand on the database engine. First, what constitutes a change to the database? Well clearly any configuration change that is made to the system. For example, adding or deleting a User are clearly going to cause a database update! Lets take a more subtle example, however. Lets consider what happens to a Agent in a Workgroup, located at a remote site, behind a distributed voice mail server. Each change that Agent makes on their Call Manager represents a database change. Logging into the system, and Logging out of the system are database changes. How about, accepting a call being offered to the Agent by a Workgroup?

Each of these Changes is communicated to the database. The change is first made on the “read/write” database and then replicated to the remote database copy. ShoreTel system processes use MS Distributed Component Object Model (DCOM) objects to share information from the configuration database among themselves and to write configuration information to the database. User configuration options are written to the database from Personal Call Manager, and the telephone interface. Each ShoreTel service on a distributed server caches it own copy of the configuration database. When a distributed server loses connection to the HQ server (read “read/write” database) any changes made are no longer received by the distributed server. If a DVM restarts without a connection the HQ database, services are started but are not functional. When the network connection is restored, the configuration is retrieved and again cached by each service as the services become functional.

If there is a flap in the WAN we note that the DVM will in fact reload a copy of the database. This movement of the database between the HQ server and the DVM servers clearly uses bandwidth and also makes additional demands on the database engine. In ShoreTel the database engine, is now MySQL. The question becomes how many simultaneous database access (read, modify, write) transactions can the MySQL server handle at one time? What happens if the transaction can not be completed? Does it queue and retry? In a large system of say 700 workgroup agents at a site, is it possible to overload the MySQL database with state change requests? If you dig down through the Server registry you will find the MAXDBQUERIES is set by default to 100. It has been our experience that, defending on the size of the system, it is sometimes necessary to dial this number back to eliminate overloading the database. This adjustment should be made only on the DVM’s in the configuration and not on the HQ server. You will need to reboot your DVM servers after making this change. You should also note the difference between HEX and Decimal!

The following SILENT file clip demonstrates how to make this adjustment.

ShoreTel Enhanced Workgroup Services!

Posted on February 17, 2010 by DrVoIP

Historically, there were three services in the ShoreTel architecture that were no distributed to other servers. To oversimplify, this meant that if the HQ server (read primary server) was unavailable, the services that were not distributed would not function. The three services were Route Points, Account Codes, and Workgroups. For example, if a user group was set to “forced” account code verification and the server was unavailable, that service would fail and the affected user would not be able to place a call. Likewise, if the HQ server were unavailable, Workgroup services would fail. ( The “best practice’ deployment strategy was to backup a Workgroup with a “hunt group” given that the HG ran on a switch and not a server, it would continue to function in this scenario. Calls targeting agents in a Workgroup would fail over to a hunt group that would target the same list of agents).

ShoreTel has steadily progressed the distribution of these services out from the HQ server to either SG switches or Distributed servers. With the latest release of ShoreTel, they have migrated critical services to include Workgroup services. This is a major enhancement and any organization that makes use of the Workgroup functionality, especially in a multi-site environment, will realize a benefit by these enhancements.

Through the ShoreTel administration portal, we now find a drop down window that enables us to select which server should be utilized to run the Workgroup we are defining. For example, in a multi-site environment, I might want to have the Workgroups organized by Site and run the workgroup service on the DVM at that site. This would keep the Workgroup local and a failure of the HQ server would not dramatically affect the workgroup at the remote site. We note that, in the absence of the HQ server, we are still unable to make database changes. For example, Logging In/Out of a Workgroup would not be possible, but the remote Workgroup would still function.

Additionally, we note that you can continue to name a Hunt Group as a backup extension. The key difference here is that the Hunt Group can contain extensions that are Workgroups on other servers! This offers a degree of flexibility not previously available and is a viable alternative to a straight Hunt Group solution. A failure of the HQ server will only effect the Workgroups that are on that server and distributed Workgroups on other servers will continue to run. A failure of a DVM with an operating Workgroup can fail to a Hunt Group that can be used to route calls to other Workgroups.

The vocabulary might be a bit confusing, but the strategy represents a significant step forward in assuring the operation of a distributed call processing application as powerful as ShoreTel Workgroups!

ShoreTel CDR Format- How to find the International Calls!

Posted on February 5, 2010 by DrVoIP

Recently, while working with a third party Call Accounting vendor, we had an opportunity to revisit ShoreTel CDR records. ShoreTel stores CDR records in two locations for two different purposes. Historically, the first format is basically the “Legacy CDR Text Files” and they are stored in the Shoreline Data folder as log files. The log files are written to \Shoreline Data\Call Records 2 and are written out at Midnight to a file named CDR-YYMMDD.HHMMSS.log. This is the file that is generally accessed by third party Call Accounting software vendors.

The second format is written to a MySQL database which is used to generate call accounting reports directly from the ShoreTel server. In version 7 ShoreTel began to migrate away from Microsoft Access to MySQL for both the CDR and the configuration database. There is a procedure for converting the older files into the new MySQL format, but we are not going to cover that as most people have already made this transition. The MySQL database also opens the opportunity to create custom reports using SQL queries. Through the ShorewareDirector portal, under Reporting options, you can set the Retention Period for CDR Data as well as the Archive retention period.

If your third party Call Accounting software uses the 011 to detect an international CDR record, you will need to make some adjustments. ShoreTel uses a Canonical format to collect digits. This means that no matter what the user actually dials on the phones keypad, the system internally converts the numbers to +country-code area-code subscriber –number. The fact that you dialed 9+011+52+3654587 will be stored in the ShoreTel CDR log file as 9+523654587 and the 011 reference will not be in the record. The following silent film clip walks you through the format and content of the CDR.log files.

Configure ShoreTel for Redundancy, Resiliency or Business Continuity?

Posted on January 21, 2010 by DrVoIP

Of late we have seen a growing interest in building “disaster recovery” solutions for both the data and the voice applications so critical for business operation. First, we need to make sure we understand the difference between redundancy, resiliency and other configuration options to assure business continuity. Many more installations now include the use of a remote “collocation” facility as an key component of the installation plan. What is the best way to configure a ShoreTel HQ server, for example to provide for continued operation under a wide variety of options.

The subject of redundancy is almost amusing at times. How much redundancy is reasonable and appropriate? You can have all the redundancy your budget can fund, but at the end of the day are you able to continue the business operation in the event of a catastrophic event. Clearly, two power supplies are better than one. If they are both plugged into the same commercial power outlet, however, it really will not matter how many power supplies you have if you lose commercial power! Again, we need to focus on what are we trying to protect?

Redundant servers? Some HQ servers have been configured with “double take” enabling a hot standby server to take over in the event of a primary server failure. Candidly, we do not see the benefit of hot standby server swaps in the ShoreTel architecture and it is a nightmare to administer, backup and restore. The cost of the solution outweighs the benefits and there are other configurations that are more cost effective and work just as well.

For example, there is no law that says you can not install a ShoreTel Distributed Voice Mail server at the same level as the ShoreTel HQ server. Actually, this works just fine! Install the servers at the same physical location, or put the HQ server in the remote “collocation” facility. If they are installed at the same “logical” level (i.e. appear on the same level in the Shoreware Director, either server can handle the load. Generally, you would put all of the users and switches for that site under the DVM and use the HQ as your “fail up” and proxy solution. Nothing wrong with this configuration, it is cost-effective and easy to administer. From time to time you might hear ShoreTel say “ please wait while I connect you to the correct server” but even that can be managed.

ShoreTel HQ has three services that are not distributed: Route Points; Account Codes and Workgroups. If you lose the HQ server, you will lose these services, but generally, that is a small price to pay for this level of resiliency! ShoreTel Version 10 promises to distribute these services, so there is no reason not to configure this way and achieve full survivability given the building is still standing.

You don’t have to think very long about a Katrina or Haiti, especially if you live in California! It is only prudent to not only plan for some level of “redundancy”, but also to plan for how the business would operation if we could not get into our building! If we put the HQ server at the “collocation” facility and we provide for Trunk Lines and “dial tone”, we can balance this possibility. The issue is, that if the building housing the people becomes unavailable, users can still log in and route their phones to cell phones or make use of RDP to access their Call Managers.

The “collocation” option often requires a trade-off between bandwidth and trunk lines. You can put all your trunk lines at the colo, in which case every call made from the sites, will traverse a WAN. So moving the trunk lines to the colo increases resiliency but also drives up your WAN cost. At the end of the day, it is most likely some combination of bandwidth and trunk lines spread between the facilities. In either case, you will work with your carrier to enable lines to be repointed in the event of an outage. This is a bit more challenging if you are in New York and your collocation facility is in Phoenix, but it can be done.

We are experimenting with the use of SIP trunk facilities at the Collocation site. Generally, this can be more cost effective especially if you can get an agreement for a burstable SIP pipe. You may not want to pay for T1’s at the collocation if you are only planning to use them for a disaster situation! SIP also enables you to be generally independent of your physical location.

It is a sign of the times that we spend so much time planning for “what if” scenarios, but being prepared is not only prudent but appropriate. Have a comment on this blog? Email:drvoip@drvoip.com

Why move the Auto Attendant into the Contact Center?

Posted on January 9, 2010 by DrVoIP

Many Call Center applications have an Automated Attendant front end call tree. Typically, you might have an Automated Attendant that plays the familiar On-Hours recoding: “Thank you for calling our company, press 1 for technical support and 2 for sales support”. The question asked in today’s blog is: should the Automated Attendant be located in the PBX or in the Call Center? There are very interesting ramifications for each of these options.

Generally, with out thinking this question through, the easy answer is to have the PBX do the front end Automated Attendant. In the ShoreTel world, the On-Hours/Off-Hours scheduling of the changes to the call tree and messages played is so “brilliantly simple” that everyone will select this implementation strategy. In our simple example above, selecting either option will direct the caller via a route-point/IRN marriage into the Contact Center to be processed by the appropriate Service, Group and Agent.

If you implement that Automated Attendant in the PBX, however simple it is, you potentially rob management of very urgent call detail information. Typically, the Off-Hours location is a general delivery mailbox in the PBX anyway, so why not just keep it all in the PBX? If the Automated Attendant shuttles calls to the Off-Hour location, that call may never become known to the Contact Center and therefore would not be captured in the Contact Center Historical Reports. Call Center Management might be very interested in knowing how many calls came into the Center before or after On-Hours! To obtain the information the Call Center, not the PBX needs to host the Automated Attendant!

What is the result of implementing the Automated Attendant in the Call Center? If you look at the above Automated Attendant script, you can see immediately that we need to add the famous “If you know the extension number of the person you want to speak with, dial it at any time during this recording”. Given that you have already concluded that this is an option you want to offer clients, something a Call Center manager might not recommend, how do you implement this feature using the ShoreTel Contact Center?

There are several ways to do this on the ShoreTel ECC, but all options require the creation of a “Call Profile” value. We have put together a quick video tutorial on how to implement a multi-digit transfer in the ShoreTel Contact Center using the Graphical Scripting Tools. Minimally, after you create the Call Profile value you will need to have a “Get Digits” and the “Transfer” Icon. In our example, we have created a Call Profile value named “ExtensionNumber”. This value anticipates a three digit integer and does not require a termination character. The GetDigits Icon is normally associated with a WAV file that prompts the caller for digits. Once the digits are collected the are deposited into the Call Profile place holder named “ExtensionNumber”. This value is then past to the Transfer Icon and the value is dialed by this function. Enjoy!

Mobile Call Manager for the iPhone?

Posted on December 29, 2009 by DrVoIP

One of the benefits of a successful blog, is the talented people you meet and the ideas that you exchange with other industry professionals. Through an earlier blog on the subject of connecting an Apple Iphone to a ShoreTel System as a SiP extension, I met such a creative talent: Matt Vlasach of Pacificswell! Matt was both an excited ShoreTel user and a Iphone aficionado. Thought Matt was happy to play with SIP his real interest was in creating a ShoreTel App for the Iphone!

As a result of Matts talented development team at Pacificswell, I have had the pleasure of playing with a beta version of StreamLine, a mobile call manager for the Iphone! If you have always wished that ShoreTel could work on your Iphone, your wish has been granted! Pacificswell’s first release of the App is a useful, easy to master, technically brilliant mobile call manager! Using Streamline you can remotely connect to your ShoreTel server and setup your call handling modes and activate your Office Anywhere feature. The App is intuitive and graphically obvious!

Even using the Apple developers platform to obtain the beta version ( an Apple strategy for enabling developers to offer the App before it appears in the App store), the download and install was remarkably simple. It downloads and installs using the already familiar App Store process! Configuration was a breeze and I had the App up and running in under five minutes.

Clearly there are some server side issues that need to be addressed and license compliance issues for the ShoreTel Mobile Call Manager, but technically, the App is brillant. More importantly it just works! I was able to select either my Office desk phone or my Iphone as the primary answer point. Each of the Call Handling modes can be accessed in a visual graphic that is experentially compatible with the ShoreTel user interface for setting up Call Handling Options.

Product Development is a process, not an event! Matt assures me that he will continue the development and enhancement of this App adding more features in future releases. The product can be explored in detail on his site at Pacificswell and I have included some screen shots below!

Keep the cards and letter coming! The App will be available at the Apple App Store on January 4th!

Select your Desktop or Iphone as prmary answering point!

ShoreTel Enterprise Contact Center Call Routing based on Schedules!

Posted on December 5, 2009 by DrVoIP

If you have been following our tech tips, you know that route points in the ShoreTel IPBX have a matching IRN in the Contact Center. If you want to route a call to a different destination based on the date and time that a call hits the Contact Center, how and where would you apply the schedule? Technicians familiar with the ease of creating schedules in the ShoreTel IPBX, might immediately apply a schedule to a route point. After all, each call to the Contact Center hits a route point first, why not apply the OnHours/OffHours call handling directly to the route point?

At the end of the day, Contact Centers are designed to provide management, detailed information to facilitate staffing, allocate resources, decrease call holding time and increase customer satisfaction. Candidly, it is all about REPORTS! My personal prejudice is that contact centers should be designed by starting with Reports! What is it that Management wants to see? If we want to know how many callers are hitting the Contact Center during Off-Hours, for example, we can not apply the schedules to the Route Points. If the Schedule applied to the Route Point deflects the caller to a Voice Mail box, that call will not appear in the total Calls presented to the Contact Center.

If you want the call to be counted, it must actually enter the Contact Center! For this reason, most Contact Center deployments are deployed with the Automated Attendant functionality being defined within the Contact Center. In this way we can accumulate accounting information on all calls that hit the Contact Center, regardless of how they are ultimately routed. The ShoreTel Enterprise Contact Center has a very powerful configuration capability as it relates to defining Schedules. Schedules are defined as “types of days” and “shifts”. At first this concept is a bit difficult to digest, but once you play with it you will realize just how powerful and impact this configuration strategy can have on your overall Contact Center call flow.

The Working Times facility enables you to define a type of day and then associate shifts to that day type. The normal ShoreTel Schedule works on a binary On-Hours Off-Hours call handling model. What happens if you want to build a call flow that needs to have calls routed differently between specific hours of the day. For example, between 12AM and 8PM, we want incoming calls to be routed to the Guard Station. Between 8AM and 12 Noon we want a live answer point at the Reception Desk. Between Noon and 1PM calls need to be routed to an outside answering service; and between 1PM and 5 PM they need to be routed back to the Reception desk. Now any technician that has been working with the ShoreTel IPBX for any period of time has developed several strategies for handling this often required call flow. The strategy usually involves cascading Hunt Groups in combination with Workgroups to achieved the desired result.

The Working Times facility within the Contact Center would handle this complexity with ease. You would define a Day Type (i.e. WeekDay) and the define the various Shifts that comprise that day. In the example above, the ticking of the clock would transition through the various “shifts” resulting in a different destination based on the time of day. This is advantageous in a call center environment and significantly less demanding to administer than the cascading Hunt group strategy. Contact Center call flow is often managed on a time of day, day of week and holiday basis at a level of sophistication that goes way beyond the On-Hours Off-Hours approach to call handling. The ShoreTel Enterprise Contact Center Working Times facility is a power strategy for achieving maximum call routing control.

VoIP QOS Network Monitoring and Pathview Cloud!

Posted on December 3, 2009 by DrVoIP

Trouble Shooting VoIP issues in a multi-site deployment is a challenge to even the most talented network engineer. It is often difficult to determine what is a voice equipment issue and what is an issue aggravated by a network conditions. As network engineer troubleshooting an issue, having access to network monitoring tools is essential. Sometimes we have to use the basic ICMP tool sets and ping our way through a trace route, but network connectivity is only one element of QOS related areas in a VoIP deployment. (Actually, it would be great if clients invested in putting network monitoring tools in place, but they only seem to appreciate their networks when something goes wrong)!

What is that we need to monitor anyway? We split the monitoring world into two basic camps: Flow based accounting and Health checking software. Flow based monitoring enables us to check the source/destination IP address; source/destination port; IP protocol; TOS and Ingress interface. This is helpful when you are trying to figure out what applications are running on your network and who is streaming real time media. Clearly important stuff, but at the end of the day, when it comes to logging into someone’s network remotely and trying to figure out why some remote user has garbled phone calls, there is nothing like an in place Health check!

When we talk about the “health” of the network we are interested in knowing about Bandwidth capacity, Loss, Jitter, Mean Opinion Score (MOS), latency and tagging.These are the words that make a VoIP engineer smile!Would it not be wonderful to log into your clients network and have this kind of history available between key end points of a multi-site deployment?Rarely, do I ever publically endorse a product but the folks Apparent Networks have gone out of their way to make their product available, useable and free!You need to stop what you are doing and download Path View Cloud, a host based network monitoring solution from Apparent Networks.

Not only is this software as useful as a button hole, but you can download a fully functional 5 node solution for absolutely no money! In previous posts, I have discussed the fact that, despite best practice, clients continue to attempt VoIP phone deployment over DSL through VPN tunnels! Path View Cloud enables you to collect real-time network health information about key endpoints in your network. Typically, it is the remote user or the WAN points that you are going to want to study. Path View Cloud enables you to create monitoring solutions that regularly report on health checks and trigger alerts when “violations” have been detected. Yes, Virginia, there is a Santa Claus and you can see packets!

Clearly Apparent Networks believes that offering 5 free nodes will get you to order more!The offer is, however, compelling and I can tell all you cheap, penny-pinching, tight wads that will not invest in network monitoring software, that you will sleep better at night with this Path View Cloud solution in place.Network and VoIP engineers and technicians, you need this arrow in your quiver to make troubleshooting more visual!

ShoreTel Enterprise Contact Center “Change Call Profile” icon

Posted on November 28, 2009 by DrVoIP

How many people hit the Auto Attendant and then dialed one for Sales? One of the most requested reports from ShoreTel clients is the analysis of Automated Attendant key strokes. With in the ShoreTel iPBX there are probably several ways to implement this, but we prefer the use of “route points” (see past blog). “ Thank you for calling our company during our normal business hours. For Sales Press 1, for Service Press 2 or stay on the line and the next available member of our staff will be right with you”. Typical Automated Attendant? We set the time out value to go to a “hunt group” and each of the menu items to a route point. You can actually run a User Detail report against a route point, as long as that route point terminates on a Shoretel end point other than a TAPI end point. For this reason, you can then run the report and find out exactly how many callers dialed one for sales!

Recently, we had to create an Automated Attendant on an Enterprise Contact Center. At first this seemed almost boring, but then we ran into an issue. You can use the MENU icon to create your Automated Attendant script, with a TRANFER icon to each destination selected by the caller. You can use the SCRIP icon to send the caller on to a script to collect information like the callers account number for a SQL database look up; but how do you send a caller to “service”? Now that was a more interesting challenge and I have to thank Chad Burnett for pointing out the use of what has become my favorite new ShoreTel ECC scripting icon: “the Change Profile” action. This icon is a powerful call profile manipulator and enables the Enterprise Contact Center configuration to explode with call processing options.

Using the Change Call Profile icon you can select various Call Profiles for manipulation. Each system contains a number of mandatory system level call profiles like ANI and Caller ID. You as a system designer can also create Call Profiles to meet the needs of your exacting design requirements. For example, you might add the Call Profile “Account Code” that you might use in a script that prompts the caller to enter digits that you will use to look up a record in a SQL database.

The Change Call Profile icon also allows you to select a previously defined SERVICE. The following video clip reviews how the iPBX and the ShoreTel ECC interconnect. It demonstrates the use of the Change Call Profile icon, by demonstrating the creation of a simple automated attendant!