date:20060620

Re: Massive SMS sent

2006-06-20 Thread Chronis N.




Giasou Kiriako,
 
Efraristo poly gia to minima.
Twra, stelvo sto kannel 10.000 sms / 20 secs. Ala 
ithela va do ama baroussa va ta stelvo pio rgrigora.
 
Ama 8eis, grapsta sta englika pio efkola eivai gia 
ollous.
 
Niko.

  - Original Message - 
  From: 
  Kiriakos 
  Tsourapas 
  To: [EMAIL PROTECTED] 
  Sent: Tuesday, June 20, 2006 8:43 
AM
  Subject: RE: Massive SMS sent
  ΚαλημέραΕίδα το μήνυμά σου στη λίστα του 
  kannel.Δουλεύω καιρό τώρα πάνω σε μαζικές αποστολές.Αν μου πεις τι 
  ακριβώς θες να κάνεις ίσως μπορώνα βοηθήσω.Πως θες να τα στείλεις 
  τα SMS? το kannel με τι το συνδέεις ?Θες να γίνεται αυτόματα η 
  αποστόλή ή κάποιος χρήστηςθα τα στέλνει όταν θέλει ?Εγώ έχω 
  φτιάξει μια εφαρμογή η οποία συνδέεταιαπευθείας σε SMSCs (CIMD ή SMPP) για 
  μαζικέςαποστολές μηνυμάτων (μιλάω για εκατομύρια όχι 
  χιλιάδες).Φιλικά Κυριάκος 
Τσουράπας

Re: Massive SMS sent

2006-06-20 Thread Julien Buratto

Yo guys this is an english-spoken list :-D
Let us understand your thoughts :-D

J

Chronis N. ha scritto:
> Giasou Kiriako,
>  
> Efraristo poly gia to minima.
> Twra, stelvo sto kannel 10.000 sms / 20 secs. Ala ithela va do ama
> baroussa va ta stelvo pio rgrigora.
>  
> Ama 8eis, grapsta sta englika pio efkola eivai gia ollous.
>  
> Niko.
> 
> - Original Message -
> *From:* Kiriakos Tsourapas 
> *To:* [EMAIL PROTECTED] 
> *Sent:* Tuesday, June 20, 2006 8:43 AM
> *Subject:* RE: Massive SMS sent
> 
> Καλημέρα
> 
> Είδα το μήνυμά σου στη λίστα του kannel.
> Δουλεύω καιρό τώρα πάνω σε μαζικές αποστολές.
> Αν μου πεις τι ακριβώς θες να κάνεις ίσως μπορώ
> να βοηθήσω.
> 
> Πως θες να τα στείλεις τα SMS? το kannel με τι το
> συνδέεις ?
> Θες να γίνεται αυτόματα η αποστόλή ή κάποιος χρήστης
> θα τα στέλνει όταν θέλει ?
> 
> Εγώ έχω φτιάξει μια εφαρμογή η οποία συνδέεται
> απευθείας σε SMSCs (CIMD ή SMPP) για μαζικές
> αποστολές μηνυμάτων (μιλάω για εκατομύρια όχι
> χιλιάδες).
> 
> 
> Φιλικά
> Κυριάκος Τσουράπας

Re: Massive SMS sent

2006-06-20 Thread Chronis N.

Hello,

That's what I just told to him ;)

Nikos
- Original Message - 
From: "Julien Buratto" <[EMAIL PROTECTED]>

To: "Chronis N." <[EMAIL PROTECTED]>
Cc: "Kiriakos Tsourapas" <[EMAIL PROTECTED]>; 
Sent: Tuesday, June 20, 2006 11:29 AM
Subject: Re: Massive SMS sent

Yo guys this is an english-spoken list :-D
Let us understand your thoughts :-D

J

Chronis N. ha scritto:

Giasou Kiriako,

Efraristo poly gia to minima.
Twra, stelvo sto kannel 10.000 sms / 20 secs. Ala ithela va do ama
baroussa va ta stelvo pio rgrigora.

Ama 8eis, grapsta sta englika pio efkola eivai gia ollous.

Niko.

- Original Message -
*From:* Kiriakos Tsourapas 
*To:* [EMAIL PROTECTED] 
*Sent:* Tuesday, June 20, 2006 8:43 AM
*Subject:* RE: Massive SMS sent

Καλημέρα

Είδα το μήνυμά σου στη λίστα του kannel.
Δουλεύω καιρό τώρα πάνω σε μαζικές αποστολές.
Αν μου πεις τι ακριβώς θες να κάνεις ίσως μπορώ
να βοηθήσω.

