Nokia WAP and SMS gateway manual Used in modemtype variable, From AT2, Name of this modem, Siemens

Page 54

Chapter 5. Setting up a SMS Gateway

Modem definitions are now multiple groups present in kannel.conf, either directly or, for example, by including the example modems.conf. (See Inclusion of configuration files)

Variable

Value

Description

group

modems

This is a mandatory variable

 

 

This is the the id that should be

 

 

used in modemtype variable

id

string

from AT2

 

 

The name of this modem

name

string

configuration. Used in logs

 

 

String to use when trying to

 

 

detect the modem. See

detect-string

string

detect-string2

 

 

Second string to use to detect the

 

 

modem. For example, if the

 

 

modem replies with "SIEMENS

 

 

MODEM M20",

 

 

detect-string could be

 

 

"SIEMENS" and

detect-string2

string

detect-strign2 "M20"

 

 

Optional initialization string.

 

 

Defaults to

init-string

string

"AT+CNMI=1,2,0,1,0"

 

 

Serial port hint speed to use.

 

 

Optional. Defaults to smsc group

speed

number

speed or autodetect

 

 

Optional AT command to enable

 

 

hardware handshake. Defaults to

enable-hwhs

string

"AT+IFC=2,2"

 

 

Optional. Defaults to false.

 

 

Some modems needs to sleep

 

 

after opening the serial port and

need-sleep

boolean

before first command

 

 

Optional. Defaults to false. If the

 

 

modem doesn’t support the PIN

no-pin

boolean

command, enable this

 

 

Optional. Defaults to false. If the

 

 

modem doesn’t support setting

 

 

the SMSC directly on the pdu,

 

 

enable this. (Default is to include

 

 

a "00" at the beginning of the

 

 

PDU to say it’s the default smsc,

 

 

and remove the "00" when

no-smsc

boolean

receiving)

47

