Interaction Workspace SIP Endpoint startup problem

Voice & Telephony
1

I’m having some problems deploying Interaction Workspace 8.1 with SIP Endpoint plugin on agent workstations.

It works when being accessed from a test server and from my own laptop, so there has to be something in the PC configuration causing a problem, but I don’t know what that could be.

In all cases, I am logging on to the machine as a user with local admin rights (not that I should have to, but to prove no permissions problems). I am also logging on to IWS as the same agent and place number each time.

Also, I’m installing the application locally (not via ClickOnce deployment).

On the agent workstations I get the following errors:


12-05-23 08:50:38.314 [            12] ERROR ndpointCommunication - Exception occurs while communicating with the Endpoint. Exception: 
System.TypeLoadException: Could not load type 'System.Security.Authentication.ExtendedProtection.ChannelBinding' from assembly 'System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

12-05-23 08:50:39.814 [             9] ERROR ndpointCommunication - The SIP Endpoint application no longer respond. Try to start a new SIP Endpoint application. There was a CommunicationException leading to that situation: 
System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

Anyone have any ideas? I’m currently comparing the config of my laptop with the agent PCs. Same versions of .NET Framework installed etc so not sure what the problem is!

2

Seems a conflict…kill all SIP software you may have running on your PC.
Install IWS and then the endpoint, right?
I have done it on some PCs from now on and no issues. Be sure IWS 8.1 needs IWS SIP Endpoint 8.0.202.04

3

Yeah I’m installing IWS then the SIP EndPoint and no other SIP software running on the PC.

I am using a lower version number than the one you mention though as that version doesn’t seem to be GA yet. I’ve requested it from Genesys.

Still not sure why it would work on some machines and not others though!

1 Like
4

I installed version 8.0.202.04 but still the same problem. Seems like a .NET issue but all pre-requisites are already installed.

I tried uninstalling Bria before installing IWS, thinking there was some conflict but I’m still having the same issue.

I haven’t tried fully uninstalling and reinstalling .NET yet but shouldn’t have to, surely!

1 Like
5

Wait…you using Bria 3.x too? If so then on the IWS you must remove the permission to use SIP Endpoint (this one is ment for the IWS SIP Endpoint, not for a 3rd party one). I think what it is complaining about is that it can’t connect to HIS IWS SIP Endpoint, not Bria…
Bria will be, remember, a third party here…SIP Server will send TLib events to IWS and SIP Events to Bria separately.

So on the user role, disable the SIP Endpoint permission and work with Bria as you always do.

1 Like
6

Sorry, didn’t explain myself very well there!

What I mean is, the customer was previously using the Bria standalone client with GAD. Now they want to go IWS & SIP Endpoint plugin.

I think the IWS SIP Endpoint is based on Bria technology so I wondered if that was causing some conflict, but even if I uninstall the old Bria client completely before installing IWS + SIP Endpoint, the problem still remains…

7

Ah ok…got it.
Can you please post which .Net Framework and revisions do you have?

8

Found the problem - it was an issue with a previously applied .NET update.

This fix from Microsoft solved the issue:

http://support.microsoft.com/kb/2262911

2 Likes
9

Great! Thanks for sharing