COBRAS message import failure to Unity Conection 7

Unanswered Question
Apr 6th, 2010


I am attempting to import messages from unity 4.0(5) to Unity connection 7. Unfortunately I fails every time with the following message "SocketError: WSAECONNREFUSED No connection could be made because the target machine actively refused it".

I have followed the configuration steps described in the documentation and tutorials. The import works well for greetings etc. but not for messages.

I have attached a word doc with the secreen shots from my setup. Any suggestions?



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
David Hailey Tue, 04/06/2010 - 07:06

2 things:  The machine you are running the COBRAS Import tool there a firewall enabled on that machine?

Second, before running the COBRAS tool - did you connect to the CUC server and install the self-signed certificate on your local PC?  In some cases, I've found that leaving a session open helps alleviate some issues.


Please rate helpful posts!

lindborg Tue, 04/06/2010 - 07:41

There's a couple troubleshooting sections in the help file that run down the ports used and has some tips here - just one clarification since a lot of folks stumble on this.

Greetings and voice names gets moved on/off the Connection server using HTTP - messages are imported using strictly SMTP.  They have nothing at all in common and one working has no bearing on the other working.  Notably the certificate that trips folks up comes into play only for greetings and voice names (HTTP) - it has no bearing on SMTP traffic.

The two most common problems I see escalated are the security for SMTP is not disabled properly.  I've seen that dozens of times - double check that the SMTP server setup on Connection allows for connections from untrusted IP Addresses, the "Require Authentication from Untrusted IP addresses" is UNchecked AND the Transport layer security from Untrusted IP Addresses is set to "Disabled" - if any of those are not configured that way you'll get active refusals of connections.

The 2nd most common issue here is a security application like Norton in play - they will block outbound SMTP traffice off the Windows box you're on by default - frustratingly many of them allow the first connection attempt up front sometimes and it will fail _later_ when messages are being sent in.  Very annoying... this thwarts the up front check to see if the path is open before the import begins.

Either way something is either blocking the SMTP traffic or the server is not accepting inbound SMTP traffic - one or the other.

richardpierce Tue, 04/06/2010 - 08:01

Thank you both for the information and suggestions.

As you both suggested it turned out to be a problem with the importing machine. I tired a different machine with no FW or anti-virus software and it now works well.



robloeber Wed, 08/04/2010 - 19:48

This helped me get my imports to work!  Thanks for taking the time to explain this!


This Discussion