Page Comparison

IMPORTANT Driver Information

wanpipe 3.3.15 RPMs are located at tech2:~gcolburn/sangoma-latest

...

Sangoma Wanpipe: Asterisk SMG/BRI Install

...

1. After wancfg_smg configures all the cards, you will have an option to stop and restart Wanpipe/SMG/BRI and Asterisk.

   If you do not select the "Restart Wanpipe/SMG/BRI and Asterisk option:

   The startup procedure is comprised of three steps:

   1. wanrouter start
      Starts all wanpipe A500 BRI ports:
      #> wanrouter start
      Usage: wanrouter [start|stop|restart]2.

   2. smg_ctrl start
      Starts SMG/BRI daemons. (equivalent to ztcfg step when working with zaptel):
      #> smg_ctrl start

      Usage: smg_ctrl [start|stop|restart]3.

   3. asterisk
      Start asterisk:
      #> asterisk

      Connect to asterisk CLI:
      #> asterisk -r
      

2. At this point we are ready to write our Dial Plan in /etc/asterisk/extensions.conf
   Asterisk will connect to the SMG daemon using a woomera channel driver.
   The Dial Plan syntax is 100% identical to Zaptel but instead of using Zap as a channel identifier we will use WOOMERA.

   This is an example of /etc/asterisk/extensions.conf
      ;Sangoma SMG Outbound context
       ;Place call on woomera channel to SMG/BRI
       ;==================================

       [outb]
       exten => _X.,1,noop
       exten => _X.,n,Dial(WOOMERA/g1/${EXTEN}|60|o)
       exten => _X.,n,Hangup

       ;Sangoma SMG Incoming Contexts
       ;Context name defined in /etc/asterisk/woomera.conf
       ;====================================

       [sangoma]
       exten => _X.,1,noop
       exten => _X.,n,Playback(demo-congrats)
       exten => _X.,n,Hangup

       ;Early Media Example
       ;To play a file without answering the call

       [sangoma4]
       exten => _X.,1,noop
       exten => _X.,n,Playback(demo-congrats|noanswer)
       exten => _X.,n,Hangup

3. At this point, the system is ready to make test calls.

...

Asterisk SMG/BRI Troubleshooting Debugging

...

If the port switched to connected state, but the call failed, you have a protocol problem. Check /var/log/sangoma_mgd and /var/log/sangoma_bri.log for protocol errors. If you cannot determine the protocol errors, email your configuration and log files to Sangoma Tech Support. List of files and info required when contacting Techdesk

6. Make an incoming call from Asterisk:
   You should see a message like:
   (sNcX) Incoming call on Trunkgrp:X....

   Once the remote party answers the call, you should see "Call connected"

...

For initial support and questions contact Sangoma Techdesk:
http://wiki.sangoma.com/SangomaTechSupport Sangoma Techdesk
    See the "Asterisk and BRI" section for list of required information

...

TRANSPARENT_OVERLAP_RCV (default = disabled)
    Only used in overlap receiving mode. On incoming calls, the call is forwared forwarded to the "s" extension in Asterisk and incoming out of band digits are forwarded as DTMF digits to Asterisk.

...