Hi,
there is quite fresh article at IBM about setting Kannel as PPG:
http://www-106.ibm.com/developerworks/wireless/library/wi-proxy.html
Hope this helps.
On Wed, 23 Mar 2005 16:48:48 -0800 (PST), Ivonne Ivonne
<[EMAIL PROTECTED]> wrote:
>
>
> Hi,
>
> I'm testing the test-ppg. (kannel1.3.1-I
Hi,
well, usually this _can_ be queued at operator's HLR as IMEI is
transfered at least for each voice call to check if it's not
black-listed. Check if your operator can't provide such an
information.
On Sat, 19 Mar 2005 12:35:12 -0400, Oscar Flores
<[EMAIL PROTECTED]> wrote:
> Hello Users
>
> D
Hi every one,
We
have connected to an operator SMSC through CIMD2 protocol using Kannel stable
1.4.0.
This is a production environment and we are
running this since six months without any problems.
But from last week we are getting error messages
from the SMSC when we submit
Hi
When Starting Kannel we need to start 1st the bearerbox like
./bearerbox -v kannel.conf
So when I will start the WAP and SMs boxes than which conf file will be used
?
will it be again kannel.conf or kannelwap.conf/smskannel.conf
I am new to kannel
Thanks for your help
Regards
Yasser
--
On Fri, Mar 25, 2005 at 10:55:23AM +0200, Dziugas Baltrunas wrote:
> well, usually this _can_ be queued at operator's HLR as IMEI is
> transfered at least for each voice call to check if it's not
> black-listed. Check if your operator can't provide such an
> information.
The IMEI will be passed i
Hi,
you should URL encode the text parameter as required by HTTP protocol.
Basicly change spaces to '+' and other special symbols to ther
equivalent %hexcode or use some function which does url encode.
And please do not cross-post to the lists. This issue should have gone to users.
On Fri, 25 Ma
Hi,
I tried by URL encoding the special characters it did not help. I
still get the same error!!
I tried by sending this following message "Test message % after"
# lynx --dump
"http://127.0.0.1:16016/cgi-bin/sendsms?username=&password=X&to=1234
56789000&from=test&text=%74%6
Hello I installed Kannel 1.4.0 on a Fedora core 2 and I always get this from
smsbox:
[3] INFO: smsbox: Got HTTP request from <*.*.*.*>
2005-03-25 13:03:08 [31336] [3] DEBUG: Status: 403 Answer:
2005-03-25 13:03:08 [31336] [3] DEBUG: HTTP: Resetting HTTPClient for
`*.*.*.*'.
2005-03-25 13:04:0
Hi,
We are using CIMD2 to connect to operator SMSC
Whne I send the following message using sendsms
"test_" (quotes included)
$ lynx --dump
"http://127.0.0.1:16016/cgi-bin/sendsms?username=&password=&to=12345
67890&from=test&text=%22%74%65%73%74%22%5F"
Kannel is
Does the recipient's phone also shows the message as "_qqtest_qq_--"?
If no, than there is no problem as according to CIMD2 specification,
double quotes(") must be translated to _qq and an underscore (_) to
_--.
It definately seems that SMSC your are connecting to does not follow the specs.
On Fr
Thanks Aarno and Dziugas for your help!
I have the following messages after that. I'm attached the log.
2005-03-25 08:30:54 [2] DEBUG: Octet string dump ends.2005-03-25 08:30:54 [2] DEBUG: HTTP: Status line: 2005-03-25 08:30:54 [1] DEBUG: TEST_PPG: push 0 done: reply from, http://172.24.249.
Yes the recipient's phone also shows the message as ""_qqtest_qq_--".
I am not very sure but I suspect it to be kannel encoding the messages in
Special combination format. But why? I need to understand it yet
warm regards,
Arun
-Original Message-
From: Dziugas Baltrunas [mailto:[EM
I might be wrong, but if you shutdown the smsc from the web interface,
the messages should be reassigned to any other available link.
I mean using stop-smsc and start-smsc from the web interface to bring
the link down (and up again after a few seconds) ONLY for the "slow"
smsc_at link.
I've used
13 matches
Mail list logo
