sysmocom
/
asterisk
11
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

chan_sip: Fix typo and re-wrap surrounding docs 

Correct typo of end-pints to end-points
Re-wrap session timer parameter docs to max 80 chars wide; this
eases reading on terminals with lower resolution, commonly the case
for those with visual impairments.

ASTERISK-26573

Change-Id: I22c94459f4bb6b8a2f6713cfd22e87c32f204e6b
Signed-off-by: C.J. Collier <cjcollier@linuxfoundation.org>
This commit is contained in:
C.J. Collier 2016-11-10 11:38:25 -08:00 committed by Joshua Colp
parent e5860ce07d
commit 73524bde9c
1 changed files with 23 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
channels/chan_sip.c
View File

@ -199,23 +199,29 @@
The session-timers parameter in sip.conf defines the mode of operation of SIP session-timers feature in
Asterisk. The Asterisk can be configured in one of the following three modes:
1. Accept :: In the "accept" mode, the Asterisk server honors session-timers requests
made by remote end-points. A remote end-point can request Asterisk to engage
session-timers by either sending it an INVITE request with a "Supported: timer"
header in it or by responding to Asterisk's INVITE with a 200 OK that contains
Session-Expires: header in it. In this mode, the Asterisk server does not
request session-timers from remote end-points. This is the default mode.
2. Originate :: In the "originate" mode, the Asterisk server requests the remote
end-points to activate session-timers in addition to honoring such requests
made by the remote end-pints. In order to get as much protection as possible
against hanging SIP channels due to network or end-point failures, Asterisk
resends periodic re-INVITEs even if a remote end-point does not support
the session-timers feature.
3. Refuse :: In the "refuse" mode, Asterisk acts as if it does not support session-
timers for inbound or outbound requests. If a remote end-point requests
session-timers in a dialog, then Asterisk ignores that request unless it's
noted as a requirement (Require: header), in which case the INVITE is
rejected with a 420 Bad Extension response.
1. Accept :: In the "accept" mode, the Asterisk server honors
session-timers requests made by remote end-points. A remote
end-point can request Asterisk to engage session-timers by either
sending it an INVITE request with a "Supported: timer" header in
it or by responding to Asterisk's INVITE with a 200 OK that
contains Session-Expires: header in it. In this mode, the Asterisk
server does not request session-timers from remote
end-points. This is the default mode.
2. Originate :: In the "originate" mode, the Asterisk server
requests the remote end-points to activate session-timers in
addition to honoring such requests made by the remote
end-points. In order to get as much protection as possible against
hanging SIP channels due to network or end-point failures,
Asterisk resends periodic re-INVITEs even if a remote end-point
does not support the session-timers feature.
3. Refuse :: In the "refuse" mode, Asterisk acts as if it does not
support session- timers for inbound or outbound requests. If a
remote end-point requests session-timers in a dialog, then
Asterisk ignores that request unless it's noted as a requirement
(Require: header), in which case the INVITE is rejected with a 420
Bad Extension response.
*/