SMG SS7 Debugging

Sangoma SMG SS7 product consists of the following:

1. Wanpipe : AFT Drivers/Utilies/MTP2
2. SS7 MTP3 Daemon :  ss7boxd
3. SS7 ISUP Daemon : ss7boost
4. Sangoma SMG Daemon : sangoma_mgd
5. Open Source PBX : Asterisk/CallWeaver/FreeSwtich
6. Woomera Debugging

Network Diagram:
 

Astersk <---(woomera) --> sangoma_mgd <---(sctp)---> sangoma_isupd <---(sctp)---> ss7box                                                    |                                                                                         |                                              wanpipe/AFT                                                           mtp2/wanpipe/AFT                                             voice only T1/E1                                                              A/F link ss7

 

FreeSwitch <---------------> OpenZap <---(sctp)---> sangoma_isupd <---(sctp)---> ss7box                                                    |                                                                                |                                              wanpipe/AFT                                                   mtp2/wanpipe/AFT                                             voice only T1/E1                                                     A/F link ss7

 
This document will describe how to debug and SMG SS7 system using the OSI Network Layer Model.  All debugging should be done from bottom up: from lowest layer wanpipe to highest Asterisk or FreeSwitch.

---

Wanpipe Debugging

Wanpipe is a suite of kernel device drivers, protocols and user space utilities that provide functionality to Sangoma AFT series cards.  A101/2/4/8.

Config FIles:

All wanpipe config files are located in /etc/wanpipe
There is a wanpipe conf file associated for each port of T1 or E1.
eg: wanpipe1.conf , wanpipe2.conf , wanpipe3.conf

Wanpipe config files are usually created using: /usr/sbin/wancfg_smg configurator 

Starting Wanpipe:

SMG product is usually started by
--> /etc/init.d/smgss7_init_ctrl start

Wanpipe can be individually started using
wanrouter start
wanrouter stop
wanrouter start wanpipe1
wanrouter stop wanpipe1

All error messages, events and status messages are logged in Kernel "INFO" messages. Usually located in /var/log/messages.

Debugging:

wanrouter status:   check the status of T1/E1 lines                            

If wanpipe card status is NOT connected you have T1/E1 issues, there is no point of going further.
You can run: wanpipemon -i w1g1 -c Ta  to check T1/E1 Alarms.

Cables:
At this point you have to check your cables usually a straight cable is needed, in some weird circumstances if smartjack is not wired properly a back to back cable could work.

Wanpipe Config File:
Check that T1/E1 clocking is set to NORMAL (so that clock is taken from telco)
For E1 confirm that your line is either CRC4 or NCRC4 (this is a common mistake)

Contact Telco and confirm what they see on their end.
Contact Sangoma Support

ifconfig:  Check for overruns

Make sure that rx and tx packet counters ARE increasing

This means that card interrupts are working properly and that voice data is flowing to and from the card

Make sure that NO rx overruns are incrementing

If you see rx overruns then interrupts are not being handled fast enough. You might have clocking issues or the system does not have proper device drives and is working in unoptimized mode.

 

---

ss7boxd (MTP3)  - ss7box Features    ss7box Manual

Config FIles:

/etc/ss7box/ss7box.conf

Starting ss7boxd

SMG product is usually started by
--> /etc/init.d/smgss7_init_ctrl start

ss7boxd can be individually started using:
--> /usr/local/ss7box/ss7boxd <enter>

Debugging

ss7boxd outputs all its events, errors and status in /var/log/messages

This indicates that the link has come in service
W:mtp3_slm.c:mtp3_lsac_ars:Link In Service:LS/LINK id follow::0:0
W:mtp3_slm.c:mtp3_llsc:LLSC_STATE_ACTIVE/LLSC_CAUSE_EMERGENCY_CEASES:lsi/caller follows:0:111

This indicates that the link is up (this message repeats every 30 sec)
R:link util:ls 0:link 0:msu oc 5584:tot oc 160000:util 0
Indicates: link 0  -  msu octet counter 5584  - total octets  160000:

MSU Logging

Start ss7boxd with show msu option.  With this option all MSU messages will be logged in /usr/local/ss7box/msu.log

--> cd /usr/loca/ss7box
--> ./ss7boxd --showmsu
      --> all MSU will be logged into /usr/local/ss7box/msu.log

More Info

ss7box Line Debugging  ss7box Features    ss7box Manual 

 

---

sangoma_isupd (ISUP) - ISUP Features   ISUP Manual   ISUP CDR Logger    ISUP CLI

Config FIles:

/etc/ss7box/sangoma_isup.conf

Starting ss7boost

SMG product is usually started by
--> /etc/init.d/smgss7_init_ctrl start

ss7boxd can be individually started using:
--> smg_ctrl stop   (stop ss7boost and smg daemon)
--> smg_ctrl start   (starts ss7boost and smg daemon)

Debugging

ss7boxd outputs all its events, errors and status in /var/log/messages

This indicates that the CICs have reset successfully
: W:sb_mpc.c:sg_crs_wait_rlc:circuit reset complet:span/chan/csupid follow:0:0:0
: W:sb_mpc.c:sg_crs_wait_rlc:circuit reset complet:span/chan/csupid follow:0:1:0
: W:sb_mpc.c:sg_crs_wait_rlc:circuit reset complet:span/chan/csupid follow:0:2:0
: W:sb_mpc.c:sg_crs_wait_rlc:circuit reset complet:span/chan/csupid follow:0:3:0
: W:sb_mpc.c:sg_crs_wait_rlc:circuit reset complet:span/chan/csupid follow:0:4:0
....

After this step the ISUP is open to send/receive calls.

ISUP Event Logging

Using ss7boost_cli one can enable and disable ss7boost (ISUP) verbosity>
--> ./ss7boost_cli --log-verbose on 1
All ISUP messages will be logged in /var/log/messages
 
To filter out only isup events in /var/log/messages run:
--> tail -f /var/log/messages | grep isup_event

   
More info :

ISUP Features   ISUP Manual   ISUP CDR Logger    ISUP CLI 

 

---

sangoma_mgd (SMG Daemon: Asterisk Mode Only)

SMG interfaces to AFT Voice Channels and sends media to Asterisk via woomera protocol.
SMG daemon also translates ss7 ISUP messages to woomera protocol and vice versa.


Config FIles:

/etc/sangoma_mgd.conf

Starting sangoma_mgd

SMG product is usually started by
--> /etc/init.d/smgss7_init_ctrl start

sangoma_mgd can be individually started using:
--> smg_ctrl stop   (stop ss7boost and smg daemon)
--> smg_ctrl start   (starts ss7boost and smg daemon)

Debugging

 sangoma_mgd outputs all its events, errors and status in /var/log/sangoma_mgd.log
 (if using syslog-ng all output will default to /var/log/messages)

 

---

Asterisk - Woomera Channel Driver

Asterisk uses woomera channel driver to communicated to sangoma_mgd.
Woomera protocol is TCP/UDP based.  TCP - control  UDP - media
For more info about woomera click here.

Woomera Config File

/etc/asterisk/woomera.conf

Starting Asterisk

safe_asterisk

Debugging:

CLI> set verbose 10
Enable verbosity all woomera call info will be displayed in CLI

CLI> woomera default version
Display woomera and sangoma_mgd version

CLI> woomera default debug 3
Enable woomera debugging all logs will be logged in /var/log/asterisk/messages
(Remember to set logging back to 1 after debugging is done)

CLI> woomera default smgdebug 3
Enable sangoma_mgd debugging all logs will be logged in /var/log/sangoma.log
(Remember to set logging back to 1 after debugging is done)