Nokia WAP and SMS gateway manual Delivery Reports

Page 99

Chapter 9. Delivery Reports

This chapter explains how to set up kannel to deliver delivery reports.

Delivery reports are a method to tell your system if the message has arrived on the destination phone. There are different things which can happen to a message on the way to the phone which are:

•Message gets rejected by the SMSC (unknown subscriber, invalid destination number etc).

•Message gets accepted by the SMSC but the phone rejects the message.

•Message gets accepted by the SMSC but the phone is off or out of reach. The message gets buffered.

•Message gets successfully delivered.

When you deliver SMS to Kannel you have to indicate what kind of delivery report messages you would like to receive back from the system. The delivery report types currrently implemented are:

•1: delivery success

•2: delivery failure

•4: message buffered

•8: smsc submit

•16: smsc reject

If you want multiple report types, you simply add the values togeter. For example if you want to get delivery success and/or failure you set the dlrmask value to 1+2. and so on. If you specify dlrmask on the URL you pass on to kannel you also need to specify dlrurl. dlrurlshould contain the URL to which kannel should place a HTTP requests once the delivery report is ready to be delivered back to your system.

An example transaction would work as following.

•1. you send a message using dlrmaks=7 and dlrurl=www.xyz.com/cgi/dlr.php?type=%d

•2. Kannel forwards the message to the SMSC and keeps track of the message

•3. The SMSC can not reach the phone and thus returns a buffered message

•4. Kannel calls http://www.xyz.com/cgi/dlr.php?type=4 to indicate the message being buffered

•5. The phone is switched on and the SMS gets delivered from the SMSC. The SMSC reports this to Kannel

•4. Kannel calls http://www.xyz.com/cgi/dlr.php?type=2 to indicate the final success

Depending on the SMSC type not all type of messages are supported. For example a CIMD SMSC does not support buffered messages. Also some SMSC drivers have not implemented all DLR types.

92

Page 98 Page 100
Image 99
Page 98 Page 100
Contents Andreas Fink Open Source WAP and SMS gatewayLars Wirzenius Kalle MarjolaBruno Rodrigues Stipe ToljAarno 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 This section needs to be written FeaturesRequirements IntroductionPage Installing the gateway Getting the source codeFinding the documentation Compiling the gateway Installing the gateway Using pre-compiled binary packagesInstalling Kannel from RPM packages Removing Kannel Log in as root Remove the RPM package Installing the gateway Installing Kannel from DEB packagesInstalling the gateway Install or upgrade the DEB package Remove the package completelyIf you don’t want Kannel to run as a daemon, run Page Using the gateway Configuring the gatewayConfiguration file syntax Inclusion of configuration files Variable Value Description Core configurationIP-listseveral addresses, separated with With admin-port, this can beLower network layer. Defaults Bool Layer. Defaults to noVariableValue IP or ’*’filename Receiving SMS messages from String to unify received phoneNumbers, for Smsc routing Handle them properly. This isOnly, i.e. for the administration Using this variable, no SMSfilename Down violently Enable the use of an Http SMS service requests toWorking as a Https client. If Type Default this is set to ’internal’When Kannel message queues Kannel is willing to trust whenAfter the bearer box, you can start the WAP box Command line optionsRunning Kannel Starting the gatewayKannel statuses Using the gateway Set debug-places for ’debug’ level outputHttp administration No other chance to resume normal operation Bring down the gateway, by setting state toSpace. Password required Shutdown a single Smsc link. PasswordSetting up a WAP gateway WAP gateway configurationWapbox configuration Left side URL to the given Default gives you 10 mappingsMap-url setting. Thus, Adds a single mapping forChecking whether the WAP gateway is alive Running WAP gatewaySMS centers Setting up a SMS GatewayRequired components SMS gateway configurationAn optional name or id for Problems, so avoid it and anySpecify the used SMS-service See below for a complete listSemicolon ’’. For example Which are accepted to be sentThrough this SMSC. Multiple Entries are separated withNokia Cimd 1.37 Machine that runs the Smsc Setting up a SMS GatewayValue. Set it to 0 to disable this FeatureThis prefix from the sender All messages sent fromKannel. If Kannel is asked to Send a message, it will removeOr hostname Connecting over a modem to anDefaults to send. All outgoing ServiceIf set, only connections from Keepalive command will beFeature. Requires username or More than this time. Defaults toError ocur Disconnect/reconnect, defaultWhen this parameter is unset or Defaults to the maximumSmpp Attempt to use a Transceiver modeUse value 0 to disable this I/O Password matchingChange the interface version Default if not set isNot defined the default device That no more than 10 defaultVariableValue 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 phonesOptional phone number Using the ’message-storage’To work with this setting are For this many seconds. IfCommand, enable this String to use when trying toOptional. Defaults to false Before first commandFake Smsc HTTP-based relay and content gateways Sema Ois At2 Http Using multiple SMS centersFeature checklist FeaturecimdCan 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 alphabetSmsbox configuration Symbol MeaningBearerbox for the purpose Smsbox Group VariablesOptional smsbox instance An smsbox connected to anSendsms-charsstring Global-sender Non-zero value Typical ’smsbox’ group could be something like thisApply Smsbox routing inside bearerboxDefines for which smsbox Instance the routing rules doSMS-service configurations Word in the SMS message Services are identified byWord Message contains If the service has aliases, they URL corresponds to oneService. b Multiple entries are You use this sms-service typeUse these kind of services is Checked using white/black-listCertain shortcut numbers to be Service. This may be used toAllowed to this service Allow only inbound SMS toNormally Content-Type for reply, it isUsed for url type services, If client does not setfile Black-list service is definedSee notes of phone number Format from numhash.h headerHow sms-service interprets the Http response SMSPush equivalent Kannel Header Extended headersHex format Kannel PostXML Post Parameter escape code Kannel Header EquivalentSetting up a SMS Gateway SendSMS-user configurations Some sample ’sendsms-user’ groups LibSDB DLR storage External delivery report DLR storageInternal DLR storage MySQL DLR storageDLR database field configuration Variable Table field that is used for the timestamp dataSample ’dlr-db’ group Over-The-Air configurations MySQL connection configurationDefaults to data Ota-setting. Any string isFor your WAP services, i.e Description of the serviceOta-bookmark. Any string is Setting up more complex servicesA ’sendsms-user’ to use with it. With concatenation enabled 14. OTA Bookmark Group VariablesSetting up operator specific services Setting up multi-operator KannelRedirected replies Using the Http interface to send SMS messages ’Authorization failed’ replyRunning SMS gateway Phone number of the sender Content can be more thanBits or to UCS2. Defaults to ReturnedIndicator, or 5,6,7,8 for Default-smscvariable canIndicator bits in DCS field. If Indicator. The accepted valuesInform SMS Center that it should Configuration, or 0X per defaultIndicator RPI value. See Etsi Optional. If given, kannel willGET method for the OTA Http interface Using the Http interface to send OTA configuration messagesBookmark document looks like this Configuration, or ’Authorization Name or ID of the ’ota-setting’Not given the first ’ota-setting’ When a XML document isSetting up a SMS&WAP gateway SMS&WAP gateway configurationRunning SMS&WAP gateway Mandatory value. Tells that we Setting up Push Proxy GatewayConfiguring ppg core group, for push initiator PI interface PPG core group configuration variablesConfiguring PPG user group variables String Username for this user String Password for this userWap-push-user String An userFinishing ppg configuration Running a push proxy gateway An example using Http SmscSetting up Push Proxy Gateway You can, of course, use more complex command line optionsDefault network and bearer used by push proxy gateway Using SSL client support Using SSL for HttpUsing SSL server support for the sendsms Http interface Using SSL server support for PPG Https interfaceUsing SSL for Http Delivery Reports Getting help and reporting bugs Appendix A. Using the fake WAP sender Appendix B. Using the fake SMS center Setting up fakesmscRunning Kannel with fakesmsc connections Fakesmsc command line options Switch Value DescriptionFake 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 qualifier string Instead of default si serviceUsing Nokia Toolkit as a part of a developing environment Testing PAP protocol over Https101 Directive Value Description filename Document Mandatory value. PPG service String User’s username 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.serverIsdn terminal Configure your phone this example is for NokiaThis section needs to be written 105 Bearerbox Access Log Appendix E. Log filesLog rotation 107 Appendix E. Log filesGlossary MClassCoding 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.
Top Page Image Contents