Hynek, It looks like the Expires value is hard coded at 360 seconds for non NAT endpoints and 90 seconds for endpoints behind NAT. It might be nice to have a parameter to define this on a per profile basis. You could have a parameter to define the default and also NAT expiration times. I'll look into this. Thanks, Spencer On Nov 13, 2011, at 4:09 AM, Hynek Cihlar wrote:
Freeswitch ignores the Expires header, instead registers SIP clients with expiration timeout of 90 seconds.
I know there are few variables/parameters which control the Expiration. I use pretty default SIP profile configuration but the directory is built with with a lua script. If the lua script defines sip-force-expires, the registrations is ok forced to this value. If the variable sip-force-expires is missing, 90 seconds is used regardless what the client sends. Any ideas?
Thanks for any help.
Hynek
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org