0% found this document useful (0 votes)
23 views34 pages

SMSR WorkBook

The document outlines the steps to configure and start a SIGTRAN stack, including running specific scripts on both SMSR and remote sides. It also details various error codes and their meanings related to user and provider errors, as well as internal errors within the stack and signaling server. Additionally, it provides information on database configuration and commands for managing connections and modules.

Uploaded by

Sageev C Gopal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
23 views34 pages

SMSR WorkBook

The document outlines the steps to configure and start a SIGTRAN stack, including running specific scripts on both SMSR and remote sides. It also details various error codes and their meanings related to user and provider errors, as well as internal errors within the stack and signaling server. Additionally, it provides information on database configuration and commands for managing connections and modules.

Uploaded by

Sageev C Gopal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 34

Steps Execution

1 Run stack at both the sides using ./startall.sh Start from root for sigtran
2 At SMSR side ->run ./config/singlenode.sh Start from root for sigtran
3 At remote ->run ./config/singlenode.sh Start from root for sigtran
4 At remote side -> ./m3ua_enable.sh Start from root for sigtran
5 At SMSR side->./m3ua_enable.sh Start from root for sigtran
6 Start SMSR using -> StartSMSR
7 At SMSR Side->/lwsg/./startlwsg

At remote
Side-/prd/stack_at_remote_side/lwsg/send_simulator
8 ./startlwsg Network stub

vi /prd/smsrouter/www/web_config/common/config.php
172.19.1.77
172.16.7.25 root/pvg_avan
172.16.7.26 root/pvgblr321
1 grep -R "172.16.7.36" *

$DD_CFG
Finds the files where 172.16.7.36 is present in the directory from where the
command was run

to goto smsrouter config path /prd/smsrouter/etc/config/


in networkstub.ini NETWORKDESTCODE = 9710 and MSC_SERIES=9710
should be same as the one set in node41.cfg
in GUI, change logtype to shm
In Service Parameters: Presentation SC value should be same sc address in node41.cfg 919845000001
http://172.16.7.36/
node41.cfg
Q To enable Error Details options in GUI
A Update $enable_rule_error_details = 1; in input.php file present in the path /prd/smsrouter/www/web_config/com
er/www/web_config/common
Result ( R ) Error (E) Error (E) Reason
Success
0x01 0 Decimal Success
User Error
0x02 0x01 1 ERROR_UNKNOWN_SUBSCRIBER
0x02 2 ERROR_UNKNOWN_BASE_STATION
0x03 3 ERROR_UNKNOWN_MSC
0x05 4 ERROR_UNIDENTIFIED_SUBSCRIBER
0x06 5 ERROR_ABSENT_SUBSCRIBER_SM
0x07 6 ERROR_UNKNOWN_EQUIPMENT
0x08 7 ERROR_ROAMING_NOT_ALLOWED
0x09 8 ERROR_ILLEGAL_SUBSCRIBER
0x0a 9 ERROR_BEARER_SERVICE_NOT_PROVISIONED
0x0b 10 ERROR_TELESERVICE_NOT_PROVISIONED
0x0c 11 ERROR_EQUIPMENT
0x0d 12 ERROR_CALL_BARRED
0x0e 13 ERROR_FORWARDING_VIOLATION
0x0f 14 ERROR_CUG_REJECT
0x10 15 ERROR_ILLEGAL_SS_OPERATION
0x11 16 ERROR_SS_ERROR_STATUS
0x12 17 ERROR_SS_NOT_AVAILABLE
0x13 18 ERROR_SS_SUBSCRIPTION_VIOLATION
0x14 19 ERROR_SS_INCOMPATIBILITY
0x15 20 ERROR_SS_FACILITY_NOT_SUPPORTED
0x19 21 ERROR_NO_HANDOVER_NUMBER_AVAILABLE
0x1a 22 ERROR_SUBSEQUENT_HANDOVER_FAILURE
0x1b 23 ERROR_ABSENT_SUBSCRIBER
0x1c 24 ERROR_INCOMPATIBLE_TERMINAL
0x1d 25 ERROR_SHORT_TERM_DENIAL
0x1e 26 ERROR_LONG_TERM_DENIAL
0x1f 27 ERROR_SUBSCRIBER_BUSY_FOR_MT_SMS
0x20 28 ERROR_SM_DELIVERY_FAILURE
0x21 29 ERROR_MESSAGE_WAITING_LIST_FULL
0x22 30 ERROR_SYSTEM_FAILURE
0x23 31 ERROR_DATA_MISSING
0x24 32 ERROR_UNEXPECTED_DATA_VALUE
0x25 33 ERROR_PW_REGISTRATION_FAILURE
0x26 34 ERROR_NEGATIVE_PW_CHECK
0x27 35 ERROR_NO_ROAMING_NUMBER_AVAILABLE
0x28 36 ERROR_TRACING_BUFFER_FULL
0x2c 37 ERROR_NUMBER_OF_PW_ATTEMPTS_VIOLATION
0x2d 38 ERROR_BUSY_SUBSCRIBER
0x2e 39 ERROR_NO_SUBSCRIBER_REPLY
0x2f 40 ERROR_FORWARDING_FAILED
0x30 41 ERROR_NOT_ALLOWED
0x31 42 ERROR_ATI_NOT_ALLOWED
0x32 43 ERROR_NO_GROUP_CALL_NUMBER_AVAILABLE
0x33 44 ERROR_RESOURCE_LIMITATION
0x34 45 ERROR_UNAUTHORIZED_REQUESTING_NETWORK
0x35 46 ERROR_UNAUTHORIZED_LCS_CLIENT
0x36 47 ERROR_POSITION_METHOD_FAILURE
0x3a 48 ERROR_UNKNOWN_OR_UNREACHABLE_LCS_CLIENT
0x47 49 ERROR_UNKNOWN_ALPHABET
0x48 50 ERROR_USSD_BUSY
0x75 51 ERROR_GATEWAY
Provider Error
Result ( R ) Error (E) Reason
0x03 0x00 PROV_DUPLICATE_INVOKE_ID
0x01 PROV_SERVICE_NOT_SUPPORTED
0x02 PROV_MISTYPED_PARAMETER
0x03 PROV_RESOURCE_LIMITATION

