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