If you would like to try VisitorLink, you need only register at this site – http://portal.visitorlink.com using the link in the upper right hand corner. Upon registering, you can access http://portal.visitorlink.com/Download in order to download the software and register your 1st VisitorLink trial kiosk. By default, VisitorLink will run with a demo configuration and use a “fake provider” which fills in fake names in the directory and plays a static video instead of actually connecting to a Lync server. If you would like to try it out connecting to your Lync server further contact us at email@example.com and we will help you get in touch with the closest VisitorLink distribution partner to your area. If you are technically inclined and looking to do an evaluation without the assistance of a partner, let us know what your user name is and that you would like to request a 30 day free trial license. However, please be aware that VisitorLink does not provide technical support for free trials, nor should you be concerned that you will pay more for VisitorLink when working through one or more of our distribution partners to assist you. Every VisitorLink is sold through a distribution partner, regardless off the level of assistance our end users do or do not require.
To enable Lync or Skype for Business connectivity for your trial kiosk:
- Make sure you have the Lync 2013 or Skype for Business client installed and that you have updated the machine you are installing VisitorLink on with the latest Windows Updates – ensuring that any Office updates have been installed. Consider also whether you are using certified VisitorLink hardware. The list of VisitorLink certified devices is growing all the time. However, not all PC, camera, card swipe, touch screen, and audio devices have been tested with VisitorLink. In general, be sure that your hardware meets the following preferred configuration requirements
- A screen resolution with a 16×9 aspect ratio, preferably 1920×1080
- Windows 8.1 or Windows 10
- Windows-compatible Touchscreen
- Only 1 webcam installed that supports DirectShow
- No additional software running that may control the installed webcam.
- Make sure you’ve installed the Lync Runtime. NOTE: Each release of VisitorLink corresponds to a compatible LyncRuntime. A download for the appropriate runtime is provided on the downloads page corresponding to any version you might download:
- Make sure your Lync 2013 client is installed and functioning with your desired Lync server and with the user account you intend to use. NOTE:
- For best results, any certificates needed for security or dialogs popping up on 1st run or 1st login should be acknowledged from the Lync client before you run VisitorLink.
- We also recommend you add groups and contacts while you are logged into the Lync or Skype for Business client, as your user’s contacts and groups will become your “directory” in a typical VisitorLink configuration.
- If you are using a Lync 2010 server, the Lync 2013 client may still be used to connect to Lync 2010 servers.
- Locate your Configurations folder (usually c:\program files(x86)\VisitorLink\Configurations). Each sub-folder in this folder is considered a “configuration” by the VisitorLink engine
- Select an existing configuration to duplicate and make a 2nd copy of that configuration (This typically means copying the “Demo” configuration and renaming it to something like “Demo-My New Config”). When you’re finished you should have something like this:
- In the newly created Demo – My New Config directory, open the Configuration.xaml file in the text editor of your choice (or Notepad, if you don’t know what I mean) and make the following edits:
- Locate the “CommunicationProvider” xml tag in this file. In a typical, demo configuration, it will looks something like this:
- Delete this section, or – if you would prefer to keep it – comment this section out by adding the characters XML uses to specify a comment tag: !– to the opening tag and – to the ending tag (of the Directory provider, since you intend to remove both the communication provider and the directory provider). When done, it would look something like this:
- You have now disabled the “Fake” Communication provider and need to add a Lync Communication Provider. Often, you will find a commented out section that you can uncomment (by removing the !– and the – comment characters that you just added to the Fake Communications Provider and Director Provider tags. If not, the typical configuration keys for a Lync or Skype for Business Communications and Directory provider look like this:
<DirectoryProvider ProviderType=”VisitorLink.LyncProvider2013.Lync2013Provider” AssemblyName=”VisitorLink.LyncProvider2013″>
< PresenceSetting Name=”TemporarilyAway” HexColor=”#cccccc”/>
< PresenceSetting Name=”Away” HexColor=”#ffff00″/>
< PresenceSetting Name=”Busy” HexColor=”#ff0000″/>
< PresenceSetting Name=”BusyIdle” HexColor=”#ff0000″/>
< PresenceSetting Name=”DoNotDistrub” HexColor=”#ff0000″/>
< PresenceSetting Name=”Free” HexColor=”#00ff00″/>
< PresenceSetting Name=”FreeIdle” HexColor=”#00ff00″/>
< PresenceSetting Name=”Invalid” HexColor=”#cccccc”/>
< PresenceSetting Name=”None” HexColor=”#cccccc”/>
< PresenceSetting Name=”Offline” HexColor=”#dddddd”/>
< CommunicationProvider ProviderType=”VisitorLink.LyncProvider2013.Lync2013Provider” AssemblyName=”VisitorLink.LyncProvider2013″>
< Setting Property=”Host” Value=”YOURVLUSER@YOURDOMAIN.COM“/>
< Setting Property=”Domain” Value=”YOURDOMAINIFNECESSARY\YOURVLUSER”/>
< Setting Property=”Password” Value=”YOURPASSWORD”/>
- YOURVLUSER@YOUDOMAIN.COM, YOURDOMAINIFNECESSARY\YOURVLUSER, and YOURPASSWORD are only listed above as placeholders for you to replace with information unique to your installation. Be sure to specify the Host, Domain, and Password values that are appropriate for the Lync Account you intend to use. NOTE: For newer Lync installations or Lync Online, Host and Domain values may both be more like YOURVLUSER@YOURDOMAIN.COM.
- If you wish to change who is dialed for direct dial buttons, you can search for the @ symbol in the configuration file and use context clues in the XML to determined which addresses to change. For example, a typical direct dial screen might look like the following. In this example, It appears that firstname.lastname@example.org is the sip address that you may wish to change for any configuration actions that redirect to the scrnDirectDial1 screen.:
- Make sure that you only have 1 Director Provider tag and 1 Communication Provider tag uncommented in your configuration file before saving.
- The next time you run VisitorLink, you should be prompted with the new configuration you built. Choose your new “Online” configuration and see if it works.