↧
Lync 2013 August 2014 Client Updates Released
↧
Configure Sonus gateway to translate a 408 to 504 for Lync
During some DR testing recently I came across an interesting situation that caused calls to fail in the event 1 of my 2 SIP services went down. I wanted to prove than in the event of a SIP provider/network failure, my 2 Front End pools would continue to route calls via the secondary gateway.
To simulate a SIP provider failure I pulled the network cable from the back of the Sonus gateway. I noticed fairly quickly that the gateway reported that the SIP signalling group was down. I then made a test call from a Lync user who's primary gateway was the one with the simulated failure. The call did not go through! After running some traces I found that the gateway was sending a "408 Request Timeout" message back to Lync. This is a problem because Lync will treat response codes in the 400 range as final, and will not attempt to route the call via any other configured gateways. This actually makes sense as 400 range response codes are client failure responses.
So how do we get around this? If we where to send a server failure response code from the 500 range, Lync will recognise that the server/service is down and attempt to re-route the call. To achieve this we will need to use an outbound translation rule on the Lync signalling group to change a 408 (Client Request Timeout) to a 504 (Server Timeout).
First create a "Message Rule Table" to add the new rule to:
![]()
Create a new "Status Line Rule" rule as follows:
![]()
Add the rule properties:
![]()
In my case I used a regex replacement to achieve a 408 to 504 re-write:
![]()
Once your translation rule has been added, go to the Lync "Signalling Group" and add as an "Outbound Message Manipulation"":
![]()
To verify the change has had the desired effect I used the Sonus LX tool. You should now see 2 invites - the first is an attempt to route the call via the primary gateway, the second is the call trying the secondary gateway.
![]()
The request to route via the down signalling group results in a 408 being generated:
![]()
The translation rule in the Lync signalling group translates the 408 to a 504 and sends it to Lync:
![]()
To simulate a SIP provider failure I pulled the network cable from the back of the Sonus gateway. I noticed fairly quickly that the gateway reported that the SIP signalling group was down. I then made a test call from a Lync user who's primary gateway was the one with the simulated failure. The call did not go through! After running some traces I found that the gateway was sending a "408 Request Timeout" message back to Lync. This is a problem because Lync will treat response codes in the 400 range as final, and will not attempt to route the call via any other configured gateways. This actually makes sense as 400 range response codes are client failure responses.
So how do we get around this? If we where to send a server failure response code from the 500 range, Lync will recognise that the server/service is down and attempt to re-route the call. To achieve this we will need to use an outbound translation rule on the Lync signalling group to change a 408 (Client Request Timeout) to a 504 (Server Timeout).
First create a "Message Rule Table" to add the new rule to:
Create a new "Status Line Rule" rule as follows:
Add the rule properties:
In my case I used a regex replacement to achieve a 408 to 504 re-write:
Once your translation rule has been added, go to the Lync "Signalling Group" and add as an "Outbound Message Manipulation"":
To verify the change has had the desired effect I used the Sonus LX tool. You should now see 2 invites - the first is an attempt to route the call via the primary gateway, the second is the call trying the secondary gateway.
The request to route via the down signalling group results in a 408 being generated:
The translation rule in the Lync signalling group translates the 408 to a 504 and sends it to Lync:
↧
↧
PowerShell Manager - Script Manager
PowerShell Script Manager is my first C# attempt to create something useful for the Microsoft community. Please let me know if you find this tool useful and I will make sure that it is improved with your feedback.
What is PowerShell Manager?
PowerShell Manager is a script manager allowing you to save and assign variables to commonly used scripts. PowerShell Manager allows you to create multiple profiles so that commonly used variables can saved and reused on a per profile/customer basis.
![]()
![]()
![]()
![]()
Important Notes
I will work on documentation as time permits, however some important notes:
Download
PSManager.zip
What is PowerShell Manager?
PowerShell Manager is a script manager allowing you to save and assign variables to commonly used scripts. PowerShell Manager allows you to create multiple profiles so that commonly used variables can saved and reused on a per profile/customer basis.
Important Notes
I will work on documentation as time permits, however some important notes:
- PowerShell scripts imported in to PowerShell Manager require defined parameters so that they can be passed in to the script. If your script does not have parameters you can still run the script with no parameters.
![]()
- Script file names are unique across all profiles. If you import a script a that currently exists you will be asked if you want to overwrite the existing one or just reference it.
![]()
If you have a script that is customized to a particular customer, rename it accordingly.
- Similarly when you delete a script you can select "Yes" to delete it from all profiles, or "No" just to remove the reference to it in the current profile.
![]()
Download
PSManager.zip
↧
Lync Phone Edition (LPE) Log Viewer
Lync Phone Edition Log Viewer allows you to view and filter the logs held on the Lync Phone Edition devices. These logs are actually very useful once the garbage has been removed, and reveal a lot about the sign-in process and the errors that come with it.
![]()
Device logs are actually available directly from the phone by using FTP e.g. ftp://<ip address of phone>
In the log viewer you can specify the IP address of the phone (optional) then browse to select the .clg log file. You can find the IP address of your phone by selecting Menu -> System Information and then looking for the IP address received via DHCP.
![]()
The log files are in .clg format which is not humanly readable so the tool first converts the file to text using readlog.exe. Once in text format the data is processed removing most of the garbage that is un-useful to troubleshooting, and displays this on screen. At this point you can filter your results for iinformational warning and error messages. Additionally there is an "Easy View" option which displays the information I have learnt to be useful (feel free to let me know if I have missed anything).
![]()
This is version 1, I will be improving the tool as time permits so please leave feedback.
Download
Download the tool here, and happy troubleshooting!
Device logs are actually available directly from the phone by using FTP e.g. ftp://<ip address of phone>
In the log viewer you can specify the IP address of the phone (optional) then browse to select the .clg log file. You can find the IP address of your phone by selecting Menu -> System Information and then looking for the IP address received via DHCP.
The log files are in .clg format which is not humanly readable so the tool first converts the file to text using readlog.exe. Once in text format the data is processed removing most of the garbage that is un-useful to troubleshooting, and displays this on screen. At this point you can filter your results for iinformational warning and error messages. Additionally there is an "Easy View" option which displays the information I have learnt to be useful (feel free to let me know if I have missed anything).
This is version 1, I will be improving the tool as time permits so please leave feedback.
Download
Download the tool here, and happy troubleshooting!
↧
Lync Updates Aug/Sept
The Lync Updates page has been updated to include the recent server, client and phone updates that were released between August and September.
http://www.lync.geek.nz/p/lync-updates.html
Updates have been downloaded and added to the public archive here.
http://www.lync.geek.nz/p/lync-updates.html
Updates have been downloaded and added to the public archive here.
↧
↧
Lync Access Edge Service requires reboot before you can sign-in with newly added SIP domain
If you have recently added a SIP domain to Lync 2013 and you are pulling your hair out because you cannot sign-in externally, then here's what you need to know....
Being a Lync hoster we need to add SIP domains on a regular basis (well our provisioning engine does). In Lync 2010 a new SIP domain could be provisioned and enabled in the time it took for CMS replication to occur. As of Lync 2013 RTM this is no longer the case; now every time a SIP domain is added the Edge server Access Edge service needs to be restarted before you can login using the newly added SIP domain.
![]()
This is less than ideal when you operate a highly available hosted Lync platform! To this date I have not been able to find a solution to the problem, nor have I been able to find a reason for this change - bug/design? If anyone knows something I don't please let me know.
How do you know you have this problem?
Client Error
The Lync client will likely throw the following error message "The server is temporarily unavailable. If the problem continues, please contact your support team"
![]()
Being a Lync hoster we need to add SIP domains on a regular basis (well our provisioning engine does). In Lync 2010 a new SIP domain could be provisioned and enabled in the time it took for CMS replication to occur. As of Lync 2013 RTM this is no longer the case; now every time a SIP domain is added the Edge server Access Edge service needs to be restarted before you can login using the newly added SIP domain.
This is less than ideal when you operate a highly available hosted Lync platform! To this date I have not been able to find a solution to the problem, nor have I been able to find a reason for this change - bug/design? If anyone knows something I don't please let me know.
How do you know you have this problem?
Client Error
The Lync client will likely throw the following error message "The server is temporarily unavailable. If the problem continues, please contact your support team"
Server Error
If you look at the SIP traces you should see this something similar to the following:
Severity: warning
Text: The source domain of the remote user client's message is not in the list of internally supported domains
Result-Code: 0xc3e93d72 SIPPROXY_E_EPROUTING_MSG_CLIENT_DOMAIN_NOT_INTERNAL
SIP-Start-Line: REGISTER sip:sipdomain.comSIP/2.0
↧
Disable Telephony in Lync 2013 Client
There may be situations where you need to disable audio/video telephony in the Lync client. This is particularly useful where you want to deploy Lync in a terminal services/session host environment, and don’t want users to be able to answer audio/video calls. The result in the Lync client is the removal of any audio/video settings or actions. Additionally inbound audio video call notifications will not be receive.
To disable telephony the following registry key needs to be added:
Reg Add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\15.0\Lync" /V "TelephonyMode" /D 5 /T REG_DWORD /F
Note: You can also add this to HKEY_CURRENT_USER
You can also do this manually in regedit. You will first need to create the keys Office -> 15.0 -> Lync, then a DWORD with the following values
↧
Repair Certificate
To repair an imported certificate that has lost is public key run the following command from command prompt:
certutil –repairstore my "SerialNumber"
![]()
![]()
certutil –repairstore my "SerialNumber"
↧
Access Denied to Address Book Folder
After installing a new Lync 2013 Standard Edition server, the event log continually presented the following error:
---------------------------
Address Book Server has encountered an unexpected exception.
Exception: Access to the path '\\LyncServerFQDN\LyncFileShare\1-WebServices-2\ABFiles\00000000-0000-0000-0000-000000000000\00000000-0000-0000-0000-000000000000' is denied.
Exception Type: System.UnauthorizedAccessException
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
at Microsoft.Rtc.ABServer.ABServer.ReadContactsFromSqlAndWriteToOutput(NormalizeRuleSet normalizationRules, SqlConnection sqlConnection, List`1 sinks)
at Microsoft.Rtc.ABServer.ABServer.Synchronize()
Cause: Internal Error
Resolution:
![]()
---------------------------
Address Book Server has encountered an unexpected exception.
Exception: Access to the path '\\LyncServerFQDN\LyncFileShare\1-WebServices-2\ABFiles\00000000-0000-0000-0000-000000000000\00000000-0000-0000-0000-000000000000' is denied.
Exception Type: System.UnauthorizedAccessException
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
at Microsoft.Rtc.ABServer.ABServer.ReadContactsFromSqlAndWriteToOutput(NormalizeRuleSet normalizationRules, SqlConnection sqlConnection, List`1 sinks)
at Microsoft.Rtc.ABServer.ABServer.Synchronize()
Cause: Internal Error
Resolution:
Contact Product Support Services.
---------------------------
To resolve the issue I had to manually add the following local system groups to the folders sharing permissions:
LOCAL\RTC Local Administrators CHANGE,READ
LOCAL\RTC Local Config Replicator CHANGE,READ
LOCAL\RTC Server Local Group CHANGE,READ
LOCAL\RTC Component Local Group CHANGE,READ
After adding these and running Update-CsUserDatabase I immediately could see the creation of the expected Address Book files.
Checking other deployments these permissions were not listed, so I am unsure why in this case they were required.
↧
↧
Lync Server 2015 to be renamed as Skype for Business Server
Microsoft has just announced that Lync will be renamed to Skype for Business. The underlying technology is not changing, and the 2 products will remain distinctly separate products, but features and client experience will become similar across the business and free versions.
For more information see the Office Blog. Also Matt Landis has a great summary here.
![]()
For more information see the Office Blog. Also Matt Landis has a great summary here.
Microsoft Frequently Asked Questions
What did Microsoft announce on November 11, 2014?
In Gurdeep Pall’s blog on November 11, 2014, Microsoft introduced Skype for Business which brings together the familiar experience and user love of Skype with the enterprise security, compliance and control of Lync. In the first half of 2015, the next version of Lync will become Skype for Business with a new client experience, new server release, and updates to the service in Office 365. We believe that Skype for Business will again transform the way people communicate by giving organizations reach to hundreds of millions of Skype users outside the walls of their business.
Why are you renaming Lync to Skype for Business?
Skype for Business brings together the familiar experience and user love of Skype with the enterprise security, compliance, and control from Lync. End users get a familiar Skype experience that is as easy to use at work as it is at home. Organizations gain reach into a network of hundreds of millions of Skype users across the globe. And, IT remains confident they are providing secure, reliable, high-quality communications to their organizations.
Why announce rebrand in advance of the general availability release?
We are making this announcement now in order to give our customers time to learn about the product and prepare their organizations so they can deploy when the product is released. We are also using this time to help partners build the offerings and capabilities to support those deployments.
When is Lync actually changing to Skype for Business?
Lync will become Skype for Business in the first half of 2015 with a new client experience, new server release, and updates to the service in Office 365.
Is there any change to the existing Skype brand used by consumers?
No. The consumer experience that people around the world know and love will continue to be referred to as Skype. Consumers will still be able to use Skype the way they always have – with the same user account, contacts, user interface and functionalities that they have always used.
When will there be future announcements about Skype for Business?
We will be launching the new brand and product in the first half of 2015. We will keep our customers informed. Lync is becoming Skype for Business – First Half of 2015
What should I do now that I know that Lync is becoming Skype for Business in the first half of 2015?
- Now that you know Lync will becoming Skype for Business in 2015, we recommend that you:
- Download the Skype for Business – Partner Kit from the Skype for Business Partner Kit in the Partner Marketing Center on the Microsoft Partner Network.
- Review all of the materials in the kit to understand why the brand is changing, when it takes effect in your area, and what it means for customers.
- Contact customers using the email template provided in the kit to let them know that Lync will become Skype for Business in the first half of 2015 and then set up calls or meetings to present the Skype for Business customer presentation.
- Register and join us at our Office 365 Summits starting in January 2015 to learn what you need to know to help your customers deploy and adopt Skype for Business.
What should I say to customers about the new brand?
Share your enthusiasm for announcement. Tell customers about the value Skype for Business will bring to their organization. Microsoft is bringing together the best of Skype and Lync without losing any of the features, security and manageability that they care about. They will see further adoption of unified communications in their businesses and the cost and efficiency benefits that go along with that because of the familiar user experience that hundreds of millions of Skype users engage with every month. Furthermore, this change truly connects them to the vast Skype network which includes many of their customers and partners.
It’s important to reassure customers that the features they care about and use the most in Lync are not going away. Remind them that as a Microsoft partner, your close connection to Microsoft best positions you to continue meeting all their development, deployment, and service needs as this product evolves.
When do I use the Skype for Business name and logo in my marketing materials, website, and customer communications?
Lync is the current product in market and the materials do not change at this time. Partners should not use Skype for Business logo/brand prior to the next release, which will be available in first half of 2015. Our partners will be provided the Skype for Business brand guidelines in the coming months in time for the new release. It will outline when and how to apply the Skype for Business name and logo to your materials and communications. Do not use the brand or logo prior to receiving the brand guidelines. Lync is becoming Skype for Business – First Half of 2015
Are you still committed to delivering Enterprise Voice in the Cloud?
Absolutely. We remain committed to our roadmap including the future delivery of enterprise voice in the cloud.
How will the product experience for Lync change when it’s Skype for Business?
The best features of Lync and Skype have been combined in a Skype-inspired user interface. The user experience is more tightly aligned between Skype for Business and Skype so the features are similar and intuitive whether you are in a work environment or communicating with friends and family.
- Skype for Business will include other new features such as:
- Familiar Skype icons for calling and video
- A call monitor to keep active calls visible while switching between apps
- Enterprise connection with the Skype network with IM, audio, and video
- A simpler upgrade and patch process for Skype for Business server
- and more…
Will Lync users lose any functions or features when the product becomes Skype for Business?
No. Skype for Business will deliver the same features and functionality as well as control, security, and reliability that enterprise customers expect. For instance, Skype for Business Admins will be able to control when and how the users interface is displayed for their users. This additional control means they can deliver Skype for Business on their terms.
Can I try out Skype for Business before it becomes available?
We have nothing to announce at this time, and will keep customers informed as more information becomes available.
↧
Application Sharing fails in Server 2012 R2 due to changes in how TLS sessions are cached
If you are running Server 2012 R2, due to changes in how TLS sessions are cached, you may see the following error message in the event log. I my experience this effected a users ability to use application sharing e.g. whiteboard, polls share application etc.
![]()
Log Name: Lync Server
Source: LS MCU Infrastructure
Date: 10/15/2013 4:02:20 AM
Event ID: 61045
Task Category: (1022)
Level: Error
Keywords: Classic
User: N/A
Computer: LyncFE01.contoso.local
Description: The DATAMCU was not able to stay connected to the Front End over the C3P channel (HTTPS Connection).
The Web Conferencing Server failed to send C3P notifications to the focus at https:// LyncFE01.contoso.local:444/LiveServer/Focus.
Cause: The Front End may not be running correctly or may be unreachable over the network (broken HTTPS connection) from the MCU. Unavailability of The C3P channel affects conference controls, and can also prevent users from joining, starting conferences.
Resolution: Verify that the Front End server is running correctly and that network connectivity and an HTTPS Connection can be established between the MCU and the Front End server.
--------------------------------------------
To resolve this add the following registry key and restart your Lync services:
![]()
Note
http://support.microsoft.com/kb/2901554
--------------------------------------------
Event 61045Log Name: Lync Server
Source: LS MCU Infrastructure
Date: 10/15/2013 4:02:20 AM
Event ID: 61045
Task Category: (1022)
Level: Error
Keywords: Classic
User: N/A
Computer: LyncFE01.contoso.local
Description: The DATAMCU was not able to stay connected to the Front End over the C3P channel (HTTPS Connection).
The Web Conferencing Server failed to send C3P notifications to the focus at https:// LyncFE01.contoso.local:444/LiveServer/Focus.
Cause: The Front End may not be running correctly or may be unreachable over the network (broken HTTPS connection) from the MCU. Unavailability of The C3P channel affects conference controls, and can also prevent users from joining, starting conferences.
Resolution: Verify that the Front End server is running correctly and that network connectivity and an HTTPS Connection can be established between the MCU and the Front End server.
--------------------------------------------
To resolve this add the following registry key and restart your Lync services:
Note
- You can disable this value without compromising the security of the system. The system will revert to handling TLS sessions exactly like the sessions were negotiated in earlier Windows Server operating systems.
- Lync Server 2013 is supported by Windows Server 2012 R2 when this registry workaround is performed.
- Click Start, type regedit in the Start search box, and then click regedit.exe in the results list.
- Locate the following registry subkey:
- HKLM\System\CurrentControlSet\Control\SecurityProviders\Schannel
- Right-click Schannel, and then click New DWORD (32-bit) value.
- Type EnableSessionTicket, then press Enter.
- Right-click EnableSessionTicket, and then click Modify.
- Change the existing value to 2, and then press Enter.
- Exit Registry editor.
- Open the Lync Server Management Shell.
- Run the following Lync Server PowerShell commands in the given order:
- Stop-CsWindowService
- Start-CsWindowsService
http://support.microsoft.com/kb/2901554
↧
New Zealand's first Crestron Lync Room System (LRS)
First Crestron Lync Room System deployed by Lexel in Auckland, NZ - Very powerful collaboration system!!
![]()
↧
Lync Room System (LRS) Configuration
Only screenshots for now, will update my experiences soon as time permits.
![]()
Assign Policies: ![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Useful Information:
- New-CsLyncRoomSystem.ps1 – Easily Deploy Lync Room Systems
- Microsoft Lync Room System Deployment Guide
- Lync Room System won't show the Exchange Calendar
The End product:
Lync/Exchange Setup:
- Run .\New-CsLyncRoomSystem.ps1 to configure Lync and Exchange
- If you dont already have suitable user policies for LRS these will need to be created
- Ensure that you assign a UserServicePolicy with Unified Contact Store (UCS) disabled
- Grant Conferencing Policy
Grant-CsConferencingPolicy -PolicyName "LyncRoomSystem Policy" -Identity "LRS User Account" - Grant UserServicePolicy
Grant-CsUserServicesPolicy -PolicyName "LyncRoomSystem Policy" -Identity "LRS User Account" - Grant Dial Plan Policy
Grant-CsDialPlan -PolicyName "LyncRoomSystem Policy" -Identity "LRS User Account" - Grant Voice Policy
Grant-CsVoicePolicy -PolicyName "LyncRoomSystem Policy" -Identity "LRS User Account" - Grant External Access Policy
Grant-CsExternalAccessPolicy -PolicyName "LyncRoomSystem Policy" -Identity "LRS User Account"
LRS Configuration Screenshots:
↧
↧
Get-DNS: Convert DNS Query Results to PowerShell Object
PowerShell v3 and below does not have any built in commandlets to assist with DNS resolution. Additionally even if you have a higher version of PowerShell, these commandlets will still not be available unless you are running Windows 8.1 or Windows Server 2012 R2.
This script uses NSLOOKUP to query DNS records and converts the output to a PowerShell object that can be used more easily in scripts that need to perform DNS lookups. Currently it only support A, CNAME and SRV records.
![]()
Due to the complexities of parsing text returned by NSLOOKUP, you may find that some DNS servers results may be incorrectly handled. If you experience this please let me know the circumstances and I will attempt to resolve the issue in a future release.
Download
This script uses NSLOOKUP to query DNS records and converts the output to a PowerShell object that can be used more easily in scripts that need to perform DNS lookups. Currently it only support A, CNAME and SRV records.
Due to the complexities of parsing text returned by NSLOOKUP, you may find that some DNS servers results may be incorrectly handled. If you experience this please let me know the circumstances and I will attempt to resolve the issue in a future release.
Download
↧
Annoying in-ear headset tones
Occasionally I see Lync headsets that decide to play dial tone in the users ear while in a call. The normal (somewhat annoying) scenario to have dial tone generated in the ear is when the dial button is pressed on the headset (which also brings the Lync client in to focus), but after the call is made it should be removed. When this doesn't happen it is usually down to the headset, however I have not found a consistent pattern of steps to resolve it. It appears to be something to do with how the headset has paired with the base station. Try the following:
Can the dial tone be turned off altogether?
The dial tone is actually generated by the Lync client, and can be turned off in Windows Sounds by following these steps.
From Lync got to the settings cog -> "Ringtones and Sounds" -> "Sound Settings":
![]()
Under the Lync category select “Dial Tone”, then change “Sounds” to “(none)”:
![]()
What about other annoying tonnes?
If any of the other tones get on your nerves you can disable them in the same way. One of my favorites is the second incoming call alert. If you wear a headset you will likely hear both the Lync alert and the device alert.
The second incoming call alert can be disabled, but this will not stop any headset generated notifications (normally a short beep in the ear).
![]()
- Remove power from base station and unplug USB
- Power off the headset
- Plug the power back then connect the USB back to the PC
- Power on the headset and re-pair
Can the dial tone be turned off altogether?
The dial tone is actually generated by the Lync client, and can be turned off in Windows Sounds by following these steps.
From Lync got to the settings cog -> "Ringtones and Sounds" -> "Sound Settings":
Under the Lync category select “Dial Tone”, then change “Sounds” to “(none)”:
What about other annoying tonnes?
If any of the other tones get on your nerves you can disable them in the same way. One of my favorites is the second incoming call alert. If you wear a headset you will likely hear both the Lync alert and the device alert.
The second incoming call alert can be disabled, but this will not stop any headset generated notifications (normally a short beep in the ear).
↧
Get Scheduled Lync Meetings from SQL
The following query will get conferences from the Lync RTC database. From a Lync Standard Edition server its in the RTCLOCAL instance, otherwise you'll find it in the backend SQL server.
USE RTC
--SELECT * FROM Resource
--SELECT * FROM Conference
SELECT ConfId,
CASE
WHEN OrganizerId IS NOT NULL THEN (SELECT TOP 1 UserAtHost FROM Resource WHERE OrganizerId LIKE ResourceId)
END AS 'UserSIPAddress',
Title,
ProvisionTime,
LastUpdateTime
FROM Conference
![]()
USE RTC
--SELECT * FROM Resource
--SELECT * FROM Conference
SELECT ConfId,
CASE
WHEN OrganizerId IS NOT NULL THEN (SELECT TOP 1 UserAtHost FROM Resource WHERE OrganizerId LIKE ResourceId)
END AS 'UserSIPAddress',
Title,
ProvisionTime,
LastUpdateTime
FROM Conference
↧
Backup Sonus SBC 1k/2k using PowerShell and the REST API
Using PowerShell 3.0+ you can backup the Sonus 1k/2k SBC's using the REST API.
Firstly you will need to create a rest user on the SBC:
![]()
Then simply run the following script in Powershell, or setup a scheduled task to automate the process:
Firstly you will need to create a rest user on the SBC:
Then simply run the following script in Powershell, or setup a scheduled task to automate the process:
↧
↧
Highlight Current/Active Menu Using Javascript
I recently wanted to convert the very basic menu on my Blogger site, to one that supported drop down menus. This was surprisingly easy to do due to the flexibility of Blogger and its built in customisation tools. Where it got tricky was highlighting the currently active menu item, but thanks to a good friend of mine Olie Mason, it was short work.
To see how it works, take a look at the menu items in this blog. The example provided supports menus to 2 levels deep.
![]()
![]()
Select "Add a Gadget" and select "HTML/JavaScript":
![]()
![]()
To see how it works, take a look at the menu items in this blog. The example provided supports menus to 2 levels deep.
JavaScript
Insert the following JavaScript code inside a <script> block above the <head> tag in the HTML editor located under "Template" -> "Edit HTML":
CSS
Now we need to add some custom CSS to style the menu. You do this from "Template" -> "Customise" -> "Advanced" -> "Add CSS". The below snippet should work for you, however you may need to customise to suit your page:
HTML
Lastly we need to add an HTML module to the navigation area in the template. From "Layout" settings, add a new gadget to the area you want the menu to be displayed. You may need to remove the default one before you can add your new one, just select "Edit" then "Remove" if that's the case.Select "Add a Gadget" and select "HTML/JavaScript":
Leave "Title" empty, and paste the following code snippet in the "Content" box:
↧
What's New in Lync Server 2013?
In preparation for my "Whats new in Skype for Business?" article, I dug up this unpublished blog. I'm a bit late to the party here I know! In any case hopefully some of you find this information useful.
Server Roles
DR/High Availability
Enterprise Voice
Integration with Lync Online
Persistent Chat
Clients
Other
More Information
New Server Features - http://technet.microsoft.com/en-us/library/gg425795.aspx
New Client Features - http://technet.microsoft.com/en-us/library/gg398192.aspx
Server Roles
- Monitoring and Archiving server is now co-located on the Front End server which reports directly to the monitoring/archiving backend database.
- A/V conferencing is now always installed on the Front End server.
- The uncommonly used Director role is no longer recommended but still available as an option.
- Persistent Chat is a new server sole that replaces Group Chat
- XMPP federation is now fully integrated
DR/High Availability
- Backup registrar is taken a step further allowing users maintain nearly all functionality in the event of a failed pool. Previously with Lync 2010 only voice was resilient. User data is now replicated between paired pools. Response Groups are still not highly available but can easily be backed up and restored manually within a 15 minutes.
- In Lync 2010 when the backend database goes down Lync goes in to a limited functionality mode. With Lync 2013 the Front End servers keep a full copy of the SQL backend databases. Lync 2013 also supports SQL mirroring on the back-end databases.
Enterprise Voice
- In Lync 2010 a Gateway could only be associated with 1 Mediation server without the use of DNS trickery. Now in Lync 2013 Gateway/Trunks can be associated to multiple Mediation servers.
- Inter-trunk routing is now supported so Lync can now be responsible for all call routing e.g. Lync could route a call from the PSTN to a legacy phone system.
- Trunk translation rules can now not only be applied to the “called party” but also the “calling Party”. This makes Caller ID presentation is much more manageable in Lync 2013.
- Delegates can now set up simultaneous ringing to their mobile devices for incoming calls to their managers. This provides delegates with more flexibility, enabling them to answer calls on behalf of their manager without being tied to a desk phone.
- With Voicemail Escape Lync can determine if the call was answered immediately without ringing (for example if the call goes straight to voicemail) and pull the call back so it continues to ring on the user’s other endpoints.
Integration with Lync Online
- Hybrid deployments now support a mixture of Lync on-premises and Lync Online users.
Persistent Chat
- Persistent Chat replaces Group Chat, and is now fully integrated in to Lync as a new server role. The Lync 2013 client supports this natively.
Clients
- Vastly revamped Windows simplifies user experience
- Windows Phone, iOS, and Android mobile clients can now join meetings as well as make audio/video calls via WiFi or mobile data
- Lync Web App has had a major overhaul making it much easier to use and now with full conference support
- Lync Room System specifically designed for meeting rooms
Other
- IPv6 supported
- VDI plugin for virtual desktop environments
- HD support up to 1080p. Clients now use best supported video quality e.g. If HD is supported by some participants but not others Lync will present the best option for each client device. Previously Lync 2010 would reduce video quality for all participants to match the least capable device.
- Skype Federation
- Unified Contact store allows Lync contacts to be stored in Exchange. This includes a feature to merge duplicate contacts.
- Archiving integration with Exchanges Legal Hold feature
- Response Groups now support the delegation of managers and administrators
More Information
New Server Features - http://technet.microsoft.com/en-us/library/gg425795.aspx
New Client Features - http://technet.microsoft.com/en-us/library/gg398192.aspx
↧
What's New in Skype for Business Server 2015?
Skype for Business Server 2015 is the successor to Lync Server 2013, and is expected to be released during the first half of 2015 This is a running commentary of the Skype for Business (Skype4B) features that are available for public consumption.
Server Roles
Enterprise Voice
DR/High Availability
Migration Options
Other
Server Roles
- Video Interop Server (VIS) is a new role introduced to enable interop with conferencing vendor products. VIS is essentially a video gateway between Skype4B and legacy video conferencing solutions (VTC's)
- VIS has no transcoding capability so VTC's will need to support H.264
- VTC users can call Skype4B users, but not the other way around
- Call Quality Dashboard (CQD) server role
- The CQD in Skype4B leverages SQL Analysis Services (SSAS) to improve BI within Skype for Business
- Skype for Business client that will ask the user for their feedback at the end of a call. This data can be compared to what the server has reported
![]()
- Revamped Windows client more closely matching the Skype (consumer) user experience
![]()
- Improvements to smartphone apps, in particular:
- Resolving the long delay sending IM's to mobile users
- Incoming IM's being lost - This will be addressed by applying the "Auto Accept" logic used by the desktop clients to accept IM's on the best available endpoint
- Conversation history is addressed by the introduction of a uniform server-based conversation history available to all endpoints. The implementation leverages Lync Storage Services to store conversation history directly in Exchange using EWS, and thus removing the dependency on the client to do so. This will only be supported on Exchange 2013+
- Multi-factor authentication
- The Skype4B Web App will support WebRTC removing the need for client plugins
- Rooms get the Surface Hub, a 55” HD or 84” 4K collaboration tool. At this stage it is not Microsoft's intention to replace Lync Room System
![]()
- Call via Work introduced, allowing outbound calls to be made via existing PABX phones
![]()
![]()
- Response Groups scale vastly improved - Supports 800 agent groups, 400 IVR groups, and 2400 agents per pool
- Remote Call Control depreciated in the Skype4B client. It will remain in the Lync 2013 client for backward compatibility
Meetings
- Meetings no longer expire after the scheduled date, and can be kept alive for up to a year. If the meeting is missed it be be re-scheduled without re-creating the Online Meeting.
- The meeting service now has automatic and silent retry capabilities to limit the visibility of these to meeting attendees
- Office Web Apps server is now protected from Domain Controller outages
- PowerPoint presentations are not made aware to attendees until they are uploaded and ready to be presented
- Screen sharing frame rates are up from 2 to 8, which Microsoft say will allow standard definition video to be stream to attendees
- Updates will be provided for Lync Room System including built in server control panel, "Room PC View" allow input another system to be presented, as well as improvements to user interface
DR/High Availability
- SQL Always on support
- Cross subnet not supported
- Supports only Synchronous commit mode
- Does not support read-only secondary replicas
- No offsite replica support (Azure)
- SQL Mirroring is depreciated
- Windows Fabric v2 introduced. Promised to address some of the issues with pool failover and startup. Start-CsPool commandlet introduced.
- Conferencing will now continue to operate during failover
- Support for in-place upgrades of purely Lync 2013 environments. In-place upgrades can be completed offline, or online if you have multiple pools.
![]()
- In-place upgrade requirements:
- Install CU5+ latest hotfix to Lync 2013 topology
- PowerShell RTM version (6.2.9200.0) or later
- Have at least SQL server 2012 SP1 installed
- Windows Server 2008 R2 - KB2533623
- Windows Server 2012 - KB2858668
- Windows Server 2012 R2 - KB2982006
- No schema updates required
- Lync 2010, OCS or mixed environments will need to follow the normal migration procedures as with Lync 2013
Server Patching
- Simplified process to apply updates
![]()
- Reliable checks for pool readiness built in to update commands
- Progress indicator to give a graphical representation on the update process.
- During installation of Skype for Business there is a new option to download and apply updates
Deployment Options
- Purely on-premise
- Purely online
- Hybrib mix of the above
Additionally Skype4B can be deployed in a resource forest, however Microsoft are discouraging this, mainly because hybrid is not supported in this scenario.
New Commandlets
- Start-CsPool
- Stop-CsPool
- Invoke-CsComputerFailover
- Invoke-CsComputerFailback
- Skype Federation improved - Voice and Video, search Skype contacts by name
- SILK codec (Skype) will be the default for peer to peer calls
- Peer to Peer screen sharing bandwidth reduced 10x when compared to Lync 2013
- IM history will now Sync across all devices
↧