Shane Hoey: Powershell script to backup UX configuration

Shane Hoey, Powershell guru, wrote fantastic PS script that backs up UX configuration. Script works great if you have production environment and done everything right. You can stop reading this and go to Shane's "Lync Cmdlets" blog.

But if you are like me trying to run this script from laptop not joined to domain, accessing UX by IP address, and UX does not have root and device certificates installed, you will run into issues with script.
First issue I ran into was related to Powershell version. This script requires Powershell v.3 otherwise you get this error:

Please read comments in the script:
#if the cert on your UX is not trusted by your browser you will need to add the certificate thumbprint via the CertificateThumbprint parameter

In my case "trusting" cert in browser didn't help with script error.

To fix issue I assigned FQDN to UX, added DNS A Record, created/imported cert on UX.

Next step was to get root cert from my lab CA and import it on my laptop as Trusted root CA cert:

Next I changd NIC settings to point to lab DC as DNS server and test browsing to UX by FQDN sbc1000.ux.net. It worked.

Now if I run PS script it does exactly what it supposed to do - copies backup config file to local PC:

For more details and Lync Powershell scripts check Shane's Lync Cmdlets blog

Exchange UM integration with UX1000 and QSIG. MWI.

 

UX1000 QSIG integration and MWI with Cisco Call Manager environment

Prepared by:

Paul Gerstner

August 15, 2012

The following lab exercise was performed to determine compatibility between the UX1000 and a Cisco environment comprising CUCM 7.1(5), MGCP Gateway using a Q.Sig PRI.
The key functionality focus was MWI.

Lab environment:

Software versions:

UX1000 – 2.1.2 build 158
E2010 SP1 – build 14.1.218.15
XM2621 – 12.4(15)T14
CUCM – 6.1.4-1000.10
CIPC – 8.6.1

Configuration:

Cisco environment configured mostly per following Integration Note:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/pbx/interop/notes/606763nt.pdf

UX1000 relevant config:

Call Routing Table:


Signaling Groups:

Test Results:

MWI off: (Cisco IOS debug isdn q931)

MWI on:

To decode the above Facility Messages, download the TripleCombo tool and MT.exe file, from the locations below and run on a windows server 2003 32-bit platform:
http://www.employees.org/~tiryaki/tc/triple_combo8.exe

http://www.employees.org/~tiryaki/tc/mt.exe

MWI off Facility IE decoded:

MWI on Facility IE decoded:

Use NET LX to review ISDN calls

Latest version (1.0.0.53) of LX added unique and exciting feature: decoding ISDN calls. Now LX can decode and extract ISDN calls and display those calls in Calls tab as it did with SIP calls.

So now you are able to see all call legs: ISDN and SIP which simplifies troubleshooting tremendously.

ISDN call flow displayed and each message presented in HEX as well as decoded:

Adding FXS ports to NET UX gateway with Adit600 FXS.

Another talent of UX platform, it can extend a life of existing equipment and bring it into VoIP infrastructure easily and seamlessly! I am talking about Adit600 Channel bank. There are multiple deployments of Adit600 for FXS ports, specifically Interactive intelligence CIC platform was using Adit's channel banks as FXS device for analog lines. Usually replacement on TDM card based CIC resulted in decommissioning Adit's and replacing them with FXS Gateways for analog devices. Not anymore! Now it is possible to keep using investment into Adit600 channel banks.

Even better with UX platform ADIT600 can find a new life in Lync environment! UX2000  allows seamlessly integrate Adit600  into Lync environment as analog end-points.

Here is how the whole setup looks like:

There is no configuration required on Adit600.

On UX there are just several configuration steps and Adit600 ready to dial!

First create CAS FXS Profile:

Next, configure T1 port for CAS:

Next, create CAS Signalling Group. Specify Line type as Digital, CAS Signalling Profile as FXS.

Assign Line extensions, all 24 of them.

Create Transformation table for Adit intercom routing:

Create Routing Table entry:

Now connect a phone to Adit600, listen to dial tone and dial!

I tested Adit600 intercom calls and calls through Ux to Tenor.

I haven't tested Supplementary services like Hold, Transfer.

Call Forking with AD integration on UX platform

Call forking is another great feature in UX platform. It allows to send a single call to up to 8 endpoints. This feature requires license. Check license for Forking.

The traditional call routing logic is that process goes through routing table top to bottom trying to match Called Number. As soon as matching routing entry is found the matching process stops and call is sent to destination specified in matching routing entry. UX Routing Table entry has parameter "Fork Call". If this option is enabled matching process doesn’t stop on first matched routing entry but proceeds to next routing entry.

As result two calls are initiated based on two different Routing Table entries. In this example we are routing calls to Lync based on Active Directory match criteria and to PBX.

Transformation tables for Lync AD routing

Transformation Table for PBX routing translating 4 digit extension to 5 digit.

Active Directory integration in UX platform

UX platform has a great features - Active Directory integration. This article will show how to use AD integration for advanced call routing.

First make sure that "Active Directory" feature license is present and by default it is since it's no fee feature in UX platform.
WebUI - Settings Tab - System - Licensing - Current Licenses:

Next, add Domain Controller to Domain Controllers Table:

Settings - Auth and Directory Services - Active Directory - Domain Controllers

Specify Domain Controller IP/FQDN, Search Scope and LDAP Query.

Configure Active Directory settings:
Settings - Auth and Directory Services - Active Directory - Configuration.
Enable AD use, specify Operating Mode, Username and password, Update Frequency, Cache Attributes and Primary Damin controller that was specified in previous step.
For AD based routing to Lync2010 use msRTCSIP-Line attribute.

Verify connectivity by going to Domain controllers and clicking on "Status". AD Connectivity Status should be "Up"

Now proceed to Transformation table:

Create new transformation table "AD Translation" and within that table add two  rows:

In this case UX normalizes Called Number to E.164 and trying to match to msRTCSIP-Line. If match is found,  msRTCSIP-Line value is used as Called Number for outbound call to Lync.

Next assign newly created "AD Translation" transformation table to Call Routing Table entry with Lync as destination.

Logging on UX1000 with SolarWinds Kiwi Syslog Server

At some point during UX1000 deployment you will need to get logs for review. With UX1000 there is a way to configure Remote log server.

There are several Syslog server options. I am going to cover SolarWinds Kiwi Syslog Server.

Kiwi download and install is no rocket science: google it on Bing, download, follow setup wizard. You can install Kiwi as Application or Server (runs as service, no need to login and start application). I installed it as an Application.

First thing is to configure Remote Log Server and subsystems for logging. ( I know you know, just saying)

 As soon as I started Kiwi Syslog server Console the messages from UX started popping up.

 

But! there is limitation: only 40 rows are shown. You can increase number of rows to display but upper range is 50, which is not enough for troubleshooting. The good news is that Kiwi writes a log in .txt.

Now you have logs to work with.