The wanpipemon utility provides the ability to debug RBS bits. The following command enables/disables WANPIPE RBS debugging and prints all debugging message into the /var/log/messages file. This feature is supported for all Sangoma digital AFT-series cards.

* To enable RBS debugging on reciever side (this command will print only changes to the RBS bit settings):
        wanpipemon -i <interface name> -c derr

* To disable RBS debugging on reciever side:
        wanpipemon -i <interface name> -c ddrr

* To enable RBS debugging on transmit side (this command will print only changes to the RBS bit settings):
       wanpipemon -i <interface name> -c dert

* To disable RBS debugging on transmit side:
       wanpipemon -i <interface name> -c ddrt

* Read the current RBS status bits from AFT-series cards:
       wanpipemon -i <interface name> -c drr

* Read the current RBS status from the Wanpipe driver:
       wanpipemon -i <interface name> -c dpr

In order to verify the RBS operations, you can run ./zttool utility and enable Sangoma RBS debugging at the same time. Zttoll shows what zaptel thinks is the RBS setting and the wanpipe utilities show what the sangoma driver thinks is the RBS setting. The two have to match at all times.

1. In one window run:  zttool
    
2. In another window run: tail -f /var/log/messages
    
3. Enable RBS debugging as stated above:
   wanpipemon -i <interface name> -c derr  #Enable rx rbs debugging
   wanpipemon -i <interface name> -c dert  #Enable tx rbs debugging
    
4. Place a call on Asterisk  with reproducable bad behaviour
    
5. Compare zttool output versus the /var/log/messages
   If driver rbs changes are identical to zttool rbs changes problem is with the telco.
   If driver rbs changes differ from zttool rbs changes there could be a problem with the drivers.
    
6. If zttool output doesnt match wanpipe rbs output please contact Sangoma Support.

Asterisk PRI Span Debugging

Please follow these steps when faced with dead span:
Record the stdout to file for each command.

1. wanrouter status
   Check that wanpipe status is Connected
    
2. wanpipemon -i w1g1 -c Ta
   Check the physical T1/E1 Alarms
    
3. Run: ifconfig
   Make sure that tx/rx counters are incrementing.
    
4. tail -f -n 100 /var/log/messages
   Check for any wanpipe errors in messages
    
5. wanpipemon -i w1g1 -c trd
   Run a dchan trace and check that you are seeing incoming and outgoing traffic.
    
6. From asterisk CLI
   run:   pri show span 1
            Check that spans are UP and Active.

Please send the output of all the above commands to sangoma support (techdesk@sangoma.com) so we can better determine the issue at hand.