Supported Hardware
Package Content
Server Install
Client Install
Gateway Install
Tech Info
PDU format
Bugs / Todo
Related Links

Jump to Vim Home Page

Project SMSLink - PDU Format Support

Please note: the purpose of the present document is not to provide a full tutorial on how to use the PDU format, nor is it a reprint of the PDU protocol spec. If you're looking for the latter, please refer to the ETSI GSM 03.40 standard, available for download from ETSI's website. There is also a very detailed description of the PDU format and its quirks available here, presented in a way that make it a lot easier to understand than ETSI's raw specs (please see also my related links section for links to sites with more info on PDU format).

Rather, the purpose of this page is to provide as accurate an information as I can on the level of support for the numerous PDU format features and quirks within SMSLink.

Table of Contents

PDU string structure summary.


<numplan> support.

The <numplan> field defines the context within which the next field, <oa> or "originating address", has to be understood. The most common numplans are 0x81 (local numbering scheme) or 0x91 (international numbering scheme).

But of course, there are situations where the originating address has to be hidden, or is meaningless, such as when the message was sent from a website. There will, of course, be other cases, but those are the ones we're aware of (thanks to the kind help of Thomas Gutzler).

<numplan> values supported in reception mode

NumplanMeaningOA containsSpotted from
0x81 local numplan local number regular mobile phones
0x83 data numplan (X.121) local or int. number
0x85 reserved or private numplan garbage [1]
0x89 [2] reserved or private numplan garbage
0x91 international numplan international number regular mobile phones
0xA1 national numplan service number (?)
0xC1 [4] subscriber number / ISDN-tel. voicemail number (?) Vodaphone South Africa
0xC8 [4] subscriber number / national local number
0xD0 Alphanum. (GSM TS 03.38) website name [3]

1: The actual contents of the <oa> field will be logged through syslog at the "notice" level before being zeroed out.
2: cf. <numplan> 0x85 -- handled in the same way.
3: Most often. Or any other short string to the choosing of the site's administrator.
4: Support included as of ver. 0.55b.

<numplan> values supported in sending mode

NumplanMeaningOA containsUsed from
0x81 local numplan local number GSM module
0x91 international numplan international number GSM module

Data Coding Scheme (<dcs>) support.

At present, only DCS_PCCP437 is supported. More on this TBD.

Last Modified: September 29th, 2006.
philipa STRUDEL scarlet PUNKT be
SourceForge Logo