Welcome to Cisco’s Black Belt Academy – a simplified enablement framework, consisting of carefully curated content, that allows partners to enhance their competitive advantage, learn more about the broad spectrum of Cisco ecosystem solutions, engage more confidently with customers and ultimately execute sales.

Following on from the success of VQ’s inclusion in the Black Belt Academy, we’re thrilled to announce that Stages 1 and 2 have been completely updated to include our latest content on both VQ Conference Manager DMA and our new end user self-service app – VQ Conference Manager Metro.

Start your Cisco Blackbelt Academy journey today

VQ DMA has been designed from the outset as the on-premise replacement for Cisco TMS, and is recommended by Cisco following the End of Life/End of Sale announcement for TMS.

VQ Conference Manager’s DMA Suite, includes One Button to Push, Directory Services, Device Configuration and Device Maintenance.

Metro is our brand-new, cross-platform, all-in-one end-user app, designed to provide a video client that works everywhere CMS is installed.

“We’ve been delighted with partner engagement in the Black Belt program to date.

We’ve been on the Black Belt Academy for two years now and it is an excellent way for our partners to learn more about our product, understand the customer problems it solves and be confident including it in sales opportunities”.

Our customers response to VQ Conference Manager DMA and Metro is amazing. For both existing and new customers, sales are strong, and our pipeline just continues to grow and grow.”
Mike Horsley – CEO VQ Communications

VQ Conference Manager 4.3 is our final release of 2023 and it looks really good.

The headline new features are new meeting management refinements to the Activity page. The focus is to provide greater control of complex meeting operations and improve the visibility of active and inactive meetings to operators…

• Filters enable the amount of meetings being displayed to be reduced to those that you want to see.
• A new “compact” mode has been introduced which allows a single meeting to be viewed. A new “Call Builder” coApp has been introduced which allows multiple meetings to be prepared and pulled together at meeting start.
• Elasticsearch and Kibana have been updated to version 8.9 which is a full major release and 9 minor releases ahead of what you see in VQ Conference Manager 3.x. The initial impressions of Kibana on 4.3 is “boy, is it quick!”.

And there’s more….

Under the hood, the CM-Admin on 4.3 looks and feels really polished. At the platform level, performance and scaling refinements increase user interface concurrency from 500 to 1500 users.

Check out our YouTube channel to see all of the headline features of 4.3 in action.

Interested in finding out more?

On Thursday 11th January we will be hosting a VQ Conference Manager 4.3 Release Webinar – sign up for the session here

If you would like to find out more about VQ Conference Manager 4.3 and what’s coming up in 2024, please contact the VQ team.

We’re introducing an extensive functionality upgrade to the Outlook Plug-in with VQ Conference Manager 3.12/4.2 (plug-in versions 120 and above). Upgrades include:

• Meet me – inject a user’s Space details into the Outlook Meeting invite
  • Users can select the Space they want to use for the ‘meet me’ call and can inject details for the Space into the Outlook calendar entry.
  • If the Space has multiple Roles, the Role can be selected.
  • The Space details are static; the PIN/passcode are those of the underlying Space
  • ‘Meet Me’ is a better name for the functionality than ‘Call’. The configuration options use the ‘Call’ naming convention.
