Web UI submission - how to change the HTTP method?

Web UI submission - how to change the HTTP method? SearchSearch
Author Message
Pentti Kurppa
New member
Username: Panu

Post Number: 2
Registered: 08-2010
Posted on Friday, August 13, 2010 - 07:22 pm:   

Hi,

my gateway provider requires using the POST method for their HTTP API instead of GET. Is there some way I can configure the web client to produce submissions like this?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2428
Registered: 08-2008
Posted on Friday, August 13, 2010 - 07:28 pm:   

Hi Pentti,

I'm sorry, but unfortunately our experience has been that HTTP POST formats vary too much between providers, and cannot be easily converted into a template format.

If you want to forward the HTTP API specifications for your provider to us, we will evaluate it further. (Send it to nowsms@nowsms.com with "Attention: Des" in the subject line, or post in reply here as an attachment.)

Perhaps your SMS provider also provides an SMPP interface which is more standardised?

--
Des
NowSMS Support
Pentti Kurppa
New member
Username: Panu

Post Number: 3
Registered: 08-2010
Posted on Friday, August 13, 2010 - 07:51 pm:   

Thanks for your reply. SMPP only for large volume customers :-( Provider's specs are here http://bulksms.vsms.net/w/eapi-sms-gateway.htm
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2429
Registered: 08-2008
Posted on Friday, August 13, 2010 - 08:24 pm:   

Try this as the "URL Template Text":

http://bulksms.vsms.net:5567/eapi/submission/send_sms/2/2.0?username=@@UserName@ @&password=@@Password@@&sender=@@Sender@@&msisdn=@@PhoneNumber@@&message=@@Text@ @&allow_concat_text_sms=1

(The bulletin board software will probably insert one or two extra spaces above. DO NOT include any spaces in the URL template.)

Be sure to set the "User Name" and "Password" in the HTTP SMSC configuration.

"Server Type" = "Custom"

"Remove + from recipient phone number" CHECKED

"Send long messages without segmentation" CHECKED

"Use 7-bit binary encoding for long text messages" NOT CHECKED

"Use hex encoding for Unicode messages" CHECKED

"Character Set" = "iso-8859-1"

This configuration should work for text messages.

Enabling support for binary and/or Unicode messages involves some tradeoffs.

I realize that their specifications warn that you should use HTTP POST instead of HTTP GET ... but this should be workable.

--
Des
NowSMS Support