If the package exceeds the MTU limit should be a problem - the TCP/IP
stack must take care of UDP fragmentation. Of course, there are some
crappy hardphones that never heard of such think :(.
regards,
bogdan
JF wrote:
Thanks for your answer.
This is a real problem when there are several SIP hops adding Vias and
Record-Routes, especially with INVITEs carrying SDPs as large as 700
bytes... Messages easily grow bigger than the MTU.
Is there a recommended way of handling this using openser? Anyone else
facing this kind of problems? The safest way is to use always TCP...
JF
On 5/10/06, Bogdan-Andrei Iancu <[EMAIL PROTECTED]> wrote:
Hi,
no, there is no way to figure out the size of the outgoing package. The
only automatic protocol selection is via NSPTR records (if the target
has such records) - please see the SIP location for this.
also you can choose the proto via the script.
regards,
bogdan
JF wrote:
> Hi all,
>
> Is there any function in openser that selects the transport protocol
> (TCP or UDP) according to the message size? E.g. if the message going
> out is bigger than MTU, use TCP... or does the script writer have to
> take this into account every time a relaying function is called?
> Also, in this second case, is the actual outgoing message size
> available in the script (i.e. after lumps are applied)?
>
> Thanks in advance,
>
> JF
>
> _______________________________________________
> Users mailing list
> [email protected]
> http://openser.org/cgi-bin/mailman/listinfo/users
>
>
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