• Scheduled Meetings – meeting instances available for specific periods of time
  • Scheduled meetings exist for specific periods of time. They are created on CMS by VQ for the date and time defined by the Outlook Meeting.
  • Scheduled meetings can exist on existing Spaces or new Spaces created to host a meeting. VQ manages the lifecycle of new Spaces created to host meetings, which are deleted once the meeting has taken place.
  • Option of one-time PIN/passcode for scheduled meetings or using the PIN/passcode of the underlying Space.
  • Recurring Meeting sequences hosted on Spaces dynamically created to host the meeting will be locked between meeting instances. They will only be usable at the times of the meeting instances.
  • Meetings (and Recurring Meetings) hosted on an existing, known, Space take precedence over the ‘self-service’ use of a Space. For example, if Space 42 has a meeting scheduled at 3pm but a non-scheduled call is overrunning, any participants in the non-scheduled call will have their meeting terminated at 3pm, and the scheduled meeting will start. At the end of the scheduled meeting, the Space will return to normal use and availability.
  • The user can select from the available set of Space Templates available at the User’s UX (User Experience) Level. If a Space Template has multiple Roles, the user can select the Role details to be injected into the meeting. If a Space Template only has a single Role, no Role options will be displayed, and the default Role used.
  • Please note that the available set of Space Templates is determined at plug-in load. The plug-in requires reloading if additional Space Templates are added or made available to the UX Profile.
  • Configuration of setup and tear down times is on the user’s Tenant. Any new meeting scheduled via the plug-in will inherit these default values from the user’s Tenant.
    • VQCM 3.12 currently rejects requests for meetings scheduled to start in the very near future (less than the setup time window). This behaviour is planned to be fixed at 4.3 where the setup window will automatically be reduced to the available time and the call will start at the requested time.
    • Plug-in versions 120+ are not compatible with VQ versions earlier than 3.12/4.2.
• Highly configurable
  • Enable/Disable ‘Meet me’ (Call) functionality.
  • Enable/Disable Space selection.
  • Enable/Disable Scheduled Meetings or One-Time scheduling.
  • Re-label ‘Meet me’ (Call) and Scheduled Meeting menu items.
  • Provide your own icons for ‘Meet me’ (Call) and Scheduled Meetings.
• Works with VQ One-Button-To-Push (OBTP)
  • Associate Microsoft Exchange Room System Resources with Endpoints in VQ.
• Works with Outlook Scheduling Assistant and Room Finder
  • Users can use Room Finder to see when a meeting room is available.

The enhanced functionality is available from VQCM 3.12/4.2 and Outlook plug-in version 3.1.120.  The previous 3.1.34 version of the plug-in can still be used with VQCM 3.12/4.2.

The Outlook plug-in requires the Self-Service Application Pack option to have been licensed.

Looking to find out more…?

Watch our Outlook Plugin demo with VQ’s Technical Pre-sales Consultant Barry Pascolutti.

Still have questions? Speak with our team today.

VQ Conference Manager – Metro^TM, also referred to here as ‘Metro’, is an end-user-focused client for use in VQCM/CMS environments. It has been designed for managing Spaces, booking meetings and joining calls with a high-quality, intuitive video client.

Using Metro, service owners and administrators can provide desktop or mobile access to basic features required by their end users, allowing them to book and manage Spaces and join calls when unable to access collaboration rooms and devices.

The ‘low/no touch’ nature of the Metro application enables its deployment quickly and seamlessly without additional infrastructure or often complex application ‘packaging’.

Note: VQ intends for this first release of Metro to be for testing and evaluation purposes. We do not recommend deploying the client or browser URL to production users.

VQ Conference Manager Metro Overview

Page features and layout

Metro is a ‘web app’, meaning it is delivered using technologies that are fully compatible with modern browsers. At the same time, it can be packaged and delivered as installable applications on common platforms such as Windows, MacOS and iOS.

Let’s look at Metro in more detail.

Bottom Bar – Main Menu

Metro functionality is grouped into three categories – Spaces, Meetings and Settings – and accessed via the bottom bar.

Spaces

The Spaces area of Metro is where users will find a list of all Spaces they have permission to manage, book or join. If you are assigned a ‘Role’ in a Space, it will appear in your list.

Meetings

Meetings in Metro are bookings made against a Space through VQ Conference Manager.

This calendar is not connected to Outlook or Exchange at this stage; you will only see bookings made against Spaces visible to you in Metro. This will include temporary Spaces created from the Metro application.

Settings

End-user preference and local device settings can be accessed and managed here. This includes default devices or applications for calls and accessibility preferences, such as language and dark mode.

Metro components and application architecture

