Introduction: The doc intends to covers all possible points inorder to achieve a fair system

understanding of ussd gateway .

Current PCN architecture:

There are two modules in Messaging platform :

USSD gateway and ESME

There is a one to many relationships between gateway and esme but not vice versa

mysql
ESME_PC ESME_BO ESME_NO
N D TIFICATIO
N
ESME_PC ESME_BO ESME_NO
N D TIFICATIO
N

TCP client
mysql

TCP client gatewa

Tcp server y

gatewa
Tcp server y Server2

Server1 Stack

Stack
 Gateway: You can find the running gateway from below command
ps –ef | grep –i USSD_GATEWAY

Or do - cd /root/Aricent/AricentStack/ and run ./check.sh

check.sh is a master script which shows all the concerned process of a messaging platform.

Above is showing one gateway and three ESME . Rest are stack processes.

All processes must be up and running.

Stack process –
./em
./ss7p –t 1 –i 1
./ss7p –t1 –i 2
./app_map –I 1
./app_map –I 2
./app_map_em

Troubleshooting individual process:

The currently running used files by above processes can be seen by:

/home/PCN_SETUP/checkPCN.sh

Gateway
Gateway generates CDR for every successful calls at location /log/GATEWAY inside file name
cdr.txt_27-11-01\:24\:00_06 .
To get the latest CDR ,check the terminal value of file and search the number accordingly.
 CDR REASON
SEND_USSN_RESP_SUCCESS
MAP_U_ABORT_SUCCESS
MAP_USSR_CNF_USER_ERROR
'ESME not
Avilable','0','SEND_USSN_RESP_SUCCESS' PCN landed at gateway
USSD_LOCAL_SESSION_TIMEOUT
MAP_USSN_CNF_SUCCESS
Treatment
This line shows incoming
PCN received and
response send back to
network (Towards IN).
This shows USSD PUSH '1','MAP_U_ABORT_SUCCESS'
sent to subscriber but get
cancellation from either 1 shows the number of
subscriber or network interaction happened between
system and user. Possible
values could be 2,3,4 etc
This shows push got an Mostly we get these cases
error from network when 2nd push attempt while
possibly from HLR first was in progress
For cases where duplicate This is discarded by gateway
and response send back to core
network .
For cases where USSD
interactive served to user
but user didn’t interact
within time.
Message successfully
delivered to the user
screen.

Stats file : Shows how many request incoming and outgoing from gateway per minute.
stats.txt_27-11-00\:00\:36_00

19:27:13 PSSR Req:0 PSSR Resp:0 USSR Req:3105 USSR Resp:152 USSN Req Sent:3
USSN Resp Sent:3781 USSN Req Recv:3781 USSN Resp Recv:3 SRI Req:0 SRI Resp:0 PABORT
Recv:0 UABORT Recv:2080 UABORT Sent:1155 NOTICE_IND Recv:0

19:28:13 PSSR Req:0 PSSR Resp:0 USSR Req:3040 USSR Resp:142 USSN Req Sent:6
USSN Resp Sent:3662 USSN Req Recv:3662 USSN Resp Recv:6 SRI Req:0 SRI Resp:0 PABORT
Recv:0 UABORT Recv:2013 UABORT Sent:1068 NOTICE_IND Recv:0

If the stats file is not growing or growing with NULL entries for USSN Req(USSN Req Recv:3662)
and RESP then PCN traffic is not coming till gateway
 If USSR Req and USSR Resp are NULL (USSN Req are non null )means no push is being sent to
customer . Either ESME down or rule engine is not responding

PSSR Req:0 indicates zero(0)BOD request hitting per minute.

14:26:51 PSSR Req:0 PSSR Resp:0 USSR Req:0 USSR Resp:0 USSN Req Sent:2501
USSN Resp Sent:3075 USSN Req Recv:3075 USSN Resp Recv:2455 SRI Req:0 SRI Resp:0 PABORT
Recv:0 UABORT Recv:180 UABORT Sent:19 NOTICE_IND Recv:0

In above line incoming PCN request is 3075 ,Interactive PUSH against PCN is zero (USSR Req:0
).

For the current running stats file ,use the above mentioned script /home/PCN_SETUP/checkPCN.sh

PCN ESME:
This ESME is running with the name ESME_PCN from directory /home/PCN_SETUP/ESME_PCN .

The module receives incoming PCN request from gateway and handover to Engine . Gateway interface
is over smpp and Engine is over XML . To see the interaction between ESME and Engine , go to XML
logs exchanged inside /log/ESME_PCN/ .

For the current running XML LOG file ,use the above mentioned script /home/PCN_SETUP/checkPCN.sh

cd /log/ESME_PCN/

ls -ltr | tail -2

tail –f XML_Log_28-11-00\:00\:00_04 | grep “9810905244” for online testing or grep the number in
XML log to see all the interactions.

Messa Meanin Sample values

ge g
Type
>IN< Incomin 0266<MSG><MODE>USSD</MODE><INITIATOR>NET</INITIATOR><MSISDN>1916520792</
g PCN MSISDN><MSGCODING>UTF-
submissi 8</MSGCODING><MSGLEN>59</MSGLEN><CIRCLE>Bangladesh</CIRCLE><MESSAGE>Call:
on to 00:00:19. Cost: Tk.0.19 (inc.tax). Balance:
Engine Tk.14.96.</MESSAGE><TYPE>IN</TYPE><STATUS>0</STATUS></MSG>
>MID< Digit 0209<MSG><MODE>USSD</MODE><INITIATOR>NET</INITIATOR><MSISDN>1919617121</
received MSISDN><MSGCODING>UTF-
from 8</MSGCODING><MSGLEN>2</MSGLEN><CIRCLE>Bangladesh</CIRCLE><MESSAGE>qq</ME
user SSAGE><TYPE>MID</TYPE><STATUS>0</STATUS></MSG>
>TR< Session 0207<MSG><MODE>USSD</MODE><INITIATOR>NET</INITIATOR><MSISDN>1956851418</
termina MSISDN><MSGCODING>UTF-
tion 8</MSGCODING><MSGLEN>0</MSGLEN><CIRCLE>Bangladesh</CIRCLE><MESSAGE></MESS
indicatio AGE><TYPE>TR</TYPE><STATUS>10</STATUS></MSG>
n to the
 Rule
Engine

How to take network traces

Currently there are three signaling servers running

Server IP STACK USSD gateway Remarks

10.21.147.5 Yes Yes
10.21.147.6 Yes NO Gateway will run on this
as the traffic increases
10.21.147.7 NO NO Gateway will run on this
as the traffic increases

Traces are always taken simultaneously on server running signaling stack . (i.e .5 and .6)

From root privilege, run the command not more than 5 minutes on .5 and .6

tshark -i any sctp -B 20 -w /tmp/trace5.pcap for 5

tshark -i any sctp -B 20 -w /tmp/trace6.pcap for 6

chmod 755 /tmp/trace5.pcap

chmod 755 /tmp/trace6.pcap

Scripts
All the scripts are scheduled explicitly from cron .

Cron Scripts
Capturing Top output
/root/Scripts/monitoring_top.sh Capturing Top output
/root/Scripts/monitoring_iostat.sh Capturing IO stat
/root/Scripts/Links_monitoring.sh Link monitoring script showing link down status.
Every running instance is being logged individually
at /cdr/link_cdr/

NON Cron scripts

Stack restart process on 5and 6 From /root/Aricent/AricentStack
./ stopnexGen.sh
./ startnexgen.sh