Πως θες να τα στείλεις τα SMS? το kannel με τι το
συνδέεις ?
Θες να γίνεται αυτόματα η αποστόλή ή κάποιος χρήστης
θα τα στέλνει όταν θέλει ?

Εγώ έχω φτιάξει μια εφαρμογή η οποία συνδέεται
απευθείας σε SMSCs (CIMD ή SMPP) για μαζικές
αποστολές μηνυμάτων (μιλάω για εκατομύρια όχι
χιλιάδες).

Φιλικά
Κυριάκος Τσουράπας

Error receiving DLRs

2006-06-20 Thread Fourat Zouari

Hello all,Am having errors in my logs saying that i have problems receiving DLRs, let's let this bearerbox log talk about it :-- BEGIN PASTING2006-06-20 16:57:08 [801] [6] DEBUG: DLR[pgsql]: Adding DLR smsc=SMPP-01-BB, ts=5B03, src="" dst=28347018, mask=31, boxc=
2006-06-20 16:57:08 [801] [6] DEBUG: sql: INSERT INTO dlr (smsc, date, soa, da, service, url, mask, boxcid, status) VALUES ('SMPP-01-BB', '5B03', '17700', '28347018', 'tt', '
http://localhost/servlets/recdlr.php?&status=%d&answer=%A&ts=%t&msgid=165574', '31', '', '0');2006-06-20 16:57:08 [801] [6] DEBUG: SMSC[SMPP-01-BB]: creating DLR message2006-06-20 16:57:08 [801] [6] DEBUG: SMSC[SMPP-01-BB]: DLR = 
http://localhost/servlets/recdlr.php?&status=%d&answer=%A&ts=%t&msgid=1655742006-06-20 16:57:08 [837] [20] DEBUG: send_msg: sending msg to box: <
127.0.0.1>2006-06-20 16:57:08 [837] [20] DEBUG: boxc_sender: sent message to <127.0.0.1>2006-06-20 16:57:08 [836] [19] DEBUG: boxc_receiver: got ack
2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'.2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Created HTTPClient area 0x8258b28.2006-06-20 16:57:09 [798] [3] DEBUG: sql: SELECT count(*) FROM dlr;
2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient area 0x8258b28.2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'.2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'.
2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Created HTTPClient area 0x8258b28.2006-06-20 16:57:09 [798] [3] DEBUG: sql: SELECT count(*) FROM dlr;2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient area 0x8258b28.
2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'.2006-06-20 16:57:15 [803] [8] DEBUG: SMPP[SMPP-01-TZ]: Sending enquire link:2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU 0x8258d48 dump:
2006-06-20 16:57:15 [803] [8] DEBUG:   type_name: enquire_link2006-06-20 16:57:15 [803] [8] DEBUG:   command_id: 21 = 0x00152006-06-20 16:57:15 [803] [8] DEBUG:   command_status: 0 = 0x2006-06-20 16:57:15 [803] [8] DEBUG:   sequence_number: 23806 = 0x5cfe
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU dump ends.2006-06-20 16:57:15 [803] [8] DEBUG: SMPP[SMPP-01-TZ]: Got PDU:2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU 0x8258d48 dump:2006-06-20 16:57:15 [803] [8] DEBUG:   type_name: enquire_link_resp
2006-06-20 16:57:15 [803] [8] DEBUG:   command_id: 2147483669 = 0x80152006-06-20 16:57:15 [803] [8] DEBUG:   command_status: 0 = 0x2006-06-20 16:57:15 [803] [8] DEBUG:   sequence_number: 23806 = 0x5cfe
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU dump ends.2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB]: Got PDU:2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU 0x8258d48 dump:2006-06-20 16:57:16 [802] [7] DEBUG:   type_name: deliver_sm
2006-06-20 16:57:16 [802] [7] DEBUG:   command_id: 5 = 0x00052006-06-20 16:57:16 [802] [7] DEBUG:   command_status: 0 = 0x2006-06-20 16:57:16 [802] [7] DEBUG:   sequence_number: 180 = 0x00b4
2006-06-20 16:57:16 [802] [7] DEBUG:   service_type: NULL2006-06-20 16:57:16 [802] [7] DEBUG:   source_addr_ton: 2 = 0x00022006-06-20 16:57:16 [802] [7] DEBUG:   source_addr_npi: 1 = 0x00012006-06-20 16:57:16 [802] [7] DEBUG:   source_addr: "28347018"
2006-06-20 16:57:16 [802] [7] DEBUG:   dest_addr_ton: 2 = 0x00022006-06-20 16:57:16 [802] [7] DEBUG:   dest_addr_npi: 1 = 0x00012006-06-20 16:57:16 [802] [7] DEBUG:   destination_addr: "17700"
2006-06-20 16:57:16 [802] [7] DEBUG:   esm_class: 4 = 0x00042006-06-20 16:57:16 [802] [7] DEBUG:   protocol_id: 0 = 0x2006-06-20 16:57:16 [802] [7] DEBUG:   priority_flag: 0 = 0x2006-06-20 16:57:16 [802] [7] DEBUG:   schedule_delivery_time: NULL
2006-06-20 16:57:16 [802] [7] DEBUG:   validity_period: NULL2006-06-20 16:57:16 [802] [7] DEBUG:   registered_delivery: 0 = 0x2006-06-20 16:57:16 [802] [7] DEBUG:   replace_if_present_flag: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG:   data_coding: 0 = 0x2006-06-20 16:57:16 [802] [7] DEBUG:   sm_default_msg_id: 0 = 0x2006-06-20 16:57:16 [802] [7] DEBUG:   sm_length: 12 = 0x000c2006-06-20 16:57:16 [802] [7] DEBUG:   short_message: "5B03 201"
2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU dump ends.2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB] handle_pdu, got DLR2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB]: Couldnot parse DLR string sscanf way,fallback to old way. Please report!
2006-06-20 16:57:16 [802] [7] ERROR: SMPP[SMPP-01-BB]: got DLR but could not find message or was not interested in it id<> dst<28347018>, type<2>2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB]: Sending PDU:
2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU 0x8258e20 dump:2006-06-20 16:57:16 [802] [7] DEBUG:   type_name: deliver_sm_resp2006-06-20 16:57:16 [802] [7] DEBUG:   command_id: 2147483653 = 0x8005-

