Wait, it works. Thank you!
On Tue, Jan 23, 2018 at 5:31 PM, Kasper Nielsen wrote:
> And making the XML smaller does work - and the SMS is sent correctly. But
> if the XML is bigger than 1 SMS, then it fails.
> Even with HTTP POST.
>
> On Tue, Jan 23, 2018 at 5:30 PM, Kasper Nielsen
> wrote:
>
>
And making the XML smaller does work - and the SMS is sent correctly. But
if the XML is bigger than 1 SMS, then it fails.
Even with HTTP POST.
On Tue, Jan 23, 2018 at 5:30 PM, Kasper Nielsen wrote:
> Thank you so much. Now it actually ships the SMS, but it still seems the
> SMS is not divided co
Thank you so much. Now it actually ships the SMS, but it still seems the
SMS is not divided correctly into multiple SMS.
SMPP trace show:
313 53.103466911 1202344522 → 125677753 WSP 262 WSP Push (0x06) (WBXML
1.3, Public ID: "-//WAPFORUM//DTD PROV 1.0//EN (Provisioning
1.0)")[Malformed Packet
Hi Kasper.
The content type should not be set to text/xml. It depends on the type of
OTA that you want to send:
text/vnd.wap.connectivity-xml
application/x-wap-prov.browser-bookmarks
application/x-wap-prov.browser-settings
The documentation is a little lacking, so have a look in gw/smsbox.c
Jaco
Tried
request({
url: 'http://127.0.0.1:13002/cgi-bin/sendota',
method: 'POST',
headers : {
'content-type': 'text/xml',
'X-Kannel-Username': 'foo',
'X-Kannel-Password': 'bar',
'X-Kannel-To': '1324422133',
'X-Kannel-From': '12023455750'
},
Just testing if this mailinglist is active, has anyone received my
questions?
On Tue, Jan 23, 2018 at 2:01 PM, Kasper Nielsen wrote:
> Seems - after a lot of Googling - that the Kannel SMS gateway actually
> doesn't support HTTP POST for sending SMSes, which is a limit to the size
> of SMSes bei
Seems - after a lot of Googling - that the Kannel SMS gateway actually
doesn't support HTTP POST for sending SMSes, which is a limit to the size
of SMSes being sent :(
On Tue, Jan 23, 2018 at 1:35 PM, Kasper Nielsen wrote:
> Looked through the contrib-examples and all examples actually uses the
Looked through the contrib-examples and all examples actually uses the HTTP
GET method to send SMS, which may fail on large SMSes.
On Tue, Jan 23, 2018 at 12:19 PM, Kasper Nielsen
wrote:
> ...and tried old school XML:
>
> var xml = ' \
> \
> \
> \
> 11021034235\
> 11076034723\
> He
...and tried old school XML:
var xml = ' \
\
\
\
11021034235\
11076034723\
Hello\
\
foo\
foo\
bar\
bar\
\
\
\
';
var options = {
method: 'POST',
uri: 'http://127.0.0.1:13002/cgi-bin/sendsms',
body: xml,
headers: {'content-type': 'text/xml'}
Also able to get: body: 'Invalid content-type' } }
But the content-type is correct http form:
application/x-www-form-urlencoded.
On Tue, Jan 23, 2018 at 11:57 AM, Kasper Nielsen
wrote:
> ...and the docs doesn't seem to tell anything about this.
>
> On Tue, Jan 23, 2018 at 11:36 AM, Kasper N
...and the docs doesn't seem to tell anything about this.
On Tue, Jan 23, 2018 at 11:36 AM, Kasper Nielsen
wrote:
> This is my NodeJS (request-promise) for sending SMS via HTTP GET:
>
> var options = {
> method: 'GET',
> uri: 'http://127.0.0.1:13002/cgi-bin/sendsms',
> qs: {
>
This is my NodeJS (request-promise) for sending SMS via HTTP GET:
var options = {
method: 'GET',
uri: 'http://127.0.0.1:13002/cgi-bin/sendsms',
qs: {
username: 'foo',
password: 'bar',
to: '127883327304',
from: '12488331359',
text: 'Hi
}
};
T
12 matches
Mail list logo
