chan_sip: Enable Session-Timers for SIP over TCP (and TLS).

Asterisk defaults to timers=accept/refresher=uas. In that scenario, only in that
scenario, Sessions-Timers (RFC 4028) had no effect via TCP. This change enables
Session-Timers for SIP over TCP (and for SIP over TLS).

However with longer international calls via TCP, the SIP channel might break,
because all hops on the Internet route must stay online (have not a single power
outage, for example). Therefore with Session-Timers enabled (which are enabled
at default), you might see dropped calls. Consequently even with this change,
you might be better-off going for session-timers=refuse in your sip.conf.

ASTERISK-19968 #close

Change-Id: I1cd33453c77c56c8e1394cd60a6f17bb61c1d957
This commit is contained in:
Alexander Traud
2016-07-22 12:46:02 +02:00
parent 0de05c2938
commit 66c9dfb272
2 changed files with 30 additions and 32 deletions

10
CHANGES
View File

@@ -18,6 +18,16 @@ chan_dahdi
The option determines how many seconds into a call before faxdetect
is disabled for the call. Setting the value to zero disables the timeout.
chan_sip
------------------
* Session-Timers (RFC 4028) work for TCP (and TLS) transports as well now.
Previously Asterisk dropped calls only with UDP transports. However with
longer international calls via TCP, the SIP channel might break, because
all hops on the Internet route must stay online (have not a single power
outage, for example). Therefore with Session-Timers enabled (which are
enabled at default), you might see additional dropped calls. Consequently
please, consider to go for session-timers=refuse in your sip.conf.
res_pjsip
------------------
* Added "fax_detect_timeout" to endpoint.