[cisco-voip] TCP/UDP ports required by Attendant Console

[Wes Sisk]

Hi Anthony,

on the AC client, edit, settings, advanced, "Local host ip address (for 
line state)"
This forces AC to use a static port for RMI communication.  Permit that 
and the rest:

There are 3 types of communication between the client and server:

client->RMI(telephony call dispatcher)
client->QBE(cti mananger)
client<-LSS(telephony call dispatcher)

In sniffer traces it appears that the client client always 
connects to RMI at server TCP port 1099-1129.  Then the server
tells the client to establish a 2nd TCP session with the
server on a 2nd TCP port.  In 2 tests this 2nd TCP session
has been TCP3328 and TCP1161.

I am working to find a fixed range of ports this 2nd session.

Then there is UDP LSS traffic coming from the servers, this
has come from UDP ports 2453,1154 been destined to UDP 3038,2888 
on the client in 2 tests now.

Fix the port for LSS using the steps above. 

Then there is the QBE communication that establishes a TCP session
with the server at TCP port 2748.

/Wes

Anthony Kouloglou wrote:

> Hi all,
> I am having problems in constructing the access list to allow traffic 
> from the data vlan to the voice vlan in a cisco callmanager 
> integration. I have used the information provided in  "TCP and UDP 
> Ports Used by Cisco CallManager 3.3" that i have foundin the following 
> link:
> http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/products_tech_note09186a00801a62b9.shtml
> The attendant console could not communicate with the server, not 
> untill i removed the access list.
> Could anyone help me with this one?
>
>------------------------------------------------------------------------
>
>_______________________________________________
>cisco-voip mailing list
>cisco-voip at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-voip
>  
>