Stipe Tolj wrote:
Oded Arbel wrote:
Speaking of sendsms' HTTP interface - I've noticed that sendsms doesn't
honor the 'Connection: close' header and always use keep-alive. can that be
fixed, please ?
I had a look in gwlib/http.c:899 where the following is inside
handle_transaction():
Oded Arbel wrote:
Speaking of sendsms' HTTP interface - I've noticed that sendsms doesn't
honor the 'Connection: close' header and always use keep-alive. can that be
fixed, please ?
I had a look in gwlib/http.c:899 where the following is inside
handle_transaction():
[...]
h =
for the sendsms HTTP interface?
Any if yes, which smsc?
I'm currently figuring out in the code where this is supported for the
GET method, but I can't find it. Any I remember that the user's guide
that's that multiple receivers are allowed seperated with a blank in
the to= argument.
Stipe
Stefan Cars wrote:
What do you meanwith multi-cast GET ?
the user guide states at
http://www.kannel.3glab.org/download/kannel-userguide-snapshot/userguide.html#AEN2521
that the to= argument may contain multiple receivers, but I can't
see any implementation of this is the code?!
I'm just
Yes, i'm using this. IT works with CIMD2 at least.
-
Stefan Cars
CTO
Globalwire Communications
Phone: +46 18 10 79 50
Mobile(UK): +44 788 061 36 69
Mobile(SE): +46 708 44 36 00
On Wed, 2 Jan 2002, Stipe Tolj wrote:
Stefan Cars wrote:
What do you meanwith multi-cast GET ?
Yes, i'm using this. IT works with CIMD2 at least.
so where is the splitting and looping of the single receiver number of
the to GET variable implemented? In smsc_cimd2.c?
Is the code within the current cvs tree or have you an own version?
Stipe
[EMAIL PROTECTED]