Re: Error receiving DLRs

2006-06-20 Thread Julien Buratto

Does the DLR gets correctly saved in the db ?

Fourat Zouari ha scritto:
> Hello all,
> Am having errors in my logs saying that i have problems receiving DLRs,
> let's let this bearerbox log talk about it :
> 
> -- BEGIN PASTING
> 2006-06-20 16:57:08 [801] [6] DEBUG: DLR[pgsql]: Adding DLR
> smsc=SMPP-01-BB, ts=5B03, src=17700, dst=28347018, mask=31, boxc=
> 2006-06-20 16:57:08 [801] [6] DEBUG: sql: INSERT INTO dlr (smsc, date,
> soa, da, service, url, mask, boxcid, status) VALUES ('SMPP-01-BB',
> '5B03', '17700', '28347018', 'tt', '
> http://localhost/servlets/recdlr.php?&status=%d&answer=%A&ts=%t&msgid=165574
> ',
> '31', '', '0');
> 2006-06-20 16:57:08 [801] [6] DEBUG: SMSC[SMPP-01-BB]: creating DLR message
> 2006-06-20 16:57:08 [801] [6] DEBUG: SMSC[SMPP-01-BB]: DLR =
> http://localhost/servlets/recdlr.php?&status=%d&answer=%A&ts=%t&msgid=165574
> 
> 2006-06-20 16:57:08 [837] [20] DEBUG: send_msg: sending msg to box: <
> 127.0.0.1 >
> 2006-06-20 16:57:08 [837] [20] DEBUG: boxc_sender: sent message to
> <127.0.0.1 >
> 2006-06-20 16:57:08 [836] [19] DEBUG: boxc_receiver: got ack
> 2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Creating HTTPClient for
> `127.0.0.1'.
> 2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Created HTTPClient area
> 0x8258b28.
> 2006-06-20 16:57:09 [798] [3] DEBUG: sql: SELECT count(*) FROM dlr;
> 2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient area
> 0x8258b28.
> 2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient for
> `127.0.0.1'.
> 2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Creating HTTPClient for
> `127.0.0.1'.
> 2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Created HTTPClient area
> 0x8258b28.
> 2006-06-20 16:57:09 [798] [3] DEBUG: sql: SELECT count(*) FROM dlr;
> 2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient area
> 0x8258b28.
> 2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient for
> `127.0.0.1'.
> 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP[SMPP-01-TZ]: Sending enquire link:
> 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU 0x8258d48 dump:
> 2006-06-20 16:57:15 [803] [8] DEBUG:   type_name: enquire_link
> 2006-06-20 16:57:15 [803] [8] DEBUG:   command_id: 21 = 0x0015
> 2006-06-20 16:57:15 [803] [8] DEBUG:   command_status: 0 = 0x
> 2006-06-20 16:57:15 [803] [8] DEBUG:   sequence_number: 23806 = 0x5cfe
> 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU dump ends.
> 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP[SMPP-01-TZ]: Got PDU:
> 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU 0x8258d48 dump:
> 2006-06-20 16:57:15 [803] [8] DEBUG:   type_name: enquire_link_resp
> 2006-06-20 16:57:15 [803] [8] DEBUG:   command_id: 2147483669 = 0x8015
> 2006-06-20 16:57:15 [803] [8] DEBUG:   command_status: 0 = 0x
> 2006-06-20 16:57:15 [803] [8] DEBUG:   sequence_number: 23806 = 0x5cfe
> 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU dump ends.
> 2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB]: Got PDU:
> 2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU 0x8258d48 dump:
> 2006-06-20 16:57:16 [802] [7] DEBUG:   type_name: deliver_sm
> 2006-06-20 16:57:16 [802] [7] DEBUG:   command_id: 5 = 0x0005
> 2006-06-20 16:57:16 [802] [7] DEBUG:   command_status: 0 = 0x
> 2006-06-20 16:57:16 [802] [7] DEBUG:   sequence_number: 180 = 0x00b4
> 2006-06-20 16:57:16 [802] [7] DEBUG:   service_type: NULL
> 2006-06-20 16:57:16 [802] [7] DEBUG:   source_addr_ton: 2 = 0x0002
> 2006-06-20 16:57:16 [802] [7] DEBUG:   source_addr_npi: 1 = 0x0001
> 2006-06-20 16:57:16 [802] [7] DEBUG:   source_addr: "28347018"
> 2006-06-20 16:57:16 [802] [7] DEBUG:   dest_addr_ton: 2 = 0x0002
> 2006-06-20 16:57:16 [802] [7] DEBUG:   dest_addr_npi: 1 = 0x0001
> 2006-06-20 16:57:16 [802] [7] DEBUG:   destination_addr: "17700"
> 2006-06-20 16:57:16 [802] [7] DEBUG:   esm_class: 4 = 0x0004
> 2006-06-20 16:57:16 [802] [7] DEBUG:   protocol_id: 0 = 0x
> 2006-06-20 16:57:16 [802] [7] DEBUG:   priority_flag: 0 = 0x
> 2006-06-20 16:57:16 [802] [7] DEBUG:   schedule_delivery_time: NULL
> 2006-06-20 16:57:16 [802] [7] DEBUG:   validity_period: NULL
> 2006-06-20 16:57:16 [802] [7] DEBUG:   registered_delivery: 0 = 0x
> 2006-06-20 16:57:16 [802] [7] DEBUG:   replace_if_present_flag: 0 =
> 0x
> 2006-06-20 16:57:16 [802] [7] DEBUG:   data_coding: 0 = 0x
> 2006-06-20 16:57:16 [802] [7] DEBUG:   sm_default_msg_id: 0 = 0x
> 2006-06-20 16:57:16 [802] [7] DEBUG:   sm_length: 12 = 0x000c
> 2006-06-20 16:57:16 [802] [7] DEBUG:   short_message: "5B03 201"
> 2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU dump ends.
> 2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB] handle_pdu, got DLR
> 2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB]: Couldnot parse
> D

