I made the suggested changes, but still have issues. I thought specifying “transport=tcp” in the peer definition section would make Asterisk use TCP. Despite the changes specified, SIP still uses UDP (verified with the Wireshark pcap tool). I have noticed, however that Asterisk is in fact listening for tcp traffic on port 5060.
I have two Asterisk instances running on two separate servers on a local network. One Cisco IP phone is connected to each Asterisk instance. The two Cisco IP Phones are using Skinny. The Asterisk instances talk to each other using SIP, instead of IAX. I need this particular setup as I am running a software that analyzes the TCP packets.
We have a network in which there are two Call Managers (CMs), and the communication between them is by SIP. Two Cisco VoIP phones (each serviced by a CM) are to make calls between them, and they transmit UDP packets. We want the SIP to be over TCP.
Asterisk’s are used as the Call Managers in our set-up (we don’t use
Cisco CMs). They use Skinny to talk to the phones and SIP to communicate
between the themselves. So:
We want to use SIP via TCP between the two Asterisks. The phones have
the SCCP firmware. We are trying to avoid replacing the firmware to SIP.
I do not know if the phones use UDP or TCP to communicate with Asterisk.
If you are using Asterisk 1.6 .You can try out Chan_SCCP to connect cisco phones with out changing to SIP.
Below given are the links you can look into it
Yes, as david55 pointed out, in our set-up connection of Phone1–CM1–CM2–Phone2, we’re interested in making the SIP signaling between CM1–CM2 run over TCP (currently, it runs over UDP). Thanks.