Administering SMS Notification Services

How SMS Notification Works

Prerequisites

Managing SMS Notification

Engineering Considerations

Administering SMS Notification Services

The uOne product supports Short Message Service (SMS) notification services to cellular telephones for voice, fax, and e-mail messages on a subscriber basis. Currently, English and Dutch are the supported languages for SMS Notification.

When a voice, fax, or e-mail message is received for a subscriber who chooses SMS notification, the uOne system sends notification to the subscriber via an SMS center. Subscribers can choose to receive message notification as a message counts (voice, fax, and e-mail) or as detailed messages.

How SMS Notification Works

When a voice, fax, or e-mail message is received, a copy of the incoming message is sent to an SMS_Notify mailbox and processed via standard protocol access. Only one copy of the message is stored in the server regardless of number of recipients on the same server.

The SMS_Notify application agent processes messages in the SMS_Notify mailbox. For each message in the notification mailbox, SMS_Notify performs the following actions for each recipient of the message:

Checks whether the recipient is a valid subscriber, is provisioned for SMS notification service, and is administered on the mail server being serviced by the SMS_Notify mailbox.
If the subscriber has SMS notification services, gets the notification options from the Directory Server—notification method, type (detailed message or message count), and language.
Builds the short message.
Sends the message to SMS Center via SMTP or SMPP.

If there is no message in the mailbox, the SMS_Notify application agent sleeps for the number of seconds as specified in the PollingInterval option in SMS_Notify.ini file. The application agent sends a NOOP IMAP command to get the status and to keep the connection alive.

After processing all the messages, the SMS_Notify application agent deletes the messages in the SMS_Notify mailbox. It then sleeps for the number of seconds as specified in the PollingInterval option.

Prerequisites

Before you start administering SMS Notification Services, ensure that the following tasks have been completed.

The SMS server(s) are installed and configured. You will need data from the SMS server(s).

Note If multiple SMS servers are used, then each SMS server must have the same System ID and Password administered for SMS_Notify application access.

The SMS_Notify application agent is installed on the appropriate Gateserver.
The notify plugin is installed and configured on the appropriate Messaging Server.
UMSA/PMA are installed and configured.

Managing SMS Notification

You can perform the following tasks for SMS Notification Services:

Setting up SMS Notification Administrators
Administering the SMS_Notify application agent.
Updating the Schedule Table
Activate the SMS feature in UMSA.
Setting up SMPP Centers

Engineering Considerations

You can have only one SMS Notification mailbox on a Messaging Server.

Adding an SMS Notification Administrator

Use the following steps to add an SMS Administrator Account. This account is the special SMS Notification mailbox that is used to hold subscribers' SMS Notification messages until the SMS_Notify application agent sends them to the SMPP Center.

Step 1 Access UMSA.

Step 2 Click on the Subscriber Administration button.

Step 3 Click on Add a Subscriber.

Step 4 Enter the data in the following input fields (Table 8-1).

Full Name
Given Name
Last Name
Telephone Number
User ID Options
E-mail Address
Mail Quota
Mail Server

Note

Step 5 Click on Submit.
Table 8-1: SMS Notification Administrator Attributes

Attribute Description Valid Values

Full Name

Required field.

notifier (by convention)

Given Name

Required field.

notifier (by convention)

Last Name

Required field.

notifier (by convention)

Telephone Number

Enter a fictitious telephone number. Required field.

4-15 digits

User ID Options

Identifies the uid attribute for storing the information on the Messaging Server.

Valid entry for the SMS Notification Administrator:

user name— the first part of the e-mail address is used as the uid attribute.

E-mail Address

This is the mailbox that stores messages used to build SMS notification messages for subscribers who use SMS Notification.

notifier@<e-mail_domain>

where <e-mail_domain> is one of the e-mail domains serviced by the messaging server.

Mail Quota

Indicates the maximum amount of disk space in bytes that will be available for this subscriber account.

Must be 0.

Default=0 (unlimited disk space)

Mail Server

Identifies the Messaging Server that contains the SMS Notification mailbox.

A valid Messaging Server from the drop-down menu.