Re: Error receiving DLRs

2006-06-20 Thread Julien Buratto

However it seems you don't receive the ID of the message from the smpp
server ?
J


Fourat Zouari ha scritto:
> Hello all,
> Am having errors in my logs saying that i have problems receiving DLRs,
> let's let this bearerbox log talk about it :
> 
> -- BEGIN PASTING
> 2006-06-20 16:57:08 [801] [6] DEBUG: DLR[pgsql]: Adding DLR
> smsc=SMPP-01-BB, ts=5B03, src=17700, dst=28347018, mask=31, boxc=
> 2006-06-20 16:57:08 [801] [6] DEBUG: sql: INSERT INTO dlr (smsc, date,
> soa, da, service, url, mask, boxcid, status) VALUES ('SMPP-01-BB',
> '5B03', '17700', '28347018', 'tt', '
> http://localhost/servlets/recdlr.php?&status=%d&answer=%A&ts=%t&msgid=165574
> ',
> '31', '', '0');
> 2006-06-20 16:57:08 [801] [6] DEBUG: SMSC[SMPP-01-BB]: creating DLR message
> 2006-06-20 16:57:08 [801] [6] DEBUG: SMSC[SMPP-01-BB]: DLR =
> http://localhost/servlets/recdlr.php?&status=%d&answer=%A&ts=%t&msgid=165574
> 
> 2006-06-20 16:57:08 [837] [20] DEBUG: send_msg: sending msg to box: <
> 127.0.0.1 >
> 2006-06-20 16:57:08 [837] [20] DEBUG: boxc_sender: sent message to
> <127.0.0.1 >
> 2006-06-20 16:57:08 [836] [19] DEBUG: boxc_receiver: got ack
> 2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Creating HTTPClient for
> `127.0.0.1'.
> 2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Created HTTPClient area
> 0x8258b28.
> 2006-06-20 16:57:09 [798] [3] DEBUG: sql: SELECT count(*) FROM dlr;
> 2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient area
> 0x8258b28.
> 2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient for
> `127.0.0.1'.
> 2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Creating HTTPClient for
> `127.0.0.1'.
> 2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Created HTTPClient area
> 0x8258b28.
> 2006-06-20 16:57:09 [798] [3] DEBUG: sql: SELECT count(*) FROM dlr;
> 2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient area
> 0x8258b28.
> 2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient for
> `127.0.0.1'.
> 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP[SMPP-01-TZ]: Sending enquire link:
> 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU 0x8258d48 dump:
> 2006-06-20 16:57:15 [803] [8] DEBUG:   type_name: enquire_link
> 2006-06-20 16:57:15 [803] [8] DEBUG:   command_id: 21 = 0x0015
> 2006-06-20 16:57:15 [803] [8] DEBUG:   command_status: 0 = 0x
> 2006-06-20 16:57:15 [803] [8] DEBUG:   sequence_number: 23806 = 0x5cfe
> 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU dump ends.
> 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP[SMPP-01-TZ]: Got PDU:
> 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU 0x8258d48 dump:
> 2006-06-20 16:57:15 [803] [8] DEBUG:   type_name: enquire_link_resp
> 2006-06-20 16:57:15 [803] [8] DEBUG:   command_id: 2147483669 = 0x8015
> 2006-06-20 16:57:15 [803] [8] DEBUG:   command_status: 0 = 0x
> 2006-06-20 16:57:15 [803] [8] DEBUG:   sequence_number: 23806 = 0x5cfe
> 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU dump ends.
> 2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB]: Got PDU:
> 2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU 0x8258d48 dump:
> 2006-06-20 16:57:16 [802] [7] DEBUG:   type_name: deliver_sm
> 2006-06-20 16:57:16 [802] [7] DEBUG:   command_id: 5 = 0x0005
> 2006-06-20 16:57:16 [802] [7] DEBUG:   command_status: 0 = 0x
> 2006-06-20 16:57:16 [802] [7] DEBUG:   sequence_number: 180 = 0x00b4
> 2006-06-20 16:57:16 [802] [7] DEBUG:   service_type: NULL
> 2006-06-20 16:57:16 [802] [7] DEBUG:   source_addr_ton: 2 = 0x0002
> 2006-06-20 16:57:16 [802] [7] DEBUG:   source_addr_npi: 1 = 0x0001
> 2006-06-20 16:57:16 [802] [7] DEBUG:   source_addr: "28347018"
> 2006-06-20 16:57:16 [802] [7] DEBUG:   dest_addr_ton: 2 = 0x0002
> 2006-06-20 16:57:16 [802] [7] DEBUG:   dest_addr_npi: 1 = 0x0001
> 2006-06-20 16:57:16 [802] [7] DEBUG:   destination_addr: "17700"
> 2006-06-20 16:57:16 [802] [7] DEBUG:   esm_class: 4 = 0x0004
> 2006-06-20 16:57:16 [802] [7] DEBUG:   protocol_id: 0 = 0x
> 2006-06-20 16:57:16 [802] [7] DEBUG:   priority_flag: 0 = 0x
> 2006-06-20 16:57:16 [802] [7] DEBUG:   schedule_delivery_time: NULL
> 2006-06-20 16:57:16 [802] [7] DEBUG:   validity_period: NULL
> 2006-06-20 16:57:16 [802] [7] DEBUG:   registered_delivery: 0 = 0x
> 2006-06-20 16:57:16 [802] [7] DEBUG:   replace_if_present_flag: 0 =
> 0x
> 2006-06-20 16:57:16 [802] [7] DEBUG:   data_coding: 0 = 0x
> 2006-06-20 16:57:16 [802] [7] DEBUG:   sm_default_msg_id: 0 = 0x
> 2006-06-20 16:57:16 [802] [7] DEBUG:   sm_length: 12 = 0x000c
> 2006-06-20 16:57:16 [802] [7] DEBUG:   short_message: "5B03 201"
> 2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU dump ends.
> 2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB] handle_pdu, got DLR
> 2006-06-20 16:57:16 [802] [7] DEBUG:

RE: What about PDU? - Re: SMPP 3.4 Optional params

2006-06-20 Thread Souza, Jeffrey R.

I've actually implemented in Kannel the ability to give smsbox a 
raw PDU (X-Kannel-PDU parameter) for it to send and to get from 
Kannel the raw PDU of a received message (I chose %x because %p
%d and %u were already taken).
I even implemented it so if X-Kannel-To is present with X-Kannel-PDU
it will replace the outgoing number in the PDU with the number in
the X-Kannel-To parameter, sort of a forwarding mechanism without
requiring the holder of the PDU to know how to change the number 
in the PDU.

I haven't submitted my changes back to the list because I wasn't 
sure how many others would find it useful. If others chime in 
that it would be handy I suppose I could work up the diffs
and send them as a patch. I'll also need to bring the files that
changed up to date with CVS as these changes were done to 1.4.0
and I'm behind in my patches. 

Also I'd want someone more familiar with the code to examine my 
mods to make sure they're not just naïve tweaks that are incomplete
and don't take into account the big picture and all possible uses.
I only use bearerbox and smsbox so I'm not sure if there are any 
repercussions of this for wapbox.

J.R.(Sydd)Souza

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Nikola Goran Cutura
Sent: Wednesday, June 07, 2006 1:52 PM
To: users@kannel.org
Subject: What about PDU? - Re: SMPP 3.4 Optional params


