Notification Handler

Notification Handler (NH) is a Windows client application that provides Lync/Skype for Business events in one of various ways to CRM systems and other external applications.

For this reason, it registers on events from the SfB client and sends them over the chosen communication channel.

It also exposes call handling to third party applications.

Setup and Configuration

Chose your communication channel.

	Communication Type	Description
	WEB
	IPC	Inter process communication to talk to WPF and similar third party .net client applications.
	MQ	ActiveMQ for centralized management of Command and Event messages. Scalable for up to 1 million clients.
	SignalR	Communicates over WebSocket or Longpolling to a website running on the local browser. For example Salesforce integration.
	URL	Doesn't add browser control to the protocol. Instead is customized for each customer to open an url in browser instead of communicating directly with an external CRM server. Normaly this includes removing of call controls local webserver. Exceptions can be made on customers wish.

Add mock CRM application

In case you want to test Notification Handler, select the Test CRM to install for your chosen communication Type.

Fill in the settings

Based on your previous selection the next page asks for a bunch of settings.

Active MQ (MQ)

Web based (WEB)

Inter Process Communication (IPC)

Open URL (Browser)

MQ

MQ Connection	The connection string for activeMQ See: https://activemq.apache.org/connection-configuration-uri
Read Queue	The Queue or Topic to read from
Write Queue	The Queue or Topic NH sends his events to
Username / Password	The username and password to authenticate on ActiveMQ See: https://activemq.apache.org/security

WEB

Local Webeserver	The Port under which the local webserver listenes with full URL. It's recommended to use localhost, but other possible values would be wild characters like * and + or the ip-address.
CRM Server URL	The URL which NH sends its Event-Webrequests to. This requests will not open a Browser and will be sent in the background.

IPC

IPC Pipe name

The name of the pipe on which any third party application can connect
to, to recieve NH Events.

Browser

Local Webserver

Same as in Web base communication. To recieve command requests.
This must be turned on specifically after installation in the app.config.

URL to open

The URL that will be opened. Can contain variables in the {VAR} format.

Possible values are:
MessageName, UserSIP, UserPhone, Type, Direction, Other, OtherSingle,
Inviter, Target, CallID, OtherCallID, Added, ErrorMessage, ErrorCode

Possible values if Local Webserver is enabled:
InteractionID, Parameters

The URL cannot contain white spaces.

Test the Installation

If you selected to start NotificationHandler, you should be able to see the Icon with the green symbol on the bottom right of your screen.

Otherwise you can still head over to the installation folder and start it from there, or use the desktop icon.

In the installation folder you also find the selected Test CRMs you chose at installation time.

Open the Test Crm exe and click on "SignIn" button on the top right.

If you see

-> EventCrmConnected {"Filter": ....
<- NH: {}

you are good to go.

If you see an <- Error: (ConnectionFailure) or if Notification Handler won't start or doesn't behave as you expected, or you see and error in the logfile,
please proceed to Chapter 1.2 Solve installation Problems.

Solve installation Problems

You can always check the logfiles for a hint why Notification Handler doesn't behave as expected.
Standart log location is C:\Company\Log\NotificationHelper\luware-nh-regularLog.txt

Notification Handler shows a red icon after startup.

Solution:

See "Test Crm shows Error: (ConnectionFailure) after click on SignIn button." solution.

NotificationHandler starts up, but does not write a logfile.

Solution:

Check NotificationHandler.exe.config for TraceAppender under <log4net><root> and replace it with the value FileAppender_RegularLog. Only there.

    <root>
        <level value="DEBUG"/>
        <appender-ref ref="TraceAppender"/>
    </root>
</log4net>

Test Crm shows Error: (ConnectionFailure) after click on SignIn button.

Solution:

Open a PowerShell as Administrator.
Enter "netsh http show urlacl" to check if NH has the rights to run a local WebServer under the port you selected at install time.
If an entry like https://*:4575/ is missing, add one by typing "netsh http add urlacl url=https://*:4466/ user=Everyone".
If you are on a german system use "netsh http add urlacl url=https://*:4466/ user=Jeder" instead.
Make sure the port and http or https is correct as you entered in during install time.
If you are not sure what you entered you can always check in the registry under "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Luware AG\LUCS.AA" for the key NH_URL
Repeat this step for the Test Crm (Registry key: CRM_URL)
If you run NH under https add the certificate binding by running " netsh http add sslcert ipport=0.0.0.0:4575 certhash=27edc0ab0a00000abc00000f0abcd000ffee000a appid="{ddcbce73-90a6-4110-9235-7f1246ae3d71}" "
Replacce the underlined parts. Make sure to keep the inner " on appid but replace certhash with your certificate. Replace the port on ipport, but keep the 0.0.0.0:
The appid does NOT need to be changed, and can be copied from here.
Repeat this step for the Test Crm if it is running under https.

Caller contains the Service or Service contains the caller.

This can happen if "Show caller in Subject" and "Impersonation" feature are both active on a LUCS service or TeamManager Team number.
Deactivate "Show caller in Subject".
If you use the f.E. ActiveMQ and Participant Added Event, consider switching to Init Event.

Notification Handler doesn't start up, or crashes shortly after.

This can only happen if the installation packeting was faulty. Usually it's due to a version missmatch from .dll files.
To analyze which dll files are faulty please contact Luware: suport@luware.com