Got it. because I'm behind an NAT and #define SOFIA_NAT_SESSION_TIMEOUT 20 515 if (switch_test_flag(tech_pvt, TFLAG_NAT) || 516 (val = switch_channel_get_variable(channel, "sip-force- contact")) || 517 ((val = switch_channel_get_variable(channel, "sip_sticky_contact")) && switch_true(val))) { 518 sticky = tech_pvt->record_route; 519 session_timeout = SOFIA_NAT_SESSION_TIMEOUT; so, session_timeout would always be 20 and I always get a Session- Expires header with value 120(the default value maybe). Based on http://tools.ietf.org/html/draft-ietf-sip-session-timer-15, I think #define SOFIA_NAT_SESSION_TIMEOUT 20 maybe not followed the standard. Anyway, OPTION packets works well for NAT KEEP-ALIVE right? Do we really need line 519(as the above code)? or should we make another setting parameter say "nat_session_timeout" in sofia profile? Do I need to post this on jira? On Mar 1, 2009, at 4:19 AM, Brian West wrote:
If you go look in sofia's code you see something like this:
/* refresh 30..60 seconds before deadline */
/* By default, refresh around half time before deadline */
/b
On Feb 28, 2009, at 12:32 PM, seven du wrote:
Thanks Brian. I didn't know that before. But doesn't set the timer to 0 disable it? Or can I set to a very large value say 9999999?
Anyway, if I change session-timeout, should I see the difference at the sip response header "Session-Expires: 120;refresher=uas" right?
Do you think it related to this?
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org