In my previous feature highlight posts they have often contained screenshots, details of the options, and given a sample a use case or two to help explain what could be accomplished with the features. The two that I’ll talk about today are mostly unseen in terms of the admin screens and really only come into play as a phone rings. So they are not as obvious as the past ones seen as options on the admin screens but could be just as useful depending on your use case. Continue reading “Feature Highlight: A Couple of Hidden Features”
Feature Highlight: Conference Rooms
The common conference room, a necessity in today’s world with employees working from home, travelling, and distant customers. No product with PBX functionalities should be without one.
Lets take a look at the options for the conference rooms provided by the Q-Suite.
The options seen are:
- Name – a Friendly name. If the room is used for a purpose, as our example is, then it’s best to name it after that. This will be the name seen elsewhere within the system.
- Extension – the extension used for directly dialing it from an extension.
- PBX Server – This is hidden if your system has a single PBX server. In the case where there is multiple this can be used to distribute load or in the case of a geo-diverse system ensure the conference is on the server closest to the majority of participants to ensure quality and limit bandwidth usage.
- PIN – a numeric pin to secure the conference with.
- Disable first member message – If checked this will not playback a message stating the first member is the only one in the conference.
- Announce user count on join – If checked this will announce to the user how many users are already in the conference they are joining.
- Play music on hold for single member – If checked this will play music on hold when the conference has a single user. Otherwise the user will only hear silence.
- Music On Hold Class – what music on hold to play when it’s a single user conference and the above is checked.
- Suppress enter/leave sound – If checked a user joining or leaving the conference will not trigger the tones to be played to all conference members.
- Announce names on enter/leave – If checked each user joining will be prompted to record their name before they join. This recording will be used as the join or leave
With all of these options you can configure the conference rooms you needed. However to fully leverage conference rooms, or any single feature, the ability to combine and interlink them to suit your needs is required. Let’s take the example of a daily standup which needs a conference room for a few remote employees. It’s always starts at 8am and lasts about 30 minutes. One way to ensure outside callers do not use it outside of this hours is a pin but you can also mix it with the Routing Rules so the DID or IVR/Auto Attendant option is not configured to point directly to the conference room but to a routing rule first. This routing rule will only route callers there at 8am until 8:30, although I’d recommend 15 mins earlier at least to allow early callers in and maybe a bit longer depending if the meeting has a strict end time or not. The routing rule can then send them to an auto attendant or elsewhere in the system if it’s outside of the hours — add multiple rules to allow different routing if it’s before to note they are to early, or if they are late to send them to a recording of the conference to hear what they missed.
Feature Highlight: Auto-Attendants
In the past we have covered the Q-Suite’s Visual Dialplan Builder with its ease of use and capabilities to handle any, from basic to very complex, requirements of an IVR. However, before the Q-Suite had the dialplan builder, we had the auto-attendant features, which allowed for a menu structure to provide the caller options to select and be sent within the system. One can argue the dialplan builder can do everything the auto-attendants can and I would not disagree. However, the auto-attendant configuration screens have been kept in the product due to their ease of use that allows anyone to have a multi-level menu system up and going within minutes. Continue reading “Feature Highlight: Auto-Attendants”
Feature Highlight: Asterisk Scripts
Within the Q-Suite we have our dialplan builder with extensive options to route and manipulate calls. The dialplan builder meets the needs of most situations but from time to time you need to get low level and go right into the asterisk dialplan. If it is only a couple of statements the dialplan builder has the Execute command, but when it’s more involved that’s where the Q-Suite’s Asterisk Scripts option comes in. Continue reading “Feature Highlight: Asterisk Scripts”
Feature Highlight: PBX Routing Rules
In the Q-Suite, we use PBX Routing Rules as the proper name for Time of Day scheduling. This feature is the backbone of the CTI Campaign Schedules, but is still quite useful for people who may not want to venture into the Contact Center portion of the product and are perfectly fine with sticking to the PBX aspect. Let’s have a look at a simple example showing how to use this feature.
Feature Highlight: PBX DIDs
As the title says it’s PBX DIDs in this highlight and sounds simple enough as you have a DID and you point it at an extension, IVR, or auto-attendant correct? Yes, but they can be used for much more.
Within the Q-Suite we have many options to link a DID:
Feature Highlight: PBX Restricted Numbers
When managing PBX extensions and their users the requirement to limit what can be called is often needed. This can be done heavy handed at the trunk level but then no calls can dial out to the blocked numbers.
Using the Q-Suite feature Restricted Numbers is a more refined solution to the issue. It can be setup to restrict certain PBX extensions from dialing a set of numbers while allowing others. For example this is useful if only a group of users are allowed and expected to make international calls while another group are to be restricted. Continue reading “Feature Highlight: PBX Restricted Numbers”