* To enable RBS debugging on reciever side (this command will print only changes to the RBS bit settings):
wanpipemon -i
* To disable RBS debugging on reciever side:
wanpipemon -i
* To enable RBS debugging on transmit side (this command will print only changes to the RBS bit settings):
wanpipemon -i
* To disable RBS debugging on transmit side:
wanpipemon -i
* Read the current RBS status bits from AFT-series cards:
wanpipemon -i
* Read the current RBS status from the Wanpipe driver:
wanpipemon -i
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.
- In one window run: zttool
- In another window run: tail -f /var/log/messages
- Enable RBS debugging as stated above:
wanpipemon -i-c derr #Enable rx rbs debugging
wanpipemon -i-c dert #Enable tx rbs debugging - Place a call on Asterisk with reproducable bad behaviour
- 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. - If zttool output doesnt match wanpipe rbs output please contact Sangoma Support.
No comments:
Post a Comment