summaryrefslogtreecommitdiff
path: root/doc/tex/sla.tex
diff options
context:
space:
mode:
authorRussell Bryant <russell@russellbryant.com>2007-10-15 13:12:51 +0000
committerRussell Bryant <russell@russellbryant.com>2007-10-15 13:12:51 +0000
commit4765cf4553924050a3c0bfa581efaba8ffc50c55 (patch)
tree10e1f9eaad925e0834d16a91560765b0c2259636 /doc/tex/sla.tex
parent27031927cf43efe9922557c011d282a0486d40aa (diff)
Another major doc directory update from IgorG. This patch includes
- Many uses of the astlisting environment around verbatim text to ensure that it gets properly formatted and doesn't run off the page. - Update some things that have been deprecated. - Add escaping as needed - and more ... (closes issue #10978) Reported by: IgorG Patches: texdoc-85542-1.patch uploaded by IgorG (license 20) git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@85547 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'doc/tex/sla.tex')
-rw-r--r--doc/tex/sla.tex33
1 files changed, 21 insertions, 12 deletions
diff --git a/doc/tex/sla.tex b/doc/tex/sla.tex
index 35975407f..afafd2ae4 100644
--- a/doc/tex/sla.tex
+++ b/doc/tex/sla.tex
@@ -56,13 +56,14 @@ An SLA trunk is a mapping between a virtual trunk and a real Asterisk device.
This device may be an analog FXO line, or something like a SIP trunk. A trunk
must be configured in two places. First, configure the device itself in the
channel specific configuration file such as zapata.conf or sip.conf. Once the
-trunk is configured, then map it to an SLA trunk in sla.conf.
-
+trunk is configured, then map it to an SLA trunk in sla.conf.
+\begin{astlisting}
\begin{verbatim}
[line1]
type=trunk
device=Zap/1
\end{verbatim}
+\end{astlisting}
Be sure to configure the trunk's context to be the same one that is set for the
"autocontext" option in sla.conf if automatic dialplan configuration is used.
@@ -84,26 +85,27 @@ going to say that they are calling the number "12564286000". Also, let's say
that the numbers that are valid for calling out this trunk are NANP numbers,
of the form \_1NXXNXXXXXX.
-In sip.conf, there would be an entry for [mytrunk]. For [mytrunk],
+In sip.conf, there would be an entry for [mytrunk]. For [mytrunk],
set context=line4.
-
+\begin{astlisting}
\begin{verbatim}
[line4]
type=trunk
device=Local/disa@line4_outbound
\end{verbatim}
+\end{astlisting}
-
+\begin{astlisting}
\begin{verbatim}
[line4]
exten => 12564286000,1,SLATrunk(line4)
[line4_outbound]
exten => disa,1,Disa(no-password,line4_outbound)
-exten => _1NXXNXXXXXX,1,Dial(SIP/\${EXTEN}@mytrunk)
+exten => _1NXXNXXXXXX,1,Dial(SIP/${EXTEN}@mytrunk)
\end{verbatim}
-
+\end{astlisting}
So, when a station picks up their phone and connects to line 4, they are
connected to the local dialplan. The Disa application plays dialtone to the
@@ -116,8 +118,9 @@ SIP trunk.
An SLA station is a mapping between a virtual station and a real Asterisk device.
Currently, the only channel driver that has all of the features necessary to
support an SLA environment is chan\_sip. So, to configure a SIP phone to use
-as a station, you must configure sla.conf and sip.conf.
+as a station, you must configure sla.conf and sip.conf.
+\begin{astlisting}
\begin{verbatim}
[station1]
type=station
@@ -125,6 +128,7 @@ device=SIP/station1
trunk=line1
trunk=line2
\end{verbatim}
+\end{astlisting}
Here are some hints on configuring a SIP phone for use with SLA:
@@ -141,7 +145,7 @@ Here are some hints on configuring a SIP phone for use with SLA:
Let's say this phone is called "station1" in sla.conf, and it uses trunks
named "line1" and line2".
\begin{enumerate}
-
+
\item Two line buttons must be configured to subscribe to the state of the
following extensions:
- station1\_line1
@@ -165,6 +169,7 @@ This is an example of the most basic SLA setup. It uses the automatic
dialplan generation so the configuration is minimal.
sla.conf:
+\begin{astlisting}
\begin{verbatim}
[line1]
type=trunk
@@ -190,8 +195,8 @@ device=SIP/station2
[station3](station)
device=SIP/station3
-
\end{verbatim}
+\end{astlisting}
With this configuration, the dialplan is generated automatically. The first
zap channel should have its context set to "line1" and the second should be
@@ -199,6 +204,7 @@ set to "line2" in zapata.conf. In sip.conf, station1, station2, and station3
should all have their context set to "sla\_stations".
For reference, here is the automatically generated dialplan for this situation:
+\begin{astlisting}
\begin{verbatim}
[line1]
exten => s,1,SLATrunk(line1)
@@ -225,7 +231,7 @@ exten => station3_line1,1,SLAStation(station3_line1)
exten => station3_line2,hint,SLA:station3_line2
exten => station3_line2,1,SLAStation(station3_line2)
\end{verbatim}
-
+\end{astlisting}
\subsection{SLA and Voicemail}
\label{voicemail}
@@ -247,6 +253,7 @@ NANP numbers for outbound calls, or 8500 for checking voicemail.
sla.conf:
+\begin{astlisting}
\begin{verbatim}
[line1]
type=trunk
@@ -271,9 +278,10 @@ device=SIP/station2
device=SIP/station3
\end{verbatim}
-
+\end{astlisting}
extensions.conf:
+\begin{astlisting}
\begin{verbatim}
[macro-slaline]
exten => s,1,SLATrunk(${ARG1})
@@ -318,6 +326,7 @@ exten => station3_line2,hint,SLA:station3_line2
exten => station3_line2,1,SLAStation(station3_line2)
\end{verbatim}
+\end{astlisting}
\section{Call Handling}
\subsection{Summary}