Parlay X 2.1 Short Messaging Statement of compliance
This section describes the standards compliance for the communication services for Parlay X 2.:
The Parlay X 2.1 interface complies toETSI ES 202 391-4 V1.2.1 (2006-12) Open Service Access (OSA); Parlay X Web Services; Part 4: Short Messaging (Parlay X 2).
Table 6-1 Statement of Compliance, Parlay X 2.1 Short Messaging
Method
Compliant
(Yes | No)
Comment
Interface: SendSms
sendSms
Y
sendSmsLogo
Y
Note: The image is not scaled.
sendSmsRingtone
Y
Note: Ringtones must be in either SmartMessaging or EMS (iMelody) format
getSmsDeliveryStatus
Y
Interface: SmsNotification
notifySmsReception
Y
notifySmsDeliveryReceipt
Y
Interface: ReceiveSms
getReceivedSms
Y
Interface: SmsNotificationManager
startSmsNotification
Y
stopSmsNotification
Y
SMPP v3.4 for Parlay X 2.1/Extended Web Services Binary SMS
The SMPP v3.4 plug-in for Parlay X 2.1 Short Messaging and for the BEA Extended Web Services (Binary SMS) acts as an External Short Message Entity (ESME) that connects to an SMSC over TCP/IP.
The plug-in instance binds itself to the SMSC either as ESME Transmitter and an ESME Receiver or as an ESME Transceiver.
The bindings occurs when the plug-in transitions from state inactive to active. It will not reach state active until it has bound. The plug-in unbinds itself prior to becoming inactive.
When an application sends an SMS with one recipient submit_sm PDU is used and when sending an SMS with 2 or more recipients submit_sm_multi is used.
Window size is configurable.
The plug-in supports segmented SMSs using either 7-, 8-, or 16 bit data coding. The maximum length of an SMS segment is:
160 Characters for 7 bit data coding (SMSC default alphabet).
140 Characters for 8 bit data coding (ASCII).
70 Characters for 16bit coding (UCS2).
Standards Compliance
The plug-in complies to Short Message Peer to Peer, Protocol Specification v3.4, Document Version:- 12-Oct-1999 Issue 1.2.
Table 6-2 Statement of Compliance, SMPP v3.4 for Parlay X 2.1 Short Messaging