Metro is delivered as a new user interface (UI) of Conference Manager 3.12 utilising the CMS’ ‘Web Bridge’ feature. As such, it introduces no new components to the customer environment and runs within the existing virtual servers hosting VQCM and CMS.

If your environment does not currently have CMS Web Bridge/WebApp running, then it will need to be configured to run on the CMS before attempting to load and run Metro.

Setting up Metro

Load the Playbook

Metro is deployable using an Ansible Playbook that can be downloaded by customers licensed for the VQCM Applications Pack on request from support@vqcomms.com

To load the Playbook, please follow the instructions provided with it. Metro can then be as a Windows or MacOS client or in a browser using the https://FQDN/metro URL.

Using Metro

Logging in

When logging in to the Metro application for the first time on Windows or MacOS, it will present you with the login page.

You should insert VQ Conference Manager’s URL into the ‘URL’ field. Users can obtain this from a browser logged in to Conference Manager or distributed via email.

Metro will then request the user to log in. Enter your Conference Manager login name and password and click Sign In.

Once logged in, Metro will display the start view.

Spaces

Start-up view

The Spaces you can access and use in Metro are in the left-hand side panel.

Metro Modules are at the bottom of the page in the menu bar; a click on these will switch to the main view of that module.

Details of the Space and options for managing, scheduling (meetings), or joining the Space are shown in the main panel.

The options and information provided in this panel have been cut down considerably from the ‘advanced’ views available in the Conference Manager browser interface. This is intended to only provide the end user with key information they might use while using Metro.

Viewing/Editing Space details

The user can edit the basic settings of the Space, its name and SIP address.

They can edit the PINs required for the roles defined in the Space on entry to meetings. This might be useful for users wanting to set the PIN for a specific meeting running in a Space, or to change it if the use of the Space changes.

Join links and Join text are available for copy/paste into invitations being sent out via other systems such as Email or Instant Messaging.

Membership of the Space can be managed by adding or removing users from the Conference Manager database.

You can access every Space in the sidebar in the same way, simply by clicking on that Space.

The Space being viewed is highlighted in blue.

Scheduling a meeting in a Space

To schedule a meeting in a Space, click on ‘Schedule Meeting’ in the main panel.

The Metro Schedule Meeting page will be displayed.

Note: This page is identical to what a user will see if clicking the Meetings button on the main bar.

On this page, the user should provide a meeting title, start/finish date & time (and time zone if required) and type or copy/paste the email addresses of the meeting attendees.

Click Schedule Meeting to save the meeting in Conference Manager and email the attendees. Email addresses must be comma-separated for Metro to accept them as valid.

Note: In a future release of Metro, we will support adding Conference Manager registered people and devices (for OBTP) from the Conference Manager ‘endpoints’ database.

Metro will then take you to the Meetings page where you will see the meeting shown in the calendar view. You can make any subsequent changes from this page.

Join a Space

In the main panel of the Spaces page you can join a meeting in a space using the WebRTC video client built into Metro.

Select the Space you want to join and then click the ‘Join Space’ button in the main panel.

Metro will launch a new window to join the Space.

When other participants join, Metro will display them in the main video pane of the client.

The video window will display controls for muting or unmuting audio, enabling or disabling a camera, settings and ending the call.

There is a sidebar which provides access to basic meeting controls by clicking the button in the top right corner of the page.

On this sidebar you can see those participants in the call, who is speaking and change settings of the call – such as the layout. For more meeting controls, you can use the Manage Space page.

It is also possible to drop from the call and go back to the Space window using the Back in the top left of the window.

Manage Space

When the Space is active (i.e., there are participants called into it), the owner of the Space can ‘manage’ the call through a simple interface designed for an end user.

On this page you can manage participant settings: audio mute/unmute, video on/off, disconnect a participant, or end the call for everyone.

In the Endpoints view, you can invite Conference Manager registered users and devices from the Endpoints database.

Meetings

Calendar

The default view of the Meetings module in Metro is the Calendar page. This page can display ‘week’, ‘work week’ (5 days) and ‘Day’ views of the Conference Manager bookings on Spaces assigned to a user.

