Thanks Jyoti, I will give it a try.
Falko, If I use UTF-8 in URL, it should be used with coding = 1, which cause
that the content will be delivered in unreadable format for the mobile.
Otherwise, If I use ISO-8859-1, i should add coding=2 which encodes it in
16-bit (the characters are normally
Hi All,
I actually want to use the modem to receive only.
So are we all saying a serial connection (COMM) interface modem is the
fastest? What of the claim the USB modem processes AT commands faster?
--
Kenny
OCA | ECSA | RHCE
p: +2348034939090
e: ke...@nuobjects.com
w: www.nuObjects.com
LEts forget about HTTP Client. When I call send-sms from .NET service, what
is the procedure of encoding that suits for kannel?
Regards
Elton
On Fri, May 8, 2009 at 8:19 AM, Elton Hoxha elt...@gmail.com wrote:
Thanks Jyoti, I will give it a try.
Falko, If I use UTF-8 in URL, it should be
Unimportant...
Your http-client (if you write some script in .NET it is also a http-
client, just a very personal one) states the encoding while connecting
and that is the one you must use. That has nothing to do with coding!
See:
you send UTF-8 string to kannel with coding=0. Than kannel
Hi Falko,,
Thanks for your comments, I tried what you said and I get
2009-05-08 02:09:50 [5317] [3] ERROR: Failed to convert string from UTF-8
to UTF-8, errno was 84
2009-05-08 02:09:50 [5317] [3] DEBUG: Found an invalid multibyte sequence at
position 0
2009-05-08 02:09:50 [5317] [3] DEBUG:
I got this error
2009-05-08 02:49:48 [5641] [3] INFO: sendsms sender:test3:ELTON
(10.1.21.146) to:355672509006 msg:é
2009-05-08 02:49:48 [5641] [3] DEBUG: Stored UUID
73f6686e-e184-4e3d-986b-32fb88d30878
2009-05-08 02:49:48 [5641] [3] WARNING: Incomplete UTF-8 char discovered,
skipped. 2
Don't set the charset!!!
You there define the output charset, not the input charset and charset
UTF-8 with coding 0 is ... well ...
The UTF-8 is NOT defined in the URL, your http-client/scipt/whatever
defines it for itself in the HTTP-header. Put all that stuff away,
just send this:
No?! é is %C3%A9 in UTF-8. é is %E9 in RAW encoding.
http://kellyjones.netfirms.com/webtools/ascii_utf8_table.shtml
Regards
Falko
Am 08.05.2009 um 10:49 schrieb Elton Hoxha:
I got this error
2009-05-08 02:49:48 [5641] [3] INFO: sendsms sender:test3:ELTON
(10.1.21.146) to:355672509006 msg:é
I tried this:
http://10.1.21.137:13014/cgi-bin/sendsms?username=test3password=test3from=ELTONto=355672509006text=%C3%A9coding=0
character is transformed again in kannel
Debug logs:
2009-05-08 03:50:23 [5641] [3] INFO: smsbox: Got HTTP request
/cgi-bin/sendsms from 10.1.21.146
2009-05-08 03:50:23
On Fri, May 8, 2009 at 12:32 PM, Elton Hoxha elt...@gmail.com wrote:
I tried this:
http://10.1.21.137:13014/cgi-bin/sendsms?username=test3password=test3from=ELTONto=355672509006text=%C3%A9coding=0
character is transformed again in kannel
The characters you are trying to send are not defined in
On Fri, May 8, 2009 at 1:12 PM, Jovan Kostovski chomb...@gmail.com wrote:
On Fri, May 8, 2009 at 12:32 PM, Elton Hoxha elt...@gmail.com wrote:
I tried this:
http://10.1.21.137:13014/cgi-bin/sendsms?username=test3password=test3from=ELTONto=355672509006text=%C3%A9coding=0
character is
It depend on several factors
_) GSM network itself. This is the main bottleneck
_) modem to network. This mainly depend on your operator. Normally
this is the 2nd main bottleneck
_) modem HW. This will depend on chipset
_) modem to server. COM ports can go normally up to 115200 and USB to
more
Hi Jovan,
All my tests included GSM 7-bit characters like é or è, I`m not interested
in ISO-8859-1.
Unfortunately all my efforts are failing...despite your help..
Elton
On Fri, May 8, 2009 at 1:14 PM, Jovan Kostovski chomb...@gmail.com wrote:
On Fri, May 8, 2009 at 1:12 PM, Jovan Kostovski
Hi,
According to SMPP v 5, 0x0004 is the submit_sm. Very essential and
recognized by kannel as seen from the logs. Strange thing is that a few lines
below, it doesn't recognize it, which can only mean that it is not expecting it
at the state it is in.
This looks hairy. Can you provide a
Hi,
SMPP Spec on submit_sm:
This operation is used by an ESME to submit a short message to the
SMSC
SMPP Spec on deliver_sm:
The deliver_sm is issued by the SMSC to send a message to an ESME.
submit_sm is only used when a client sends data to a server. When the
server wants to send data
So,
this one: wget http://localhost:13013/cgi-bin/sendsms?username=XXXpassword=XXXto=0049173XXXfrom=0049173XXXtext=%E9
created a sms with é BUT: (my) wget uses the charset ISO-8859-1
where é is %E9. It think the problem is, that the script you use
says in the http-header that it uses
Hello Sangprabv,
One sms per second look to be a little bit optimistic, our tests (on large
volume during hours) on different brand name such as Nokia, Siemens and
wavecom indicate more something like 1 sms every 5-6 second. So I am more
agree with Alvaro result.
One SMS per second should be
17 matches
Mail list logo
