Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following snippet show examples of the two Dahdi configuration files which must be manually created to use OpenR2 with Asterisk.  
All the parameters listed below are further explained in the next section of this page.  Full A102 sample config files can be found in the quick-configuration section.

Example chan_dahdi.conf

Code Block
group=0
context=from-pstn
signalling=mfcr2
mfcr2_variant=mx
mfcr2_get_ani_first=no
mfcr2_max_ani=10
mfcr2_max_dnis=4
mfcr2_category=national_subscriber
mfcr2_call_files=yes
mfcr2_logdir=span1
mfcr2_logging=all
mfcr2_mfback_timeout=-1
mfcr2_metering_pulse_timeout=-1
channel => 1-15,17-31

...

Code Block
#Sangoma A101 port 1 [slot:4 bus:2 span:1] <wanpipe1>
span=1,1,0,cas,hdb3
cas=1-15,17-31:1101
dchan=16
echocanceller=mg2,1-15,17-31
  • NOTES:The “span” lines determines, of course, the span configuration. You can see an span as a group of channels. You can see how many spans are registered by listing the contents of directory /proc/dahdi. Each file listed in that directory represents a span, whether or not this span represents a hardware group of channels or a software emulation channel depends on the type of the span

Configure chan_dahdi.conf

...

This snippet states that the range of channels from x to y (integer values) will report CAS bits. The :1101 is the initial position
of the CAS bits (also known as ABCD bits) which are used by R2 to signal line state (see the R2 troubleshooting section for details). 
The 1101 signal means “Blocked” in R2, which means that when the hardware wakes
up for the first time it is not able to receive calls (Asterisk or any other software using R2 will later
change this bits to 1001, which means IDLE, or ready to make calls).

...

Wanpipe Configuration

As shown in the quick-configuration section a good way to start the configuration of an R2 system for use with Asterisk is to run the normal Sangoma configuration script:

...