From the calendar you can go directly to the Schedule page to make a booking.

Alternatively, you can ‘drag and create’ a meeting on the calendar using your mouse.

Once you have marked the required time/date on the calendar, Metro will take you to the Schedule page to complete the booking.

You will notice that unlike the page presented when making a booking from within a Space, the Space field will be prompting you to ‘Select a Space’.

Click in the field and it will prompt you to type search text. It will display Spaces that match the search. Click on your required Space and the client will return to the schedule page to complete your booking entry.

If you want to use a Temporary Space for the meeting – a Space that only exists for the duration of the meeting – move the ‘Use Temporary Space’ slider to ‘On’.

Metro will create a temporary Space just before a meeting starts based on your Conference Manager’s ‘set up time’ setting.

The Conference Manager calendar will then display the meeting.

When a Space is created, it will also appear in the sidebar. You can join the meeting by clicking the Join Space button in the Space view.

Settings

Main page

The main page of the Settings module in Metro is in three sections: User, Behaviour and Display.

You can force a logout from Metro in the User section.

It is unnecessary to logout each time you want to close Metro, though it is useful if you need to switch users or VQ has advised you to do so while troubleshooting.

In Behavior you can select your default Space which will be displayed at the top of your sidebar list. Note: Space with active calls in progress will show above the default Space.

You can also select the default client that Metro will launch when joining calls. The default is the Metro WebRTC client, but this can also be the CMS WebApp in a browser, Webex or a SIP client.

You can also change the settings for your preferred camera, microphone, and speaker (if supported by your browser) here.

Finally, in Display, you can select your preferred language, time zone and color theme (Light or Dark).

The currently supported languages are English (US), English (UK), German, French and Arabic.

Interested in finding out more?

Looking for more technical information on Metro? There is an on-demand webinar waiting for you.

For any enquiries, please contact us.

Device Maintenance is the final release in VQ’s first phase of DMA – DMA Suite, adding to One Button to Push (OBTP), Directory Services and Device Configuration.

We’ve designed DMA in close cooperation with Cisco to ensure your unified communications devices remain healthy and secure and to troubleshoot specific equipment.

This blog explores DMA’s Device Maintenance functionality, explaining how to onboard and monitor device health.

What does DMA Device Maintenance do?

Onboarding Devices

Device onboarding is the process of adding devices to VQ DMA for provisioning and management.

To onboard a new device, navigate to DMA’s Devices Onboarding page from Devices -> Add:

You can use single IP addresses, DNS names, IP address ranges and multiple ranges. In this example, we’re adding one device with its IP address. You need to set the Time and Location. This example uses the Europe/London time zone, and the device location is Parallel House.

We are also going to assign the device a Device Template. In this example, we have selected the Desk Mini Global Template:

If you want to learn more about Device Templates and template modules, watch our Device Templates tutorial.

Optional information includes “Labels”. In this example, we’ve labelled both the device and usage type as “Personal System”.

Click Start, and you’ll see the device has been found and configured and the onboarding has been successful:

If you go back to the Devices page, you can see the Desk Mini is in the devices list:

Status Monitoring

From the Devices page, you can monitor the status of all your devices, updated in real-time:online, offline, incall or online with issues:

In the screenshot above, you can see that the VQ Brighton device is offline. The full range of device statuses can be seen here:

Trouble Shooting using DMA Analytics

DMA includes several useful Dashboards, providing real-time and historical status data for your devices to monitor and troubleshoot.

This dashboard shows devices laid out geographically:

The colours of the pins reflect the device status from the Device page – all devices in this screenshot are green and, therefore, online.

The summary table on the right shows the number of devices by system type. By scrolling down the dashboard page, you can find more detailed information, including:

• Name
• Labels
• Tenant
• Device state
• And more

The summary bar at the top of the dashboard provides information on total devices. For troubleshooting, the “Devices Online with Issues” data is important. Clicking this zooms in to the map view, showing the location of the device:

Scrolling further provides the summary information for the device:

Click the plus button next to the device and select View Device’s Activities:

This shows a timeline of the device’s status history:

You can filter this information over time ranges, and zoom into specific areas on the timeline using the Kibana drag and zoom function.

Scrolling down to the device details shows the SIP Registration status changed to failed after a device settings configuration request:

Having identified the issue with the device, go back to the Device Settings page. Once you change the settings as required and fix the problem, the device status will change to “Online”.

Want to find out more about DMA?

Watch our Learn More about DMA series to learn more about this and other DMA functionalities.

If you want to buy VQ DMA, browse our sales information.

Contact our sales team or you can keep up to date with our latest news by joining our Ask VQ Space.

We’re with you every step of the way

System migrations can be stressful, especially if you’ve been using your legacy system for years or decades. We want to help by making the migration journey from Cisco’s TMS to VQ’s DMA as stress free and simple as possible.

From the very beginning, we developed VQ DMA as the natural replacement for TMS. We worked in close co-operation with Cisco throughout this development. DMA is the Cisco endorsed replacement to TMS.

With the announcement of TMS’ end of life, it became clear that existing TMS environments will need to be migrated to DMA. Our goal has been to make this as planned and controlled as possible by developing a phased approach for you to manage your migration.

Are Cisco’s TMS and VQ’s DMA similar?

To make the migration process from TMS to DMA easier, the two systems have many commonalities. Let’s discuss their similarities and differences….

TMS has six modules of functionality:

• Portal – DMA Dashboard
• Booking – Scheduling and management (OBTP)
• Monitoring
• Systems – Device Configuration/Maintenance
• Phone Books – Directory Services
• Reporting – Reporting and Analytics (Kibana)

Like, Cisco’s TMS, VQ DMA has a similar modular approach with six modules:

• DMA Dashboard
• Scheduling and Management – OBTP
• DMA Configuration/Maintenance
• DMA Directory Services
• Reporting and Analytics (Kibana)

VQ DMA is not a direct replica of TMS, and this may take some time to adjust to.

We’ve given DMA’s areas of functionality different names. However, while they have different names, all available TMS functions are available and more, including:

• Cisco customers delivering collaboration services using on-premises deployed systems
• Using Cisco CMS and associated infrastructure

VQ Conference Manager functionality can be mapped to the six TMS modules. This enables customers currently running TMS to quickly and easily understand and navigate DMA.

One important difference between TMS and DMA, is that we haven’t directly replaced TMS monitoring (graphical monitoring function). That said, within the DMA dashboard we provide a rich visualization activity and performance data within your environment. This will be expanded over time.

The TMS to DMA journey migration path

We understand that TMS is deeply embedded into organisational conferencing environments. ‘Big Bang’ migration approaches aren’t often supported by existing users. We’ve developed DMA so customers can migrate in stages, running both TMS and DMA in parallel until a full migration has been completed.

To help make the migration process easier and enable quicker, streamlined adoption, we’ve developed a phased approach.

Four-step migration from TMS to VQ DMA:

The first phase of the TMS to DMA migration journey involves switching current bookings and schedule management. Here’s what that process looks like:

Step 1 – Meeting Services/Scheduling and Management

• Switch all new bookings to VQ Conference Manager
  • One button to push (OBTP)
    • Available since VQCM 3.9.0 Exchange Online integration planned to replace TMS EX
  • Outlook plug-in
    • Exchange Meeting Room Resources/Room Finder
    • “Meet Me” (Space call-in details only) and VQCM scheduled meetings
• Migrate existing bookings to VQ Conference Manager
  • Meeting extraction tooling
  • Creates new meetings using VQ Conference Manager methods
  • Replace meetings to be cancelled and communicated

In the second phase of the TMS to DMA migration journey, we focus on moving address book information into the DMA environment.

Step 2 – Directory Services – Address Books

• Switch endpoints to use VQ DMA Directory Services for ‘PhoneBooks’

The VQ DMA Address Books function is designed to replace TMS PhoneBooks. It:

• Replicates TMS hierarchical model
  • Uses same connection method
  • Tools to export/import existing Phone Books from TMS
  • Import connectors planned for CUCM and LDAP/AD
    

Once you’ve reached the third phase, you’re getting close to the end of your migration. This phase focuses on device configuration within the DMA environment.

Step 3 – Device Configuration

• Templates and Modules

The key part of configuration is our Templates Modules capability. It allows:

• Configuration management through templates and Cisco API
  • Enhance scheduling and automation
• Locations
  • Import or define the hierarchy of devices
• Labels – new feature in VQ DMA which did not exist in TMS
  • Add new labels for additional grouping/filtering

Finally, the fourth and final step in the TMS to DMA migration journey is device maintenance. Device maintenance ensures your DMA system is running smoothly, giving you access to a variety of features and functions, designed to ensure your system is always at peak performance.

Step 4 – Device Maintenance

• Device Maintenance provides access to the greatest number of features and functions in DMA:
  • Devices
  • Provisioning
  • Status
  • Activity monitoring
  • Health checks
  • Trouble shooting (change settings)
  • Security configuration management (replacing certificates etc.)
  • Firmware image management and deployment

This migration path, plus the planning and support provided by the VQ services team and your Cisco partner, will guide you through the process ensuring a smooth migration.

Once step four is complete, you have a fully up and running DMA that is ready to help you manage your environment. That means it’s time to turn off TMS.

Why migrate to VQ DMA from Cisco TMS?

Cisco’s TMS is now end of life. VQ DMA is Cisco’s recommended on-premise replacement to TMS.

Benefits of migrating to DMA:

• DMA has all the capabilities you need to replace TMS in an on-premise, CMS environment
• DMA can be deployed as modules. When migrating from TMS, you can choose to migrate module by module or in a single, step-by-step migration
• We’ve developed tooling to aid migration and minimize the amount of re-keying required, with our starting goal always being zero-rekeying

Want to find out more?

Contact the VQ team for more information or stay up to date with the latest VQ news via our ‘Ask VQ’ Webex Space

Following Cisco’s recent announcement that the End of Sale/End of Life process has started for TMS, we’re incredibly pleased to announce that we’ve released VQCM 3.12 and it is now available for download.

3.12 represents a major milestone, it completes the first phase of DMA suite, OBTP, Directory Services, Device Configuration and now Device Maintenance.

Device Maintenance is all about knowing what is happening to your device fleet, and where required, being able to trouble shoot and onboard new devices.

Device Maintenance adds.…

• Device Status and Activity Monitoring
• Device Health Checks
• Device Onboarding
• Trouble Shooting (interactivity changing settings)
• Security Configuration management (certificates)
• Kibana based visualizations including Mapping

Interested in finding out more?

VQ DMA overview

VQ DMA migration path

Video: How to migrate from TMS to DMA

Directory Services

Device Configuration

Our website is full of other useful information. Visit the Resources section of our website for further details.

If you’ve any other questions and would like to speak with us, please contact us

In August 2023, Cisco’s TMS product page was updated to announce that the End of Sale and End of Life process has started for TMS.

Until 31^st January 2024, it will still be possible to order TMS subscriptions. After that time, you will not be able to order TMS, but customers can continue to use existing TMS deployments with valid support contracts.

As part of the End of Sale announcement, the migration detail section encourages customers who cannot migrate to Webex cloud services to consider VQ Conference Manager.

We are delighted that Cisco are recommending VQ Conference Manager and DMA in this manner.

“DMA is another example where we listened to what our customers were asking for. We are delighted that we’ve been able to work closely on it with Cisco’s support. Our customers really like the results and we have an amazing number of new customers who have chosen to migrate onto the VQ platform. And in addition, our pipeline keeps on growing.””
Mike Horsley – CEO VQ Communications

What is VQ Conference Manager DMA?

