Bibliography

RFC 2616 - Hypertext Transfer Protocol -- HTTP/1.1,

http://www.w3.org/Protocols/rfc2616/rfc2616.html, Request for Comments: 2616, The Internet

Society, 1999.

3GPP 23.038, http://www.3gpp.org/ftp/Specs/latest/Rel-5/23_series/23038-500.zip, ..., 3GPP, ?.

3GPP 23.040, http://www.3gpp.org/ftp/Specs/latest/Rel-5/23_series/23040-530.zip, ..., 3GPP, ?.

109

Page 116

Image 116

Nokia WAP and SMS gateway manual Bibliography, RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1 Society 109

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

Open Source WAP and SMS gateway Lars WirzeniusKalle Marjola Andreas Fink Aarno Syvänen Bruno RodriguesStipe Tolj 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 List of Tables Vii Introduction Overview of WAP Overview of WAP Push Overview of SMS Features RequirementsIntroduction This section needs to be writtenPage Finding the documentation Installing the gatewayGetting the source code Compiling the gateway Installing Kannel from RPM packages Installing the gatewayUsing pre-compiled binary packages Removing Kannel Log in as root Remove the RPM package Installing Kannel from DEB packages Installing the gateway If you don’t want Kannel to run as a daemon, run Installing the gateway Install or upgrade the DEB packageRemove the package completely Page Conﬁguration ﬁle syntax Using the gatewayConﬁguring the gateway Inclusion of conﬁguration ﬁles Core conﬁguration Variable Value Description With admin-port, this can be Lower network layer. DefaultsBool Layer. Defaults to no IP-listseveral addresses, separated with ﬁlename VariableValueIP or ’*’ String to unify received phone Numbers, for Smsc routingHandle them properly. This is Receiving SMS messages from Using this variable, no SMS ﬁlename Down violently Enable the use of an HttpSMS service requests to Only, i.e. for the administration Type Default this is set to ’internal’ When Kannel message queuesKannel is willing to trust when Working as a Https client. If Command line options Running KannelStarting the gateway After the bearer box, you can start the WAP box Using the gateway Set debug-places for ’debug’ level output Kannel statuses Http administration Bring down the gateway, by setting state to Space. Password requiredShutdown a single Smsc link. Password No other chance to resume normal operation Wapbox conﬁguration Setting up a WAP gatewayWAP gateway conﬁguration Default gives you 10 mappings Map-url setting. Thus,Adds a single mapping for Left side URL to the given Running WAP gateway Checking whether the WAP gateway is alive Setting up a SMS Gateway Required componentsSMS gateway conﬁguration SMS centers Problems, so avoid it and any Specify the used SMS-serviceSee below for a complete list An optional name or id for Which are accepted to be sent Through this SMSC. MultipleEntries are separated with Semicolon ’’. For example Nokia Cimd 1.37 Setting up a SMS Gateway Value. Set it to 0 to disable thisFeature Machine that runs the Smsc All messages sent from Kannel. If Kannel is asked toSend a message, it will remove This preﬁx from the sender Connecting over a modem to an Defaults to send. All outgoingService Or hostname Keepalive command will be Feature. Requires username orMore than this time. Defaults to If set, only connections from Disconnect/reconnect, default When this parameter is unset orDefaults to the maximum Error ocur Smpp Transceiver mode Use value 0 to disable this I/OPassword matching Attempt to use a Default if not set is Not deﬁned the default deviceThat no more than 10 default Change the interface version VariableValue Sema Group SMS2000 OIS 4.0 SM/ASI for CriticalPath InVoke SMS Center GSM modem Modem Type Modems Default value 0 means to try to Nokia 6210, 7110, 8210 testedProbably other Nokia phones Too Using the ’message-storage’ To work with this setting areFor this many seconds. If Optional phone number String to use when trying to Optional. Defaults to falseBefore ﬁrst command Command, enable this Fake Smsc HTTP-based relay and content gateways Using multiple SMS centers Feature checklistFeaturecimd Sema Ois At2 Http Smsc driver internal features Can set Validity Can set Deferred Can set PID Can set RPICan send 8 bits Correctly send GSM alphabet Can send octet data without UDH Symbol Meaning Smsbox conﬁguration Smsbox Group Variables Optional smsbox instanceAn smsbox connected to an Bearerbox for the purpose Sendsms-charsstring Global-sender Typical ’smsbox’ group could be something like this Non-zero value Smsbox routing inside bearerbox Deﬁnes for which smsboxInstance the routing rules do Apply SMS-service conﬁgurations Services are identiﬁed by Word Message contains If the service has aliases, theyURL corresponds to one Word in the SMS message You use this sms-service type Use these kind of services isChecked using white/black-list Service. b Multiple entries are Service. This may be used to Allowed to this serviceAllow only inbound SMS to Certain shortcut numbers to be Content-Type for reply, it is Used for url type services,If client does not set Normally Black-list service is deﬁned See notes of phone numberFormat from numhash.h header ﬁle How sms-service interprets the Http response Extended headers SMSPush equivalent Kannel Header Kannel Post XML PostParameter escape code Kannel Header Equivalent Hex format Setting up a SMS Gateway SendSMS-user conﬁgurations Some sample ’sendsms-user’ groups External delivery report DLR storage Internal DLR storageMySQL DLR storage LibSDB DLR storage DLR database ﬁeld conﬁguration Sample ’dlr-db’ group VariableTable ﬁeld that is used for the timestamp data MySQL connection conﬁguration Over-The-Air conﬁgurations Ota-setting. Any string is For your WAP services, i.eDescription of the service Defaults to data Setting up more complex services A ’sendsms-user’ to use with it. With concatenation enabled14. OTA Bookmark Group Variables Ota-bookmark. Any string is Redirected replies Setting up operator speciﬁc servicesSetting up multi-operator Kannel Running SMS gateway Using the Http interface to send SMS messages’Authorization failed’ reply Content can be more than Bits or to UCS2. Defaults toReturned Phone number of the sender Default-smscvariable can Indicator bits in DCS ﬁeld. IfIndicator. The accepted values Indicator, or 5,6,7,8 for Conﬁguration, or 0X per default Indicator RPI value. See EtsiOptional. If given, kannel will Inform SMS Center that it should Using the Http interface to send OTA conﬁguration messages GET method for the OTA Http interface Bookmark document looks like this Name or ID of the ’ota-setting’ Not given the ﬁrst ’ota-setting’When a XML document is Conﬁguration, or ’Authorization Running SMS&WAP gateway Setting up a SMS&WAP gatewaySMS&WAP gateway conﬁguration Setting up Push Proxy Gateway Conﬁguring ppg core group, for push initiator PI interfacePPG core group conﬁguration variables Mandatory value. Tells that we Conﬁguring PPG user group variables String Password for this user Wap-push-userString An user String Username for this user Finishing ppg conﬁguration An example using Http Smsc Setting up Push Proxy GatewayYou can, of course, use more complex command line options Running a push proxy gateway Default network and bearer used by push proxy gateway Using SSL for Http Using SSL client support Using SSL for Http Using SSL server support for the sendsms Http interfaceUsing SSL server support for PPG Https interface Delivery Reports Getting help and reporting bugs Appendix A. Using the fake WAP sender Running Kannel with fakesmsc connections Appendix B. Using the fake SMS centerSetting up fakesmsc Fake messages Fakesmsc command line optionsSwitch Value Description Send a maximum of max Creating push content and control document for testing Starting necessary programs Table C-1. Testppg’s command line options Use content qualiﬁer stringInstead of default si service Default any. Application 101 Using Nokia Toolkit as a part of a developing environmentTesting PAP protocol over Https Directive Value Description String User’s password 103 ﬁlename Document Mandatory value. PPG serviceString User’s username Mandatory value. PPG service Appendix D. Setting up a dial-up line Analog modemAdd the following lines to /etc/ppp/options.server 104 This section needs to be written 105 Isdn terminalConﬁgure your phone this example is for Nokia Log rotation Bearerbox Access LogAppendix E. Log ﬁles Appendix E. Log ﬁles 107 Coding GlossaryMClass Bibliography RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1 Society 109