Thanks for the reply.

Please note that I didn't mean 'telnet' for MGMT purposes, but for checking out if there is a TCP port listening on a device or not...e.g. you may check your cisco.com connectivity by using: 'telnet cisco.com 80' and you will receive some information or at least get a connection.

When I enable TCP as a transport for SIP on ATA say on port 5000, I don't get listening port on the device. What else should be done to enable TCP transport. If nothing is listening is it an ok behavior? Is the ATA not suppose to listen on a TCP port the way it does on UDP 5060 port?

Thanks.

Thanks for your reply Alberto,

If ATA wouldn't listen on TCP port, it would render the ATA to act only as a UAC [not as a UAS] when TCP is used...is that correct? When a call comes in for this ATA, the SIP server would know the location of this ATA [but it registered using TCP] but how would it initiate a connection to it or forward the call to this ATA? Since it is not listening on any ports.

Regards.

The ATA should still use the SIP port that is defined. Meaning it will only use TCP on the transport layer of the TCP/OSI model to communicate over IP. It would still choose the destination port (as defined one the ATA) but it would be sent via TCP instead of UDP. TCP meaning it has retransmission of lost packets, and support for security. When you say it registered via TCP that is a bit of a misnomer in that it actually regstered using SIP but it ran on top of the TCP protocol and carried by IP. The completion of the call would be handled by source and destination IP/port and the type of transmission (at the Application layer) would be a SIP transmission. Hope this helps.

Bill