Author Topic: Contact Center Client try to connect (host ip) on port 5024  (Read 5023 times)

Offline manchester7

  • Contributer
  • *
  • Posts: 21
  • Karma: +0/-0
    • View Profile
Contact Center Client try to connect (host ip) on port 5024
« on: October 13, 2016, 08:05:19 AM »
Hi there,

I need help on this. After succesfully install MICC V8.0.1, synchronize Yoursite and Mxe with no problem.

But when i open contact center client, the real time turn to grey colour and it try to connect port (host ip) on port 5024.

Firewall turn off and no antivirus install.

I used MIVB v13.2.1.27, MICC V8.0.1.. any idea on log error below. Thank you

RTClient trying to connect - Host:[10.85.23.76] Port:[5024] Interval:[15000 ms]   ()
Error: 2016-Oct-13 13:06:54.456   RTClient OnSocketError OnSocketError() - Code -1, Desc: System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 10.85.23.76:5024
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP


Offline dilkie

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 344
  • Karma: +11/-0
    • View Profile
Re: Contact Center Client try to connect (host ip) on port 5024
« Reply #1 on: October 13, 2016, 09:55:25 AM »
I assume 10.85.23.76 is the ip of the contact center server?

Offline manchester7

  • Contributer
  • *
  • Posts: 21
  • Karma: +0/-0
    • View Profile
Re: Contact Center Client try to connect (host ip) on port 5024
« Reply #2 on: October 13, 2016, 10:10:32 AM »
Yes. We have try to install V8.0.1 and reinstall it with SQL 2012 and SQL 2014. Still not solve it.

Currently install V8.0.1 with SQL 2014

Thank in advanced

Offline sunspark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 986
  • Country: mx
  • Karma: +16/-1
    • View Profile
Re: Contact Center Client try to connect (host ip) on port 5024
« Reply #3 on: October 27, 2016, 07:20:02 PM »
Hi ,

We are in the same situation , any idea ? thanks !! :) :)

Offline sunspark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 986
  • Country: mx
  • Karma: +16/-1
    • View Profile
Re: Contact Center Client try to connect (host ip) on port 5024
« Reply #4 on: October 28, 2016, 05:02:28 AM »
If you dont use Mitel auditor port  :

On YOursite --> entreprise , --> entreprise :

Put in Real-time port : 5025
in Auditor port : 5024

it works for me

Offline sunspark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 986
  • Country: mx
  • Karma: +16/-1
    • View Profile
Re: Contact Center Client try to connect (host ip) on port 5024
« Reply #5 on: October 31, 2016, 03:33:27 AM »

Basically the Masstransit service has to create a data base on the local sqlexpress instance called masstransitruntimeservices.  This was not being created due to the databases already existing, in the sql folder , , So i stopped MT service , removed the databases from the folder and restarted the MT service , this then created the DB correctly and now the Enterprise service , which also requires port 5024 now connects and can subscribe to this MT db .

Offline imanm93

  • Jr. Member
  • **
  • Posts: 76
  • Country: au
  • Karma: +0/-0
  • Keep it simple!
    • View Profile
    • Iman Mohammadi's Blog
Re: Contact Center Client try to connect (host ip) on port 5024
« Reply #6 on: April 24, 2019, 06:29:42 AM »
Hello guys,
I have the same problem here. I've changed the port 5024 with 5025 and I was able to connect to Contact Center Client. But, the monitoring information of my profiles was failed to transfer (It was stacked on "Retrieving Information").
I've tried many ways but none of them solve my problem and this problem really pisses me off!!
I run MiCC Setup many times, updated my licenses and even install another windows server, but I still have got it!
Please help my if you guys have any other solutions.
Thank you all in advance 

Offline imanm93

  • Jr. Member
  • **
  • Posts: 76
  • Country: au
  • Karma: +0/-0
  • Keep it simple!
    • View Profile
    • Iman Mohammadi's Blog
Re: Contact Center Client try to connect (host ip) on port 5024
« Reply #7 on: August 08, 2019, 08:59:39 AM »
Hello everyone,
I found a solution for solving this annoying problem a few days ago as we again faced this problem.

This port (5024) is depend on MiContact Center Enterprise Service and when this service faces infinite loop issue (automatically starting and stopping) due to being unable to connect to another service named MiContact Center Mass Transit Runtime, this problem will happen.
Mass Transit Runtime is in charge of making a connection between Enterprise Service and Messaging Queue and since the bus of Mass Transit Runtime was full we will receive the "Insufficient Resources to Perform Operation" log which indicates that Message Queuing buffer is full.

Here is the solution:
1. Stop these services from Services.msc:
i. MiContact Center Enterprise
ii. MiContact Center Mass Transit Runtime
iii. Message Queuing

2. Go to Computer Management> Services and Applications> Message Queuing> Private Queues>
Enterprise> Queue Messages
right click on Queue Messages> All tasks> Purge
(this will erase the buffer of Queue Messaging)

3. Start following services:
i. Message Queuing
ii. MiConact Center Mass Transit Runtime
iii. MiContact Center Enterprise
« Last Edit: August 08, 2019, 09:01:10 AM by imanm93 »

Offline imanm93

  • Jr. Member
  • **
  • Posts: 76
  • Country: au
  • Karma: +0/-0
  • Keep it simple!
    • View Profile
    • Iman Mohammadi's Blog
Re: Contact Center Client try to connect (host ip) on port 5024
« Reply #8 on: August 08, 2019, 09:06:24 AM »
I hope this will work for you guys  ;)
« Last Edit: August 08, 2019, 09:08:49 AM by imanm93 »

Offline Ronan

  • Full Member
  • ***
  • Posts: 149
  • Country: fr
  • Karma: +1/-0
    • View Profile
Re: Contact Center Client try to connect (host ip) on port 5024
« Reply #9 on: May 15, 2020, 07:36:49 AM »
You saved my bacon imanm93

2 hours I'm pulling my last remaining hairs on this

I have a dozen agents connected and using CCC so I know the server config is alright.

I connect agent A it works.

I connect agent B it doesn't work.

Thing is, I just programmed agent B, so I'm thinking I made a mistake, forgot something (there are so many things, security roles etc.).

Agent A I configured a couple days ago always works. Agent B never works.

It's really maddening !

I would have restarted the server but it's so busy right now (IT hotline when everyone is working from home) it's just not possible.

I followed your solution except I didn't do the purge, just stopped the 3 services, started them again, and all is working now !

Thanks


 

Sitemap 1 2 3 4 5 6 7 8 9 10