<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lync Voice on Zachary Loeber's Blog</title><link>https://blog.zacharyloeber.com/tags/lync-voice/</link><description>Recent content in Lync Voice on Zachary Loeber's Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 12 Sep 2015 20:05:26 +0000</lastBuildDate><atom:link href="https://blog.zacharyloeber.com/tags/lync-voice/index.xml" rel="self" type="application/rss+xml"/><item><title>Skype For Business: Planning for Voice – Part 3</title><link>https://blog.zacharyloeber.com/blog/2015/09/12/skype-for-business-planning-for-voice-part-3/</link><pubDate>Sat, 12 Sep 2015 20:05:26 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2015/09/12/skype-for-business-planning-for-voice-part-3/</guid><description>&lt;p>If you have been following along this series you already know the importance of getting a recent PSTN provider bill and performing an onsite visit. Next we will go into more depth on how the site PSTN is configured with your PBX at a site. There is lots of ground to cover so lets dive right in!&lt;/p></description></item><item><title>Skype For Business: Planning for Voice – Part 2</title><link>https://blog.zacharyloeber.com/blog/2015/09/03/skype-for-business-planning-for-voice-part-2/</link><pubDate>Fri, 04 Sep 2015 03:18:40 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2015/09/03/skype-for-business-planning-for-voice-part-2/</guid><description>&lt;p>I’ve already gone over the basic phases of a Skype for Business enterprise voice deployment &lt;a href="https://blog.zacharyloeber.com/2015/08/25/skype-for-business-planning-for-voice-part-1/">in my prior article&lt;/a>. Now it is time to skip right over the first two of those phases and start preparing to replace your existing PBXs. To prepare you need to know what you are going to be replacing. In this article we will be focusing on beginning the information gathering process.&lt;/p></description></item><item><title>Skype For Business: Planning for Voice – Part 1</title><link>https://blog.zacharyloeber.com/blog/2015/08/25/skype-for-business-planning-for-voice-part-1/</link><pubDate>Tue, 25 Aug 2015 07:47:39 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2015/08/25/skype-for-business-planning-for-voice-part-1/</guid><description>&lt;p>When planning for a full Skype for Business voice deployment there are a number of elements which should be aligned and setup properly for a smooth transition. This is an introduction article for a series where I’ll provide some insight on what info you need to collect and understand for a successful PBX replacement within your organization.&lt;/p></description></item><item><title>Lync 2013: Scripting QoS Config on Edge Servers</title><link>https://blog.zacharyloeber.com/blog/2015/04/04/lync-2013-scripting-qos-config-on-edge-servers/</link><pubDate>Sat, 04 Apr 2015 21:41:51 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2015/04/04/lync-2013-scripting-qos-config-on-edge-servers/</guid><description>&lt;p>In many environments the Lync 2013 edge servers are configured in a standalone workgroup without any easy method for setting standard policies (such as GPOs). To make QoS configuration a bit less manual and error prone I’ve put together this script which can be run in an administrative powershell prompt. It will update the NLA setting (or create it if it doesn’t already exist), backup and prompt for removal any existing Qos settings, then import the registry settings for Audio, Video, and App QoS settings as defined in the script parameters.&lt;/p></description></item><item><title>Lync 2013: Scripting QoS Config on Edge Servers</title><link>https://blog.zacharyloeber.com/blog/2015/04/04/lync-2013-scripting-qos-config-on-edge-servers/</link><pubDate>Sat, 04 Apr 2015 21:41:51 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2015/04/04/lync-2013-scripting-qos-config-on-edge-servers/</guid><description>&lt;p>In many environments the Lync 2013 edge servers are configured in a standalone workgroup without any easy method for setting standard policies (such as GPOs). To make QoS configuration a bit less manual and error prone I’ve put together this script which can be run in an administrative powershell prompt. It will update the NLA setting (or create it if it doesn’t already exist), backup and prompt for removal any existing Qos settings, then import the registry settings for Audio, Video, and App QoS settings as defined in the script parameters.&lt;/p></description></item><item><title>Lync: Local and Site-to-Site Dial Plan GUI Script</title><link>https://blog.zacharyloeber.com/blog/2015/01/12/lync-local-and-site-to-site-dial-plan-gui-script/</link><pubDate>Tue, 13 Jan 2015 02:37:46 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2015/01/12/lync-local-and-site-to-site-dial-plan-gui-script/</guid><description>&lt;p>In a multiple, or even single, site VOIP deployment there are some  steps you can take to make life a whole lot easier on your end users. One of of the common features implemented across phone deployments (VoIP or otherwise) is site local and site-to-site dialing shortcuts. These shortcuts generally reduce the number of digits users have to dial to reach one another. In this post I’ll go over how you might setup such a dial plan in Lync. First I’ll go over how you might setup such a plan manually then I’ll provide a GUI tool to do the same thing.&lt;/p></description></item><item><title>Lync: Voice Route Diagram Creation Script</title><link>https://blog.zacharyloeber.com/blog/2014/12/02/lync-voice-route-diagram-creation-script/</link><pubDate>Tue, 02 Dec 2014 18:11:31 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2014/12/02/lync-voice-route-diagram-creation-script/</guid><description>&lt;p>Lync voice routing boils down to three basic components working in concert to decide call flow. It seems quite simple on paper, you assign voice policies which determine call routes based on PSTN usages (often called the ‘glue’). After looking at Lync voice routing way too many times I finally caved into producing a script to create diagrams of the things over the Thanksgiving holiday weekend.&lt;/p></description></item></channel></rss>