List of Tables, Vii | Nokia WAP and SMS gateway specification

List of Tables
3-1. Core Group Variables	14
3-2. Kannel Command Line Options	20
3-3. Kannel HTTP Administration Commands	22
4-1. Wapbox Group Variables	24
5-1. SMSC Group Variables	27
5-2. SMSC driver features	49
5-3. SMSC driver internal features	50
5-4. Smsbox Group Variables	52
5-5.Smsbox-route Group Variables	55
5-6.SMS-Service Group Variables	56
5-7. Parameters (Escape Codes)	61
5-8.X-Kannel Headers	63
5-9.X-Kannel Post Headers	64
5-10.SendSMS-User Group Variables	66
5-11. DLR Database Field Conﬁguration Group Variables	69
5-12. MySQL Connection Group Variables	71
5-13. OTA Setting Group Variables	72
5-14. OTA Bookmark Group Variables	73
5-15. SMS Push (send-sms) CGI Variables	75
5-16. OTA CGI Variables	80
7-1. PPG core group conﬁguration variables	83
7-2. PPG user group conﬁguration variables	85
B-1. Fakesmsc command line options	95
C-1. Test_ppg’s command line options	99
C-2. Test_ppg’s conﬁguration ﬁle directives	101

vii

Page 7

Image 7

Nokia WAP and SMS gateway manual List of Tables, Vii

WAP and SMS gateway specifications

Nokia has long been a pivotal player in the telecommunications industry, and its contributions to mobile communication technology are numerous. Among these contributions, the Nokia WAP and SMS Gateway stand out as essential elements in enabling mobile internet access and messaging services in the early days of wireless communication.

The Nokia WAP (Wireless Application Protocol) gateway was introduced to facilitate mobile access to the internet and to allow users to interact with web services through their mobile devices. Built on a client-server architecture, the WAP gateway acted as a bridge between the mobile network and the internet, translating traditional web content into a format that mobile devices could effectively render. This conversion was crucial, given the limitations of early mobile devices regarding screen size, processing power, and network bandwidth.

One of the main features of the Nokia WAP gateway was its ability to provide users with real-time access to information such as weather updates, news, and stock prices. By using a lightweight markup language called WML (Wireless Markup Language), the gateway allowed developers to create mobile-friendly websites that could be accessed via WAP-enabled devices. This marked a significant step toward the mobile internet we know today, creating a new realm of possibilities for developers and users alike.

Another critical aspect of Nokia's offering was the SMS (Short Message Service) gateway. The SMS gateway provided a robust platform for sending and receiving text messages across various mobile networks. It enabled seamless communication between devices, regardless of the underlying technology. This feature made SMS a popular choice for both personal communication and business applications, such as marketing campaigns and customer service notifications.

The Nokia SMS gateway utilized established protocols, such as SMPP (Short Message Peer-to-Peer), to ensure reliable message delivery and efficient interaction between SMS applications and mobile networks. Its characteristics included scalability, allowing service providers to handle large volumes of messages, and flexibility to integrate with existing applications and systems.

In summary, the Nokia WAP and SMS gateway played a vital role in the evolution of mobile communication. With features that enabled mobile internet access and streamlined messaging capabilities, these technologies laid the groundwork for the mobile-centric world we live in today. Their legacy continues to influence mobile application development and the broader telecommunications landscape. As the industry progresses, the innovations introduced by Nokia serve as a reminder of the foundational technologies that paved the way for modern mobile experiences.

Contents

Andreas Fink Open Source WAP and SMS gatewayLars Wirzenius Kalle Marjola Stipe Tolj Bruno RodriguesAarno Syvänen Kannel 1.3.1 User’s Guide Open Source WAP and SMS gateway Table of Contents Extended headers Kannel Post XML Post Fake messages Fakesmsc command line options Vii List of Tables Overview of WAP Introduction Overview of WAP Push Overview of SMS This section needs to be written FeaturesRequirements IntroductionPage Getting the source code Installing the gatewayFinding the documentation Compiling the gateway Using pre-compiled binary packages Installing the gatewayInstalling Kannel from RPM packages Removing Kannel Log in as root Remove the RPM package Installing the gateway Installing Kannel from DEB packages Remove the package completely Installing the gateway Install or upgrade the DEB packageIf you don’t want Kannel to run as a daemon, run Page Conﬁguring the gateway Using the gatewayConﬁguration ﬁle syntax Inclusion of conﬁguration ﬁles Variable Value Description Core conﬁguration IP-listseveral addresses, separated with With admin-port, this can beLower network layer. Defaults Bool Layer. Defaults to no IP or ’*’ VariableValueﬁlename Receiving SMS messages from String to unify received phoneNumbers, for Smsc routing Handle them properly. This is Only, i.e. for the administration Using this variable, no SMSﬁlename Down violently Enable the use of an Http SMS service requests to Working as a Https client. If Type Default this is set to ’internal’When Kannel message queues Kannel is willing to trust when After the bearer box, you can start the WAP box Command line optionsRunning Kannel Starting the gateway Kannel statuses Using the gateway Set debug-places for ’debug’ level output Http administration No other chance to resume normal operation Bring down the gateway, by setting state toSpace. Password required Shutdown a single Smsc link. Password WAP gateway conﬁguration Setting up a WAP gatewayWapbox conﬁguration Left side URL to the given Default gives you 10 mappingsMap-url setting. Thus, Adds a single mapping for Checking whether the WAP gateway is alive Running WAP gateway SMS centers Setting up a SMS GatewayRequired components SMS gateway conﬁguration An optional name or id for Problems, so avoid it and anySpecify the used SMS-service See below for a complete list Semicolon ’’. For example Which are accepted to be sentThrough this SMSC. Multiple Entries are separated with Nokia Cimd 1.37 Machine that runs the Smsc Setting up a SMS GatewayValue. Set it to 0 to disable this Feature This preﬁx from the sender All messages sent fromKannel. If Kannel is asked to Send a message, it will remove Or hostname Connecting over a modem to anDefaults to send. All outgoing Service If set, only connections from Keepalive command will beFeature. Requires username or More than this time. Defaults to Error ocur Disconnect/reconnect, defaultWhen this parameter is unset or Defaults to the maximum Smpp Attempt to use a Transceiver modeUse value 0 to disable this I/O Password matching Change the interface version Default if not set isNot deﬁned the default device That no more than 10 default VariableValue Sema Group SMS2000 OIS 4.0 SM/ASI for CriticalPath InVoke SMS Center GSM modem Modem Type Modems Too Default value 0 means to try toNokia 6210, 7110, 8210 tested Probably other Nokia phones Optional phone number Using the ’message-storage’To work with this setting are For this many seconds. If Command, enable this String to use when trying toOptional. Defaults to false Before ﬁrst command Fake Smsc HTTP-based relay and content gateways Sema Ois At2 Http Using multiple SMS centersFeature checklist Featurecimd Can send octet data without UDH Smsc driver internal featuresCan set Validity Can set Deferred Can set PID Can set RPI Can send 8 bits Correctly send GSM alphabet Smsbox conﬁguration Symbol Meaning Bearerbox for the purpose Smsbox Group VariablesOptional smsbox instance An smsbox connected to an Sendsms-charsstring Global-sender Non-zero value Typical ’smsbox’ group could be something like this Apply Smsbox routing inside bearerboxDeﬁnes for which smsbox Instance the routing rules do SMS-service conﬁgurations Word in the SMS message Services are identiﬁed byWord Message contains If the service has aliases, they URL corresponds to one Service. b Multiple entries are You use this sms-service typeUse these kind of services is Checked using white/black-list Certain shortcut numbers to be Service. This may be used toAllowed to this service Allow only inbound SMS to Normally Content-Type for reply, it isUsed for url type services, If client does not set ﬁle Black-list service is deﬁnedSee notes of phone number Format from numhash.h header How sms-service interprets the Http response SMSPush equivalent Kannel Header Extended headers Hex format Kannel PostXML Post Parameter escape code Kannel Header Equivalent Setting up a SMS Gateway SendSMS-user conﬁgurations Some sample ’sendsms-user’ groups LibSDB DLR storage External delivery report DLR storageInternal DLR storage MySQL DLR storage DLR database ﬁeld conﬁguration Table ﬁeld that is used for the timestamp data VariableSample ’dlr-db’ group Over-The-Air conﬁgurations MySQL connection conﬁguration Defaults to data Ota-setting. Any string isFor your WAP services, i.e Description of the service Ota-bookmark. Any string is Setting up more complex servicesA ’sendsms-user’ to use with it. With concatenation enabled 14. OTA Bookmark Group Variables Setting up multi-operator Kannel Setting up operator speciﬁc servicesRedirected replies ’Authorization failed’ reply Using the Http interface to send SMS messagesRunning SMS gateway Phone number of the sender Content can be more thanBits or to UCS2. Defaults to Returned Indicator, or 5,6,7,8 for Default-smscvariable canIndicator bits in DCS ﬁeld. If Indicator. The accepted values Inform SMS Center that it should Conﬁguration, or 0X per defaultIndicator RPI value. See Etsi Optional. If given, kannel will GET method for the OTA Http interface Using the Http interface to send OTA conﬁguration messages Bookmark document looks like this Conﬁguration, or ’Authorization Name or ID of the ’ota-setting’Not given the ﬁrst ’ota-setting’ When a XML document is SMS&WAP gateway conﬁguration Setting up a SMS&WAP gatewayRunning SMS&WAP gateway Mandatory value. Tells that we Setting up Push Proxy GatewayConﬁguring ppg core group, for push initiator PI interface PPG core group conﬁguration variables Conﬁguring PPG user group variables String Username for this user String Password for this userWap-push-user String An user Finishing ppg conﬁguration Running a push proxy gateway An example using Http SmscSetting up Push Proxy Gateway You can, of course, use more complex command line options Default network and bearer used by push proxy gateway Using SSL client support Using SSL for Http Using SSL server support for PPG Https interface Using SSL server support for the sendsms Http interfaceUsing SSL for Http Delivery Reports Getting help and reporting bugs Appendix A. Using the fake WAP sender Setting up fakesmsc Appendix B. Using the fake SMS centerRunning Kannel with fakesmsc connections Switch Value Description Fakesmsc command line optionsFake messages Send a maximum of max Creating push content and control document for testing Starting necessary programs Default any. Application Table C-1. Testppg’s command line optionsUse content qualiﬁer string Instead of default si service Testing PAP protocol over Https Using Nokia Toolkit as a part of a developing environment101 Directive Value Description String User’s username Mandatory value. PPG service ﬁlename Document Mandatory value. PPG serviceString User’s password 103 104 Appendix D. Setting up a dial-up lineAnalog modem Add the following lines to /etc/ppp/options.server Conﬁgure your phone this example is for Nokia Isdn terminalThis section needs to be written 105 Appendix E. Log ﬁles Bearerbox Access LogLog rotation 107 Appendix E. Log ﬁles MClass GlossaryCoding RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1 Society 109 Bibliography