Hi, I am Gilbert Lee.
There are 3 ways of keep-alive mechanism from my experience.
1. CRLF
2. OPTION
3. REGISTER
It seems to be called SIP Session Timer while sending REGISTER message again
is called SIP Expire Time.
I do not know what is best policy of SIP Session Timer for network.
Any way, is there any standard declared document in RFC?
2009/3/24 Bengt Werstén <bengt.wers...@enea.com>
> Hi,
>
>
>
> Is it possible to change the behavior of NAT keep-alive to send empty or
> double CLRF UDP packets? The standard solution in Sofia-SIP seems to be
> sending OPTIONS and that would require much traffic and a big load on the
> proxy if many clients.
>
>
>
> Best regards,
>
> Bengt Werstén
>
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Sofia-sip-devel mailing list
> Sofia-sip-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
>
>
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