0x04 PROV_INITIATING_RELEASE

0x05 PROV_UNEXPECTED_RESPONSE
0x06 PROV_SERVICE_COMPLETION_FAILURE
0x07 PROV_NO_RESPONSE_FROM_PEER
0x08 PROV_INVALID_RESPONSE

Internal Errors (Stack and Sigserver)


Result ( R ) Error (E) Reason
0x04 1 MAP_USER_SPECIFIC_REASON
4 2 MAP_USER_RESOURCE_LIMITATION
4 3 MAP_RESOURCE_UNAVAILABLE

4 4 MAP_APPLICATION_PROCEDURE_CANCELLATION

4 7 SIGNALLING SERVER TIME OUT

4 10 MAP_PROVIDER_MALFUNCTION

4 11 MAP_SUPPORTING_DIALOG_TRAN_RELEASED
4 12 MAP_DLG_RESOURCE_LIMITATION
4 13 MAP_MAINTENANCE_ACTIVITY
4 14 MAP_VERSION_INCOMPATIBILITY

4 15 MAP_ABNORMAL_MAP_DIALOGUE
4 20 MAP_ABNORMAL_EVENT_DETECTED_BY_PEER
4 21 MAP_RESPONSE_REJECTED_BY_PEER
4 22 MAP_ABNORMAL_EVENT_RECEIVED_FROM_PEER

4 23 MAP_CANNOT_DELIVER_MESSAGE
4 30 MAP_APPLICATION_CONTEXT_NOT_SUPPORTED

4 31 MAP_DLG_INVALID_DESTINATION_REFERENCE

4 32 MAP_INVLAID_ORIGINATION_REFERENCE

4 33 MAP_NO_REASON
4 34 MAP_REMOTE_NODE_NOT_REACHABLE

4 35 MAP_POTENTIAL_VERSION_INCOMPATIBILITY
4 36 MAP_SECURED_TRANSPORT_NOT_POSSIBLE
4 37 MAP_USR_TRANSPORT_PROTECTION_NOT_ADEQUATE

$all_error_code = 0;
$err_absent_subscriber = 27;
$err_call_barred = 13;
$err_ss_incompatible = 20;
$err_not_supported = 21;
$err_busy_for_mt = 31;
$err_sm_del_fail = 32;
$err_msg_list_full = 33;
$err_sys_failure = 34;
$err_data_missing = 35;
$err_unexpected_data = 36;
$err_absent_subscriber_for_sri = 6;
$err_busy_subscriber = 45;
$err_no_subscriber_reply = 46;
$err_unidentified_subscriber = 5;

