SummaryThis article applies to the following:
|
ProcedureMany applications have a back-end architecture that uses Short Message Service (SMS) to notify or communicate with the application. When porting this solution to BlackBerry devices, a common problem with legacy device models is that these SMS application messages may also appear in the BlackBerry device user’s inbox. To set up the SMS listener, leverage the private static class ListeningThread extends Thread {
To prevent this message from appearing in the BlackBerry device user’s inbox, the sending server should configure the SMS message so that the message type is a system message. This message type can be defined by setting the Protocol Identifier (TP-PID) to 64 (0x40), and the Digital Coding Scheme (TP-DCS) to 244 (0xF4), as shown below: 07913180998000F0040491369740F43080224100238A116865 Note: TP-PID and TP-DCS show up in the above message as 40F4 in the octets in which they are expected. This definition will make sure that the SMS message will reach the receiving application but that the BlackBerry device user will not receive an alert, nor will they see it in their inbox. Additional InformationFor more information on SMS specifications, see the 3GPP™ web site. |