Synopsis The /etc/asterisk/zapata.conf file contains parameters relating to channels provided by the zaptel interface layer. Channels must be defined in this file before they can be used by Asterisk. In addition, a number of features relating to Asterisk's operation of the channels may be configured here. Arrangement The /etc/asterisk/zapata.conf file consists of keyword and valuepairs. Keywords set parameters for the operation of channels. They may be boolean (yes/no) or contain values specific to the keyword. Most keywords set parameters for the operation of channels. Values remain in effect for all following channel definitions until they are overidden.
These keywords are available in /etc/asterisk/zapata.conf. context: Defines the initial context for thechannel. This will be the context available to the channel upon the initiation of a call. Note that contexts are an important part of maintaining site security. The initial context will govern the availability of extensions to a given channel. If an extension is placed in a different context from the initial context, that extension is unavailable to the caller. Note: Careless use of contexts canallow open access to billable services and internal features. channel: Define a channel or range of channels. Each channel definition will inherit all options stated ahead of it in the file. Examples channel => 2 channel => 1-8 group: Allows a number of channels to be treated as one for the purpose of dialing. For dialing out, the channels will be called on a first available basis. For the purposeof ringing stations, all channels in the group will ring at once. Takes an integer.
switchtype: Sets the type of signalling used for a PRI line. Values available for switchtype are: national: dms100: 4ess: 5ess: euroisdn: Example switchtype => national National ISDN Nortel DMS100 AT&T 4ESS Lucent 5ESS EuroISDN
pri_dialplan: Sets an option required for some (rare) switches that require adialplan parameter to be passed. This option is ignored by most PRI switches. It may be necessary on a few pieces of hardware. Valid options are unknown, local, private, national, and international. This option can almost always be left unset. signalling: Sets the signaling type for following channel definitions. These should follow the channels as defined in /etc/zaptel.conf. Correct choices arebased on the hardware available. Asterisk will fail to start if a channel signaling definition is incorrect or unworkable, if the statements do not match zaptel.conf, or if the device is not present or properly configured. Values available for signalling are: Note: Analog phone signalling can be a source of some confusion. FXS channels are signalled with FXO signalling, and vice versa. Asterisk'talks' to internal devices as the opposite side. An FXO interface card is signalled with FXS signalling by Asterisk, and should be configured as such. fxo_ks: Use FXO Kewlstart signalling. Used to signal an FXS device within the system, which would normally drive a handset or other station device. fxs_ks: The opposite side of fxo_ks. To signal an internal (or T1 connected) FXO device. fxo_gs: Use FXOgroundstart signalling. fxs_gs: Use FXS groundstart signalling. fxo_ls: Use FXO loopstart signalling fxs_ls: Use FXS loopstart signalling pri_cpe: Use PRI signalling, customer equipment side. Used when terminating a PRI line into Asterisk channels. pri_net: Use PRI signalling, network side. em: Use E&M signalling em_w: Use E&M wink signalling featd: Feature Group D, Adtran compatible. For use withthe Atlas and similar equipment made by Adtran. featdmf: standard Feature Group D.
featb: Feature Group B Examples signalling => fxs_ks signalling => featd Analog Call Progress These items are used to attempt to emulate having a smarter line (like a PRI) that gives us call progress information, when using analog channels that don't pass us any digital information. busydetect: Attempt to...