Re: Newbie question

[Monim Benaiad]

Hi,

install libxml2 using:
yum install libxml2 libxml2-devel

Re: Transaction Delivery Failure

[Monim Benaiad]

Hi Gustavo,

use dlr-mask=16 to handle this type of failed send sms.

regards

On Sun, Sep 21, 2008 at 7:37 PM, Gustavo Mohme C. <[EMAIL PROTECTED]> wrote:

> Hi All,
> My SMSC randomly returns this error:
>
> ERROR: SMSC returned error code 0x00fe (Transaction Delivery Failure)
> in response to submit_sm.
>
> My question is, after this error is received, is the message resent? And if
> not, why not?
> Thanks,
> Gustavo Mohme C.
>

Re: Transaction Delivery Failure

[Monim Benaiad]

Dear Gustavo,

The failed to submit to smsc dlr is generated by the gateway itself, so,
when ypu submit a message to kannel use a dlr-url (with dlr-mask=16) which
will make kannel request this url when a failed send sms is happen.
and don't forget to encode your dlr-url string before submitting it.
I can post some code, if you are using java.
also you can check the source code for this in "bb_smscconn.c"
Regards.

On Mon, Sep 22, 2008 at 4:19 PM, Gustavo Mohme C. <[EMAIL PROTECTED]> wrote:

> Hi Monim,
> My SMSC doesn't support dlr. And even if it did, this won't make kannel
> resend the sms but only store it as failed, right? Is there a way to
> automatically resend this sms?
> Regards
>
>
> On Mon, Sep 22, 2008 at 3:07 AM, Monim Benaiad <[EMAIL PROTECTED]> wrote:
>
>> Hi Gustavo,
>>
>> use dlr-mask=16 to handle this type of failed send sms.
>>
>> regards
>>
>>
>> On Sun, Sep 21, 2008 at 7:37 PM, Gustavo Mohme C. <[EMAIL PROTECTED]>wrote:
>>
>>> Hi All,
>>> My SMSC randomly returns this error:
>>>
>>> ERROR: SMSC returned error code 0x00fe (Transaction Delivery Failure)
>>> in response to submit_sm.
>>>
>>> My question is, after this error is received, is the message resent? And
>>> if not, why not?
>>> Thanks,
>>> Gustavo Mohme C.
>>>
>>
>>
>

Re: How to route SMSC to SMS-services?

[Monim Benaiad]

Hi janson,
This is my working configuration:
BEGIN###
group = core
admin-port = 11000
smsbox-port = 11001
admin-password = kannelisthebest
admin-deny-ip = "*.*.*.*"
admin-allow-ip = "127.0.0.1;192.168.*.*"
box-deny-ip = "*.*.*.*"
box-allow-ip = "127.0.0.1;192.168.0.*"
log-level = 1
sms-combine-concatenated-mo = false
log-file = "/var/log/sms/bearerbox.log"
access-log = "/var/log/sms/access.log"
store-type = spool
store-location = "/usr/smspool"

group = smsbox
sendsms-port = 11003
global-sender = ""
mo-recode = true
http-request-retry=500
http-queue-delay=20


# SMSC SMPP==>23033
group = smsc
smsc = smpp
smsc-id=23033
denied-smsc-id ="23330;13013;23535"
host = 10.10.1.2
port = 1534
#transceiver-mode=true
receive-port = 1534
smsc-username = 23033
smsc-password = mysecret
system-type = VAS23033
max-pending-submits = 100

group = sendsms-user
username = user23033
password = 23033
forced-smsc = 23033
default-smsc = 23033
user-deny-ip = "*.*.*.*"
user-allow-ip = "127.0.0.1;localhost"
concatenation= true
max-messages = 10

group = sms-service
keyword = default
accepted-smsc=23033
concatenation = true
get-url = "http://127.0.0.1:8080/s23033?phone=%p&text=%a&receiver=%i";
assume-plain-text = true
omit-empty = true
max-messages = 0
#text = "Welcom, Received by 23033"

# SMSC SMPP==>23330
group = smsc
smsc = smpp
smsc-id=23330
denied-smsc-id ="23033;13013;23535"
host = 10.10.1.2
port = 1534
#transceiver-mode=true
receive-port = 1534
smsc-username = 23330
smsc-password = mysecret
system-type = VAS23330
max-pending-submits = 100

group = sendsms-user
username = user23330
password = 23330
forced-smsc = 23330
default-smsc = 23330
user-deny-ip = "*.*.*.*"
user-allow-ip = "127.0.0.1;localhost"
concatenation= true
max-messages = 10

group = sms-service
keyword = default
accepted-smsc=23330
concatenation = true
get-url = "http://127.0.0.1:8080/s23330?phone=%p&text=%a&receiver=%i";
assume-plain-text = true
omit-empty = true
max-messages = 0
#text = "Welcom, Received by 23330"

# SMSC SMPP==>13013
group = smsc
smsc = smpp
smsc-id=13013
denied-smsc-id ="23033;23330;23535"
host = 10.10.1.2
port = 1534
#transceiver-mode=true
receive-port = 1534
smsc-username = 13013
smsc-password = mysecret
system-type = VAS13013
max-pending-submits = 100

group = sendsms-user
username = user13013
password = 13013
forced-smsc = 13013
default-smsc = 13013
user-deny-ip = "*.*.*.*"
user-allow-ip = "127.0.0.1;localhost"
concatenation= true
max-messages = 10

group = sms-service
keyword = default
accepted-smsc=13013
concatenation = true
get-url = "http://127.0.0.1:8080/s13013?phone=%p&text=%a&receiver=%i";
assume-plain-text = true
omit-empty = true
max-messages = 0
#text = "Welcom, Received by 13013"

# SMSC SMPP==>23535
group = smsc
smsc = smpp
smsc-id=23535
denied-smsc-id ="23033;23330;13013"
host = 10.10.1.2
port = 1534
#transceiver-mode=true
receive-port = 1534
smsc-username = 23535
smsc-password = mysecret
system-type = VAS23535
max-pending-submits = 100

group = sendsms-user
username = user23535
password = 23535
forced-smsc = 23535
default-smsc = 23535
user-deny-ip = "*.*.*.*"
user-allow-ip = "127.0.0.1;localhost"
concatenation= true
max-messages = 10

group = sms-service
keyword = default
accepted-smsc=23535
concatenation = true
get-url = "http://127.0.0.1:8080/gec?phone=%p&text=%a&receiver=%i";
assume-plain-text = true
omit-empty = true
max-messages = 0
#text = "Welcom, Received by 23535"
##END

Re: How to route SMSC to SMS-services?

[Monim Benaiad]

Hi Janson,
The "system-type" option has no mean to our smpp server, so, it's just used
to differentiate between the services.

and you can differentiate between the services in the application side not
in the SMS gateway, you can use  the phone number of the receiver of the SMS
message in the get url, see %P in the manual.
also when sending SMS use the parameter "from".

Regards


On Fri, Sep 26, 2008 at 7:40 AM, janson <[EMAIL PROTECTED]> wrote:

>  Monim Benaiad:
>
> Thanks a lot!
> I have some question for you config.
>
> What for "system-type" option?  In userguide I found only next: "
> system-type (m)  string  Usually you can get away with 'VMA' which stands
> for Voice Mail Activation".  And nothing more about this for smsc = smpp.
>
>
>
> Now I think, the problem with route is not in my kannel configuration but
> is problem in operator connection organize.
> Because operator give only one pass and username for both numbers: 9918 and
> 0220. I see - I have one channel from operator for my connections to 9918
> and 0220.
> Is the only one possible way to solve problem: keywords for different
> servives?
>
>
> "Monim Benaiad" <[EMAIL PROTECTED]> сообщил/сообщила в новостях следующее:
> news:[EMAIL PROTECTED]
> Hi janson,
> This is my working configuration:
> BEGIN###
> group = core
> admin-port = 11000
> smsbox-port = 11001
> admin-password = kannelisthebest
> admin-deny-ip = "*.*.*.*"
> admin-allow-ip = "127.0.0.1;192.168.*.*"
> box-deny-ip = "*.*.*.*"
> box-allow-ip = "127.0.0.1;192.168.0.*"
> log-level = 1
> sms-combine-concatenated-mo = false
> log-file = "/var/log/sms/bearerbox.log"
> access-log = "/var/log/sms/access.log"
> store-type = spool
> store-location = "/usr/smspool"
>
> group = smsbox
> sendsms-port = 11003
> global-sender = ""
> mo-recode = true
> http-request-retry=500
> http-queue-delay=20
>
>
> # SMSC SMPP==>23033
> group = smsc
> smsc = smpp
> smsc-id=23033
> denied-smsc-id ="23330;13013;23535"
> host = 10.10.1.2
> port = 1534
> #transceiver-mode=true
> receive-port = 1534
> smsc-username = 23033
> smsc-password = mysecret
> system-type = VAS23033
> max-pending-submits = 100
>
> group = sendsms-user
> username = user23033
> password = 23033
> forced-smsc = 23033
> default-smsc = 23033
> user-deny-ip = "*.*.*.*"
> user-allow-ip = "127.0.0.1;localhost"
> concatenation= true
> max-messages = 10
>
> group = sms-service
> keyword = default
> accepted-smsc=23033
> concatenation = true
> get-url = "http://127.0.0.1:8080/s23033?phone=%p&text=%a&receiver=%i";
> assume-plain-text = true
> omit-empty = true
> max-messages = 0
> #text = "Welcom, Received by 23033"
>
> # SMSC SMPP==>23330
> group = smsc
> smsc = smpp
> smsc-id=23330
> denied-smsc-id ="23033;13013;23535"
> host = 10.10.1.2
> port = 1534
> #transceiver-mode=true
> receive-port = 1534
> smsc-username = 23330
> smsc-password = mysecret
> system-type = VAS23330
> max-pending-submits = 100
>
> group = sendsms-user
> username = user23330
> password = 23330
> forced-smsc = 23330
> default-smsc = 23330
> user-deny-ip = "*.*.*.*"
> user-allow-ip = "127.0.0.1;localhost"
> concatenation= true
> max-messages = 10
>
> group = sms-service
> keyword = default
> accepted-smsc=23330
> concatenation = true
> get-url = "http://127.0.0.1:8080/s23330?phone=%p&text=%a&receiver=%i";
> assume-plain-text = true
> omit-empty = true
> max-messages = 0
> #text = "Welcom, Received by 23330"
>
> # SMSC SMPP==>13013
> group = smsc
> smsc = smpp
> smsc-id=13013
> denied-smsc-id ="23033;23330;23535"
> host = 10.10.1.2
> port = 1534
> #transceiver-mode=true
> receive-port = 1534
> smsc-username = 13013
> smsc-password = mysecret
> system-type = VAS13013
> max-pending-submits = 100
>
> group = sendsms-user
> username = user13013
> password = 13013
> forced-smsc = 13013
> default-smsc = 13013
> user-deny-ip = "*.*.*.*"
> user-allow-ip = "127.0.0.1;localhost"
> concatenation= true
> max-messages = 10
>
> group = sms-service
> keyword = default
> accepted-smsc=13013
> concatenation = true
> get-url = "http://127.0.0.1:8080/s13013?phone=%p&text=%a&receiver=%i";
> assume-plain-text = true
> omit-empty = true
> max-messages = 0
> #text = "

Re: SMPP Warning Message

[Monim Benaiad]

The first warning is normal because you are trying to use a short code as a
sender and kannel suggests  you "generally expected at least 7 digits"
But the second warning means the "smsbox" not running.

Re: Need help with sending Arabic with diacritics

[Monim Benaiad]

Maybe the handsets doesn't support these arabic diacritics.

On Thu, Jan 8, 2009 at 3:13 PM, tamer qtaish  wrote:

> Dear Jovan,
> My problem isn't Sending Arabic text!
> My problem is to send Arabic text with diacritics, is it is even possible,
> I just wanna know its possible and if so how would I do it, It might be the
> simple fact that diacritics are not supported, but would I make sure?
>
> "A diacritic (/daɪəˈkrɪtɪk/) (also diacritical mark, diacritical point,
> diacritical sign) is a small sign added to a letter to alter pronunciation
> or to distinguish between similar words. The term derives from the Greek
> διακριτικός (diakritikós, "distinguishing"). Diacritic is both an adjective
> and a noun, whereas diacritical is only an adjective. Some diacritical
> marks, such as the grave and acute accents, but not the cedilla, are often
> called accents." (Wikipedia)
>
> Thanks for your reply...
>
> All the best,
> Tamer Qtaish
>

Re: Recover MO when httpd is down

[Monim Benaiad]

IMHO, you can use the configuration parameters  "http-request-retry" and
"http-queue-delay"
to keep the messages in kannels queue, until you restart apache.

On Thu, Jan 8, 2009 at 6:21 PM, Villada, Gustavo
wrote:

> Hello,
>
> We have correctly configured and are running kannel cvs-20081009.
>
> All the sms-services configured with get-url to the app and the response
> are via sendsms.
>
> The problem that we have is:
> When apache is down:
>
> 2009-01-08 15:05:42 [24312] [9] DEBUG: HTTP: Opening connection to
> `servername:80' (fd=28).
> 2009-01-08 15:05:42 [24312] [9] DEBUG: Socket connecting
> 2009-01-08 15:05:42 [24312] [8] DEBUG: Get info about connecting socket
> 2009-01-08 15:05:42 [24312] [8] DEBUG: Socket not connected
> 2009-01-08 15:05:42 [24312] [8] ERROR: Couldn't fetch  parameters>
>
>
>
> And the MO is dropped...
> Is it possible to recover from this situation?
>
> If not: is it possible to save all the messages to a file and/or database?
>
> I saw that the only parameter that I may use is 'exec' but we don't want
> execute an aplication for recover...
>
>
> Thanks in advance...
>
>
>
>
>
>
>

Re: Problem with delivery report message about "0: Accepted for delivery"

[Monim Benaiad]

NOTE: The get-url points to sendsms cgi itself, and the second sms you
receive is the result of submiting a msg to kannel.

On 1/9/09, Pham Ngoc Khanh  wrote:
> Hi all,
>
> I got a problem with the delivery report message about "0: Accepted for
> delivery". Below is my configuration
>
> group = core
> admin-port = 13000
> smsbox-port = 13001
> admin-password = bar
> log-file = "/tmp/kannel.log"
> log-level = 0
> box-allow-ip = "127.0.0.1"
>
> group = modems
> id = nokiaphone
> name = "Nokia"
> detect-string = "Nokia"
> detect-string2 = "E51"
> need-sleep = true
> init-string = "AT+CPMS=?"
>
> group = smsc
> smsc = at
> smsc-id=nokia
> modemtype = nokiaphone
> device=/dev/ttyACM0
> my-number = x
> sms-center = x
> speed = 0
>
> group = smsc
> smsc = smpp
> smsc-id = smpp
> port = 2775
> connect-allow-ip = *.*.*.*
> host = localhost
> smsc-username = smsc
> smsc-password = smsc
> system-type = "VMA"
> address-range = ""
> denied-smsc-id = smpp;nokia
>
> group = smsbox
> bearerbox-host = 127.0.0.1
> sendsms-port = 13013
> global-sender = 
> log-level = 0
>
> group = sendsms-user
> username = user
> password = user
> concatenation= true
>
> group = sms-service
> keyword = default
> text = "No action specified"
>
> group = sms-service
> keyword = mibento
> get-url =
> "http://localhost:13013/cgi-bin/sendsms?username=user&password=user&from=%p&to=%P&text=%S&smsc=nokia";
> max-messages = 1
> accepted-smsc = smpp
>
> The problem is that after Kannel sent message to client it then sends the
> message "0: Accepted for delivery" to client as well. I read somewhere on th
> internet that set: max-messages=0 will prevent sending reply message. But if
> I do that, Kannel does not send any message to client.
> So could someone tell me what i was wrong, and help me out?
>
> Thank in advance
> K
>
>
>
>
>

-- 
Sent from my mobile device

Re: Receiving long messages

[Monim Benaiad]

I think it's "sms-combine-concatenated-mo = true" in the core group. with
the stable release

Re: Sending messages via url stuck

[Monim Benaiad]

I didn't see your configuration, but I think the port is 13003 instead of
13001.

Good Luck...

-
Abdulmnem Benaiad
Almontaha ICT Co.


On Thu, Feb 12, 2009 at 12:59 PM, kriko  wrote:

> Hello! I've got a N95 from which I can send messages in such way:
> AT+CMGF=1
> AT+CMGS="##"
>
> Now, I've configure kannel in this way:
> http://pastebin.com/m735918b9
>
> but when I try to send a message via URL:
>
> http://localhost:13001/cgi-bin/sendsms?username=user&password=send&to=041443396&text=ping
>
> I just get:
> 2009-02-12 11:56:25 [26139] [5] INFO: Client connected from <127.0.0.1>
>
> and here it gets stuck. It doesn't send a message and it doesn't respond to
> the client.
> Did I miss something while configuring?
>
> Device is initialized and working, no errors in log.
>
> --
> Kristjan Ugrin
>

Re: Wap Push Java Code

[Monim Benaiad]

Dear Ishtiaq Ahmed,
Sorry for my late response, I wrote a method to do the job:
Note:- you have to change: encoding=\"ISO-8859-6\" in the buffer code.

Start of method/
public String sendWapPush(String target,String downloadURL,String
downloadDetail) {
try {
StringBuffer buffer = new StringBuffer();
String vMessageID = "" + Math.random();
String message = "";
String host = "127.0.0.1";//kannel host
String port = "55012";//ppg port
String url = "http://"; + host + ":" + port + "/wappush";
buffer.append("--asdlfkjiurwgasf\r\n").append("Content-Type:
application/xml\r\n\r\n").append("\r\n").append("http://www.wapforum.org/DTD/pap_1.0.dtd\";>\r\n").append("\r\n").append("\r\n").append("\r\n").append("").append("\r\n").append("\r\n\r\n").append("--asdlfkjiurwgasf\r\n").append("Content-Type:
text/vnd.wap.si\r\n\r\n").append("\r\n").append("http://www.wapforum.org/DTD/si.dtd\";>\r\n").append("\r\n").append("").append(downloadDetail).append("\r\n").append("\r\n").append("--asdlfkjiurwgasf--\r\n\r\n");
message = buffer.toString();
target = url;
String content = message;
//public static String postData(String target, String content)
throws Exception {
//System.out.println("About to post\nURL:" +
target + "content: " + content);
String responseD = "";
URL urlc = new URL(target);
URLConnection conn = urlc.openConnection();

// Set connection parameters.
conn.setDoInput(true);
conn.setDoOutput(true);
conn.setUseCaches(false);
conn.setRequestProperty("Content-Type", "multipart/related;
boundary=asdlfkjiurwgasf; type=application/xml");

//conn.setRequestProperty("Authorization", "Basic \"foo:bar\"");
conn.setRequestProperty("X-Kannel-SMSC", "smsc" + smsc);
conn.setRequestProperty("X-Kannel-From", smsc);
conn.setRequestProperty("Content-Length", "" +
content.length());

DataOutputStream outs = new
DataOutputStream(conn.getOutputStream());
// Write out the bytes of the content string to the stream.
outs.writeBytes(content);
outs.flush();
// Read response from the input stream.
BufferedReader in = new BufferedReader(new
InputStreamReader(conn.getInputStream()));
String temp;
while ((temp = in.readLine()) != null) {
responseD += temp + "\n";
}
temp = null;
outs.close();
in.close();
//System.out.println("Server response:\n" + responseD + "");
return responseD;
} catch (Exception e) {
e.printStackTrace();
return null;
}
}
end of method

On Thu, Feb 26, 2009 at 3:58 PM, Ishtiaq Ahmed wrote:

> Hi Fellows:
>
>
> Can someone help with the exact java code and minimum header set / PAP
> configuration / Content File... for sending the WAP Push through Kannel
> The problem with my code is that The message is being sent in two
> segments
>
>
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP (UNIT): event arrived
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP_UNIT: Connectionless push
> accepted
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping
> `application/vnd.wap.sic', WSP 1.2 to 0x002e.
> 2009-02-20 06:35:02 [23465] [2] ERROR: HTTP: Header does not contain a
> colon. BAD.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `X-Unknown', WSP 1.3 to
> 0x.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `Cache-Control', WSP
> 1.3 to 0x003d.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `Pragma', WSP 1.3 to
> 0x001f.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `User-Agent', WSP 1.3
> to 0x0029.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `Accept', WSP 1.3 to
> 0x.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `text/html', WSP 1.2 to
> 0x0002.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `image/gif', WSP 1.2 to
> 0x001d.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `image/jpeg', WSP 1.2
> to 0x001e.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `*', WSP 1.2 to
> 0x.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `q', WSP 1.2 to 0x.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `*/*', WSP 1.2 to
> 0x.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `q', WSP 1.2 to 0x.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `Content-Length', WSP
> 1.3 to 0x000d.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `Content-Type', WSP 1.3
> to 0x0011.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `Encoding-Version', WSP
> 1.3 to 0x0043.
> 2009-02-20 06:35:02 [23465] [2] DEBUG: WDP (wapbox): delivering 2 segments
> to bearerbox
>
>
>
> Regards,
>
> Ishtiaq Ahmed
>
>

Re: Wap Push Java Code

[Monim Benaiad]

Asalam Alaikom Ishtiaq:

>> the message is being delivered in two segments
Maybe it's a configuration issue, because I've tested this with many types
of ME , even with Chinese brands and it works the wap push message
successfully received and recognized by the ME.
here my configuration regarding ppg and wap box:

group   = wapbox
bearerbox-host  = localhost
log-file= "/var/log/wapbox.log"
log-level   = 1
syslog-level= none

group = ppg
ppg-url   = /wappush
ppg-port  = 55012
concurrent-pushes = 100
users = 1024
ppg-allow-ip  = "127.0.0.1;192.168.0.*"
trusted-pi= true
service-name  = ppg1

group   = wap-push-user
wap-push-user   = wappush
ppg-username= foo
ppg-password= bar
allow-ip= "127.0.0.1;192.168.0.*"

Regards.


On Tue, Mar 3, 2009 at 7:33 AM, Ishtiaq Ahmed wrote:

> Hi Monim,
>
> We have tried the method you wrote... but its the same issue.. the message
> is being delivered in two segments... Following are the wappush logs..
>
>
> 2009-03-03 10:23:34 [17163] [11] DEBUG: HTTP: Creating HTTPClient for
> `172.21.21.21'.
> 2009-03-03 10:23:34 [17163] [11] DEBUG: HTTP: Created HTTPClient area
> 0x32a9170.
> 2009-03-03 10:23:34 [17163] [14] WARNING: Your ppg core configuration allow
> all ips
> 2009-03-03 10:23:34 [17163] [14] INFO: PPG: Accept request  from
> <172.21.21.21>
> 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: http_read_thread: pap
> multipart accepted
> 2009-03-03 10:23:34 [17163] [14] INFO: client address was <+923028560819>,
> accepted
> 2009-03-03 10:23:34 [17163] [14] DEBUG: PAP COMPILER: doing semantic
> analysis for address type a phone number
> 2009-03-03 10:23:34 [17163] [14] DEBUG: using defaults instead of anys
> 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: http_read_thread: pap control
> entity compiled ok
> 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: transform_message: push
> message content and headers valid
> 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: push machine 1 created
> 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: store_push_data: push machine
> 1 appended to unit push list
> 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: send_push_response: telling pi
> 2009-03-03 10:23:34 [17163] [14] DEBUG: HTTP: Resetting HTTPClient for
> `172.21.21.21'.
> 2009-03-03 10:23:34 [17163] [14] INFO: PPG: handle_push_message: push
> message accepted for processing
> 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: OTA request for unit push
> 2009-03-03 10:23:34 [17163] [9] DEBUG: OTA: event arrived
> 2009-03-03 10:23:34 [17163] [14] INFO: PPG: unconfirmed push delivered to
> OTA
> 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: destroying push machine 1
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP (UNIT): event arrived
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP_UNIT: Connectionless push
> accepted
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping
> `application/vnd.wap.sic', WSP 1.2 to 0x002e.
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Cache-Control', WSP
> 1.3 to 0x003d.
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Pragma', WSP 1.3 to
> 0x001f.
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `User-Agent', WSP 1.3
> to 0x0029.
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Accept', WSP 1.3 to
> 0x.
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `text/html', WSP 1.2 to
> 0x0002.
> 2009-03-03 10:23:34 [17163] [9] DEBUG: OTA: made connectionless session
> service request
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `image/gif', WSP 1.2 to
> 0x001d.
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `image/jpeg', WSP 1.2
> to 0x001e.
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `*', WSP 1.2 to
> 0x.
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `q', WSP 1.2 to 0x.
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `*/*', WSP 1.2 to
> 0x.
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `q', WSP 1.2 to 0x.
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Content-Length', WSP
> 1.3 to 0x000d.
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Content-Type', WSP 1.3
> to 0x0011.
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Encoding-Version', WSP
> 1.3 to 0x0043.
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WDP (wapbox): delivering 2 segments
> to bearerbox
> 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP (UNIT): delivering to wdp
> 2009-03-03 10:23:34 [17163] [0] WARNING: Received other message than
> wdp/admin, ignoring!
> 2009-03-03 10:23:34 [17163] [0] WARNING: Received other message than
> wd

Re: Java<->Kannel connection

[Monim Benaiad]

Hello

Try this method:

public String send(String serverIP, String serverSendPort, String user,
String password, String smsc, String mt, String text, String from) {
String result = "";
try {
String data = java.net.URLEncoder.encode(text, "UTF8");
String msisdn = java.net.URLEncoder.encode(mt, "UTF8");
String sendURL = "http://"; + serverIP + ":" + serverSendPort +
"/cgi-bin/sendsms?username=" + user + "&password=" + password +
"&charset=utf-8&coding=2&to=" + msisdn + "&text=" + data + "&smsc=" + smsc+
"&from=" + from;

java.net.URL url = new java.net.URL(sendURL);
java.io.InputStream in = url.openStream();
java.io.BufferedInputStream bufIn = new
java.io.BufferedInputStream(in);
for (;;) {
int car = bufIn.read(); // Check for EOF
if (car == -1) {
break;
} else {
result = result + (char) car;
}
}
bufIn.close();
in.close();

} catch (Exception e) {
e.printStackTrace();
}

return result;
}



On Mon, Mar 9, 2009 at 1:21 AM, Peter Elmered  wrote:

> Hello
>
> I'm writing a java application that handles and sends out SMS with Kannel.
>
> When i use the HTTP-interface i get this error message:
> java.io.IOException: Server returned HTTP response code: 400 for URL:
> http://83.253.156.183:13013/cgi-bin/sendsms?username=tester&password=foobar&to=3467565&text=Hello+world1
>
> Anyone knows why i get this and how to solve it. It works like i should
> when i type in the same url in my browser.
>
> Does anyone have some working examplecode for this i Java. Preferably with
> SSL support.
>
> Thanks!
> SincerelySincerhhh
>
> Sincerely,
> Peter
>

Re: hone-no/serviceid of the operator to which SMS was sent

[Monim Benaiad]

Hi,
I think it's %P instead of %p.


On Mon, Mar 23, 2009 at 6:00 PM, Latitude Berlin  wrote:

> Hi,
>
> I have a 2-way SMPP account configured with Kannel and I am getting sms
> forwarded to servlet. I want to get the TO field which in this case is the
> phone-no/serviceid of the operator. I tried using %p but got the port no
> (13013).
>
> Please advise.
>
> - Latitude
>

Re: sending/receiving unicode SMS via Kannel

[Monim Benaiad]

I'm using Kannel to send Arabic messages, and coding with Java:
1- in smsbox group add "mo-recode=true".
2- in my servlet, I convert the received sms from "ISO-8859-1" to "utf-8".
3- in the sendsms url I add the parameters "&charset=utf-8&coding=2".
4- mysql uses "utf-8" charset.

Thanks

Abdulmnem Benaiad
Almontaha
almontaha.com

On Tue, May 5, 2009 at 10:32 AM, Latitude Berlin  wrote:

> Hi,
>
> I want to send and receive unicode SMS via Kannel. For example sms written
> in arabic language. Please guide.
>
> Thanks
> - Latitude
>

Re: CMS ERROR: Unknown error. -> maybe Sim storage is full? I'll have a look at it. (500)

[Monim Benaiad]

I've seen this when "enable-mms = true" is used in the modems group

TIA

Abdulmnem Benaiad
Almontaha
almontaha.com

2009/5/5 चेतन @ MANIKS SYS 

> HI,
> I am new to using kannel.
>
> I had configure the kannel to send sms using nokia mobile as modem.
>
> It works fine for sometime, but now it gives me the error as,
>
>  CMS ERROR: Unknown error. -> maybe Sim storage is full? I'll have a look
> at it. (500)
>
> I had googled this error, but could not able to figured out the solution,
>
> Some say to delete the messages from sim, somewhere  I had seen apply new
> patches,
>
> But exact cause due to which such kind of error occurred.
>
> As it is an generic error (Unknown Error).
>
> How to find exact cause.
>
>
> Thanks and Regards,
> Chetan Menge
>

Re: Messages intermittently getting stuck in kannel's queue

[Monim Benaiad]

On Thu, May 14, 2009 at 8:58 AM, shaded 4  wrote:

> Hi,
>
> Is there any known problem in kannel such that it sometimes
> refuses to send messages? (I'm talking about just transmitter
> functionality here, not receiver.)
> It seems to happen sometimes after connectivity to a SMSC is
> disrupted and reconnected.
>
> The only way that kannel eventually sends the messages
> is if I restart kannel, or after it again loses and regains
> connectivity the next time.
>

AFAIK, The "transceiver-mode" variable in the smsc group will solve this
problem.
I think it's a bug in that version, because Kannel reconnect the receiver
only.
also remove the "receive-port".

TIA

Abdulmnem Benaiad
Almontaha
almontaha.com