Nokia WAP and SMS gateway manual If client does not set, Content-Type for reply, it is, Normally

Page 68

 

 

Chapter 5. Setting up a SMS Gateway

Variable

Value

Description

 

 

If client does not set

 

 

Content-Type for reply, it is

 

 

normally

 

 

application/octet-stream which is

 

 

then handled as data in kannel.

 

 

This can be forced to be

 

 

plain/text to allow backward

 

 

compatibility, when data was not

assume-plain-text

bool

expected.

 

 

Long messages can be sent as

 

 

independent SMS messages with

 

 

concatenation = false or

 

 

as concatenated messages with

 

 

concatenation = true.

 

 

Concatenated messages are

 

 

reassembled into one long

 

 

message by the receiving device.

concatenation

bool

 

 

 

Allowed characters to split the

 

 

message into several messages.

 

 

So, with "#!" the message is split

 

 

from last ’#’ or ’!’, which is

split-chars

string

included in the previous part.

 

 

If the message is split into

 

 

several ones, this string is

 

 

appended to each message except

split-suffix

string

the last one.

 

 

Normally, Kannel sends a

 

 

warning to the user if there was

 

 

an empty reply from the service

 

 

provider. If omit-emptyis set to

 

 

’true’, Kannel will send nothing

omit-empty

bool

at all in such a case.

 

 

If specified, this string is

 

 

automatically added to each

 

 

SMS sent with this service. If the

 

 

message is split, it is added to

header

string

each part.

 

 

As header, but not inserted into

footer

string

head but appended to end.

 

 

Stuff in answer that is cut away,

 

 

only things between prefix and

 

string

suffix is left. Not case sensitive.

prefix

Matches the first prefix and then

 

 

the first suffix. These are only

 

 

used for url type services, and

 

 

only if both are specified.

61

Page 67 Page 69
Image 68
Page 67 Page 69
Contents Open Source WAP and SMS gateway Lars WirzeniusKalle 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 List of Tables ViiIntroduction Overview of WAPOverview of WAP Push Overview of SMS Features RequirementsIntroduction 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 Kannel from DEB packages Installing the gatewayIf 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 Core configuration Variable Value DescriptionWith admin-port, this can be Lower network layer. DefaultsBool Layer. Defaults to no IP-listseveral addresses, separated withfilename VariableValueIP or ’*’ String to unify received phone Numbers, for Smsc routingHandle them properly. This is Receiving SMS messages fromUsing this variable, no SMS filename Down violently Enable the use of an HttpSMS service requests to Only, i.e. for the administrationType Default this is set to ’internal’ When Kannel message queuesKannel is willing to trust when Working as a Https client. IfCommand line options Running KannelStarting the gateway After the bearer box, you can start the WAP boxUsing the gateway Set debug-places for ’debug’ level output Kannel statusesHttp administration Bring down the gateway, by setting state to Space. Password requiredShutdown a single Smsc link. Password No other chance to resume normal operationWapbox configuration Setting up a WAP gatewayWAP gateway configuration Default gives you 10 mappings Map-url setting. Thus,Adds a single mapping for Left side URL to the givenRunning WAP gateway Checking whether the WAP gateway is aliveSetting up a SMS Gateway Required componentsSMS gateway configuration SMS centersProblems, so avoid it and any Specify the used SMS-serviceSee below for a complete list An optional name or id forWhich are accepted to be sent Through this SMSC. MultipleEntries are separated with Semicolon ’’. For exampleNokia Cimd 1.37 Setting up a SMS Gateway Value. Set it to 0 to disable thisFeature Machine that runs the SmscAll messages sent from Kannel. If Kannel is asked toSend a message, it will remove This prefix from the senderConnecting over a modem to an Defaults to send. All outgoingService Or hostnameKeepalive command will be Feature. Requires username orMore than this time. Defaults to If set, only connections fromDisconnect/reconnect, default When this parameter is unset orDefaults to the maximum Error ocurSmpp Transceiver mode Use value 0 to disable this I/OPassword matching Attempt to use aDefault if not set is Not defined the default deviceThat 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 Default value 0 means to try to Nokia 6210, 7110, 8210 testedProbably other Nokia phones TooUsing the ’message-storage’ To work with this setting areFor this many seconds. If Optional phone numberString to use when trying to Optional. Defaults to falseBefore first command Command, enable thisFake Smsc HTTP-based relay and content gateways Using multiple SMS centers Feature checklistFeaturecimd Sema Ois At2 HttpSmsc driver internal features Can set Validity Can set Deferred Can set PID Can set RPICan send 8 bits Correctly send GSM alphabet Can send octet data without UDHSymbol Meaning Smsbox configurationSmsbox Group Variables Optional smsbox instanceAn smsbox connected to an Bearerbox for the purposeSendsms-charsstring Global-sender Typical ’smsbox’ group could be something like this Non-zero valueSmsbox routing inside bearerbox Defines for which smsboxInstance the routing rules do ApplySMS-service configurations Services are identified by Word Message contains If the service has aliases, theyURL corresponds to one Word in the SMS messageYou use this sms-service type Use these kind of services isChecked using white/black-list Service. b Multiple entries areService. This may be used to Allowed to this serviceAllow only inbound SMS to Certain shortcut numbers to beContent-Type for reply, it is Used for url type services,If client does not set NormallyBlack-list service is defined See notes of phone numberFormat from numhash.h header fileHow sms-service interprets the Http response Extended headers SMSPush equivalent Kannel HeaderKannel Post XML PostParameter escape code Kannel Header Equivalent Hex formatSetting up a SMS Gateway SendSMS-user configurations Some sample ’sendsms-user’ groups External delivery report DLR storage Internal DLR storageMySQL DLR storage LibSDB DLR storageDLR database field configuration Sample ’dlr-db’ group VariableTable field that is used for the timestamp data MySQL connection configuration Over-The-Air configurationsOta-setting. Any string is For your WAP services, i.eDescription of the service Defaults to dataSetting up more complex services A ’sendsms-user’ to use with it. With concatenation enabled14. 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 Content can be more than Bits or to UCS2. Defaults toReturned Phone number of the senderDefault-smscvariable can Indicator bits in DCS field. IfIndicator. The accepted values Indicator, or 5,6,7,8 forConfiguration, or 0X per default Indicator RPI value. See EtsiOptional. If given, kannel will Inform SMS Center that it shouldUsing the Http interface to send OTA configuration messages GET method for the OTA Http interfaceBookmark document looks like this Name or ID of the ’ota-setting’ Not given the first ’ota-setting’When a XML document is Configuration, or ’AuthorizationRunning SMS&WAP gateway Setting up a SMS&WAP gatewaySMS&WAP gateway configuration Setting up Push Proxy Gateway Configuring ppg core group, for push initiator PI interfacePPG core group configuration variables Mandatory value. Tells that weConfiguring PPG user group variables String Password for this user Wap-push-userString An user String Username for this userFinishing ppg configuration An example using Http Smsc Setting up Push Proxy GatewayYou can, of course, use more complex command line options Running a push proxy gatewayDefault network and bearer used by push proxy gateway Using SSL for Http Using SSL client supportUsing 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 Table C-1. Testppg’s command line options Use content qualifier stringInstead 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 Appendix D. Setting up a dial-up line Analog modemAdd 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 Appendix E. Log files 107Coding GlossaryMClass Bibliography RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1 Society 109

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