Page 53 Page 55
Image 54
Page 53 Page 55
Contents Kalle Marjola Open Source WAP and SMS gatewayLars Wirzenius Andreas FinkBruno 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 List of Tables ViiIntroduction Overview of WAPOverview of WAP Push Overview of SMS Introduction FeaturesRequirements This section needs to be writtenPage 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 Kannel from DEB packages Installing the gatewayInstalling 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 Core configuration Variable Value DescriptionBool Layer. Defaults to no With admin-port, this can beLower network layer. Defaults IP-listseveral addresses, separated withVariableValue IP or ’*’filename Handle them properly. This is String to unify received phoneNumbers, for Smsc routing Receiving SMS messages fromSMS service requests to Using this variable, no SMSfilename Down violently Enable the use of an Http Only, i.e. for the administrationKannel is willing to trust when Type Default this is set to ’internal’When Kannel message queues Working as a Https client. IfStarting the gateway Command line optionsRunning Kannel After the bearer box, you can start the WAP boxUsing the gateway Set debug-places for ’debug’ level output Kannel statusesHttp administration Shutdown a single Smsc link. Password Bring down the gateway, by setting state toSpace. Password required No other chance to resume normal operationSetting up a WAP gateway WAP gateway configurationWapbox configuration Adds a single mapping for Default gives you 10 mappingsMap-url setting. Thus, Left side URL to the givenRunning WAP gateway Checking whether the WAP gateway is aliveSMS gateway configuration Setting up a SMS GatewayRequired components SMS centersSee below for a complete list Problems, so avoid it and anySpecify the used SMS-service An optional name or id forEntries are separated with Which are accepted to be sentThrough this SMSC. Multiple Semicolon ’’. For exampleNokia Cimd 1.37 Feature Setting up a SMS GatewayValue. Set it to 0 to disable this Machine that runs the SmscSend a message, it will remove All messages sent fromKannel. If Kannel is asked to This prefix from the senderService Connecting over a modem to anDefaults to send. All outgoing Or hostnameMore than this time. Defaults to Keepalive command will beFeature. Requires username or If set, only connections fromDefaults to the maximum Disconnect/reconnect, defaultWhen this parameter is unset or Error ocurSmpp Password matching Transceiver modeUse value 0 to disable this I/O Attempt to use aThat no more than 10 default Default if not set isNot defined the default device Change the interface versionVariableValue Sema Group SMS2000 OIS 4.0 SM/ASI for CriticalPath InVoke SMS Center GSM modem Modem Type Modems Probably other Nokia phones Default value 0 means to try toNokia 6210, 7110, 8210 tested TooFor this many seconds. If Using the ’message-storage’To work with this setting are Optional phone numberBefore first command String to use when trying toOptional. Defaults to false Command, enable thisFake Smsc HTTP-based relay and content gateways Featurecimd Using multiple SMS centersFeature checklist Sema Ois At2 HttpCan send 8 bits Correctly send GSM alphabet Smsc driver internal featuresCan set Validity Can set Deferred Can set PID Can set RPI Can send octet data without UDHSymbol Meaning Smsbox configurationAn smsbox connected to an Smsbox Group VariablesOptional smsbox instance Bearerbox for the purposeSendsms-charsstring Global-sender Typical ’smsbox’ group could be something like this Non-zero valueInstance the routing rules do Smsbox routing inside bearerboxDefines for which smsbox ApplySMS-service configurations URL corresponds to one Services are identified byWord Message contains If the service has aliases, they Word in the SMS messageChecked using white/black-list You use this sms-service typeUse these kind of services is Service. b Multiple entries areAllow only inbound SMS to Service. This may be used toAllowed to this service Certain shortcut numbers to beIf client does not set Content-Type for reply, it isUsed for url type services, NormallyFormat from numhash.h header Black-list service is definedSee notes of phone number fileHow sms-service interprets the Http response Extended headers SMSPush equivalent Kannel HeaderParameter escape code Kannel Header Equivalent Kannel PostXML Post Hex formatSetting up a SMS Gateway SendSMS-user configurations Some sample ’sendsms-user’ groups MySQL DLR storage External delivery report DLR storageInternal DLR storage LibSDB DLR storageDLR database field configuration Variable Table field that is used for the timestamp dataSample ’dlr-db’ group MySQL connection configuration Over-The-Air configurationsDescription of the service Ota-setting. Any string isFor your WAP services, i.e Defaults to data14. OTA Bookmark Group Variables Setting up more complex servicesA ’sendsms-user’ to use with it. With concatenation enabled Ota-bookmark. Any string isSetting up operator specific services Setting up multi-operator KannelRedirected replies Using the Http interface to send SMS messages ’Authorization failed’ replyRunning SMS gateway Returned Content can be more thanBits or to UCS2. Defaults to Phone number of the senderIndicator. The accepted values Default-smscvariable canIndicator bits in DCS field. If Indicator, or 5,6,7,8 forOptional. If given, kannel will Configuration, or 0X per defaultIndicator RPI value. See Etsi 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 When a XML document is Name or ID of the ’ota-setting’Not given the first ’ota-setting’ Configuration, or ’AuthorizationSetting up a SMS&WAP gateway SMS&WAP gateway configurationRunning SMS&WAP gateway PPG core group configuration variables Setting up Push Proxy GatewayConfiguring ppg core group, for push initiator PI interface Mandatory value. Tells that weConfiguring PPG user group variables String An user String Password for this userWap-push-user String Username for this userFinishing ppg configuration You can, of course, use more complex command line options An example using Http SmscSetting up Push Proxy Gateway Running a push proxy gatewayDefault network and bearer used by push proxy gateway Using SSL for Http Using SSL client supportUsing 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 Instead of default si service Table C-1. Testppg’s command line optionsUse content qualifier string Default any. ApplicationUsing 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 Add the following lines to /etc/ppp/options.server Appendix D. Setting up a dial-up lineAnalog modem 104Isdn terminal Configure your phone this example is for NokiaThis section needs to be written 105 Bearerbox Access Log Appendix E. Log filesLog rotation Appendix E. Log files 107Glossary MClassCoding 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