Nokia manual Open Source WAP and SMS gateway, Lars Wirzenius, Kalle Marjola, Andreas Fink

Page 1

Kannel 1.3.1 User’s Guide

Open Source WAP and SMS gateway

Lars Wirzenius

Gateway architect

Wapit Ltd

liw@wapit.com

http://www.wapit.com

http://www.kannel.org

Kalle Marjola

Manager

Wapit Ltd

rpr@wapit.com

http://www.wapit.com

http://www.kannel.org

Andreas Fink

Chairman & CTO

Global Networks Inc.

Image 1

Contents Lars Wirzenius Open Source WAP and SMS gatewayKalle Marjola Andreas FinkStipe 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 TablesOverview of WAP IntroductionOverview of WAP Push Overview of SMS Requirements FeaturesIntroduction This section needs to be writtenPage 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 packagesRemove 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ﬁgurationLower network layer. Defaults With admin-port, this can beBool Layer. Defaults to no IP-listseveral addresses, separated withIP or ’*’ VariableValueﬁlename Numbers, for Smsc routing String to unify received phoneHandle them properly. This is Receiving SMS messages fromﬁlename Down violently Enable the use of an Http Using this variable, no SMSSMS service requests to Only, i.e. for the administrationWhen Kannel message queues Type Default this is set to ’internal’Kannel is willing to trust when Working as a Https client. IfRunning Kannel Command line optionsStarting the gateway After the bearer box, you can start the WAP boxKannel statuses Using the gateway Set debug-places for ’debug’ level outputHttp administration Space. Password required Bring down the gateway, by setting state toShutdown a single Smsc link. Password No other chance to resume normal operationWAP gateway conﬁguration Setting up a WAP gatewayWapbox conﬁguration Map-url setting. Thus, Default gives you 10 mappingsAdds a single mapping for Left side URL to the givenChecking whether the WAP gateway is alive Running WAP gatewayRequired components Setting up a SMS GatewaySMS gateway conﬁguration SMS centersSpecify the used SMS-service Problems, so avoid it and anySee below for a complete list An optional name or id forThrough this SMSC. Multiple Which are accepted to be sentEntries are separated with Semicolon ’’. For exampleNokia Cimd 1.37 Value. Set it to 0 to disable this Setting up a SMS GatewayFeature Machine that runs the SmscKannel. If Kannel is asked to All messages sent fromSend a message, it will remove This preﬁx from the senderDefaults to send. All outgoing Connecting over a modem to anService Or hostnameFeature. Requires username or Keepalive command will beMore than this time. Defaults to If set, only connections fromWhen this parameter is unset or Disconnect/reconnect, defaultDefaults to the maximum Error ocurSmpp Use value 0 to disable this I/O Transceiver modePassword matching Attempt to use aNot deﬁned the default device Default if not set isThat no more than 10 default Change the interface versionVariableValue Sema Group SMS2000 OIS 4.0 SM/ASI for CriticalPath InVoke SMS Center GSM modem Modem Type Modems Nokia 6210, 7110, 8210 tested Default value 0 means to try toProbably other Nokia phones TooTo work with this setting are Using the ’message-storage’For this many seconds. If Optional phone numberOptional. Defaults to false String to use when trying toBefore ﬁrst command Command, enable thisFake Smsc HTTP-based relay and content gateways Feature checklist Using multiple SMS centersFeaturecimd Sema Ois At2 HttpCan set Validity Can set Deferred Can set PID Can set RPI Smsc driver internal featuresCan send 8 bits Correctly send GSM alphabet Can send octet data without UDHSmsbox conﬁguration Symbol MeaningOptional smsbox instance Smsbox Group VariablesAn smsbox connected to an Bearerbox for the purposeSendsms-charsstring Global-sender Non-zero value Typical ’smsbox’ group could be something like thisDeﬁnes for which smsbox Smsbox routing inside bearerboxInstance the routing rules do ApplySMS-service conﬁgurations Word Message contains If the service has aliases, they Services are identiﬁed byURL corresponds to one Word in the SMS messageUse these kind of services is You use this sms-service typeChecked using white/black-list Service. b Multiple entries areAllowed to this service Service. This may be used toAllow only inbound SMS to Certain shortcut numbers to beUsed for url type services, Content-Type for reply, it isIf client does not set NormallySee notes of phone number Black-list service is deﬁnedFormat from numhash.h header ﬁleHow sms-service interprets the Http response SMSPush equivalent Kannel Header Extended headersXML Post Kannel PostParameter escape code Kannel Header Equivalent Hex formatSetting up a SMS Gateway SendSMS-user conﬁgurations Some sample ’sendsms-user’ groups Internal DLR storage External delivery report DLR storageMySQL DLR storage LibSDB DLR storageDLR 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ﬁgurationFor your WAP services, i.e Ota-setting. Any string isDescription of the service Defaults to dataA ’sendsms-user’ to use with it. With concatenation enabled Setting up more complex services14. OTA Bookmark Group Variables Ota-bookmark. Any string isSetting up multi-operator Kannel Setting up operator speciﬁc servicesRedirected replies ’Authorization failed’ reply Using the Http interface to send SMS messagesRunning SMS gateway Bits or to UCS2. Defaults to Content can be more thanReturned Phone number of the senderIndicator bits in DCS ﬁeld. If Default-smscvariable canIndicator. The accepted values Indicator, or 5,6,7,8 forIndicator RPI value. See Etsi Conﬁguration, or 0X per defaultOptional. If given, kannel will Inform SMS Center that it shouldGET method for the OTA Http interface Using the Http interface to send OTA conﬁguration messagesBookmark document looks like this Not given the ﬁrst ’ota-setting’ Name or ID of the ’ota-setting’When a XML document is Conﬁguration, or ’AuthorizationSMS&WAP gateway conﬁguration Setting up a SMS&WAP gatewayRunning SMS&WAP gateway Conﬁguring ppg core group, for push initiator PI interface Setting up Push Proxy GatewayPPG core group conﬁguration variables Mandatory value. Tells that weConﬁguring PPG user group variables Wap-push-user String Password for this userString An user String Username for this userFinishing ppg conﬁguration Setting up Push Proxy Gateway An example using Http SmscYou can, of course, use more complex command line options Running a push proxy gatewayDefault network and bearer used by push proxy gateway Using SSL client support Using SSL for HttpUsing 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 Use content qualiﬁer string Table C-1. Testppg’s command line optionsInstead of default si service Default any. ApplicationTesting 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 Analog modem Appendix D. Setting up a dial-up lineAdd the following lines to /etc/ppp/options.server 104Conﬁ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 ﬁlesMClass GlossaryCoding RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1 Society 109 Bibliography

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.