| Sending configuration messages (OTA and OMA Client Provisioning) to... |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through March 09, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Mehmet Ali Meram New member Username: Meram Post Number: 1 Registered: 01-2004 |
Hi there, I develop a simple application to send configuration messages to S60 phones, e.g Siemens Sx1, Nokia 6220, 3650. I look into Smart messaging and OMA Client provisioning specification. However, I rather preferred NowSMS's WEB interface and log files to obtain binary representation of these (configuration) messages instead of being puzzled by mind-boggling specs. My questions are 1) As you guess I need only binary data dumped to the log file, not really sending it out. Can you give me usecases serving that aim? 2) I simply tried concatenating UDH=... and Data=... section to compose my SMS body. It's recognized as config msg by phone but it fails to parse and process. HOwever, it succeeds when being sent by NowSMS directly thru GSM modem. I use UCS2 as encoding scheme. Shall I employ 8-bit instead? Thanks in advance Best Wishes | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1943 Registered: 10-2002 |
Hi, We have some customers that use similar types of approaches to what you describe. Parsing the log file is a brute force approach ... what works better is if you can write an HTTP script on another web server. Configure that script as an HTTP SMSC in NowSMS ... NowSMS will then call your script when it has a message to be sent out, and your script can then interface into the SMS system that you are using. (Usually, when we have customers using this type of technique they are in phone test labs.) Without knowing about the SMS interface in your system, I can only give some very generic suggestions. Do not use UCS2 as the encoding scheme. 8-bit encoding scheme (DCS=0x04) will generally work ok. You also need to be able to set the user data header indicator (UDHI) flag in the outbound SMS message. This tells the receiving client that the message body includes a UDH. -bn | |||
| Mehmet Ali Meram New member Username: Meram Post Number: 2 Registered: 01-2004 |
Hi Bryce, The solution you offer is not clear to me. Where can i tell NOWsms to use my script? Does it have to be a http cgi script at all? Or can be simply a perl script parsing? If the answer to the former is yes where in NOwSms gateway menu it can be configured? S60 platform has SMS APIs accessing each and every field of TPDU and UDH . Data can also be inserted directly into message buffer, hence composing a complete msg is not a problem. Thanks in advance Regards | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1952 Registered: 10-2002 |
On the "SMSC" page of the configuration dialog, add an "SMSC Connection type" of "HTTP over TCP/IP". Every time NowSMS has a message to send out, it will make an HTTP request based on the parameters that you define here, passing the message details as parameters in the HTTP request. So depending on your setup, if you need to automate things, you could configure NowSMS to make an HTTP request to a script on another web server, and have that web server make the appropriate API call directly. We do expect to initiate the request over HTTP. So if you wanted to use Perl, you'd have to have a web server setup (potentially on the same PC, just listening on a different HTTP port number). NowSMS would generate an HTTP request to call the Perl script. The following page explains the parameters that you can configure on the NowSMS side for this type of link: http://www.nowsms.com/documentation/ProductDocumentation/configuring_smsc_connec tions/HTTP_SMSC.htm It may or may not be appropriate for your setup. But we have found that this can provide some flexibility in allowing NowSMS to interface into some different SMS systems. -bn | |||
