Page 105 - Asterisk™: The Future of Telephony
P. 105

# /sbin/ztcfg -vv
               The channels that are configured and the signaling method being used will be displayed.
               For example, a TDM400P with one FXO module has the following output:
                   Zaptel Configuration
                   ======================
                   Channel map:
                   Channel 02: FXS Kewlstart (Default) (Slaves: 02)
                   1 channels configured.
               If you receive the following error, you have configured the channel for the wrong sig-
               naling method (or there is no hardware present at that address):
                   ZT_CHANCONFIG failed on channel 2: Invalid argument (22)
                   Did you forget that FXS interfaces are configured with FXO signaling
                   and that FXO interfaces use FXS signaling?
               To unload drivers from memory, use the rmmod (remove module) command, like so:
                   # rmmod wctdm
               The zttool program is a diagnostic tool used to determine the state of your hardware.
               After running it, you will be presented with a menu of all installed hardware. You can
               then select the hardware and view the current state. A state of “OK” means the hardware
               is successfully loaded:
                   Alarms          Span
                   OK              Wildcard TDM400P REV E/F Board 1

               Zapata Hardware Configuration

               Asterisk uses the zapata.conf file to determine the settings and configuration for tel-
               ephony hardware installed in the system. The zapata.conf file also controls the various
               features and functionality associated with the hardware channels, such as Caller ID,
               call waiting, echo cancellation, and a myriad of other options.
               When you configure zaptel.conf and load the modules, Asterisk is not aware of anything
               you’ve configured. The hardware doesn’t have to be used by Asterisk; it could very well
               be used by another piece of software that interfaces with the Zaptel modules. You tell
               Asterisk about the hardware and control the associated features via zapata.conf:
                   [trunkgroups]
                   ; define any trunk groups
                   [channels]
                   ; hardware channels





               * It is generally safe to assume that the modules have loaded successfully, but to view the debugging output
                 when loading the module, check the console output (by default this is located on TTY terminal 9, but this is
                 configurable in the safe_asterisk script—see the previous chapter for details).

                                                      Configuring an FXO Channel for a PSTN Connection | 77
   100   101   102   103   104   105   106   107   108   109   110