SkypeValidator Next Gen

It’s time to talk about next generation of the Skype Validator.  My goal is each year have a major update to the product and this year is no different.  This year the goal is to address three primary items:

  • Improve navigation.  This includes making it easier to use other features without having to go through the entire design model.
  • Improve the Phone Provisioning processes.  Last year we introduced a very basic Polycom VVX provisioning server.  It was based on HTTPS, allowed you to generate files and you could even point phones to it.  But it lacked flexibility, logs viewing, etc.
  • Improve Monitoring Tools.  Current system creates way too many false positives, too many e-mails get lost in spam and it’s just not easy to setup.

At this time I’m ready to talk about item #1 and #2.  We are shooting for end of year for the Next Gen release to everyone.  I’ll review the new monitoring items in the future.

Improved Navigation

One of the biggest issues with SkypeValidator is that you essentially were forced to enter all of your information to get to monitoring or VVX config.  And if you had all of this information already entered into the system, clicking on your deployment made you click a bunch of times before you got to what you wanted.

With the new update when creating a new deployment you will see the following:

1

(This is a mock up – not final icons by any means.)

Clicking on Design will be able to send to the traditional design tools.  Monitoring will default to the monitoring tools.  And Phone Provisioning will bring you to the VVX phone setup.

In addition to this, once you are in the deployment, you will see a full menu of options and no longer need to step through each item.

2

Phone Provisioning

The existing tools for phone provisioning worked but the goal was to make it more robust in nature.  So let’s look at some changes.

Introduction of Locations

At the top most level you can define different locations.  You can treat a location either as a global setting for your entire organization or physical location broken up by DHCP Servers.

3

In our example, we have two different locations.  The first is our Main Office and the second is the MSP Office.  You will notice we always remove spaces on names (you will see why in a second).  Additionally we see if provisioning files have been generated for that location and the option to delete that location.

When we open up the settings for the location a few things to note.

4

First, we have moved from HTTPS to an FTPS site.  This allows individuals devices to upload log files, call logs and much more.  Each location has it’s own provisioning server URL.  A single username and password is used for all locations in your deployment.

In addition to that change, you will notice that all settings are displayed in an easy to use tab interface making organized by section.  You can also download your master and custom config files if you want to use your own on-prem provisioning server.

Groups

Once you have created your location configuration you can now create as many groups as you want for your organization.

5

Devices can ultimately be assigned to the groups created.  Each group will have it’s own configuration which looks identical to the above location configuration.  The group configuration will be initially built upon the location configuration but you can customize the group however you want.

Devices

When you go to devices you will see all devices for that location.  Any device that has uploaded it’s log files to the FTPS server will automatically be displayed here.  Additionally, you can add your own list of devices.

6

When you view the details of a device, you will see the model, firmware installed and when it last was updated/checked in.  From here you can assign a device to a group, view files including log/config, etc.

7

What else is coming.

  • Being able to assign devices to group in a mass process
  • Better UI updates so its easier to figure out
  • Fix a chicken/egg scenario with devices and groups. Right now when you assign a device to a group, you have to go back and re-generate files for the entire group.

Remember, these are features that are coming by the end of the year but wanted to give a sneak peak of what we are working on.  If you would like to get involved with testing the phone provisioning features feel free to drop me an e-mail at richard -at- masteringlync.com and I can get you access to the beta.  We are looking for only about 5 people to start with.

1 comment on “SkypeValidator Next Gen”

  1. Pingback: Monthly IT Newsletter – October 2016 – Guy UC World

Leave A Reply

Your email address will not be published. Required fields are marked *