[asterisk-commits] russell: branch russell/sla_updates r57363 - in
/team/russell/sla_updates: co...
asterisk-commits at lists.digium.com
asterisk-commits at lists.digium.com
Thu Mar 1 16:32:03 MST 2007
Author: russell
Date: Thu Mar 1 17:32:03 2007
New Revision: 57363
URL: http://svn.digium.com/view/asterisk?view=rev&rev=57363
Log:
So yeah, about those IP trunks that I claimed didn't work ... they work.
I have added docs describing how to set them up. While I was at it, I wrote
a section describing how to configure an SLA system with voicemail.
Modified:
team/russell/sla_updates/configs/sla.conf.sample
team/russell/sla_updates/doc/sla.txt
Modified: team/russell/sla_updates/configs/sla.conf.sample
URL: http://svn.digium.com/view/asterisk/team/russell/sla_updates/configs/sla.conf.sample?view=diff&rev=57363&r1=57362&r2=57363
==============================================================================
--- team/russell/sla_updates/configs/sla.conf.sample (original)
+++ team/russell/sla_updates/configs/sla.conf.sample Thu Mar 1 17:32:03 2007
@@ -18,7 +18,10 @@
;type=trunk ; This line is what marks this entry as a trunk.
;device=Zap/3 ; Map this trunk declaration to a specific device.
- ; NOTE: At this point, this *must* be a zap channel!
+ ; NOTE: You can not just put any type of channel here.
+ ; Zap channels can be directly used. IP trunks
+ ; require some indirect configuration which is
+ ; described in doc/sla.txt.
;autocontext=line1 ; This supports automatic generation of the dialplan entries
; if the autocontext option is used. Each trunk should have
@@ -52,7 +55,10 @@
;[line4]
;type=trunk
-;device=Zap/4
+;device=Local/disa at line4_outbound ; A Local channel in combination with the Disa
+ ; application can be used to support IP trunks.
+ ; See doc/sla.txt on more information on how
+ ; IP trunks work.
;autocontext=line4
; --------------------------------------
Modified: team/russell/sla_updates/doc/sla.txt
URL: http://svn.digium.com/view/asterisk/team/russell/sla_updates/doc/sla.txt?view=diff&rev=57363&r1=57362&r2=57363
==============================================================================
--- team/russell/sla_updates/doc/sla.txt (original)
+++ team/russell/sla_updates/doc/sla.txt Thu Mar 1 17:32:03 2007
@@ -18,7 +18,10 @@
basic operation if the "autocontext" option is set for trunks and stations in
sla.conf. However, for reference, here is an automatically generated dialplan
to help with custom building of the dialplan to include other features, such as
-voicemail:
+voicemail.
+
+However, note that there is a little bit of additional configuration needed if
+the trunk is an IP channel. This is discussed in the TRUNKS section.
[line1]
exten => s,1,SLATrunk(line1)
@@ -49,14 +52,52 @@
-------------------------------------------------------------------------------
TRUNKS
-For the trunk side of SLA, the only channels that are currently supported are
-Zap channels. Support for IP trunks is planned, but not yet implemented.
-
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.
+This would be done in the regular device entry in zapata.conf, sip.conf, etc.
+Note that the automatic dialplan generation creates the SLATrunk() extension
+at extension 's'. This is perfect for Zap channels that are FXO trunks, for
+example. However, it may not be good enough for an IP trunk, since the call
+coming in over the trunk may specify an actual number.
If the dialplan is being built manually, ensure that calls coming in on a trunk
-execute the SLATrunk() application with an argument of the trunk name.
+execute the SLATrunk() application with an argument of the trunk name, as shown
+in the dialplan example before.
+
+IP trunks can be used, but they require some additional configuration to work.
+
+For this example, let's say we have a SIP trunk called "mytrunk" that is going
+to be used as line4. Furthermore, when calls come in on this trunk, they are
+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],
+set context=line4.
+
+
+sla.conf:
+
+[line4]
+type=trunk
+device=Local/disa at line4_outbound
+
+
+extensions.conf:
+
+[line4]
+exten => 12564286000,1,SLATrunk(line4)
+
+[line4_outbound]
+exten => disa,1,Disa(no-password|line4_outbound)
+exten => _1NXXNXXXXXX,1,Dial(SIP/${EXTEN}@mytrunk)
+
+
+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
+phone and collects digits until it matches an extension. In this case, once
+the phone dials a number like 12565551212, the call will proceed out the
+SIP trunk.
-------------------------------------------------------------------------------
@@ -91,3 +132,94 @@
is taken off hook, then the phone should be automatically configured to
dial "station1" when it is taken off hook.
-------------------------------------------------------------------------------
+
+
+-------------------------------------------------------------------------------
+VOICEMAIL
+
+This is an example of how you could set up a single voicemail box for the
+phone system. The voicemail box number used in this example is 1234, which
+would be configured in voicemail.conf.
+
+For this example, assume that there are 2 trunks and 3 stations. The trunks
+are Zap/1 and Zap/2. The stations are SIP/station1, SIP/station2, and
+SIP/station3.
+
+In zapata.conf, channel 1 has context=line1 and channel 2 has context=line2.
+
+In sip.conf, all three stations are configured with context=sla_stations.
+
+When the stations pick up their phones to dial, they are allowed to dial
+NANP numbers for outbound calls, or 8500 for checking voicemail.
+
+
+sla.conf:
+
+[line1]
+type=trunk
+device=Local/disa at line1_outbound
+
+[line2]
+type=trunk
+device=Local/disa at line2_outbound
+
+[station](!)
+type=station
+trunk=line1
+trunk=line2
+
+[station1](station)
+device=SIP/station1
+
+[station2](station)
+device=SIP/station2
+
+[station3](station)
+device=SIP/station3
+
+
+extensions.conf:
+
+[macro-slaline]
+exten => s,1,SLATrunk(${ARG1})
+exten => s,n,Goto(s-${SLATRUNK_STATUS}|1)
+exten => s-FAILURE,1,Voicemail(1234|u)
+exten => s-UNANSWERED,1,Voicemail(1234|u)
+
+[line1]
+exten => s,1,Macro(slaline|line1)
+
+[line2]
+exten => s,2,Macro(slaline|line2)
+
+[line1_outbound]
+exten => disa,1,Disa(no-password|line1_outbound)
+exten => _1NXXNXXXXXX,1,Dial(Zap/1/${EXTEN})
+exten => 8500,1,VoicemailMain(1234)
+
+[line2_outbound]
+exten => disa,1,Disa(no-password|line2_outbound)
+exten => _1NXXNXXXXXX,1,Dial(Zap/2/${EXTEN})
+exten => 8500,1,VoicemailMain(1234)
+
+[sla_stations]
+
+exten => station1,1,SLAStation(station1)
+exten => station1_line1,hint,SLA:station1_line1
+exten => station1_line1,1,SLAStation(station1_line1)
+exten => station1_line2,hint,SLA:station1_line2
+exten => station1_line2,1,SLAStation(station1_line2)
+
+exten => station2,1,SLAStation(station2)
+exten => station2_line1,hint,SLA:station2_line1
+exten => station2_line1,1,SLAStation(station2_line1)
+exten => station2_line2,hint,SLA:station2_line2
+exten => station2_line2,1,SLAStation(station2_line2)
+
+exten => station3,1,SLAStation(station3)
+exten => station3_line1,hint,SLA:station3_line1
+exten => station3_line1,1,SLAStation(station3_line1)
+exten => station3_line2,hint,SLA:station3_line2
+exten => station3_line2,1,SLAStation(station3_line2)
+
+-------------------------------------------------------------------------------
More information about the asterisk-commits
mailing list