TopBanner

Get-csRgsWorkflowDiagram: Auto Diagram Your Skype for Business (Lync) Response Groups With Visio

 

Get-csRgsWorkflowDiagram uses Powershell to output your Response Group(s) to a txt file that can be imported into Visio to display in a visual format that is much easier to follow. Below is an example:

image

You can run Get-csRgsWorkflowDiagram without command line input and it will prompt you csv output path and filename and response group name.

image

Or you can input parameters from command line: (the below will output all response groups to n:\temp\r55.csv)

image

The below example will output a specific response group named “_Int Service Group” and will open Vision and the Org Chart Wizard after its done.

image

NOTE: Passing –ResponseGroupName value of “*All” will add ALL response groups to the file. Visio will chart one RGS per Visio page.

Import the CSV File Into Visio

This can be done using command line: (where ‘N:\temp\r55.csv’ is visio csv file)

OrgWiz.exe /FILENAME=N:\temp\r55.csv /NAME-FIELD=Name /MANAGER-FIELD=ReportsTo /DISPLAY-FIELDS=Name,Title,More

NOTE: OrgWiz.exe is located in the Office folder (something like C:\Program Files (x86)\Microsoft Office\Office15)

…or using the Org Chart Wizard:

image

We will be creating this “Org chart” from “Information that’s already stored in a file or database” and Next

image

Our script output the file to .csv so we will select “Text or Excel file” and click Next

image

Enter the path and filename and click Next

image

Define the org chart by select Name:=Name; Reports to:=ReportsTo

image

Now select what fields you want displayed on each object in the chart. (your discretion)

image

We are currently not populating a “Shape Data Field” so you can let this empty/as it.

image

How Org Chart” is designed: just let defaults

image

The Visio Org Chart Wizard has a bug in that it does render Org Charts in sorted order so you might want to go to  Design | Re-Layout Page to sort objects by ID.

image

You could also select all object and change color/shapes.

Voila-Visio Diagram (Hung Group example)

image

Example of a Interactive Response Group:

image

Current limitations:

  • Currently this tool is BETA
  • Get-csRgsWorkflowDiagram only follows “DefaultAction” branch of RGS Workflow (to be extended in subsequent versions) Now included in script
  • 1 RGS Workflow at a time. (in future can generate all or a group of RGS at one time) Now included in script.
  • Does not support Interactive Response Group at this time. (working on it)
    • IRG are now supported but Queue details are not charted (under a question) at this time
  • There is a command line switch (-OpenVisio) that will open Visio and the Org Chart Wizard, but at the moment it does not automate the Visio Org Chart Wizard.
  • The script is not signed, so you may need to copy past to run at this time.

Download Here:
http://gallery.technet.microsoft.com/office/Get-csRgsWorkflowDiagram-b4465297

Update History:

  • 1.00 – Does Queue based RGS diagrams
  • 1.01 – Added IRG based RGS
  • 1.01 – Ability to diagram all RGS Workflows at one time using –ResponseGroupName *All
    • 1 RGS Workflow per Visio page
  • 1.01 – many fixes
  • 2.00 – coming

I plan to add Visio Org Chart Import Wizard into PowerShell when I get a moment. If you have any suggestions for improvement, please comment or contact me.

Download Here: http://gallery.technet.microsoft.com/Get-csRgsWorkflowDiagram-b4465297

Wish you could diagram Exchange UM Auto Attendants using Visio too? You can!
http://windowspbx.blogspot.com/2014/01/get-umautoattendantdiagram-auto-diagram.html

Other:
http://visioautomation.codeplex.com/documentation

How to Automate Visio Org Chart Wizard via @visprocess: Click Here

snom Announces New snom 715: Adds Gigabit & USB

image

snom 715 expands on existing snom 710 (see 1st Impression review here).

New features that I notice:

  • Gigabit
  • USB (for optional WIFI dongle)

Considering the snom 710 is Lync Qualified I expect this model to be as well.

Brochure:
http://downloads.snom.net/documentation/data_snom715_en.pdf

Lync Server 2013 & Lync Phone Edition Get Updates In Cumulative Update January 2014

Looks like CU January 2014 is largely fixes.

Lync Phone Edition gets some fixes: Click Here

  • 2918039 Voice is distorted when you resume a call from hold by using Lync Phone Edition for Aries telephone

  • 2918044 Exchange integration fails in Lync Phone Edition when an Exchange mailbox is enabled for the Exchange Online service

Lync Server 2013 Gets features & fixes: Click Here

  • Feature
    • Click Here "operator assistance" feature during a PSTN dial-in conference in a Lync Server 2013
      • This update enables administrators to provide support for the *0 Dual Tone Multi Frequency (DTMF) command in a public switched telephone network (PSTN) dial-in conference in a Microsoft Lync Server 2013 environment. After the update is installed, a PSTN caller is able to be transferred to an operator number that the administrator defines.
      • To enable this feature, the administrator must provide a valid help desk telephone number in the OperatorLineUri parameter by using the New-CsDialInConferencingDtmfConfiguration cmdlet or the Set-CsDialInConferencingDtmfConfigurationcmdlet.
  • Fixes
    • 2912334 Event ID 57006 is logged when you cannot restart the Lync Server 2013 front-end service

    • 2912338 Can't call Enterprise Voice-enabled users when the users have the same main telephone number in a Lync Server 2013 environment

    • 2912340 An external call is routed based on Location-Based Routing that is configured for internal AD sites in a Lync Server 2013 environment

    • 2912342 Lync Server 2013 supports TDE in SQL Server 2008 or a later version on a back-end server

    • 2912343 Event ID 1001 is logged when the RTCSrv.exe progress crashes on a Lync Server 2013 Edge server

  •  

image

#Sonus SBC1000/2000 Gateways Report QoE to #Lync Monitoring in FW v3.1

image

It looks like Sonus has implemented Lync monitoring QoE in version 3.1 of their firmware for SBC 1000 and 2000.

Other new features Sonus is noting in Firmware 3.1:

  • Lync Monitoring QoE reported to Lync monitoring
  • Greater Session count on SBC 1000 from 100 to 160 session
  • 3G/4G Failover on SBA’s
  • Sonus EMS integration


How QoE on SBC 1K/2K Work? (Click Here for Step by Step Install)

Sonus SBC 1K/2K uses the Lync QoE Agent running on a Windows Server (the Sonus ASM) to collect QoE data.

On the gateway UI the QoE options under System | QoE

image


Some notes on requirements:

  • Sonus QoE license required (click here)
  • ASM required on the SBC node functioning as the QoE Agent Server Gateway.


Summary

For Lync Enterprise Voice it is essential to have integrated insight into the quality of all media paths: real-time media hardware  that does not report QoE is like driving a car without a dashboard. All gateways, SBC's and IP phones designed for Lync should have native QoE reporting into Lync Monitoring Server. Currently QoE is not a requirement for Microsoft Lync Qualified Gateways (or IP phones/endpoints) and it is good to see Sonus continuing its Lync related innovation by bringing this very essential functionality to its SBC1000/2000 devices.

While some vendors have their own monitoring tools, in Lync scenarios admins are not looking for yet another tool or pane of glass to implement, monitor and maintain.

Source:
http://discoveruc.com/ai1ec_event/webinar-sonus-introduces-release-3-1-sbc-1000-sbc-2000/?instance_id=22

Webinar on Jan 9, 2013:
https://cc.readytalk.com/cc/s/registrations/new?cid=hbkarqvb8abf

Sonus SBC1000/2000 Firemware 3.1 Release Notes:
https://support.sonus.net/display/UXDOC31/Sonus+SBC+1000-2000+Documentation

Lync Hacker: Step by Step Native #Lync DoorBell Using #snom PA1

 

Lync administrator Daryl Sensenig is using full Enterprise Voice at Tents for Rent and wanted to extend Lync as far as possible so he put his hacking skills to use to turn the snom PA1 into a complete native Microsoft Lync door bell. I appreciate Daryl giving permission to repost his solution and if you have any ideas to improve or if you have a low cost external/weather proof door bell to suggest, comment below.  Here is what he did…

I spent a lot of time figuring out how to build a door phone for Lync 2013. The documentation was very poor and fragmented. So, I thought I'd share how I did it so that others could benefit.

  1. I started with the Snom PA1 and updated it to the UC edition firmware.
  2. I purchased an AIPHONE LE-A and a mini mic from Amazon.
  3. I setup a ring group for the doorbell in Microsoft Lync
  4. I entered the UC account data into the PA Web UI.
  5. I setup speed dial "1" to be the doorbell ring group.
  6. I set auto dial to "after 2 seconds" It is located in Advanced > Behavior > Auto Dial
  7. I set it to auto answer in Identity 1 > SIP > Auto Answer. This allows me to call it if necessary.
  8. I inserted the mini mic into the "mic in" jack.
  9. I opened the AIPHONE and soldered wires from the AIPHONE speaker and connected them to the "Speaker" connectors on the PA1.
  10. I connected the wiring harness to the KBD (keyboard) port of the PA1 and soldered the white and purple (6 and 7) wires onto switch on the board in the AIPHONE. Thus by pressing the button on the AIPHONE, it dials the number 1 and after 2 seconds, speed dials my doorbell ring group.
  11. I connected the wiring harness to the I/O 2 port of the PA 1. The black wire is ground, brown is always 12 V (good as a power supply for a relay). Yellow is pin 3 and purple is pin 4. These can be connected to a relay for a door strike, door opener and etc. I haven't done this yet, but I plan to. The first PA1 unit I had did not supply 3.3V to pin 3 and 4 when activated. So, I had to get another unit.
  12. You can turn these pins on by dialing 3# or 4# when in a call to the PA1. You can also turn them on in the web UI: Preferences > PA1 controls > Pin 3.

There were numerous other steps and dead-ends that I ran into before I came up with this simplified list. I've eliminated all my "wrong" steps to keep it simple.

Please let me know if I've missed anything. I hope this is helpful to those who would like to do the same thing.

My total costs were:

  • $105 for the PA1
  • $24 for the AIPHONE
  • $5.05 for the mini mic
  • Total out of pocket $134.05
  • Lots of time, hassle, forum reading, posting and soldering

My next project is an outdoor doorbell. I'm looking for an affordable weather resistant door bell. If you have any ideas, please post.

Connecting the Call Switch (below)

1

Call switch connection

2

snom PA1 and

3

snom PA1 Connections

4

Attribution:
https://twitter.com/djtentman
http://paevent.com/tfr/

More discussion:
https://forum.snom.com/index.php?showtopic=12303&hl=video
http://social.technet.microsoft.com/Forums/lync/en-US/d99ef94b-0f17-4f94-83d7-0cf36006516e/compatible-door-entry-systems-for-lync?forum=ocsinterop