Contact Centers, CRM Customer Engagement

Hello,

I have CMS R18 and have problem with CMS Supervisor R18.

I install it without problem, setup server properties(choose SSH- port 22) but when I try to login I get this error "a connection to the specified cms server could not be established".

I installed it on win10Pro with administrative user and tests with same user.

Where is the problem?

Thanks in advance.

Under the server properties ensure that you identify the correct server version - the server IP and Network port 23.

Bill Perkins

23years Bell Support 6 years Lucent Team Lead

Hello,

Yes, I choose correct version in server properties R18.
I use SSH port 22 and get error.
When select network and port 23 I get error "connection time out".

With the laptop with Win10 Enterprise which is external for company where CMS is installed, I connects to CMS without problem.

Very strange.

We had this problem a lot with CMS18 MA41 client. There is an advisory to
apply a registry change to allow for a longer SSH timeout which fixes the
problem in most cases;


On 25 January 2018 at 06:55, Teodor Georgiev <
iaug-cc-crm-apds@lists.iaug.org> wrote:

> Hello,
>
> Yes, I choose correct version in server properties R18.
> I use SSH port 22 and get error.
> When select network and port 23 I get error "connection time out".
>
> With the laptop with Win10 Enterprise which is external for company where
> CMS is installed, I connects to CMS without problem.
>
> Very strange.
>
> -----End Original Message-----
>

Sorry the cut and paste didn't work!

*Solution*I recommend you to follow the below procedure in such situation :

• Remove the previous CMS supervisor version (Refer the document to
uninstall it properly)
• Install the latest CMS Supervisor R18MA38 from Support site
• Change the SSHDelay parameter’s value to 25000 from 5000, under registry
key :
o run --> Type 'regedit'
o
HKEY_CURRENT_USER\Software\Avaya\Supervisor\18.0\Servers\xx.xx.xx.xx\SSH\SSHDelay
• Delete the cache file after the above changes
[C:\Users\\AppData\Roaming\Avaya\CMS Supervisor R18\Cache.]

On 25 January 2018 at 06:55, Teodor Georgiev <
iaug-cc-crm-apds@lists.iaug.org> wrote:

> Hello,
>
> Yes, I choose correct version in server properties R18.
> I use SSH port 22 and get error.
> When select network and port 23 I get error "connection time out".
>
> With the laptop with Win10 Enterprise which is external for company where
> CMS is installed, I connects to CMS without problem.
>
> Very strange.
>
> -----End Original Message-----
>

Good to know! THX.

Bill Perkins

23years Bell Support 6 years Lucent Team Lead

There is no success.

Using Putty can you try creating both telnet and SSH connections to your
CMS server from the problem client and check that you can log in ok with
each of them.

I think your problem may be underlying as the CMS Supervisor client is
little more than a putty connection in itself.

On 27 January 2018 at 07:56, Teodor Georgiev <
iaug-cc-crm-apds@lists.iaug.org> wrote:

> There is not success.
>
> -----End Original Message-----
>

There was a problem with DNS of CMS Server, I change DNS and edit file in CMS Server /etc/host.allow and add in it in.telnetd line.

Now I can login successfully with network type Connection and port 23.

Now I have other problem, I add one more user via putty like root and set password for new user and when try login into CMS Supervisor with new user, port 23 I get error "the connection to the CMS server has timed out. Login cannot be completed".

Why I can login with one user but with next user I cannot login? Second user is in same user group like first.

Resolve problem- first add user from supervisor application then only set password from cli (putty).

There is a known issue with Windows 10 update 1709 and SSH CMS Supervisor connections with R18.  

CMS MA48 resolves the issue.

For more details:

https://downloads.avaya.com/css/P8/documents/101045018

 

Just to update for January 2021, I had to uninstall 18.1 and reinstall 18.0 because I could not get 18.1 to connect to CMS Supervisor over VPN. TE works great over VPN and inside my office Supervisor works just fine. Over VPN 18.0 works now.

------------------------------
Mark Whitchurch
Senior Systems Administrator
InterContinental Hotels Group
------------------------------

Original Message:
Sent: 02-23-2018 12:49 PM
From: Siobhan Williams
Subject: CMS R18

There is a known issue with Windows 10 update 1709 and SSH CMS Supervisor connections with R18.  

CMS MA48 resolves the issue.

For more details:

https://downloads.avaya.com/css/P8/documents/101045018