MAP Failure Errors


Unknown subsriber = 1
System failure = 34
Teleserive not supported = 11
Call Bar = 13
Absent subscriber = 27
Absent subscriber for SM = 6
Facility not support = 21
Unexpected Data = 36
Data missing = 35
User Error
ovider Error

On Same Invoke Id two message is sent


Those services which is not supported
Resource is limited I.e link is not available as per requirement.
The peer has already initiated release of the dialogue and the service has to be
released
If we send Lu message with ISD but receive response Lu without ISD ,this error
comes.
Suppose if we send sri request ,at peer side after open confirm abort comes without
giving
sri response,this error comes.
After sending request no response comes from peer this error comes.
Received response from peer but that response donot match Corresponding to
request.
rs (Stack and Sigserver)

The requested user resource is unavailable due to congestion


The requested user resource is unavailable for reasons other than congestion

Handover cancellation,Network path release,Call release,Associated procedure


failure,Remote operations failure
If response donot come with in spacified time signaling server timeout comes.

Unrecognised message type,Badly formatted transaction portion,Badly formatted


transaction portion
Unrecognised transaction ID received
Congestion towards MAP peer service-user
Maintenance at MAP peer service-user
A Provider Abort indicating "No common dialogue portion" is received in the
dialogue initiated state.
MAP dialogue is not in accordance with specified application context.
Network Failure, Network Congestion
When response donot come from peer
if the invoke ID is already in use by an active service, request the transfer of a reject
component using the TC-UREJECT
request primitive with the appropriate problem code (duplicated invokeID) and
issue a MAP-NOTICE
indication primitive with a diagnostic parameter set to "abnormal event received
from the peer"
When message donot deliver to peer.
This parameter identifies the type of application context being established.This
parameter shall indicate the highest version supported.
This parameter is a reference which refines the identification of the called process.If
called address not identified this error comes.
This parameter is a reference which refines the identification of the calling process.If
calling address not identified then this error comes.

if message is send but this message does not go to remote node,due to not correct
gt,this error comes.
E:07 R:04 = No response from
Stack
smsr configuration
Remarks
0 TCP 2310 mor
1 TCP 14420 sri
2 TCP 14422 mor-sri
3 TCP 14423 smpp_sri
4 TCP 14421 mts

For Sigtran enable following Layers

SP
ST
MA
HI
SB
IT

For SS7 enable following Layers

SN
SP
ST
MA
SD
Status value in CDR.

ST:0 MESSAGE ACCEPTED


ST:1 Success
ST:2 Timed out considered as temp error
ST:3 Expired
ST:4 Permanent Error
ST:6 Temproary Error
ST:7 Used Internally Ignore
ST:8 Dropped, Permanent Error
ST:11 Handed over to next module
ST:13 Relay failed
ST:12 SUCCESFULLY RELAYED
ST:10 Fwded to DBM for Retry
ST:17 -ve response from Dbill
ST:18 Dbill Timeout
ST:19 Dbill internal error
ST:20 Succ Redirect to other SMSC "
ST: 21 Peer node relay
ST:26 Declined
ST: 30 DBM accept

MD values:
MD: 0 MOR
MD:1 SRI
MD:2 MTS
MD:3 RR
MD:4
MD:5 SMPP_SERVER (SMPP protocol)
MD:6 SMPP_SERVER (UCP protocol)
MD:7 SMPP_CLIENT
MD:8 SMPP_SERVER (CIMD protocol)
MD:9 DBM
MD:10 CRM

LWSG PDU decode

perl /prd/lwsg/etc/scripts/lwsg_decode_cdr.pl "H=PL-150:PV-1:MV-2:PT-SRIP:SN-8:NT-6:AI-0:PF-8:ER-0:SRC-0:RT-1


I-0:PF-8:ER-0:SRC-0:RT-1:FC-32768|B=10:16:96404123456789012|2:1:1|1:13:91919910111110|11:4:919B4AB7|59:12:TT-0 NP-1 NAI-4 S
59:12:TT-0 NP-1 NAI-4 SSN-0 AI-0 ES-2 PC-0 LEN-12 ADDR-919810047015|49:4:45|"
Q
A