Attribute	Description	Valid Values
Full Name	Required field.	notifier (by convention)
Given Name	Required field.	notifier (by convention)
Last Name	Required field.	notifier (by convention)
Telephone Number	Enter a fictitious telephone number. Required field.	4-15 digits
User ID Options	Identifies the uid attribute for storing the information on the Messaging Server.	Valid entry for the SMS Notification Administrator: user name— the first part of the e-mail address is used as the uid attribute.
E-mail Address	This is the mailbox that stores messages used to build SMS notification messages for subscribers who use SMS Notification.	notifier@<e-mail_domain> where <e-mail_domain> is one of the e-mail domains serviced by the messaging server.
Mail Quota	Indicates the maximum amount of disk space in bytes that will be available for this subscriber account.	Must be 0. Default=0 (unlimited disk space)
Mail Server	Identifies the Messaging Server that contains the SMS Notification mailbox.	A valid Messaging Server from the drop-down menu.

Administering the SMS_Notify Application Agent

The following steps provide the SMS_Notify application agent with the information to communicate with the GateServer and the Directory Server. This information is required for SMS Notification and is set up during the initial configuration of your uOne system..

Step 1 Go to the GateServer where the SMS_Notify application agent resides.

Step 2 Type: cd $PARMLIB/apps/SMS_Notify

Step 3 Edit the SMS_Notify.ini file and set the following attributes (Table 8-2).

[LDAPConfig]

LDAPhost=

LDAPport=

Notifier=

LDAPBindDn=

LDAPDnPassword=

LDAPsearchbase=

If SMTP will be used, set this attribute:

[SMTPConfig]

SMTPHosts=

[Mailbox]

PollingInterval=

ReturnPath=

If SMPP will be used, set the following attributes:

[SMS]

SystemID=

Password=

SystemType=

InterfaceVersion=

ServiceType=

TON=

NPI=

Address=

Note

Table 8-2: SMS_Notify.ini Attributes

Attribute	Description	Valid Values
LDAPphost	LDAP host name	A valid host name.
LDAPport	LDAP port number This number can be found on the LDAP server; it is the port entry in the slapd.conf file.	By convention, use 389
Notifier	The user ID of the SMS Notification mailbox.	Must be the uid for the SMS Notification mailbox. notifier (by convention)
LDAPBindDn	The LDAP distinguishing name of the LDAP "superuser." This name can be found on the LDAP server; it is the rootdn entry in the slapd.conf file.	Example: cn=Directory Manager, o=Organization Default= N/A
LDAPDnPassword	LDAP password for the LDAP "superuser"	This password resides on the LDAP server; it is the rootpw entry in the slapd.conf file. This can be encrypted.
LDAPsearchbase	The LDAP search base. This search base can be found on the LDAP server; it is the searchbase entry in the slapd.conf file.	Default: o=Organization
SMTPHosts	Used if SMS Notification messages are sent to the SMPP Center via the SMTP protocol.	Any valid SMTP host name; host names must be separated by a comma, space, or TAB.
PollingInterval	The time period that must elapse before the SMS_Notify application agent checks the SMS notification mailbox for messages to send.	Any reasonable number. Units is in seconds
ReturnPath	The e-mail account to which returned mail should be sent.	A valid e-mail address Postmaster (by convention)
SystemId	Login ID for the SMPP server.	Up to 16 characters
Password	Password for the SMPP server log in account.	Up to 9 characters
SystemType	An attribute supplied by the SMPP Center.	Up to 13 characters
InterfaceVersion	An attribute supplied by the SMPP Center.	0-127
ServiceType	An attribute supplied by the SMPP Center.	0-127
TON	An attribute supplied by the SMPP Center.	0-127
NPI	An attribute supplied by the SMPP Center.	0-127
Address	An attribute supplied by the SMPP Center.	Up to 41 characters

Updating the Schedule Table for SMS_Notify

This task is performed during the initial configuration of your uOne system by the Quick Configuration tool.

Step 1 If this is a new installation, add the SMS_Notify application agent to Schedule.<hostname> file. Go to the GateServer where the SMS_Notify application should reside and type:

$PARMLIB/parms/APP

Step 2 Add the following information to the Schedule.<hostname> file:

STATIC_NOWAIT 100 1 1 0 * * SMS_Notify SMS_Notify/SMS_Notify

Figure 8-1: Example of Schedule.<hostname>

Step 3 If the system is operational and you are reloading changes to an existing SMS_Notify application agent, you must stop the application first.

Type: kill <PID>
where PID is the process ID of the application instance that you want to stop

Step 4 Reload the schedule table. Type:

umcli

resched static SMS_Notify

Activating SMS in UMSA

When UMSA/PMA is installed, the SMS feature is disabled. You must enable SMS in the schemaConfig.ini file.

Step 1 Go to the GateServer on which UMSA resides.

Step 2 Type:
cd /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata

Step 3 Edit schemConfig.ini files and set the following attribute to yes.

[FeatureSet]

SMS=yes

Managing SMPP Centers

