| TSP Lab
| The 'Who Called' and 'Notify Me' system
| Sga-CallNotification
|
The 'Who Called' and 'Notify Me' system
Installation - Configuration
Overview - Applications, Files and Folders
For the applications that are composing the Sga-CallNotification system some Sga related folders should be created.
These are the followings:
- c:\Sga-WhoCalled - Location of the main application and its configuration file
- c:\Sga-Trapper - Location of Trap agent application and its configuration file (if sending SNMP traps to a network maintenance center is need)
- c:\Sga-SMS - Location of SMS sender module and its configuration file
- c:\Gy4 - The Network Time Protocol Client and its configuration file
- d:\LogFiles - Place of the logfiles created by Sga modules
- d:\StatFiles - Place of the statistics created by Sga-WhoCalled
- d:\TrapFiles - Location of temporary taps files to be sent as SNMP traps to a trap manager
- d:\SMSFiles - Location of SMS files generated by Sga-WhoCalled
and sent to the SMSC by the SgaSMS module
- d:\SMS_NOK - Location of SMS's for which sending failed
After creating folders copy the applications and the files belong to them into the proper folders.
If more than one Sga-WhoCalled applications should be run on the same computer create the necessary number of copies
of the "SgaWC_SS7.exe" and rename them with different filenames to distinguish amongs them. It is suggested to use the interfacecard base
address in the filename for the easy distinction which one is which. For example: create a copy named "SgaWC_SS7.D800.exe"
for the 0xD800 base addressed card, and another one named "SgaWC_SS7.D900.exe" for the 0xD900 base addressed card.
Configuration files also should be renamed after the application ("SgaWC_SS7.D800.ini" and "SgaWC_SS7.D900.ini").
Contents of the application packages:
- Sga-WhoCalled
- SgaWC_SS7.exe - Main application
- SgaWC_SS7.ini - Configuration file of the main application
- MTP2_47 v2.06 (+00 dB 120 Ohm).obj - Firmware for the interface card for 120 ohm impedance and without transmission amplification
- MTP2_47 v2.06 (+12 dB 120 Ohm).obj - Firmware for the interface card for 120 ohm impedance and with 12dDB transmission amplification
- SgaWC_SS7_BL_WCBusy.lst - List for those people who do not allow a WhoCalled SMS sent while he/she is busy.
- SgaWC_SS7_BL_WCOther.lst - List for those people who do not allow a WhoCalled SMS sent while he/she is not reachable.
- SgaWC_SS7_BL_NotifyB.lst - List for those people who do not allow a NotifyMe SMS sent when his/her called party becomes available again.
- SgaWC_SS7_BL_NotifyA.lst - List for those people who do not allow a NotifyMe SMS sent to others about his/her availability.
- SgaWC_SS7_WL_NotifyA.lst - Execption list for those people whose numbers are covered by a range defined in SgaWC_SS7_BL_NotifyA.lst
and allowed to get NotifyMe SMS sent after all.
- SgaWC_InvisibleSMS.sms - Contains an invisible SMS which is used to make the SMSC interrogating the unavailable subscriber
when he/she is available again
- Sga-SMS
- SgaSMS.exe - The SMS sender application
- SgaSMS.ini - Configuration file of SMS sending application
- WhiteList.txt - List of MSISDN's only who will receive short messages (if any restriction is needed)
- SMSEdit.exe - The SMS editor utility
- SMSEdit.ini - Configuration for SMS editor
- Sga-Trapper
- Trapper.exe - SNMP (Simple Network Management Protocol) Trap agent application
- Trapper.ini - Configuration for SNMP Trap agent application
- SgaTrapD.dll - It should be copied into the C:\Windows\System32 folder!
- Trapper.mib - Sga related SNMP Management Information Base (MIB) file should be imported on the SNMP manager(s).
- Gy4
- Gy4.exe - Network Time Protocol client
- Gy4.ini - Configuration for NTP Client
Applications can be started from the application folders but it is recommended to create shortcuts on the desktop
for the convenient starting of the system.
Configuration
At least these configurations should be done before using the system.
The Sga-WhoCalled application
Open SgaWC_SS7.ini and set the following entries to the proper values:
- [Sga-47 Card]/wBaseAddress=0xD800: This entry defines which base address should be used to reach the Sga-47 by the software.
(The base address is set on the Sga-47 card by the DIP switch. Default value is 0xD800.)
- [SGA-47 Card]/sMTP2ObjectFile: The firmware file defines the transmitter impedance and level.
Full path should be given, for example: "c:\Sga-WhoCalled\MTP2_47 v2.06 (+00 dB 120 Ohm).obj".
- [SS7 Advanced]/bySS7ATimeSlot: SS7 timeslot of the signaling link for channel A
- [SS7 Advanced]/bySS7BTimeSlot: SS7 timeslot of the signaling link for channel B
- [SS7 Advanced]/wLocalPointCode_NI2: The local point code of the Sga equipment for national numbering.
(It can be decimal or hexadecimal value. If hexadecimal value is used do not forget to prefix it with '0x'.)
- [SS7 Advanced]/wLocalPointCode_NI3: The local point code of the Sga equipment for international numbering
- [SS7 Advanced]/wLocalGT: Global Title of the Sga application used in MAP messages
- [SS7 Advanced]/wSS7ARemotePointCode: The point code of the remote node which the PCM A is connected to.
- [SS7 Advanced]/wSS7ARemotePointCode: The point code of the remote node which the PCM B is connected to.
- [SS7 Advanced]/wSS7ACICOffset: Default CIC code is originated from the timeslot number.
The CIC code for PCM A can be shifted by this value. Default value is set to 0 which means no offset.
- [SS7 Advanced]/wSS7ACICOffset: Default CIC codes are from the timeslot number.
The CIC code for PCM B can be shifted by this value. Default is set to 0.
- [SS7 Advanced]/sMCC: This is the contry code (a prefix) which is used to prefix the calling number and this number is put
into a reportSM_DeliveryReport message as the MSISDN
- [SS7 Advanced]/dwChannelSeizedTimeOutSec: A speech channel is released after this time (time between ACM and REL)
- [SS7 Advanced]/byISUPReleaseCause: Release cause value in the REL message (28 - Invalid number format)
- [SS7 Advanced]/wFakeGT: Used in ForwardSM/SM-RP-OA as SCAddressOA; should usually be the same as the value of sSS7LocalGT
- [Advanced]/sLogFilesPath: Place of the logfiles created by the Sga-WhoCalled module (d:\LogFiles)
- [Advanced]/sSMSPath: Location of the SMS files to be send to the Caller (d:\SMSFiles)
- [Advanced]/sTrapFilesPath: Location of the temporary trap files generated by the Sga-WhoCalled module
to be sent to a Trap Manager (d:\TrapFiles)
- [Advanced]/sStatFilesPath: Location of the csv files containing statistics (d:\StatFile)
- [TimeSlots_A]/wTS#NN=1: Create entry for each timeslots which are used as speech channel where
NN refers to the timeslot in the PCM A. NN can be 0...31 and "bySS7ATimeSlot" must not be listed here or disable it with the value '0'!
If the value of an entry is 0 the timeslot is not a speech channel and if it is greater than 0 the timeslot is considered as a speech channel.
- [TimeSlots_B]/wTS#NN=1: Create entry for all timeslots which are used as speech channel where
NN refers to the timeslot in the PCM B. NN can be 0...31 and "bySS7BTimeSlot" must not be listed here!
- [TimeSlots_X]/200=1,17,29,34: Entries in this section defines 'virtual' timeslots with a point code
where IAM messages can arrive from using the listed CIC numbers. The given example means that IAM
messages using speech channel 1 or 17 or 29 or 34 can arrive from PC=200.
- [SMS Templates]/sWCBusy: The template for the "Busy" case SMS's. The given template would help to define customized one.
- [SMS Templates]/sWCBusySenderMSISDN: This value will appear as the sender of the SMS on the subscriber's phone.
- [SMS Templates]/byWCBusySenderNoA: Set it to 0x91 if sWCBusySenderMSISDN is numeric or to 0xD0 if the sWCBusySenderMSISDN is alphanumeric.
- [SMS Templates]/sWCOther: The template for the "Not Reachable" case SMS's. The given template would help to define customized one.
- [SMS Templates]/sWCOtherSenderMSISDN: This value will appear as the sender of the SMS on the subscriber's phone.
- [SMS Templates]/byWCOtherSenderNoA: Set it to 0x91 if sWCOtherSenderMSISDN is numeric or to 0xD0 if the sWCOtherSenderMSISDN is alphanumeric.
- [SMS Templates]/sNotify: The template for the "Notify" SMS's. The given template would help to define customized one.
- [SMS Templates]/sNotifySenderMSISDN: This value will appear as the sender of the SMS on the subscriber's phone.
- [SMS Templates]/byNotifySenderNoA: Set it to 0x91 if sNotifySenderMSISDN is numeric or to 0xD0 if the sNotifySenderMSISDN is alphanumeric.
After editing the SgaWC_SS7.ini save the modifications and (re)start the Sga-WhoCalled
application to use the new configuration values.
The SMS sender module (SgaSMS)
The SgaSMS module has some configuration entries in the SgaSMS.ini file.
- [SMSC]/sConnectID1: This is sent to the SMPP server as connection ID during establishing even conncetions
- [SMSC]/sConnectID2: This is sent to the SMPP server as connection ID during establishing odd conncetions
- [SMSC]/sPassword1: Password for the SMSC
- [SMSC]/sPassword2: Password for the (other) SMSC
- [SMSC]/sIPAddress1: IP address of the SMSC
- [SMSC]/sIPAddress2: IP address of the (other) SMSC
- [SMSC]/wTCPPort1: Communication port of SMSC1
- [SMSC]/wTCPPort2: Communication port of SMSC2
- [SMSC]/bBindAsTransceiver1: "True" means even connections will be bound as Transceiver
and "False" makes connections in Transmitter mode.
- [SMSC]/bBindAsTransceiver2: "True" means odd connections will be bound as Transceiver
and "False" makes connections in Transmitter mode.
- [SMSC]/sLocalMSISDN1: If set and the ANumber in the SMS file created by the Sga-WhoCalled is empty
then this will be the ANumber (the sender of the SMS). This can be numeric and alphanumeric value, as well.
- [SMSC]/sLocalMSISDN2: If set and the ANumber in the SMS file created by the Sga-WhoCalled is empty
then this will be the ANumber (the sender of the SMS). This can be numeric and alphanumeric value, as well.
- [Advanced]/sSMSPath: Location where from the module reads inputs files (d:\SMSFiles).
- [Advanced]/sSMSNOKPath: Location of the short messages which sending failed (d:\SMS_NOK).
- [Advanced]/sLogFilesPath: The place of the logfiles created by the Trapper module (d:\LogFiles).
- [Advanced]/sTrapFilesPath: Location of the temporary trap files generated by the Trapper module.
to be sent to the Trap Manager (d:\TrapFiles)
Execute the SgaSMS.exe to start the application. On the user interface the [SMSC]/Allow auto-connect to SMSC
menu item makes the module connect to the SMSC. The [SMSC]/Check and load input queue menu item enables the reading of
the input SMS files and the [SMSC]/Process waiting SM requests enables the sending of the SMS's.
The SNMP Trap agent (Trapper)
To set up the Trap Agent module edit the Trapper.ini file in the c:\Sga-Trapper folder:
- [SNMP Traps]/dwHeartBeatIntervalSec: Defines how often the module sends heartbeat trap to the manager.
- [SNMP Traps]/dwHwCheckIntervalSec: Period of the hardware checking.
- [SNMP Traps]/dwHwCheckNoRepeatSec: This defines the trap sending period of permanent hardware problem.
- [SNMP Traps Advanced]/sManagerIPAddress: IP address of the SNMP Trap Manager (NOC/NMC)
- [Advanced]/sLocalIPAddress: IP address of the Trap Agent
- [Advanced]/wRemoteUDPPort: UDP port of the Trap Manager when it waits for the connection
- [Advanced]/bCeaseBeforeSwitchingAlertLevel: If "True" a "Ceasing" will be sent to the manager
before changing the level of an alarm (for example when a Warning changes to Error)
- [Advanced]/sLogFilesPath: The place of the logfiles created by the Trapper module (d:\LogFiles)
- [Advanced]/sTrapFilesPath: Location of the temporary trap files generated by the Trapper module
to be sent to the Trap Manager (d:\TrapFiles)
Limits of the hardware resources for the various alarm levels can be set by the following entries
(these are examples, limits depend on the real resources):
- [SNMP Traps Advanced]/dw_WAR_BelowFreeKBytesOnDriveC: Alarm threshold of disk usage on drive C for WARNING level
- [SNMP Traps Advanced]/dw_ERR_BelowFreeKBytesOnDriveC: Alarm threshold of disk usage on drive C for ERROR level
- [SNMP Traps Advanced]/dw_CRI_BelowFreeKBytesOnDriveC: Alarm threshold of disk usage on drive C for CRITICAL level
- [SNMP Traps Advanced]/dw_{WAR, ERR, CRI}_BelowFreeKBytesOnDriveD: Alarm thresholds for disk usage on drive D as above
- [SNMP Traps Advanced]/dw_{WAR, ERR, CRI}_BelowFreeKBytesOfPhysicalRAM: Alarm thresholds for memory usage
- [SNMP Traps Advanced]/by_{WAR, ERR, CRI}_AboveMemoryLoadPercent: Alarm thresholds for memory load
If more than one TrapManagers should be used the parameter of them can be defined in this section
- [SNMP Secondary Managers]/sManagerIPAddress1: IP address of the secondary Manager
- [SNMP Secondary Managers]/wRemoteUDPPort1: UDP port of the secondary Manager
- [SNMP Secondary Managers]/sManagerIPAddress2: IP address of the third Manager
- [SNMP Secondary Managers]/wRemoteUDPPort2: UDP port of the third Manager
On the manager(s) the Sga related SNMP Management Information Base (MIB) file should be imported.
When the configuration is done start the SNMP Trap Agent by executing Trapper.exe.
On the user interface enable sending trap to the SNMP Trap Manager by [SNMP traps]/Send traps to SNMP manager menuitem.
To reading and sending the temporary trap files select the [SNMP traps]/Check and load input queue menuitem.
Heartbeat traps will be generated when the [SNMP traps]/Generate periodic heart-beat traps menuitem is checked.
Doing periodic hardware checking can be enabled by the [SNMP traps]/Do periodic hw checking menuitem.
Recommendation: When before the first start of the Trapper module a lot of traps
have been generated and stored in the d:\TrapFiles the suggestion is to delete these
previous trap files (*.tmp).
The NTP Client module (Gy4)
The Gy4 module has some configuration entries in the Gy4.ini file.
- [Advanced]/sNTPServer: IP address of the NTP server
- [Advanced]/dwQueryDelaySecWhenOK: period of NTP synchronizations (preset to fifteen minutes (900 secs))
- [Advanced]/dwQueryDelaySecWhenFailed: the next query will be done in this time when the previous was unsuccesful
- [Advanced]/dwRTTMaxMS: round trip time limit (can be network dependent)
- [Advanced]/sLogFilesPath: path for logging (d:\LogFiles)
Executing the Gy4.exe starts the application. On the user interface the "Apply required shifts"
checkbox should be checked to allow the client to adjust the local system clock.