; THIS CONFIGURATION PROVIDES SIP AND IAX2 CONNECTIVITY TO LEGACY ; OR COLLECTIBLE TELEPHONE SYSTEMS THAT ARE SET UP AS PBXES. ; ; THIS EXAMPLE FILE ASSUMES A CERTAIN CONFIGURATION, BUT CAN EASILY BE ; MODIFIED TO PROVIDE FOR DIFFERENCES WITH INDIVIDUAL PHONE SWITCHES. ; ; THIS SAMPLE SYSTEM IS CONFIGURED AS FOLLOWS: ; + MEMBERSHIP ON THE PRIVATE "976" OFFICE CODE (NXX). ; + OWNERSHIP OF THE DID BLOCK 976-9900 THROUGH 976-9999. ; + TWO-DIGIT DIALING TOWARDS PHONE SYSTEM FROM ASTERISK ; + DIAL-8 AND 4-DIGIT DIALING ACROSS THE NET ; ; The "General" category is for certain variables. ; [general] ; ; You can include other config files, use the #include command (without the ';') ; Note that this is different from the "include" command that includes contexts within ; other contexts. The #include command works in all asterisk configuration files. ;#include "filename.conf" ; The "Globals" category contains global variables that can be referenced ; in the dialplan with ${VARIABLE} or ${ENV(VARIABLE)} for Environmental variable ; ${${VARIABLE}} or ${text${VARIABLE}} or any hybrid ; ; ; exten => i,1,Background(ss-noservice) ; ; [globals] CNETANI=9769900 CONSOLE=Console/dsp ; Console interface for demo MYNAME=DOAKES JOE TRUNK=Zap/g1 ; Trunk interface (TK GP 1) TRUNKMSD=1 ; ; ; Any category other than "General" and "Globals" represent ; extension contexts, which are collections of extensions. ; ; Extension names may be numbers, letters, or combinations ; thereof. If an extension name is prefixed by a '_' ; character, it is interpreted as a pattern rather than a ; literal. In patterns, some characters have special meanings: ; ; X - any digit from 0-9 ; Z - any digit from 1-9 ; N - any digit from 2-9 ; [1235-9] - any digit in the brackets (in this example, 1,2,3,5,6,7,8,9) ; . - wildcard, matches anything remaining (e.g. _9011. matches ; anything starting with 9011 excluding 9011 itself) ; ; For example the extension _NXXXXXX would match normal 7 digit dialings, ; while _1NXXNXXXXXX would represent an area code plus phone number ; preceeded by a one. ; ; Contexts contain several lines, one for each step of each ; extension, which can take one of two forms as listed below, ; with the first form being preferred. One may include another ; context in the current one as well, optionally with a ; date and time. Included contexts are included in the order ; they are listed. ; ;[context] ;exten => someexten,priority,application(arg1,arg2,...) ;exten => someexten,priority,application,arg1|arg2... ; ; Timing list for includes is ; ;