[OpenSIPS-Users] REGISTER reply > MTU size?

[Ovidiu Sas]

One example could be third party registration that controls all the
bindings and it needs to know the binding's status in order to manage
(remove some of) them.

-ovidiu

On Thu, Feb 7, 2013 at 3:18 PM, Pauba, Kevin L <KLPauba at west.com> wrote:
> Out of curiosity, what might be the use cases where a registering client needs/wants to know all of the others with the same binding?  I'm probably blinded by the functions of our platform and can't imagine a use for that.
>
> Thanks!
>
> -----Original Message-----
> From: users-bounces at lists.opensips.org [mailto:users-bounces at lists.opensips.org] On Behalf Of Ovidiu Sas
> Sent: Thursday, February 07, 2013 1:15 PM
> To: OpenSIPS users mailling list
> Subject: Re: [OpenSIPS-Users] REGISTER reply > MTU size?
>
> If you have a few bindings, there shouldn't be any issues (assuming that you have reasonable tags and headers).  In the end it's all about fitting the whole info into the max packet size.  If you have large bindings, then your chances to fit many bindings into a UDP packet are small ... If the bindings are really large, you can try to trim them before saving them (remove parameters if the client will be happy with that).
>
> -ovidiu