Q
A

Q
A
mysql too many connections
mysql -uroot
show variables;
set GLOBAL max_connections=1000;

hdc commands
/usr/net/Adax/qcx/qcx_conf -s
Send Blue to port 0 using following command.
/usr/net/Adax/qcx/qcx_conf -B 0
/usr/net/Adax/qcx/qcx_conf -s
If 0 and 1 are connected then BLU will be seen on port 1.

To remove Blue
/usr/net/Adax/qcx/qcx_conf -N 0
/usr/net/Adax/qcx/qcx_conf -rsv
To run in smsr user : chmod 777 /dev/hdcx
crm - need to open GUI and press done to work
/usr/net/Adax/hdc/hdctest -d hdcx -p 0 -b 0x1 -c
/usr/net/Adax/hdc/hdctest -d hdcx -p 1 -b 0x400 -c
/usr/net/Adax/hdc/hdctest -d hdcx -p 1 -b 0x7fffffff -c

if HBA is not able to initialise and other modules are also not able to come up
check whether respective module directories are available under the path /prd/smsrouter/logs/HBA

[smsr@localhost HBA]$ pwd


/prd/smsrouter/logs/HBA
[smsr@localhost HBA]$ ll
total 72
drwxrwxr-x 2 smsr smsr 4096 Mar 14 12:19 crm
drwxrwxr-x 2 smsr smsr 4096 Mar 14 12:19 dbm
drwxrwxr-x 2 smsr smsr 4096 Mar 14 12:16 logserver
drwxrwxr-x 2 smsr smsr 4096 Mar 14 12:18 mor
drwxrwxr-x 2 smsr smsr 4096 Mar 14 12:18 mts
drwxrwxr-x 2 smsr smsr 4096 Mar 14 12:19 rr
drwxrwxr-x 2 smsr smsr 4096 Mar 14 12:19 smpp_client
drwxrwxr-x 2 smsr smsr 4096 Mar 14 12:19 smpp_server
drwxrwxr-x 2 smsr smsr 4096 Mar 14 12:18 sri

DB configuration
/prd/smsrouter/www/web_config/common/config.php
$db_name = "rsp_smsr";
$db_user = "rsp_smsr";
$db_pass = "rsp_smsr";
$db_host = "172.19.1.189";

### Rule Reload updation ####


$rule_server_ip = array ("172.19.1.189");
$rule_server_port = array (9990);

mts GUI - Alert Send IP Pairs


Alert Send IP Pairs- it should be 172.19.1.189:28884/172.19.1.189:28885

Sigserver for not to add default SC address


MULTIPLE_GT="1" # 1 for not to add default SC to carry whatever being sent from Network, 0 for adding default SC from
sigserver configuration

Clearing shared memory

~/.semrm.sh
~/.shmrm.sh
ipcrm

LWSG PDU decode

perl /prd/lwsg/etc/scripts/lwsg_decode_cdr.pl "H=PL-150:PV-1:MV-2:PT-SRIP:SN-8:NT-6:AI-0:PF-8:ER-0:SRC-0:RT-1:FC-


32768|B=10:16:96404123456789012|2:1:1|1:13:91919910111110|11:4:919B4AB7|59:12:TT-0 NP-1 NAI-4 SSN-0 AI-0 ES-
2 PC-0 LEN-12 ADDR-919810047015|49:4:45|"

route add net - default 172.16.1.145


route add net default 172.16.1.145
route add net - default 172.19.1.1
(if you don’t remove this message will not flow)
reset

LSL
For high speed link test
./udp_sim_press_key -l 0.0.0.0 -p 28881 -s 127.0.0.1 -q 25551 -f test1.txt -c 1
./udp_simulator -l 0.0.0.0 -p 28881 -s 127.0.0.1 -q 25551 -f test1.txt -c 1
update dbill send port as 5555 in all module GUI
DBill Send IP Pairs 172.16.7.36:5555

./stub_in_in_1561 172.16.7.36 10068 to start stub


Remote Stack Application side Stack

cld=SC addr
MO req calling= GT
MO ind
Mobile R
E
M cld= GT
O calling= SC addr
T MO confirm
E
S cld= Dst MSDN
T calling= SC addr
C SRI ind
SRI ind K
cld= SC addr
HLR SRI resp calling= Dst MSDN SRI cfm