Besides Kannel's intention to abstract specific protocols, I believe that 
passing complete PDU would have great value, too. People not familiar with 
protocols find great value in being able to use Kannel's abstractions but 
developers faimiliar with protocols (like myself) may feel better parsing 
and composing PDUs on their own.

This specific case with SMPP optional headers is a very good use case. There 
is a need NOW for optional headers. However, Kannel has its own architecture 
and some time has to be spent to design the necessary changes in generic 
fashion. Meanwhile, users would use ability to construct PDU and send it via 
Kannel. After the implementation, users would switch to Kannel's generic way 
of dealing with optional parameters as it is always better to use Kannel's 
generic features than to reinvent them.

To summarize my suggestion, I would like to have possibility to obtain PDU 
either as '%some_letter" or in HTTP header from Kannel when receiving and to 
be able to specify PDU to Kannel when sending. smsc-id would give the 
information on protocol since each configured smsc connection has also 
protocol specified and PDU would be given as array of bytes..

Would it be hard to implement in Kannel?

Regards,
NGC

RE: USB Modem supported ?

2006-06-20 Thread Souza, Jeffrey R.

I've gotten MultiTech (formerly Wavecom) USB GSM Modems Model MTCBA-G-U-F1
to work with Kannel under Linux kernel 2.6.12.2 and Debian. As near as
I can tell these modems are the same guts as their serial versions but
they added a USB-Serial device inside and they get their power from the
USB bus (so if you use a hub it may need to be a powered hub). Seems
like a sensible solution. You access them through /dev/ttyUSB# rather
than /dev/ttyS#. I believe they cost in the area of 200-300 USD.
http://www.multitech.com/PRODUCTS/Families/MultiModemGPRS/

J.R.(Sydd)Souza

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Stipe Tolj
Sent: Sunday, June 11, 2006 10:03 PM
To: Julien Buratto
Cc: users@kannel.org
Subject: Re: USB Modem supported ?

Julien Buratto wrote:

> Leonard ha scritto:
> 
>>Could not say for sure, but if it supports AT command set and is CDC-ACM
>>complaint it should work.. (on linux box anyways.)
>>
>>Can you please mail me off list with the details. we require a stack of
>>modems as well
> 
> 
> Yep it works! :D
> I have some problems with my Redhat 9 USB support, but it works perfect
> on  Fedora Core 3.
> 
> Note: on that redhat 9 I always had usb problems, so is not
> modem-related trouble.
> 
> If you need some, write me directly.

nevertheless it may be interesting for others from the list to know which 
vendor 
this is of the specific GSM modem and how much the pricing is?

We may get into touch with the manufacturer to promote the device if it works 
reliable and it's a price breaker ;)

Stipe

---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany

tolj.org system architecture  Kannel Software Foundation (KSF)
http://www.tolj.org/  http://www.kannel.org/

mailto:st_{at}_tolj.org   mailto:stolj_{at}_kannel.org
---

Re: USB Modem supported ?

2006-06-20 Thread Linkas





Yes, the solution I found is the same and costs around 150€.
Usb powered with antenna really easy to access, has also gprs for mms.
I am using it under fedora core 3.

J

