|
|
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 message counts (voice, fax, and e-mail) or as detailed messages.
When a voice, fax, or e-mail message is received, a copy of the incoming message is sent to an SMS_Notify mailbox. Only one copy of the message is stored on the server regardless of the 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:
If there is no message in the mailbox, the SMS_Notify application agent sleeps for the number of seconds specified in the PollingInterval parameter 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 specified in the PollingInterval parameter.
Before you start administering SMS notification services, ensure that the following tasks have been completed.
![]() |
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. |
You can perform the following tasks for SMS Notification Services:
For information about setting up SMS Notification for subscribers see "Provisioning Subscribers".
Use the following steps to add an SMS Administrator Account. This account is the special SMS Notification mailbox that acts as a queue and is used to hold subscribers' SMS Notification messages until the SMS_Notify application agent sends them to an SMS server.
![]() |
Note You must create a common SMS Notification Administrator shared by all COIs on your system. Cisco recommends doing so in a "dummy COI" accessible by only the top level administrator. |
Step 2 Click on the Subscriber Administration button.
![]() |
Note Although the account is an administrative account, it is added as a subscriber. |
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 Use the defaults for the remaining parameters. |
Step 5 Click on Submit.
.
| Field | Description | Valid Values |
|---|---|---|
Required field. | notifier (by convention) | |
Required field. | notifier (by convention) | |
Required field. | notifier (by convention) | |
Enter a fictitious telephone number. Required field. | 4-15 digits | |
User ID Options | Identifies the uid parameter for storing the information on the messaging server. | Valid entry for the SMS Notification Administrator:
|
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. | |
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) | |
Identifies the messaging server that contains the SMS Notification mailbox. | A valid messaging server from the drop-down menu. |
The SMS_Notify.ini file provides 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.
![]() |
Note The $TNTHOME/parms/DialMap.ini file SMS_MAPPING section is used to map mobile phone numbers to international numbers. See the Gateserver Installation and Configuration Manual for information about addressing and dialing rules. |
Step 2 Type: cd $PARMLIB/apps/SMS_Notify
Step 3 Edit the SMS_Notify.ini file as desired (Table 8-2).
![]() |
Note You must configure these parameters for SMS notification to work. |
| Parameter | Description | Valid Values |
|---|---|---|
LDAP host name | A valid host name. | |
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 (uid LDAP attribute) of the SMS Notification mailbox. | Must be the uid for the SMS Notification mailbox. notifier (by convention) |
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 | |
This password resides on the LDAP server; it is the rootpw entry in the slapd.conf file. This can be encrypted. | ||
The LDAP search base. This search base can be found on the LDAP server. | Default: o=Organization | |
SMTPHosts | Used if SMS Notification messages are sent to the SMS server 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 | A parameter supplied by the SMPP Center. | Up to 13 characters |
InterfaceVersion | A parameter supplied by the SMPP Center. | 0-127 |
ServiceType | A parameter supplied by the SMPP Center. | 0-127 |
TON | A parameter 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 |
This task is performed during the initial configuration of your uOne system by the Quick Configuration tool.
cd $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
| DATATOKEN 100 1 * * 8049354629 amisain/amisain DATATOKEN 100 1 * * 804 UM/UM UM.ini STATIC_NOWAIT 100 1 * * * MWI_Notify/MWI_Notify DATATOKEN 100 1 * * MWI_OnOff MWI_OnOff/MWI_OnOff STATIC_NOWAIT 100 1 1 0 ** SMS_Notify SMS_Notify/SMS_Notify
|
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
reload sched all
When uOne Administration/PMA is installed, the SMS feature is disabled. You must enable SMS in the schemaConfig.ini file.
Step 2 Type:
cd /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata
Step 3 Edit schemaConfig.ini file and set the following attribute to yes.
[FeatureSet]
SMS=yes
The SMPP Center LDAP entries on the directory server contain SMPP Center 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 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. |
![]() |
Note You should create SMPP center entries only within COIs. Otherwise, they won't be accessible to members of the COI. |
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 Peer to Peer (SMPP) Interface Specification, v 3.3 and ETSI Standard GSM 03.40. |
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 3 through 5.
.
| Field | Description | Valid Values |
|---|---|---|
The current directory server. System-generated entry. | This field cannot be modified. | |
Indicates where in the LDAP database this entry resides. The entry distinguished name (dn) to which the SMPP Center belongs. | Select a dn from the drop-down menu. | |
SMPP Center Identification | Identifies the SMPP Center. | A valid name with no special characters. Default = N/A |
SMPP Center IP Address | The IP address of the SMPP Center. | 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 SMPP Center. | 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 parameter 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 |
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 3 through 9.
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 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 attributes 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 entry, repeat steps 3 through 8.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Mon Sep 25 20:08:01 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.