The SMPP Center LDAP entries on the Directory Server contain SMS servers attributes. When the SMS_notify application agent sends SMS notification messages to an SMPP Center, this information is used to establish a network connection with an SMS Server at the SMPP Center.

Note If SMTP is used for SMS notification, you do not have to set up SMPP centers. The SMS Information entry for the subscriber must contain a notification e-mail address, instead of an SMPP Center ID.

Adding SMPP Centers

Use the following steps to add an SMPP Center to the uOne system.

Note For information about the GSM Data Coding Scheme, GSM Protocol Identification, Type of Number, and Numbering Plan Indicator attributes, refer to the following standards specifications: Short Message Per to Peer (SMPP) Interface Specification, v 3.3 and ETSI Standard GSM 03.40.

Step 1 Access UMSA.

Step 2 Click on the Global Configuration button.

Step 3 Click on Add a SMPP Center.

Step 4 Enter the appropriate data in the input fields (Table 8-3).

Step 5 Click on Submit

Step 6 To add another SMPP Center account, repeat steps Step 3 to Step 5.
Table 8-3: Add SMPP Center Attributes

Attribute Description Valid Values

Directory Server

The current Directory Server. System-generated entry.

This field cannot be modified.

Entry DN

Indicates where in the LDAP database this entry resides. The entry distinguished name (dn) to which the administrator account belongs.

Select a dn from the drop-down menu.

SMPP Center Identification

Identifies the SMS center.

A valid name with no special characters.

Default = N/A

SMPP Center IP Address

The IP address of the SMS server.

A valid IP address in the following format: xxx.xxx.xxx.xxx,

xxx = 0 -255

Default = N/A

SMPP Center Port Number

The port number of the SMS server.

0 - 32768

Default = N/A

GSM Data Coding Scheme

The GSM data coding scheme supplied by the SMS Center.

0 - 127

Default = N/A

GSM Protocol Identification

The GSM Protocol Identification supplied by the SMS Center.

0 -127

Default = N/A

Type of Number

The Type of Number attribute supplied by the SMS Center.

0 - 127

Default = N/A

Numbering Plan Indicator

The Numbering Plan Indicator supplied by the SMS Center.

0 - 127

Default = N/A

Attribute	Description	Valid Values
Directory Server	The current Directory Server. System-generated entry.	This field cannot be modified.
Entry DN	Indicates where in the LDAP database this entry resides. The entry distinguished name (dn) to which the administrator account belongs.	Select a dn from the drop-down menu.
SMPP Center Identification	Identifies the SMS center.	A valid name with no special characters. Default = N/A
SMPP Center IP Address	The IP address of the SMS server.	A valid IP address in the following format: xxx.xxx.xxx.xxx, xxx = 0 -255 Default = N/A
SMPP Center Port Number	The port number of the SMS server.	0 - 32768 Default = N/A
GSM Data Coding Scheme	The GSM data coding scheme supplied by the SMS Center.	0 - 127 Default = N/A
GSM Protocol Identification	The GSM Protocol Identification supplied by the SMS Center.	0 -127 Default = N/A
Type of Number	The Type of Number attribute supplied by the SMS Center.	0 - 127 Default = N/A
Numbering Plan Indicator	The Numbering Plan Indicator supplied by the SMS Center.	0 - 127 Default = N/A

Modifying SMPP Center Accounts

Step 1 Access UMSA.

Step 2 Click on the Global Configuration button.

Step 3 Click on Modify a SMPP Center.

Step 4 Select a search option from the drop-down list box. The options correspond to fields in LDAP entries.

Step 5 Enter the data in the input field.

Step 6 Click on Search.

Step 7 Click on the appropriate account, if necessary.

Step 8 Enter the appropriate data in the input fields (Table 8-3).

Step 9 Click on Submit

Step 10 To modify another SMPP Center account, repeat steps Step 3 to Step 9.

Deleting SMPP Center Accounts

Ensure that there are no subscribers currently using the SMPP Center information in their Subscriber SMS entry. If there are any subscribers still using this SMPP Center information, the SMPP Center entry will not be deleted.

Step 1 Access UMSA.

Step 2 Click on the Global Configuration button.

Step 3 Click on Delete a SMPP Center.

Step 4 Select a search option from the drop-down list box. The options correspond to fields in LDAP entries.

Step 5 Enter the data in the input field.

Step 6 Click on Search.

Step 7 Click on the appropriate account, if necessary.

Step 8 Click on Delete.

Step 9 To delete another SMPP Center account, repeat steps Step 3 to Step 8.