Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
A
asterisk
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Issue analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Voice
asterisk
Commits
3d5c61d2
Commit
3d5c61d2
authored
8 years ago
by
zuul
Committed by
Gerrit Code Review
8 years ago
Browse files
Options
Downloads
Plain Diff
Merge "chan_sip: Fix typo and re-wrap surrounding docs"
parents
9df59d9f
73524bde
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
channels/chan_sip.c
+23
-17
23 additions, 17 deletions
channels/chan_sip.c
with
23 additions
and
17 deletions
channels/chan_sip.c
+
23
−
17
View file @
3d5c61d2
...
...
@@ -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.
*/
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment