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
Page 99
Image 99
Nokia WAP and SMS gateway manual Delivery Reports
Page 98 Page 100

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