You are on page 1of 9

Sangoma Servers Sangoma Media Gateway (SMG) or Sangoma server is a newly redesigned signaling and media gateway that

provides VoIP/SIP to TDM connectivity OR Sangoma servers are used to convert SIP/VoIP calls to TDM based SS7/ISUP calls.

Sangoma SS7 box Services SS7 box along with the Sangoma servers provides 5 different services. 1. 2. 3. 4. 5. SS7boxd SS7boost Sangoma mgd Asterisk CDR Logger

Before explaining each of the service, lets check few commands to check the services of ss7box Ldivoip# cd /ss7box ss7box# ./xps - This command will take you in the directory of ss7box. - This command will tell you how many services of Sangoma are running

Here, you will see all the 5 services running along with their specific numbers. Now we will move towards the explanation of every service. Terms Related to the Services 1. Wanpipe : A wanpipe states an E1 line connected between two ends. These wanpipes can be further shown in channels and spans. 2. Channel: A channel is equal to one time slot of an E1. So that one wanpipe or one E1 has 32 channels/time slots in it. 3. Span: Span is the word used to describe an E1 when you have multiple E1s are placed. If 8 E1s are placed between two ends, we can check the summary of every channel by these spans. Span 0 -> 32 channels Span1 -> 32 channels 4. Sangoma Hardware: In Sangoma, there are 4 physical slots available in which 8 wanpipes can be connected. Therefore, every slot has 2 wanpipes connected to it. Wanpipe 1 and 5 are fixed on slot 0. Wanpipe 2 and 6 are fixed on slot 1. Wanpipe 3 and 7 are fixed on slot 2. Wanpipe 4 and 8 are fixed on slot 3.

1
2,6 connecting port1

3
4,8 connecting port 3

1,5 connecting port 0

3,7 connecting port 2

Wanpipes 1

1 E1 has 4 pairs and 8 wires in it. Now we will how they are used to send and receive the signal. For Wanpipes 1, 2, 3 and 4 1 2 1, 2 -- Receive For Wanpipes 5, 6, 7 and 8 3 3, 6 -- Receive Sangoma Servies 1. SS7boxd This service handles all the signaling between Sangoma server and Switch. It reads a file ss7box.conf in which all the wanpipe info is stored, however, cards are physically fixed on sangoma slots. ss7box# ./ss7boxd ss7box# ss7box.conf - This command will start the services of boxd - This command has the all the information to make interconenct with switch. 6 7 8

4,5 -- Transmit

7, 8 -- Transmit

In SS7box, we have the information of OPC, DPC of switch since it handles all the signalling between sangoma server and switch. Singaling Link Selection is created here. For Example, DPC 2154 (Switch), SLC time slot 15 for wanpipe 1, 2 and 3. After starting the boxd service, wanrouter is also started which starts all the wanpipes without having any signaling information in it. You can check the wanrouter status by using command : Root# /etc/wanpipe/wanrouter.rc WAN_DEVICES # wanrouter start # wanrouter stop - This command Starts all devices specified in - This command Stops all devices specified in

# wanrouter start wanpipe# # wanrouter stop wanpipe#

- This command Start a single device - This command Stops a single device

Now, all the information of a single wanpipe is also checked by using command: # cd /etc/wanpipe/ # vi wanpipe1.conf - This command will take you to the directory of wanpipe - This command will run wanpipe1 file.

All the information of E1 is stored in this file. For Example, for a single E1, 1 15 = Voice Channels 16 Signaling link 1732 = Voice channels

Clock Normal = When E1 is up.

Clock Master = For Testing purpose.

Whatever the slot and PCI bus information stored in wanrouter/hwprobe, We put the same configuration in wanpipe1.conf.

2. SS7boost This service handles all the trunkgroups definded between the sangoma server and swtich. It reads a file ss7boost.conf in which the trunkgroup information is stored. # vi ss7boost.conf - This command has the information of all the CICs of E1 lines.

NADI (Nature of Address Indicator) and different groups (g1, g2) are defined here depending upon their routes. We can also check the report of all the spans and its channels by using the command. ss7box# ./ss7boost_cli ckt-report chan all span all | more Now you can see all the 8 spans along with their channels, connected to the sangoma ports. You can also block the CICs of a particular span by using the command: ss7box# ./ss7boost_cli ckt-block chan all span 7 | more Similarly, you can reset a complete span by using the command: ss7box# ./ss7boost_cli ckt-reset chan all span 1 | mor

3. Sangoma_mgd This service handles all the hardware configuration of wanpipes. The command used to start the Sangoma_mgd and boost services is: #. /smg_Ctrl start - This command starts the Sangoma_mgd and boost services.

Starting and Stopping Services You can either start all the services at once or one by one. In order to start all the services, we use # monit start all # monit stop all Checking var/log Messages: We can check the entire server or service related messages by using the command: # tail f /var/log/messages - This command shows all the messages. - This command is used to start all the services - This command is used to stop all the services

If the services are stopped, out of services messages are received here. When all the services are started, we will receive the in services messages.

4. CDR_Logger : This service manages the CDRs (Call Detailed Records) of all the calls passing through sangoma servers. We can run the service of cdr_logger by using the command: # ./cdr_logger All the CDRs are made on the file named master.csv. This file is placed on the directory: # cd /var/log/asterisk/cdr_csv # ./master.csv - This command shows all the call logs made.

All the call logs are made in the specified form showing the following information: PNR, Calling Party number, Called Party number, Context (to be called from extensions.conf), IP address, Woomera group, Date, Time, Status of Call, Reason (Cause code), Codec. We can also select the particular calls being failed for a particular reason like Cancel by using command: # cat master.csv | more | grep 19| | wc l - This command will tell how many calls are failed for the reason of cancel.

Cause Code: Cause code is a specific code used to determine the cause of the failure of the code. You can check all these codes from 5. Asterisk This service is used for handling all the calls. The context of all the calls are defined on the file extensions.conf while the registration of a particular user, codecs to be used, their IPs and the parameters and context to transfer the call are defined on the file sip.conf. If a user has more than one IP, then in order to distinguish between each IP, some host indexes are defined against each user IP in the file peers.conf. Now, we will have a look at the different commands used in the asterisk: # cd /etc/asterisk/ - This command takes you to the console of asterisk.

# cd asterisk r x show channels - This command will give you the information about all the Active Channels (Attempts made for call), Active calls (Calls in progress), Status of call and the Call number. # cd asterisk r x sip show channels - This command will give you the information about the Call ID, Process of Call, State of Call, Codecs used for the call and all the Active calls. # cd asterisk r x sip show peers

For checking codecs in machine:

Asterisk r x sip show chaneels | (codec ) Asterisk r x sip show chaneels | wc l Asterisk r x sip show chaneels | wc

Checking block code list: [root@ASVP2 asterisk]# ls -l block* [root@ASVP2 asterisk]# ls -l block* -rw-r--r-- 1 root root 141169 Oct 26 2010 blocked_codes2.txt -rw-r--r-- 1 root root 147594 Apr 20 13:36 blocked_codes.txt [root@ASVP2 asterisk]# [root@ASVP2 asterisk]# [root@ASVP2 asterisk]# grep 1631 blocked_codes.txt If to check the master levels: [root@ECSS1 asterisk]# more blocked_codes.txt | grep ^67 [root@ECSS1 asterisk]#cat blocked_codes.txt | grep 442/^442

New customer Adding route in machine: route add net [ip] [netmask] [gw]

Testing aspan/E1: iServe ~ # cd /ss7box/ iServe ss7box # ./ss7boost_cli --ckt-report --chan all --span all | more ckt-report begin span: 0 chan cfg inuse inrst rhb lhbs lhbm lhbc lhbr rmb lmb 0 Y n 1 Y n 2 Y n 3 Y n 4 Y n 5 Y n 6 Y n n n n n n n n n n n n n Y Y n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n

7 Y n 8 Y n 9 Y n 10 Y n 11 Y n 12 Y n 13 Y n 14 Y n 15 n 16 Y n 17 Y n 18 Y n 19 Y n 20 Y n 21 Y n 22 Y n 23 Y n 24 Y n 25 Y n 26 Y n 27 Y n 28 Y n 29 Y n 30 Y n

n n n n n n n n n n n n n n n n n n n n n n n

n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n - - - - - - n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n

block all span using command except one for testing: ss7box# ./ss7boost_cli ckt-block chan all span all | more

in case block all: unblock only the testing E1 or span say span2 using command: ss7box# ./ss7boost_cli ckt-block chan all span 2 | more

Now select kicks to test : (particular channel) ss7box# ./ss7boost_cli ckt-block chan all span 2 | more

now select particular kick using command: ss7box# ./ss7boost_cli ckt-block chan no span 2 | more say 2 ss7box# ./ss7boost_cli ckt-unblock chan 2 span 7 | more

now make test call and observe the output.

Channels: ACTIVE_CH = 1-15.17-31

To grep a call: Ps aux | grep Call Show process of sip calls for client

Lahore server commands: Cd /etc/asterisk Vi ss7.conf (shows wanpipe connectivity between ldi and ptcl)

Creating a routing group: [OutboundCalls] extension_bu.conf/extensions_fxs.conf exten => _X.,n,GotoIf($["${BParty:0:3}" = "099"]?LucentLocalRoute2) This will add prefix before giving call to ldi/lucent exten => _X.,n(LucentLocalRoute2),Dial(WOOMERA/g1/021${BParty:1}f|60|o,30) exten => _X.,n,Goto(HNGUP)

021${BParty:1} This will append 0 from prefix 099 above and gives call to lucent.as 02199 Note

You might also like