DMA is built on the robust and secure VQ Conference Manager platform and provides vital functionality for Cisco video endpoint management. DMA is deployed ‘on-premise’ as part of a Cisco Meeting Server and Cisco videoconferencing devices eco-system.

What functionality is in DMA?

The goal of DMA was to extend VQ Conference Manager so that DMA plus Conference Manager’s existing functionality gave customers the functional equivalent of TMS and, in doing so, provide a transition path for TMS customers requiring a modern, secure, scalable on-premises solution designed to enable the delivery of modern video/unified communications services.

Under DMA, we group OBTP, Directory Services, Device Configuration and Device Maintenance.

DMA leverages the core benefits of the VQ Conference Manager platform – US Defence Department Approved Product List status (from 4.2) and Kibana based Reporting and Analytics.

How do I migrate from Cisco TMS to DMA?

Our migration path and support will guide you through the process ensuring you have a smooth migration from TMS.

We expect customers will want to migrate services in a controlled manner over several phases. We are not expecting customers to migrate away from TMS in a single, high pressure and risky, “big bang” step.

DMA was developed to enable this; with tools to aid migration from TMS available now and CUCM integration in an upcoming release.  We expect VQ and TMS to operate in a side-by-side mode during the migration process.

Interested in finding out more?

Our resources area is full of useful information about DMA.

If you’ve got any questions and would like to speak with with the team, contact us:

• Email us – info@vqcomms.com
• Join our ‘Ask VQ’ Webex Space

Did you know you can schedule Recurring Calls from the VQ UI? The great news is that you can now also schedule a Recurring Call where each instance of the meeting has its own Passcode.

Scheduling Recurring Calls

Before we begin, it’s important to mention that a Recurring Call must happen in a permanent Space.

Let’s show you how to create a permanent Space. Permanent Spaces are created from System, then Space Templates.

In this example, we are scheduling a basic Recurring Call. The first thing you need to do is create the Space.

The Template we are using has auto generated URIs (Uniform Resource Identifier) and Host and Guest roles. Otherwise, it’s fairly standard.

An important Space Template setting is “Space Locked”. Space Locked is the second option in the list of settings.

Enabling Space Locked locks the Space as soon as you create it. Locking the Space means no one can dial into it. When you schedule a call, VQ unlocks the Space at the meeting start time and then locks it again once the meeting has finished. This setting makes it so the Space can only be used for scheduled calls.

Creating the Space

From the Activity Page, click on the green plus at the top of the page.

On the form, you’ll need to complete the Space Name In this example “Jack Test Space”, we’ve filled out the Owner, Jack Larkin, and Space Type (Template) fields. Once you’ve filled in these fields, click Done.

Next, you need to schedule the Recurring Calls.

Once again, we’re using the test Space we created, “Jack Test Space”.

To schedule Recurring calls, click on the blue Schedule button, then click on the green Add button (denoted by a green plus sign on the left side of the screen).

Clicking on the ‘Add’ button brings up a new window. In this window, you’ll need to:

• Give the Recurring Meeting a title – we’ve used “Demo of recurring calls”
• Set a Start and End time for your recurring meetings – our example recurring call will be from 9am – 11am on the 4^th of May

Once you’ve completed these, click on the Recurring check box.

Clicking on the Recurring check box brings up a settings window.

Here, you’ll set the number of recurring meetings or choose when these recurring meetings end, and what day they occur on.

Now, add a Participant and click Done.

You can check the Recurring Call you created by looking at the Meeting list or Meeting page.

Remember, on both these pages, the default filter shows calls occurring within the next 24 hours. This means, in our example, you will only see one occurrence of the call. Expand the filter to a future time to see all occurrences of the Recurring Call within a specified period.

To edit or cancel an occurrence, click on the Meeting you wish to edit, and choose Edit. You can either make the changes to just that occurrence or apply the changes to all the occurrences in the series.

Find out more about VQ Conference Manager

If you want to learn more about the VQ Conference Manager visit our website

Looking for more VQ product information? Check out the Resources section of our website.

If you need additional help, contact us or join our Webex Space.