DLR group patch bug or what?
Dears,
I have SMPP connection one RX and TX, when I send SMS using the TX
connection, the DLR back on the RX one, so I used this patch -DLR group -
http://www.nabble.com/Multiple-SMSCs-and-a-DLR-group-td8655999.html#a8655999
but I always get the following error
2008-11-24 22:48:41 [24613] [7] DEBUG: message_id: 4049149130
2008-11-24 22:48:41 [24613] [7] DEBUG: SMPP PDU dump ends.
2008-11-24 22:48:41 [24613] [7] DEBUG: DLR[mysql]: Adding DLR
smsc=MYDLRGROUP, *ts=1226084656*, src=9, dst=96xx, mask=31,
boxc=
2008-11-24 22:48:41 [24613] [7] DEBUG: sql: INSERT INTO dlr (smsc, ts,
source, destination, service, url, mask, boxc, status) VALUES ('MYDLRGROUP',
'1226084656', '9', '96xx', 'tester', '
http://localhost/my.php?status=%danswer=%A', '31', '', '0');
2008-11-24 22:48:41 [24613] [7] DEBUG: SMSC[MYTXCON]: creating DLR message
-
--
-
2008-11-24 22:49:01 [24613] [6] DEBUG: SMPP[MYRXCON] handle_pdu, got DLR
2008-11-24 22:49:01 [24613] [6] DEBUG: DLR[mysql]: Looking for DLR
smsc=MYDLRGROUP,* ts=4049149130*, dst=96xx, type=1
2008-11-24 22:49:01 [24613] [6] DEBUG: sql: SELECT mask, service, url,
source, destination, boxc FROM dlr WHERE smsc='MYDLRGROUP' AND *
ts='4049149130';*
2008-11-24 22:49:01 [24613] [6] DEBUG: no rows found
2008-11-24 22:49:01 [24613] [6] WARNING: DLR[mysql]: DLR from
SMSCMYDLRGROUP for DST96xx not found.
2008-11-24 22:49:01 [24613] [6] ERROR: SMPP[MYRXCON]: got DLR but could not
find message or was not interested in it id4049149130 dst96xx,
type1
*NOTE: the kannel when insert the DLR the ts === 1226084656(the timestamp)
when looking for the DLR ts =** **4049149130 which is the message id*
following my config =
group = smsc
smsc = smpp
smsc-id = MYRXCON
host = xx.xxx.xxx.xxx
port = 0
receive-port =
smsc-username = MYUSER
smsc-password = x
system-type = smtype
service-type = 200
dlr-group-id = MYDLRGROUP
allowed-smsc-id = MYRXCON
interface-version = 34
address-range = 9
max-pending-submits = 1
reconnect-delay = 10
source-addr-ton = 1
source-addr-npi = 1
dest-addr-ton = 1
dest-addr-npi = 1
bind-addr-ton = 1
bind-addr-npi = 1
msg-id-type = 0x01
log-file = /var/log/kannel/9.log
log-level = 0
group = smsc
smsc = smpp
smsc-id = MYTXCON
host = xx.xxx.xxx.xxx
port =
receive-port = 0
smsc-username = MYUSER
smsc-password = x
system-type = smtype
service-type = 200
dlr-group-id = MYDLRGROUP
allowed-smsc-id = MYTXCON
interface-version = 34
address-range = 9
max-pending-submits = 1
reconnect-delay = 10
source-addr-ton = 5
source-addr-npi = 1
dest-addr-ton = 1
dest-addr-npi = 1
bind-addr-ton = 1
bind-addr-npi = 1
msg-id-type = 0x01
log-file = /var/log/kannel/9.log
log-level = 0
Any Ideas what is the problem, please ?
Regards,
Hafez
Re: DLR group patch bug or what?
On Tue, Nov 25, 2008 at 9:26 AM, hafez ahmad [EMAIL PROTECTED] wrote: NOTE: the kannel when insert the DLR the ts === 1226084656(the timestamp) when looking for the DLR ts = 4049149130 which is the message id following my config = msg-id-type = 0x01 Are you sure that you should use 0x01, deliver_sm is sent in decimal and submit_sm is in hex? Usually this problems with unmatched DLR happen because kannel is not configured correctly for the number format of the deliver_sm and sumbit_sm ids, for example: the SMSC sends the deliver_sm in decimal format but Kannel is configured that the deliver_sm is in hex format. HTH, Jovan
unsubscribe
Re: DLR group patch bug or what?
i assume you use identical user pass system-type values
so,
use this single smsc config instead of the two separated:
group = smsc
smsc = smpp
smsc-id = MYRXCON
host = xx.xxx.xxx.xxx
port = the port for MYTXCON
receive-port =
smsc-username = MYUSER
smsc-password = x
system-type = smtype
service-type = 200
dlr-group-id = MYDLRGROUP
allowed-smsc-id = MYRXCON
interface-version = 34
address-range = 9
max-pending-submits = 1
reconnect-delay = 10
source-addr-ton = 1
source-addr-npi = 1
dest-addr-ton = 1
dest-addr-npi = 1
bind-addr-ton = 1
bind-addr-npi = 1
msg-id-type = 0x01
log-file = /var/log/kannel/9.log
log-level = 0
cheers
hafez ahmad wrote:
Dears,
I have SMPP connection one RX and TX, when I send SMS using the TX
connection, the DLR back on the RX one, so I used this patch -DLR group -
http://www.nabble.com/Multiple-SMSCs-and-a-DLR-group-td8655999.html#a8655999
but I always get the following error
2008-11-24 22:48:41 [24613] [7] DEBUG: message_id: 4049149130
2008-11-24 22:48:41 [24613] [7] DEBUG: SMPP PDU dump ends.
2008-11-24 22:48:41 [24613] [7] DEBUG: DLR[mysql]: Adding DLR
smsc=MYDLRGROUP, *ts=1226084656*, src=9, dst=96xx, mask=31,
boxc=
2008-11-24 22:48:41 [24613] [7] DEBUG: sql: INSERT INTO dlr (smsc, ts,
source, destination, service, url, mask, boxc, status) VALUES ('MYDLRGROUP',
'1226084656', '9', '96xx', 'tester', '
http://localhost/my.php?status=%danswer=%A', '31', '', '0');
2008-11-24 22:48:41 [24613] [7] DEBUG: SMSC[MYTXCON]: creating DLR message
-
--
-
2008-11-24 22:49:01 [24613] [6] DEBUG: SMPP[MYRXCON] handle_pdu, got DLR
2008-11-24 22:49:01 [24613] [6] DEBUG: DLR[mysql]: Looking for DLR
smsc=MYDLRGROUP,* ts=4049149130*, dst=96xx, type=1
2008-11-24 22:49:01 [24613] [6] DEBUG: sql: SELECT mask, service, url,
source, destination, boxc FROM dlr WHERE smsc='MYDLRGROUP' AND *
ts='4049149130';*
2008-11-24 22:49:01 [24613] [6] DEBUG: no rows found
2008-11-24 22:49:01 [24613] [6] WARNING: DLR[mysql]: DLR from
SMSCMYDLRGROUP for DST96xx not found.
2008-11-24 22:49:01 [24613] [6] ERROR: SMPP[MYRXCON]: got DLR but could not
find message or was not interested in it id4049149130 dst96xx,
type1
*NOTE: the kannel when insert the DLR the ts === 1226084656(the timestamp)
when looking for the DLR ts =** **4049149130 which is the message id*
following my config =
group = smsc
smsc = smpp
smsc-id = MYRXCON
host = xx.xxx.xxx.xxx
port = 0
receive-port =
smsc-username = MYUSER
smsc-password = x
system-type = smtype
service-type = 200
dlr-group-id = MYDLRGROUP
allowed-smsc-id = MYRXCON
interface-version = 34
address-range = 9
max-pending-submits = 1
reconnect-delay = 10
source-addr-ton = 1
source-addr-npi = 1
dest-addr-ton = 1
dest-addr-npi = 1
bind-addr-ton = 1
bind-addr-npi = 1
msg-id-type = 0x01
log-file = /var/log/kannel/9.log
log-level = 0
group = smsc
smsc = smpp
smsc-id = MYTXCON
host = xx.xxx.xxx.xxx
port =
receive-port = 0
smsc-username = MYUSER
smsc-password = x
system-type = smtype
service-type = 200
dlr-group-id = MYDLRGROUP
allowed-smsc-id = MYTXCON
interface-version = 34
address-range = 9
max-pending-submits = 1
reconnect-delay = 10
source-addr-ton = 5
source-addr-npi = 1
dest-addr-ton = 1
dest-addr-npi = 1
bind-addr-ton = 1
bind-addr-npi = 1
msg-id-type = 0x01
log-file = /var/log/kannel/9.log
log-level = 0
Any Ideas what is the problem, please ?
Regards,
Hafez
Message queueing on sms push gateway
Hello, I'm looking at Kannel to possibly use as a fix to an issue we're having with our present sms push of content to the wireless carriers in Canada. My question is, If I have multiple outgoing sms centers defined do they each have their own queue for messages received by our content generator? The reason for this is to determine how Kannel provides protection or guarantee that messages for carriers A,B,C are not affected by carrier D being unavailable and does the backlog of messages for carrier D have an adverse effect on carriers A,B or C? Richard Andrews Systems Administrator - IT Operations Pelmorex Media Inc.
Re: Message queueing on sms push gateway
Dear Andy, Kannel is pretty flexible in its configuration. Bearerbox will do routing as well as load balancing using rand(). The queue is single and sms' are queued based on availability of servers. If carrier D is unavailable the sms will be picked up sometime later by another smsc based on the rand(). Which means that there might be a small delay to pushes for carrier D as are rerouted and picked up by other SMScs. Additionaly each push SMS-user can specify forced-smsc and default-smsc. Any smsc definition can specify denied-smsc-id, allowed-smsc-id and preferred-smsc-id. With these 2 options you can have either sms to D accumulating until D is up and ready, picked up by other smsc after they fail (delay) on D or you can route all sms to the available smscs directly (no delay). BR, Nikos - Original Message - From: Richard Andrews [EMAIL PROTECTED] To: users@kannel.org Sent: Tuesday, November 25, 2008 9:28 PM Subject: Message queueing on sms push gateway Hello, I'm looking at Kannel to possibly use as a fix to an issue we're having with our present sms push of content to the wireless carriers in Canada. My question is, If I have multiple outgoing sms centers defined do they each have their own queue for messages received by our content generator? The reason for this is to determine how Kannel provides protection or guarantee that messages for carriers A,B,C are not affected by carrier D being unavailable and does the backlog of messages for carrier D have an adverse effect on carriers A,B or C? Richard Andrews Systems Administrator - IT Operations Pelmorex Media Inc.
