From FreeSWITCH Wiki

Contents 1 Examples for specific cards 1.1 Wildcard T100P 1.2 Sangoma A101 1.3 Sangoma A200/A400 1.4 Tormenta2 1.5 Digium TDM400

Examples for specific cards

Wildcard T100P

• Wildcard T100P (should also work with similar zaptel cards):

 [span zt]
 trunk_type => t1
 b-channel => 1-23
 d-channel=> 24

Sangoma A101

• A101, A102, A104, A108 series and variants

 [span wanpipe]
 trunk_type => t1
 b-channel => 1:1-23
 d-channel=> 1:24

Sangoma A200/A400

• A200, A200D, A400, A400D series and variants

The configuration depends on wether wanpipe is configured to use Zaptel TDM Voice, or the Sangoma standalone TDM Voice API. This is determined in the installation and configuration of the Sangoma wanpipe software.

If wanpipe is using Zaptel, you need to configure openconf.conf with [span zt] entries. For example, if ports 1 and 2 are FXO (e.g. configured to accept PSTN analog lines), and ports 3 and 4 are FXS (e.g. configured to accept analog phone connections) you will need:

/etc/openzap/openzap.conf:

[span zt]
name => OpenZAP
number => 3001
fxo-channel => 1
number => 3002
fxo-channel => 2

[span zt]
name => OpenZAP
number => 4165551111
fxs-channel => 3
number => 4165552222
fxs-channel => 4

If wanpipe is standalone, you need to configure openconf.conf with [span wanpipe] entries. For the same example as above this would be:

/etc/openzap/openzap.conf:

[span wanpipe]
name => OpenZAP
number => 3001
fxo-channel => 1:1
number => 3002
fxo-channel => 1:2

[span wanpipe]
name => OpenZAP
number => 4165551111
fxs-channel => 1:3
number => 4165552222
fxs-channel => 1:4

Also, note that in addition to configuring /etc/openzap/openzap.conf, you need to properly configure openzap.conf.xml in freeswitch/conf/autoload_configs/.

Tormenta2

• A sample Tor2 setup with spans 1 and 2 set for FXO/FXS and spans 3 and 4 set for PRI, corresponds to Second openzap.conf.xml example:

[span zt]
name => OpenZAP
number => 1
fxs-channel => 1-24

[span zt]
name => OpenZAP
number => 2
fxo-channel => 25-48
# Note: when using FXO/FXS on a digital span, do not set the trunk_type; OpenZAP will do it automatically

[span zt]
name => OpenZAP
number => 3
trunk_type => t1
b-channel => 49-71
d-channel => 72

[span zt]
name => OpenZAP
number => 4
trunk_type => t1
b-channel => 73-95
d-channel => 96

• The /etc/zaptel.conf file for this tor2 config looks something like this:

## Test FreeSWITCH/OpenZAP config

span=1,0,0,esf,b8zs # FS to FXS span
fxoks=1-24

span=2,0,0,esf,b8zs # FS to FXO span
fxsks=25-48

span=3,1,0,esf,b8zs # PRI circuit
bchan=49-71
dchan=72

span=4,1,0,esf,b8zs # PRI circuit
bchan=73-95
dchan=96

# Global data

loadzone        = us
defaultzone     = us

Digium TDM400

• A sample Digium TDM400 setup with spans 3 and 4 set for FXO and span 1 for FXS

[span zt]
name => OpenZAP-FXS
number => 1
fxs-channel => 1

[span zt]
name => OpenZAP-FXO1
number => 2
fxo-channel => 3

[span zt]
name => OpenZAP-FXO2
number => 3
fxo-channel => 4