DVMSC, IMSI

MT ind
MT ind

MSC MT resp MT resp MT cfm

cld= VMSC
cld= SC addr calling= SC addr
calling= VMSC

153
network stub
913333333333
Application side Stack

MO ind
A MO ind
P
GT P
L MO resp MOR
g= SC addr
I
C
A
Dst MSDN T
g= SC addr I SRI req
O
N

S SRI+
I SRI cfm
D
E

S
T MT req
A
C
K MT
MT cfm MT cfm
MSC
= SC addr

136/86
911111111111
101888

101889

101890

101891

101892

101893

101894

101895

101896

101897

101898

101899
101899

101900
1 101888
TUNG863 Smoke_checking the presence of all the folders in the installable. All the folders should be created
with the relevan... Checking the presence of all the folders in the installable.

and previous reported bugs ReadMe, Release Notes for version, Build No and pr...
Check for presence of ReadMe, Release Notes for version, Build No and previous <BR/>reported bugs
2 TUNG864 Smoke_Check for presence of ReadMe, Release Notes for version, Build No
3 101889
TUNG865 Smoke_Installation of all the components namely SMSRouter, Database and

Database tables creations, Stack etc via Installation script All the components namely SMSRouter, Database
and ... Installation of all the components namely SMSRouter, Database and Database <BR/
>tables creations, Stack etc via Installation script
4 101890
TUNG866 Smoke_Configuration and start/Stop/Restart of all the Modules namely SRI,MOR,SMPP

server, SMPP client, DBM,CRM etc Start,Stop and Restart SMSR script should Start,St...
Configuration and start/Stop/Restart of all the Modules namely SRI,MOR,SMPP <BR/
>server, SMPP client, DBM,CRM etc
101891
5 TUNG867 Smoke_Configure and start Application stack(CCPU/NextGen/Sigtran) All the stack application
binaries should come up ... Configure and start Application stack(CCPU/NextGen/Sigtran)
6 101892
TUNG868 Smoke_Configure and Start Remote stack All the remote side stack binaries should come up ...
Configure and Start Remote stack
7 101893
TUNG869 Smoke_Configure and start Sigserver Sigserver binaries should come up while running th...
Configure and start Sigserver
8 101894
TUNG870 Smoke_Configure and start iBUS ibus binaries should come up while running the HBM...
Configure and start iBUS
9 101895
TUNG871 Smoke_Configure and start OAM Logserver and check logs are generated for

application, sigserver, iBUS 1 Should be able to configure the logserver.cfg 2 ...


Configure and start OAM Logserver and check logs are generated for application, <BR/>sigserver, iBUS
10101896
TUNG872 Smoke_Test the MO-MT message flow with the stack and check whether message

reaches Loadocr with No rules configured There should be a normal call flow from mor to sir... Test the MO–
MT message flow with the stack and check whether message reaches <BR/>Loadocr with No rules configured
11101897
TUNG873 Smoke_Test for AO-MT message flow with the stack and check whether application
is binded with a configured short code and message is sent successfully
to LoadOCR with No rules configured There should be a normal call flow from smpp_serve... Test for AO–
MT message flow with the stack and check whether application <BR/
>is binded with a configured short code and message is sent successfully <BR/
>to LoadOCR with No rules configured
12101898
TUNG874 Smoke_Test for MO-AT message flow with the stack and check message is

sent successfully to the application binded with No rules configured There Should be a normal call flow from mor
to smp... Test for MO–AT message flow with the stack and check message is sent successfully <BR/
>to the application binded with No rules configured
13101899
TUNG875 Smoke_Test for AO-AT message flow with the stack and check message is successfully
101899

sent from one application to another application with No rules configured Should be able to send message from
one applicatio... Test for AO–AT message flow with the stack and check message is successfully <BR/
>sent from one application to another application with No rules configured
14101900
TUNG876 Smoke_Test Store and forward feature for AO-MT message flow using DBM

module for a configured retry policy with the stack Message should be stored in the DBM module for 1 m...
Test Store and forward feature for AO–MT message flow using DBM module <BR/
>for a configured retry policy with the stack
TUNG974 Smoke_Configure and Start LWSG server Should be able to configure and start lwsg server
To check the configuration and working of lwsg server

You might also like