Souza, Jeffrey R. ha scritto:

  I've gotten MultiTech (formerly Wavecom) USB GSM Modems Model MTCBA-G-U-F1
to work with Kannel under Linux kernel 2.6.12.2 and Debian. As near as
I can tell these modems are the same guts as their serial versions but
they added a USB-Serial device inside and they get their power from the
USB bus (so if you use a hub it may need to be a powered hub). Seems
like a sensible solution. You access them through /dev/ttyUSB# rather
than /dev/ttyS#. I believe they cost in the area of 200-300 USD.
http://www.multitech.com/PRODUCTS/Families/MultiModemGPRS/

J.R.(Sydd)Souza

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Stipe Tolj
Sent: Sunday, June 11, 2006 10:03 PM
To: Julien Buratto
Cc: users@kannel.org
Subject: Re: USB Modem supported ?


Julien Buratto wrote:

  
  
Leonard ha scritto:



  Could not say for sure, but if it supports AT command set and is CDC-ACM
complaint it should work.. (on linux box anyways.)

Can you please mail me off list with the details. we require a stack of
modems as well
  


Yep it works! :D
I have some problems with my Redhat 9 USB support, but it works perfect
on  Fedora Core 3.

Note: on that redhat 9 I always had usb problems, so is not
modem-related trouble.

If you need some, write me directly.

  
  
nevertheless it may be interesting for others from the list to know which vendor 
this is of the specific GSM modem and how much the pricing is?

We may get into touch with the manufacturer to promote the device if it works 
reliable and it's a price breaker ;)

Stipe

---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany

tolj.org system architecture  Kannel Software Foundation (KSF)
http://www.tolj.org/  http://www.kannel.org/

mailto:st_{at}_tolj.org   mailto:stolj_{at}_kannel.org
---

Re: Massive SMS sent

2006-06-20 Thread Chronis Nikos




I found how to accelerate the rate of sendsms over 
a webinterface.
 
We have just to fork() the process (and log 
everything in a separated file)
What I just finished to do :)
 
Nikos.

RE: Massive SMS sent

2006-06-20 Thread Rene Kluwen




Does 
the Kannel http interface even support long lived 
connections?
 
Rene 
Kluwen
Chimit
 

  -Original Message-From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]On Behalf Of Chronis 
  NikosSent: woensdag 21 juni 2006 0:06To: 
  users@kannel.orgSubject: Re: Massive SMS sent
  I found how to accelerate the rate of sendsms 
  over a webinterface.
   
  We have just to fork() the process (and log 
  everything in a separated file)
  What I just finished to do :)
   
  Nikos.

Re: Massive SMS sent

2006-06-20 Thread Chronis N.




Yes Rene, it work for me
 
-Nikos-

  - Original Message - 
  From: 
  Rene 
  Kluwen 
  To: Chronis Nikos ; users@kannel.org 
  Sent: Wednesday, June 21, 2006 12:09 
  AM
  Subject: RE: Massive SMS sent
  
  Does 
  the Kannel http interface even support long lived 
  connections?
   
  Rene 
  Kluwen
  Chimit
   
  
-Original Message-From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED]On Behalf Of Chronis 
NikosSent: woensdag 21 juni 2006 0:06To: users@kannel.orgSubject: Re: 
Massive SMS sent
I found how to accelerate the rate of sendsms 
over a webinterface.
 
We have just to fork() the process (and log 
everything in a separated file)
What I just finished to do :)
 
Nikos.

Re: Don't remove DLR from mysql database

2006-06-20 Thread Alejandro Guerrieri


The mysql DLR implementation is one of many ways to handle DLR's
(internal in-memory handling is also available). In those case,
failing to delete the DLR's would mean filling memory with more and
more DLR's forever (not a practical approach IMHO). It could be
possible of course to do this _only_ on the mysql implementation, but
that's not a good approach IMO.

You should handle the DLR logging on the application level, meaning
the page being pointed by "dlr-url" that's called when a DLR arrives.

Hope it helps.

On 6/18/06, Rehuel Lobato de Mesquita <[EMAIL PROTECTED]> wrote:


Hi,

Is it possible to keep the DLR in the mysql database?  I see that now the
dlr is remove right away from the db when sending the sms. I need to keep it
in the db, for I need this to check if it was delivered for my sms
application.

I hope my question is clear.

Rehuel



--
Alejandro Guerrieri
Magicom
http://www.magicom-bcn.net/
LinkedIn: http://www.linkedin.com/in/aguerrieri

deferred parameters

2006-06-20 Thread Alejandro Guerrieri


Hi all,

Has anyone tried using the "deferred" parameter with an SMPP link?
User-Guide puts a question mark on it, so I assume that means "not
tested".

