System information

complete the call. In this example, we use the DISA() application locally to provide a
dialtone and collect digits. Once a complete number has been dialed, the call will pro-
ceed to go out to a SIP provider:
[line1_outbound]
exten => disa,1,DISA(no-password,line1_outbound)
;
; Add extensions for whatever numbers you would like to
; allow to be dialed.
;
exten => _1NXXNXXXXXX,1,Dial(SIP/${EXTEN}@myprovider)
[line2_outbound]
exten => disa,1,DISA(no-password,line2_outbound)
exten => _1NXXNXXXXXX,1,Dial(SIP/${EXTEN}@myprovider)
Shared Extension Example
The previous two examples were for small key system emulation. For this example,
we’ll try something quite different. Many PBX vendors offer the ability to have the same
extension shared across multiple phones. This is not simply a matter of having multiple
phones ring when an extension is called: it is deeper integration than that. The behavior
of the line key for a shared extension is similar to that of a line key on a key system. For
example, you can simply put a call on hold from one phone and pick it up from another.
Also, if multiple phones press the key for the shared extension, they will all be bridged
into the same call. That is why this functionality is often also referred to as Bridged Line
Appearances (BLA).
In the previous two examples, we had two trunks and four stations. For this example,
we’re going to set up a single shared extension on two phones. The shared extension
will be referred to as extension 5001.
sla.conf
Every usage of the SLA applications requires trunk and station definitions. This exam-
ple, like the previous ones, will be making use of the DISA() application and the
sla.conf file will look very similar:
[5001]
type = trunk
device = Local/disa@5001_outbound
[5001_phone1]
device = SIP/5001_phone1
trunk = 5001
[5001_phone2]
Shared Line Appearances | 325