Nokia WAP and SMS gateway manual Fake Smsc

Page 55

 

 

Chapter 5. Setting up a SMS Gateway

Variable

Value

Description

 

 

Optional, defaults to 100

 

 

miliseconds. The sleep time after

sendline-sleep

number (miliseconds)

sending a AT command.

 

 

Optional, defaults to "AT". If

 

 

keepalive is activated in AT2

 

 

group, this is the command to be

 

 

sent. If your modem supports it,

 

 

for example, use

 

 

"AT+CBC;+CSQ", and see in

 

 

logs the reply "+CBC: 0,64"

 

 

(0=On batery, 64% full) and

 

 

"+CSQ: 14,99" (0-31, 0-7: signal

 

 

strenght and channel bit error

 

 

rate; 99 for unknown). See 3GPP

keepalive-cmd

string

27007.

 

 

Message storage memory type

 

 

to enable for "SIM buffering".

 

 

Possible values are: "SM" - SIM

 

 

card memory or "ME" - Mobile

 

 

equipment memory (may not be

 

 

suppoerted by your modem).

 

 

check your modem’s manual for

 

 

more types. By default, if the

 

 

option is not set, no message

 

 

storage command will be sent to

 

 

the modem and the modem’s

 

 

default message storage will be

message-storage

string

used (usually "SM").

 

 

Optional, defaults to false. If

 

 

enabled, kannel would send an

 

 

AT+CMMS=2 if it have more

 

 

than one message on queue and

 

 

hopefully will be quickier

enable-mms

boolean

sending the messages.

A note about delivery reports and GSM modems: while it is possible (and supported) to receive delivery reports on GSM modems, it may not work for you. if you encounter problems, check that your modem’s init string (if not the default) is set to correctly allow the modem to send delivery reports using unsolicted notification (check your modem’s manual). If the init-string is not set as si, some modems will store delivery reports to SIM memory, to get at which you will need to enable sim-buffering. finally your GSM network provider may not support delivery reports to mobile units.

Fake SMSC

Fake SMSC is a simple protocol to test out Kannel. It is not a real SMS center, and cannot be used to send or receive SMS messages from real phones. So, it is ONLY used for testing purposes.

48

Page 54 Page 56
Image 55
Page 54 Page 56
Contents Andreas Fink Open Source WAP and SMS gatewayLars Wirzenius Kalle MarjolaStipe 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 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 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 Configuring the gateway Using 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 noIP or ’*’ VariableValuefilename 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. PasswordWAP gateway configuration Setting up a WAP gatewayWapbox 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 Table field that is used for the timestamp data VariableSample ’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 multi-operator Kannel Setting up operator specific 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 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 isSMS&WAP gateway configuration Setting up a SMS&WAP gatewayRunning 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 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 qualifier string Instead of default si serviceTesting 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 filename 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.serverConfigure your phone this example is for Nokia Isdn terminalThis section needs to be written 105 Appendix E. Log files Bearerbox Access LogLog rotation 107 Appendix E. Log filesMClass 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.
Top Page Image Contents