I don’t disagree with that Mike. And yet, sip TCP fixes faxing problems from time to time (it has for me in the past). While that could be an indicator of other issues rather than just a change in protocol; as I said earlier, with faxing, a fix is a fix and I don’t ask questions.
Sent from my iPhone > On May 9, 2018, at 13:02, Norton, Mike <mikenor...@pwsd76.ab.ca> wrote: > > Ryan Huff wrote: >> Yes, the handshake “noise” samples, so to speak (RTP payload) in a fax over >> SIP will always be UDP; the signaling (SIP) could be TCP or UDP. If you do >> have a poor connection, you could lose signaling due to packet loss, and the >> connection terminate (whereas TCP would attempt a retransmission). > > I think it's a myth that TCP's built-in retransmission mechanism somehow > makes TCP SIP more reliable than UDP SIP. The truth is, for all SIP messages > of any importance, the SIP protocol already has its own retransmission > mechanism. Otherwise SIP would have always been TCP from its very beginnings. > A lost UDP packet will be noticed by the sender not receiving any ACK > message, who will then re-send. > > -mn > _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
