[cisco-voip] Unified Assistant Console won't log in

[Wolfe, Robert]

That "IP blocked" is a find and replace on the production IP, as we
don't forward that info to newsgroups without NDA.  Please ignore.  The
server is pingable by name and IP.

Thanks for the input.

Rob Wolfe  |  Burwood Group  |  Chicago |  rwolfe at burwood.com

Cell: 312.593.0605  |  Fax: 312.327.4601  |  IP: 312.327.4634

-----Original Message-----
From: J. Oquendo [mailto:sil at infiltrated.net] 
Sent: Thursday, August 31, 2006 2:35 PM
To: Wolfe, Robert
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Unified Assistant Console won't log in

Wolfe, Robert wrote:
>
> Has never worked.  CallManager 4.2.  Any ideas?  Going to open a TAC 
> case in the mean time
>
> 5: Thu Aug 31 14:21:03 CDT 2006 % ServerConnect: Initializing sockets
>
> 6: Thu Aug 31 14:21:03 CDT 2006 % ServerConnect: Creating a socket 
> connection to host: <IP BLOCKED> on port: 2912
>
> 7: Thu Aug 31 14:21:03 CDT 2006 % ServerConnect: Created a socket 
> connection to host: <IP BLOCKED> on port: 2912
>

Your answer is directly in front of you. The machine isn't opening up 
the proper port for anything to work. Is there a firewall rule somewhere

blocking it, some other program using that port? Have you tried 
telnetting to that port number, scanning the address. The "IP BLOCKED" 
is straightforward, that address cannot access that port so either a) 
some firewall/filter/IDS/IPS/*whatever_else* is blocking it from making 
the connection, or b) another program decided to use that port number. 
I'm sticking with a.

-- 
====================================================
J. Oquendo
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x1383A743
sil . infiltrated @ net http://www.infiltrated.net 

The happiness of society is the end of government.
John Adams