| Is it possible to get the complete PDU |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through February 02, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Mikael Christersson New member Username: Micke_c Post Number: 11 Registered: 01-2005 |
Hi! When enabling the receive messages function I need to get the complete PDU from NowSMS. Is this possible? The only parameters that I have found that will work for incoming SMS are: @@SENDER@@ @@FULLSMS@@ @@RECIP@@ @@BINARY@@ @@DCS@@ @@PID@@ @@UDH@@ But are there something like @@PDU@@ that could solve my problem? // Micke | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5250 Registered: 10-2002 |
Hi Micke, No, it is not possible. Keep in mind that the GSM modem interface is only one supported interface, so the raw PDUs would vary considerably by interface. Is there some specific information that you are looking for from the PDU? -bn | |||
| Mikael Christersson New member Username: Micke_c Post Number: 12 Registered: 01-2005 |
Hi Bryce! I need SMS-Deliver, Sender number (already available), TP-PID, TP-DCS, TP-SCTS (Timestamp from smsc), UDH and UD. As you can see I need almost everything.... I am developing an application that will send messages to a SMSC. NowSMS will then get them from the SMSC. The messages will be sent in 8-bit and may also be concatenated (not test messages). Because of this I need the UDH and UD. Because of the concatenated messages I also need the SMS-Deliver (TP-UDHI). My next problem is that I will also reveice messages coded in 7-bit and 16-bit that I also need to process. Will this be possible to handle with NowSMS? // Micke | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5317 Registered: 10-2002 |
Hi Micke, Apologies for the long delay. Delivering the raw PDU is a problem. You can get PID, DCS, UDH and UD. UDHI can be logically deduced (if UDH is present, then UDHI is set). But the SMSC timestamp is a problem, as that is currently not saved. (We could probably save it, but we'd be hard pressed to try to make any changes in this area until after NowSMS 2006 is released.) Another issue is that we automatically recombine any unsegmented messages. It would appear that you do not want us to do this? We could probably put in a configuration setting to skip this decode, but again I'm hesitant to commit to this until we can get NowSMS 2006 released. (Once we clear that backlog of feature updates, it will be easier to schedule others.) -bn | |||
