The SMS receiver module
("SgaMSMS")

• Connection to the signaling network using SS7 over PCM or Ethernet
• Handling up to 50.000 subscribers
• Possibility of sorting short messages into different directories (max. 10)
• Monitoring of SMS list length
• Optional incoming short message filtering
• Possibility to receive remote LocUpd requests
• Automatic Warm Reserve feature (switching two between SGASS7MSMS modules if one of them is down)

• Connects to GyX_SS7 or GyX_SCTP interface modules according to the needed connection type
• Handles connections with the HLR and the SMSC using MAP (Phase 1 or Phase 2) protocol over SS7
• Executes periodic Location Update procedures with the HLR(s)
• Receives and acknowledges SMS delivery on SS7/MAP protocol
• Creating CDR files hourly
• Logs HLR and SMSC responses
• Provides simple statistical data and logging on the operation

The main menu

Menu	Menuitem	Shortcut(s)	Meaning
[Log]
	Find line containing...	(Ctrl-F)	Finds text in log window
	Find next matching line	(F3)	Finds next occurrence of text in log window
	Details		Detail level of logging (Off, Normal, Detailed, or Debug)
[Subscribers]
	Auto-send UpdLoc's	(Ctrl-A, or )	Allows automatic sending of the Update Location MSUs for the active subscribers
	Send PurgeMS for all active	(Ctrl-P)	Sends MAP/PurgeMS MSUs to the HLR with the corresponding identifier for the all subscribers
	Import list from file		Refreshes the list of the subscribers from the Subscribers.lst file
	Export list to file		(Not available in this version)
	Zero SM counter of *all* subscribers		Resets all short message counters to zero
[Options]
	Auto scroll	(ScrollLock, or )	Allows automatic scrolling of the log screen
	Show log	(Ctrl-Tab)	Shows the log screen
	Show subscriber list	(Ctrl-Tab)	Shows the subscriber list screen
	Save settings		Saves actual settings into the configuration (SgaMSMS.ini) file

The columns of the subscriber list screen

• Act: State of the subscriber ('+' means active (UpdLoc is performed periodically), '-' means inactive subscriber)
• IMSI: IMSI of the subscriber
• MSISDN: MSISDN belonging to the IMSI
• SM count: Number of received SMSs. In round brackets the number of unsuccessfully received SMSs is indicated (due to some limitation - i.e. SMS path limit, A number or SMSC rule).
• Last SM: Date and time of the last received SMS
• Active TID: TID of the pending forwardSM operation.

The colors of the subscriber list screen

• gray: not active (so no periodic LocUpd is performed)
• purple: UpdLoc is in progress, TID in hexadecimal
• red: there has been no successful UpdLoc; or there has been a CancelLoc or a PurgeMS
• yellow: last successful UpdLoc was earlier, than INI/[SS7]/dwLocUpdValiditySec
• black: OK

The popup menu of the subscriber list screen

The bottom status-line

• UpdLoc Tx/Ack: The number of transmitted and the number of acknowledged MAP/UpdLoc MSU's
• FwdSM Tx/Ack: The number of received and the number of acknowledged MAP/ForwardSM MSU's
• GyX: Status of the connection to the signaling interface module (its color is gray in normal works, red refers to error)
• bps: Current transfer speed
• Rx OK/Fail: All received right and failed messages
• Tx OK/Fail: All transmitted right and failed messages
• E: Error counters
  • msu: Number of badly formatted or addressed (e.g. wrong point code) messages
  • tcap: Number of messages with incorrect TCAP/TID
• Uptime: time elapsed since module has been started up

The subscriber list

• The SMS recipient can be described here by its IMSI and MSISDN numbers
• The list can contain both active and inactive entries
• Sorting messages to different directories can be described here
• Input message filtering can be described here
• Cyclic digits to be concatenated to BNumber also can be described here
• Every line ends with ;

+ 216012780080055F 36208770055123456    SMSCCfg1 ANumCfg1 0 ;

The SMSC configuration files

• Specifies filters based on SMSC number filtering
• The messages can be accepted, rejected or deleted
• On delete the received message deleted immediately
• Every line ends with ;
• The result of the examination indicated in the ch8CauseForTermination in the CDR files

	36559300098          REJECT ;
  	3655930*             ACCEPT ;

The A number configuration files

• Specifies filters based on A number filtering
• The messages can be accepted, rejected or deleted
• On delete the received message deleted immediately
• On accepting, the destination directory for sorting the messages into different directories also can be described here
• Every line ends with ;
• The result of the examination indicated in the ch8CauseForTermination in the CDR files

	3655?3?0?98          REJECT    ;
	365593034*           ACCEPT 99 ;
	36559300097          DELETE    ;

Automatic Location Update feature

• Sends Location Update to the HLR periodically
• It prevents the messages waiting in the SMSC when the SS7 path brakes down
• It prevents from registering the subscriber in an another VLR, as automatically re-sends UpdLoc MSU to the HLR in case a CancelLocation MSU received
• Periodic UpdateLocation is sent for the last updated active, if its validity has timed out

• It is possible to execute location update from a remote client if INI/[Advanced]/bAcceptRemoteLocUpdRequests enabled
• Only the IMSIs defined in the subscribers.lst file can be used
• Only authenticated users can use remote location update

• Creates files hourly contain information for billing
• Name of a CDR file could contains a system ID (INI/[CDR File]/bySystemID)
• File ID is automatically updated at every file closing

• The number of stored short messages can be limited by [Advanced]/dwSMSPathNNLimit parameter in SgaMSMS.ini file
• On case the limit exceeded, the program can reply "sm_DeliveryFailure"/"MemoryCapacityExceeded"
• An alarm (trap) is generated when "Memory Capacity Exceeded" occurs for a particular SMS path (only if bAlternateTrapUID is set to True; note: no CEA is generated)

• Required entries in the INI file (with sample settings):
  [WarmReserve]
  sIPAddress=11.22.33.44
  wUDPPort=1971
  dwTimeOutSec=90
  bIAmTheReserve=False
• Note that while sIPAddress and bIAmTheReserve entries can be changed at any time during the normal operation (they are 'read on-the-fly'), wUDPPort and dwTimeOutSec entries should be set before module start-up.
• If wUDPPort is set (and the given port is not unavailable), then the following rules will apply:
  • WarmReserve info packets are sent to the remote party in every 10 seconds, containing the sum of UpdLocAck+FwdSMRx for both signaling links;
  • if the corresponding sum from the remote site does not increase within dwTimeOutSec seconds, then local side will switch "Auto-send UpdLoc's" ON; event is logged and an appropriate ERR trap is issued;
  • if the corresponding sum from the remote site subsequently (i.e., after a time-out) increases, then event is logged, CEA trap is issued, and if bIAmTheReserve is set to 'True' then local side will switch "Auto-send UpdLoc's" OFF.

v2.00
• First release based on SS7MSMS.exe v1.35.