Nice Perform working through VPN - Design Considerations / Port list

[IPOpotamus]

Hello nice boys

A customer of us has required to use the nice application trought VPN (checkpoint / Connectra)

I've used to use VPN to enter nice servers and configure them, but this is for supervisors to remotely monitor agents.

As far I have done, all the applications (NBA, my universe, reporter, sysadmin, lists editors, users admin, etc) run smoothly on VPN.

but! monitor is the only applilcation that had give me a headache always

I have noted that official nice port ist 62141. good

the reality is that when the remote client opens monitor app.
it connects to server:62141 and starts listing the agentes
but server open a port in the client (checked on a local client) 1024 and estaablishes a second connection to send the updates of the agent activity. once this is done monitor will update agent state.

the weird thing is that I got the monitor trying to open the 1024 port only once, and if it is not succesful it will wait 60 seconds and show
"monitor servers is down, please contact your system administrator"

any hints about that?

had you make "monitor" works full on a VPN connection?

nice has a design considerations document - but is there a VPN considerations document?

thanks a lot

 

[azphoneguy]

Hi

We do not allow our remote users to playback screen calls. However while we were setting them up we realized that the VPN users had to have access to all NICE servers for complete functionality. We did this by attaching and access control list to the VPN profile with each NICE server IP.

Make sure your client can access all servers including the screen logger.

 

[IPOpotamus]

AZ, thanks for your reply

the customer has tweaked the ACLs to let a "any to any" rule, but still getting errors, considering that the system has no screen rec.

we got "the document" covering this config
NAT PAT Configuration Guide - NP - 3.1, 3.2, 3.5, 4.1.pdf

(its on extranice like zillions of other unknown documents)

got to mess with config files
and a thing so-called GENUINE CHANNELS

Gotta reboot all the platform, and later
we got finally monitor to show agent events, and surprisingly no only the 1024 problem dissapeared but moreover this connection seems to not be needed anymore, now the new 62075 port connection seems to transport everything.


Anyway, still got no live audio when trying to monitor an specific agent.

 

[IPOpotamus]

Hello everyone

I would like to save you many headaches you can have when configuring NICE PERFORM to work through VPN / NAT / PAT

note: the system i configured only records audio (no screen)

first get the document NAT PAT Configuration Guide - NP - 3.1, 3.2, 3.5, 4.1.pdf on extranice (i found it fetching by "pat")

first of all, you can do this change without affecting production BUT, you NEED TO RESTART ALL THE SYSTEM (all the servers) for this changes to be done. If you restart only applications you can lose connectivity both local (LAN) and VPN (proven!)

page 17
later its necessary to enter the applications server and modify one the config file of the application we wan tu run through VPN.
they are on the path
‘Application Installation Route’\Applications\ServerBin
in this case monitor:
NiceApplications.Monitor.Host.exe.config
<add key="usemachinename" value "true">

configure events or "genuine channels" (other interesting and intrincated ms techology used by nice)

once again go to:
'Application Installation Rote' \Applications\ServerBin\
NiceApplication.SystemAdministrator.Host.exe.config.

Change the useGenuineChannels parameter to TRUE.

RESTART ALL THE SYSTEM
"Restart all servers and clients in the system."

After doing that we got monitor effectively monitoring AGENTS CTI activity, anyway to be able to monitor audio, we got to reconfigure static routes for the VPN client to access the loggers and Storage Center.

Thanks a lot, and hope to contribute with the community.