Nokia WAP and SMS gateway manual Kannel statuses

Page 29

--verbosity <level>

-D <places>

--debug <places>

-F <file-name>

--logfile <file-name>

-V <level>

--fileverbosity <level>

-S

--suspended

-I

--isolated

-H

--tryhttp

Chapter 3. Using the gateway

Set debug-places for ’debug’ level output.

Log to file named file-name, too. Does not overrun or affect any logfile defined in configuration file.

Set verbosity level for that extra logfile (default 0, which means ’debug’). Does not affect verbosity level of the logfile defined in configuration file, not verbosity level of the stdout output.

Start the system initially at SUSPENDED state (see below, bearerbox only)

Start the system initially at ISOLATED state (see below, bearerbox only)

Only try to open HTTP sendsms interface; if it fails, only warn about that, do not exit. (smsbox only)

Kannel statuses

In Kannel, there are four states for the program (which currently directly only apply to bearerbox):

a. Running. The gateway accepts, proceeds and relies messages normally. This is the default state for the bearerbox.

b. Suspended. The gateway does not accept any new messages from SMS centers nor from UDP ports. Neither does it accept new sms and wapbox connections nor sends any messages already in the system onward.

c. Isolated. In this state, the gateway does not accept any messages from external message providers, which means SMS Centers and UDP ports. It still processes any messages in the system and can accept new messages from sendsms interface in smsbox.

d. Full. Gateway does not accept any messages from SMS centers, because maximum-queue-length is achieved.

e. Shutdown. When the gateway is brought down, it does not accept any new messages from SMS centers and UDP ports, but processes all systems already in the system. As soon as any queues are emptied, the system exits

22

Page 28 Page 30
Image 29
Page 28 Page 30
Contents Lars Wirzenius Open Source WAP and SMS gatewayKalle Marjola Andreas FinkAarno 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 Vii List of TablesOverview of WAP IntroductionOverview of WAP Push Overview of SMS Requirements FeaturesIntroduction 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 the gateway Installing Kannel from DEB packagesIf you don’t want Kannel to run as a daemon, run Installing the gateway Install or upgrade the DEB packageRemove the package completely Page Configuration file syntax Using the gatewayConfiguring the gateway Inclusion of configuration files Variable Value Description Core configurationLower network layer. Defaults With admin-port, this can beBool Layer. Defaults to no IP-listseveral addresses, separated withfilename VariableValueIP or ’*’ Numbers, for Smsc routing String to unify received phoneHandle them properly. This is Receiving SMS messages fromfilename 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 operationWapbox configuration Setting up a WAP gatewayWAP gateway configuration 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 configuration 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 prefix 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 defined 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 first 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 configuration 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 thisDefines for which smsbox Smsbox routing inside bearerboxInstance the routing rules do ApplySMS-service configurations Word Message contains If the service has aliases, they Services are identified 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 definedFormat from numhash.h header fileHow 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 configurations Some sample ’sendsms-user’ groups Internal DLR storage External delivery report DLR storageMySQL DLR storage LibSDB DLR storageDLR database field configuration Sample ’dlr-db’ group VariableTable field that is used for the timestamp data Over-The-Air configurations MySQL connection configurationFor 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 isRedirected replies Setting up operator specific servicesSetting up multi-operator Kannel Running SMS gateway Using the Http interface to send SMS messages’Authorization failed’ reply Bits or to UCS2. Defaults to Content can be more thanReturned Phone number of the senderIndicator bits in DCS field. If Default-smscvariable canIndicator. The accepted values Indicator, or 5,6,7,8 forIndicator RPI value. See Etsi Configuration, 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 configuration messagesBookmark document looks like this Not given the first ’ota-setting’ Name or ID of the ’ota-setting’When a XML document is Configuration, or ’AuthorizationRunning SMS&WAP gateway Setting up a SMS&WAP gatewaySMS&WAP gateway configuration Configuring ppg core group, for push initiator PI interface Setting up Push Proxy GatewayPPG core group configuration variables Mandatory value. Tells that weConfiguring PPG user group variables Wap-push-user String Password for this userString An user String Username for this userFinishing ppg configuration 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 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 Use content qualifier string Table C-1. Testppg’s command line optionsInstead of default si service Default any. Application101 Using Nokia Toolkit as a part of a developing environmentTesting PAP protocol over Https Directive Value Description String User’s password 103 filename Document Mandatory value. PPG serviceString User’s username Mandatory value. PPG service Analog modem Appendix D. Setting up a dial-up lineAdd the following lines to /etc/ppp/options.server 104This section needs to be written 105 Isdn terminalConfigure your phone this example is for Nokia Log rotation Bearerbox Access LogAppendix E. Log files 107 Appendix E. Log filesCoding GlossaryMClass 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