I've tried with some SMPP links we have without success: the messages
get delivered without any delay, blatantly ignoring the "deferred"
parameter setting.

Is that a problem related to Kannel, the SMPP protocol or just the
SMSC ignoring it?

On the other hand, specially if this is something related to
protocols, it would be cool to have some sort of "soft-deferring",
meaning Kannel doing the deferral (on the store-file perhaps). This
would work on all kind of links ('at' modems included) since Kannel
would be keeping the messages until delivery time.

Thank you in advance,
--
Alejandro Guerrieri
Magicom
http://www.magicom-bcn.net/
LinkedIn: http://www.linkedin.com/in/aguerrieri

Re: deferred parameters

2006-06-20 Thread Mi Reflejo


Yes it's tested and used. Take a look to cvs user guide
(http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html)

deferrednumber (minutes) Optional. If given, the SMS center will
postpone the message to be delivered at now plus this many minutes.
Note: you must have your Kannel box time synchronized with the SMS
Center.

Which version of kannel are you using?

If you are using cvs head please post the smpp trace. if not please
upgrade to head.

Martín.

On 6/21/06, Alejandro Guerrieri <[EMAIL PROTECTED]> wrote:

Hi all,

Has anyone tried using the "deferred" parameter with an SMPP link?
User-Guide puts a question mark on it, so I assume that means "not
tested".

I've tried with some SMPP links we have without success: the messages
get delivered without any delay, blatantly ignoring the "deferred"
parameter setting.

Is that a problem related to Kannel, the SMPP protocol or just the
SMSC ignoring it?

On the other hand, specially if this is something related to
protocols, it would be cool to have some sort of "soft-deferring",
meaning Kannel doing the deferral (on the store-file perhaps). This
would work on all kind of links ('at' modems included) since Kannel
would be keeping the messages until delivery time.

Thank you in advance,
--
Alejandro Guerrieri
Magicom
http://www.magicom-bcn.net/
LinkedIn: http://www.linkedin.com/in/aguerrieri

Re: deferred parameters

2006-06-20 Thread Alejandro Guerrieri

Martín,

I've read the user-guide (a few thousand times perhaps ;) ) and
noticed the "?" on the SMPP protocol. That lead me to think that it
wasn't tested. My unsuccesful trying didn't help...

It was an 1.4.0 at the time of testing. I'll do a new round of tests
this week with a new snapshot, maybe it's now fixed (or the SMSC it's
ignoring the parameter...).

Regards,

On 6/21/06, Mi Reflejo <[EMAIL PROTECTED]> wrote:

Yes it's tested and used. Take a look to cvs user guide
(http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html)

deferrednumber (minutes) Optional. If given, the SMS center will
postpone the message to be delivered at now plus this many minutes.
Note: you must have your Kannel box time synchronized with the SMS
Center.

Which version of kannel are you using?

If you are using cvs head please post the smpp trace. if not please
upgrade to head.

Martín.

On 6/21/06, Alejandro Guerrieri <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Has anyone tried using the "deferred" parameter with an SMPP link?
> User-Guide puts a question mark on it, so I assume that means "not
> tested".
>
> I've tried with some SMPP links we have without success: the messages
> get delivered without any delay, blatantly ignoring the "deferred"
> parameter setting.
>
> Is that a problem related to Kannel, the SMPP protocol or just the
> SMSC ignoring it?
>
> On the other hand, specially if this is something related to
> protocols, it would be cool to have some sort of "soft-deferring",
> meaning Kannel doing the deferral (on the store-file perhaps). This
> would work on all kind of links ('at' modems included) since Kannel
> would be keeping the messages until delivery time.
>
> Thank you in advance,
> --
> Alejandro Guerrieri
> Magicom
> http://www.magicom-bcn.net/
> LinkedIn: http://www.linkedin.com/in/aguerrieri
>
>

--
Alejandro Guerrieri
Magicom
http://www.magicom-bcn.net/
LinkedIn: http://www.linkedin.com/in/aguerrieri

Re: Massive SMS sent

Re: Massive SMS sent

Re: Massive SMS sent

Error receiving DLRs

Re: Error receiving DLRs

Re: Error receiving DLRs

RE: What about PDU? - Re: SMPP 3.4 Optional params

RE: USB Modem supported ?

Re: USB Modem supported ?

Re: Massive SMS sent

RE: Massive SMS sent

Re: Massive SMS sent

Re: Don't remove DLR from mysql database

deferred parameters

Re: deferred parameters

Re: deferred parameters

16 matches

Site Navigation

Mail list logo

Footer information