09-07-2012 02:50 PM - edited 03-21-2019 06:15 AM
I have a linksys SPA922 phone transporting SIP over TCP. Each particular SIP message is being carried in two of more TCP segments. When the TCP connection is established, the server announces MSS=1460 and despite of that, the phone is sending IP datagrams smaller than 576 octects, apparently disregarding the MSS option and acting as if it doesn't know the maximum segment size the server is able to receive.
I have stated that it is not a problem related to MTU knowledge, as the phone announces a MSS=1460 too when opening TCP connections.
Any idea about why the phone is not taking into account the maximum segment size the server can admit?
09-07-2012 09:18 PM
Even if a device advertise a certain MSS, it is not obligated to only send packts up to that size.
That shoyuld not cause any problem and everyt should work anyway.
09-10-2012 09:19 AM
That's right, but the smaller the segment, the less efficient is the communication. One would expect Cisco TCP implementation be a good one. That's why I find very strange such a behaviour.
09-10-2012 10:22 AM
There is no performance issue in compacting messages that are only occasionally sent.
09-10-2012 11:25 AM
It all depends on how many phones are sending messages. If there are many, perhaps SIP traffic would be noticeable. And for debugging reasons, having SIP messages scattered doesn't help.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide