kannel-on-windows

2007-02-13 Thread sri ganeshan

hi all,

i'm to install kannel on windows.i have installed cygwin already.could
some one please give me some guidlines on how to move further
from this point.i also have downloaded the kannel-source.

regards

sri


Re: sendota can't use DLR ?

2007-02-13 Thread Enver ALTIN

On 2/7/07, Julien Buratto [EMAIL PROTECTED] wrote:

Quote strange,


Hi,


when using sendota to send come otas, DLR seems not to work (I don't
mean I get a failure dlr, I mean dlr-mask and dlr-url seems to be ignored)
When I do it manually with sendsms and use a binary message I get the DLRs


Obviously this is a bug. Please file a bug report at
http://bugs.kannel.org with any logs attached to prove your point, so
we can look at it later.

Thanks,
--
Enver



Re: emi/ucp NPID value

2007-02-13 Thread Enver ALTIN

On 2/12/07, Hofferek Attila [EMAIL PROTECTED] wrote:

Hofferek Attila írta:
 Hi!
...blah...
 tia

Ok, i've found those cfg values in rtfm to solve this, but...
in 53 reply, -my operator said (hungarian t-mobile)- there is no laid
and timestamp. How can I put those into the 53 reply?
00/00020/R/53/A///96


If you can read some C, I'd recommend taking a look at
gw/smsc/smsc_emi.c and see the differences between msg31 and msg53. I
have little experience with UCP, so the stuff you posted looks like
Hebrew to me.

-HTH
--
Enver


Re: i don't think so (Re: I found a serious bug in kannel !!)

2007-02-13 Thread avudz
Dear,

Thursday, September 21, 2006, 5:29:33 PM, Yudi menulis:

YW Hello Ady,

YW ok, the text: (test) is solved by add ''.
YW So, in smskannel.conf :
YW exec = /usr/local/bin/kannel_incoming %t %q '%a'

YW when i sent, text: (test)
YW 2006-09-19 06:33:04 [1399] [4] INFO: Starting to service (test) from
YW + to 1234
YW 2006-09-19 06:33:04 [1399] [4] INFO: No reply sent, denied.


YW but problem when i sent this text:
YW [EMAIL PROTECTED] (at 3 clock) how?! -/+ 30 $ cool 'n dry

YW there is error:
YW 2006-09-19 06:43:32 [1399] [4] INFO: Starting to service foo!msn.com
YW (at 3 clock) how?! -/+ 30 $ cool 'n dry from + to 1234
YW sh: -c: line 1: unexpected EOF while looking for matching `''
YW sh: -c: line 2: syntax error: unexpected end of file
YW 2006-09-19 06:43:32 [1399] [4] INFO: No reply sent, denied.


YW so what's wrong with that?
YW The problem is text: cool 'n dry

+++ i believe you already solve this problem, sorry i come up with old
thread again because i'm having same problem like urs :-)

i tried sending sms which contain ' ( also error, i believe this is
application error not kannel, i just want to know how you solve the
problem ? could you please share here ?

2007-02-13 18:44:48 [4368] [4] INFO: Starting delivery report SMSThrower from 
+62812699
2007-02-13 18:44:52 [4368] [4] INFO: Starting to service test \' test ) test \ 
 from +62812699 to 1234
sh: -c: line 0: syntax error near unexpected token `)'
sh: -c: line 0: `/usr/local/bin/kannel_incoming 2007-02-13+11:57:31 
%2B62812699 'test+%5C'+test+)+test+%5C''
2007-02-13 18:44:52 [4368] [4] INFO: No reply sent, denied.
2007-02-13 18:44:56 [4368] [4] INFO: Starting delivery report SMSThrower from 
+62812699
2007-02-13 18:46:41 [4368] [4] INFO: Starting to service test ( ) '  from 
+628136082 to 1234
sh: -c: line 0: unexpected EOF while looking for matching `''
sh: -c: line 1: syntax error: unexpected end of file
2007-02-13 18:46:41 [4368] [4] INFO: No reply sent, denied.
2007-02-13 18:47:29 [4368] [4] INFO: Starting to service ( from 
+628136082 to 1234
2007-02-13 18:47:29 [4368] [4] INFO: No reply sent, denied.
2007-02-13 18:47:48 [4368] [4] INFO: Starting to service ' from 
+628136082 to 1234
sh: -c: line 0: unexpected EOF while looking for matching `''
sh: -c: line 1: syntax error: unexpected end of file


in kannel, i put line like this :

group = sms-service
keyword = default
max-messages = 0
exec =/usr/local/bin/kannel_incoming %t %q '%a'

and for /usr/local/bin/kannel_incoming

i believe same like yours as well :

#!/bin/bash
KANNEL_PATH=/usr/local
KANNEL_FILE=`mktemp -q $KANNEL_PATH/cache/smsd/ERR.in.XX`
touch $KANNEL_FILE
chmod 666 $KANNEL_FILE
# exec = /usr/local/bin/kannel_incoming %t %q %a
# $1 : %t
# $2 : %q
# $3 : %a
echo -e $1\n$2  $KANNEL_FILE
echo $3  $KANNEL_FILE

i tried changing echo $3 to echo -e $3 still can't resolv :-)
i also read email from Stuart Beck to convert it to %28 but
stuck how to convert it :-) is there any doc that i can read about
this issue ? please advice.



-- 
Best regards,
  avudz




2 connections and use of allowed-smsc-id preferred-smsc-id

2007-02-13 Thread Juan Nin

Hi!

We got the following situation:  

A carrier requires us to configure a receiver connection to one IP 
address and a transmitter connection to another one.
Obviously in this setup, inbound messages will com through the receiver 
connection, and outboud must go through de transmitter one.


Till now, we've always worked on transceiver-mode, routing the outgoing 
messages through the same SMSC where messages come through,  which it's 
the most common situation


Our scripts are made to route MTs through the same smsc-id from where 
the MOs were received, so we must now route the outbound messages 
through the new transmitter connection, but using the same smsc-id of 
the receiver connection


We're thinking of using an allowed-smsc-id directive on the receiver 
connection, containing the receiver's smsc-id, and a preferred-smsc-id 
directive with the same receiver's smsc-id


Here's the conf we would use:

# Receiver connection
#
group = smsc
smsc  = smpp
interface-version = 34
smsc-id   = A
allowed-smsc-id   = A
host  = 196.168.1.1
receive-port  = 8038
port  = 0
smsc-username = myUsername
smsc-password = myPassword
enquire-link-interval = 300
system-type   = NULL
source-addr-ton   = 1
source-addr-npi   = 1
dest-addr-ton = 5
dest-addr-npi = 1
throughput= 5
address-range = 161
msg-id-type   = 0x01
log-file  = /var/log/kannel/mySmscA.log
log-level = 0

# Transmitter connection
#
group = smsc
smsc  = smpp
interface-version = 34
smsc-id   = B
allowed-smsc-id   = A
preferred-smsc-id = A
host  = 192.168.1.2
port  = 8038
receive-port  = 0
smsc-username = myUsername
smsc-password = myUsername
enquire-link-interval = 300
system-type   = NULL
source-addr-ton   = 1
source-addr-npi   = 1
dest-addr-ton = 5
dest-addr-npi = 1
throughput= 5
address-range = 161
msg-id-type   = 0x01
log-file  = /var/log/kannel/mySmscB.log
log-level = 0


Is this the correct way to accomplish the beheaviour we desire?
Also is it fine to use the:

allowed-smsc-id   = A

on the receiver connection or we don't need it since we got the 
preferred-smsc-id set in the transmitter connection?


Thnx in advance,

Juan



SMS operator globally

2007-02-13 Thread Goksie
Dear all,

Can someone give me  name of operators that can interconnect my smsc
inorder to send and receive sms globally?

Goksie





Connecting SMS globally.

2007-02-13 Thread Goksie
Dear all,

I am sorry for double posting, however, it was because i dont know if there is 
any commercial list for kannel. 

Can someone give me  name of operators that can interconnect my smsc inorder to 
send and receive sms globally?

Goksie




Re: 2 connections and use of allowed-smsc-id preferred-smsc-id

2007-02-13 Thread Juan Nin

well, it worked fine  :)

if anyone disagrees on something of this conf, pls let me know!!!

thnx

Juan

Juan Nin wrote:


Hi!

We got the following situation: 
A carrier requires us to configure a receiver connection to one IP 
address and a transmitter connection to another one.
Obviously in this setup, inbound messages will com through the 
receiver connection, and outboud must go through de transmitter one.


Till now, we've always worked on transceiver-mode, routing the 
outgoing messages through the same SMSC where messages come through,  
which it's the most common situation


Our scripts are made to route MTs through the same smsc-id from where 
the MOs were received, so we must now route the outbound messages 
through the new transmitter connection, but using the same smsc-id of 
the receiver connection


We're thinking of using an allowed-smsc-id directive on the receiver 
connection, containing the receiver's smsc-id, and a preferred-smsc-id 
directive with the same receiver's smsc-id


Here's the conf we would use:

# Receiver connection
#
group = smsc
smsc  = smpp
interface-version = 34
smsc-id   = A
allowed-smsc-id   = A
host  = 196.168.1.1
receive-port  = 8038
port  = 0
smsc-username = myUsername
smsc-password = myPassword
enquire-link-interval = 300
system-type   = NULL
source-addr-ton   = 1
source-addr-npi   = 1
dest-addr-ton = 5
dest-addr-npi = 1
throughput= 5
address-range = 161
msg-id-type   = 0x01
log-file  = /var/log/kannel/mySmscA.log
log-level = 0

# Transmitter connection
#
group = smsc
smsc  = smpp
interface-version = 34
smsc-id   = B
allowed-smsc-id   = A
preferred-smsc-id = A
host  = 192.168.1.2
port  = 8038
receive-port  = 0
smsc-username = myUsername
smsc-password = myUsername
enquire-link-interval = 300
system-type   = NULL
source-addr-ton   = 1
source-addr-npi   = 1
dest-addr-ton = 5
dest-addr-npi = 1
throughput= 5
address-range = 161
msg-id-type   = 0x01
log-file  = /var/log/kannel/mySmscB.log
log-level = 0


Is this the correct way to accomplish the beheaviour we desire?
Also is it fine to use the:

allowed-smsc-id   = A

on the receiver connection or we don't need it since we got the 
preferred-smsc-id set in the transmitter connection?


Thnx in advance,

Juan






help me please....

2007-02-13 Thread Tushar
 

 

Hi all,

 

 

   I m using kannel from last 1 month. I am able to send sms, wap push thru
kannel, but unable to receive any messages. Plz help me with the
configuration for receiving messages. Even I m not receiving DLRs. The
following is the log of bearerbox:

 

 

 

2007-02-07 17:15:51 [15840] [7] DEBUG:Octet string at 0x81cc2f0:

 

 2007-02-07 17:15:51 [15840] [7] DEBUG:  len:  113

 

 2007-02-07 17:15:51 [15840] [7] DEBUG:  size: 114

 

 2007-02-07 17:15:51 [15840] [7] DEBUG:  immutable: 0

 

 2007-02-07 17:15:51 [15840] [7] DEBUG:  data: 69 64 3a 34 35 43 42

 38 44 35 39 20 73 75 62 3a   id:45CB8D59 sub:

 

 2007-02-07 17:15:51 [15840] [7] DEBUG:  data: 20 20 30 20 64 6c 76

 72 64 3a 20 20 30 20 73 75 0 dlvrd:  0 su

 

 2007-02-07 17:15:51 [15840] [7] DEBUG:  data: 62 6d 69 74 20 64 61

 74 65 3a 30 37 30 32 30 37   bmit date:070207

 

 2007-02-07 17:15:51 [15840] [7] DEBUG:  data: 31 36 35 38 20 64 6f

 6e 65 20 64 61 74 65 3a 30   1658 done date:0

 

 2007-02-07 17:15:51 [15840] [7] DEBUG:  data: 37 30 32 30 37 31 36

 35 39 20 73 74 61 74 3a 44   702071659 stat:D

 

 2007-02-07 17:15:51 [15840] [7] DEBUG:  data: 45 4c 49 56 52 44 20

 65 72 72 3a 30 30 30 20 54   ELIVRD err:000 T

 

 2007-02-07 17:15:51 [15840] [7] DEBUG:  data: 65 78 74 3a 74 65 73

 74 20 6d 65 73 73 61 67 65   ext:test message

 

 2007-02-07 17:15:51 [15840] [7] DEBUG:  data: 34

 4

 

 2007-02-07 17:15:51 [15840] [7] DEBUG:Octet string dump ends.

 

 2007-02-07 17:15:51 [15840] [7] DEBUG:   message_state: 2 = 0x0002

 

 2007-02-07 17:15:51 [15840] [7] DEBUG:   receipted_message_id:

 45CB8D59

 

 2007-02-07 17:15:51 [15840] [7] DEBUG: SMPP PDU dump ends.

 

 2007-02-07 17:15:51 [15840] [7] DEBUG: SMPP[mysmpp] handle_pdu, got 

 DLR

 

 2007-02-07 17:15:51 [15840] [7] DEBUG: DLR[mysql]: Looking for DLR 

 smsc=mysmpp, ts=45CB8D59, dst=919820245371, type=1

 

 2007-02-07 17:15:51 [15840] [7] DEBUG: sql: SELECT mask, service, url, 

 source, destination, boxc FROM dlr WHERE smsc='mysmpp' AND 

 ts='45CB8D59';

 

 2007-02-07 17:15:51 [15840] [7] DEBUG: no rows found

 

 2007-02-07 17:15:51 [15840] [7] WARNING: DLR[mysql]: DLR for 

 DST919820245371 not found.

 

 2007-02-07 17:15:51 [15840] [7] ERROR: SMPP[mysmpp]: got DLR but could 

 not find message or was not interested in it id45CB8D59 

 dst919820245371, type1

 

 

 

 

 

Thanks and regards,

Tushar