DLR rerouting for smsc id disabled
Hello, I am unable to receive DLR in Kannel using SMPP Connectivity., The log is showing when start binding , this INFO: DLR rerouting for smsc id disabled. Any help would be appreciated below are my configuration details # CORE group = core admin-port = 13000 smsbox-port = 13001 wapbox-port = 13002 wdp-interface-name = "xx.xx.xx.xx" admin-password = kannelpass status-password = kannelpass store-type = spool store-location = /var/spool/kannel/store dlr-storage = mysql box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" sms-resend-freq = 30 sms-resend-retry = 2 sms-incoming-queue-limit = "-1" sms-outgoing-queue-limit = 999 smsbox-max-pending = 999 log-level=0 log-file = /var/log/kannel/core.log access-log = /var/log/kannel/access-core.log ## # DLR SETUP group = mysql-connection id = mydlr host = localhost port = 3306 username = root password = kannelpass database = kannel_db max-connections = 25 # DLR TABLE STRUCTURE group = dlr-db id = mydlr table = dlr field-smsc=smsc field-timestamp=ts field-destination=destination field-source=source field-service=service field-url=url field-mask=mask field-status=status field-boxc-id=boxc ## # SMSBOX group = smsbox bearerbox-host = localhost bearerbox-port = 13001 sendsms-port = 13301 sendsms-chars = "0123456789+ " mo-recode = true http-request-retry = 10 http-queue-delay = 60 immediate-sendsms-reply = false log-level = 0 log-file = /var/log/kannel/smsbox.log access-log = /var/log/kannel/access-smsbox.log ## # SENDSMS-USER group = sendsms-user default-smsc = mysmsc forced-smsc = mysmsc username = user password = pass max-messages = 1000 concatenation = true #dlr-url="http://IPadress:port /dlr.php?smscID=%i===%d=%A=%p=%P=%t=%T=%C_id=%I=%b" ## # WAPBOX group = wapbox bearerbox-host = localhost log-level = 0 log-file = /var/log/kannel/wapbox.log ########## # SMSC group = smsc smsc = smpp smsc-id = mysmsc allowed-smsc-id = mysmsc preferred-smsc-id = mysmsc interface-version = 34 allowed-prefix = xxx host = xx.xx.xx.xx port = 8899 receive-port = 0 transceiver-mode = 0 smsc-username = user smsc-password = pass system-type = VMA source-addr-ton = 5 source-addr-npi = 1 dest-addr-ton = 0 dest-addr-npi = 0 keepalive = 600 reconnect-delay = 3 enquire-link-interval = 30 esm-class = 0 #max-pending-submits = 50 #throughput = 50 #wait-ack = 240 #wait-ack-expire = 0x00 msg-id-type = 0x01 log-level = 0 log-file = /var/log/kannel/smsc-transmitter.log group = smsc smsc = smpp smsc-id = mysmsc allowed-smsc-id = mysmsc preferred-smsc-id = mysmsc interface-version = 34 allowed-prefix = xxx host = xx.xx.xx.xx port = 0 receive-port = 8899 smsc-username = user smsc-password = pass system-type = VMA source-addr-ton = 5 source-addr-npi = 1 dest-addr-ton = 0 dest-addr-npi = 0 keepalive = 600 reconnect-delay = 3 enquire-link-interval = 30 esm-class = 0 msg-id-type = 0x01 log-level = 0 log-file = /var/log/kannel/smsc-receiver.log
RE: smsc-id
Hey Denis, I applied your patch which eventually fixed both the crashing and the routing of AO->MT. Thanks! Davor From: Денис Давыдов [mailto:dyna...@gmail.com] Sent: 29 September 2016 15:17 To: Davor Spasoski <davor.spaso...@onevip.mk> Cc: Rene Kluwen <rene.klu...@chimit.nl>; users@kannel.org Subject: Re: smsc-id Davor, use-systemid-as-smsboxid = true (not 0 or 1) Buy the way, I've got crash too on kannel.svn-r5173. My config: ---8<--- # opensmppbox.conf group = core dlr-storage = sqlite3 include = "/etc/kannel/dlr-sqlite3.conf" group = opensmppbox opensmppbox-id = opensmppbox2 opensmppbox-port = 1522 bearerbox-host = localhost bearerbox-port = 13002 our-system-id = opensmppbox2 smpp-logins = "/etc/kannel/smpplogins.txt.bug" use-systemid-as-smsboxid = true log-level = 0 log-file = /var/log/kannel/opensmppbox-bug.log group = smsc-route smsbox-id = nc-prod smsc-id = "megafon-starcom" ---8<--- Program received signal SIGABRT, Aborted. 0x00110424 in __kernel_vsyscall () Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.166.el6_7.3.i68 6 keyutils-libs-1.4-5.el6.i686 krb5-libs-1.10.3-42.el6.i686 libcom_err-1.41.12-2 2.el6.i686 libgcc-4.4.7-16.el6.i686 libselinux-2.0.94-5.8.el6.i686 libxml2-2.7.6 -20.el6.i686 openssl-1.0.1e-42.el6.i686 sqlite-3.6.20-1.el6_7.2.i686 zlib-1.2.3- 29.el6.i686 (gdb) bt full #0 0x00110424 in __kernel_vsyscall () No symbol table info available. #1 0x00a2e871 in raise () from /lib/libc.so.6 No symbol table info available. #2 0x00a3014a in abort () from /lib/libc.so.6 No symbol table info available. #3 0x00a6e735 in __libc_message () from /lib/libc.so.6 No symbol table info available. #4 0x00a74c81 in malloc_printerr () from /lib/libc.so.6 No symbol table info available. #5 0x00a775c2 in _int_free () from /lib/libc.so.6 No symbol table info available. #6 0x080ae442 in octstr_destroy (ostr=0x8391a90) at gwlib/octstr.c:327 __func__ = "octstr_destroy" #7 0x08051858 in init_smsc_routes (cfg=) at opensmppbox.c:2388 grp = items = smsc_id = shortcodes = 0x0 j = list = 0x83919a8 boxc_ids = 0x8391a90 ---Type to continue, or q to quit--- receiver_shortcodes = i = #8 init_smppbox (cfg=) at opensmppbox.c:2514 grp = logfile = lvl = 0 __func__ = "init_smppbox" #9 0x08056da2 in main (argc=2, argv=0xb5e4) at opensmppbox.c:2615 cf_index = 1 filename = version = 0x8202700 __func__ = "main" Try this patch: --- addons/opensmppbox/gw/opensmppbox.c.orig2016-09-29 10:11:51.031021727 + +++ addons/opensmppbox/gw/opensmppbox.c 2016-09-29 13:11:28.409256265 + @@ -2318,6 +2318,7 @@ octstr_get_cstr(item)); } gwlist_destroy(items, octstr_destroy_item); + octstr_destroy(receiver_shortcodes); }; /* consider now the 3 possibilities: */ @@ -2383,10 +2384,9 @@ } gwlist_destroy(items, octstr_destroy_item); octstr_destroy(shortcodes); +octstr_destroy(boxc_ids); } -octstr_destroy(smsc_id); -octstr_destroy(boxc_ids); -octstr_destroy(shortcodes); + octstr_destroy(smsc_id); } gwlist_destroy(list, NULL); -- С уважением, Денис Давыдов 2016-09-29 12:16 GMT+03:00 Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>: group = core dlr-storage = mysql … … … group = opensmppbox bearerbox-host = 127.0.0.1 bearerbox-port = 4001 opensmppbox-id = ex_one_smpp_clients opensmppbox-port = 3339 … our-system-id = exone smpp-logins = /vas/config/kannel/clients use-systemid-as-smsboxid = 1 timeout = 300 group = smsc-route smsbox-id = "vasgw" smsc-id = "vasgw;vasgw_OS" I also tried the last line with a single smsc-id and with use-systemid-as-smsboxid = 1 or 0 Davor From: Rene Kluwen [mailto:rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>] Sent: 29 September 2016 10:30 To: Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>> Cc: users@kannel.org<mailto:users@kannel.org> Subject: RE: smsc-id What’s your config? Van: Davor Spasoski [mailto:davor.spaso...@onevip.mk] Verzonden: woensdag 28 september 2016 10:37 Aan: Rene Kluwen <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>> CC: users@kannel.org<mailto:users@kannel.org> Onderwerp: RE: smsc-id And then setting the smsc-route properly results in opensmppbox crashing like this: *** Error in `/vas/bin/opensmppbox': munmap_chunk(): invalid pointer: 0x01f6f8a0 *** /lib/x86_64-linux-gnu/libc.so.6(+0x77725)[0x7fe249b6a725] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1a8)[0x7fe249b76c18] …. Davor From: users [mailto:u
Re: smsc-id
Davor, use-systemid-as-smsboxid = true (not 0 or 1) Buy the way, I've got crash too on kannel.svn-r5173. My config: ---8<--- # opensmppbox.conf group = core dlr-storage = sqlite3 include = "/etc/kannel/dlr-sqlite3.conf" group = opensmppbox opensmppbox-id = opensmppbox2 opensmppbox-port = 1522 bearerbox-host = localhost bearerbox-port = 13002 our-system-id = opensmppbox2 smpp-logins = "/etc/kannel/smpplogins.txt.bug" use-systemid-as-smsboxid = true log-level = 0 log-file = /var/log/kannel/opensmppbox-bug.log group = smsc-route smsbox-id = nc-prod smsc-id = "megafon-starcom" ---8<--- Program received signal SIGABRT, Aborted. 0x00110424 in __kernel_vsyscall () Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.166.el6_7.3.i68 6 keyutils-libs-1.4-5.el6.i686 krb5-libs-1.10.3-42.el6.i686 libcom_err-1.41.12-2 2.el6.i686 libgcc-4.4.7-16.el6.i686 libselinux-2.0.94-5.8.el6.i686 libxml2-2.7.6 -20.el6.i686 openssl-1.0.1e-42.el6.i686 sqlite-3.6.20-1.el6_7.2.i686 zlib-1.2.3- 29.el6.i686 (gdb) bt full #0 0x00110424 in __kernel_vsyscall () No symbol table info available. #1 0x00a2e871 in raise () from /lib/libc.so.6 No symbol table info available. #2 0x00a3014a in abort () from /lib/libc.so.6 No symbol table info available. #3 0x00a6e735 in __libc_message () from /lib/libc.so.6 No symbol table info available. #4 0x00a74c81 in malloc_printerr () from /lib/libc.so.6 No symbol table info available. #5 0x00a775c2 in _int_free () from /lib/libc.so.6 No symbol table info available. #6 0x080ae442 in octstr_destroy (ostr=0x8391a90) at gwlib/octstr.c:327 __func__ = "octstr_destroy" #7 0x08051858 in init_smsc_routes (cfg=) at opensmppbox.c:2388 grp = items = smsc_id = shortcodes = 0x0 j = list = 0x83919a8 boxc_ids = 0x8391a90 ---Type to continue, or q to quit--- receiver_shortcodes = i = #8 init_smppbox (cfg=) at opensmppbox.c:2514 grp = logfile = lvl = 0 __func__ = "init_smppbox" #9 0x08056da2 in main (argc=2, argv=0xb5e4) at opensmppbox.c:2615 cf_index = 1 filename = version = 0x8202700 __func__ = "main" Try this patch: --- addons/opensmppbox/gw/opensmppbox.c.orig2016-09-29 10:11:51.031021727 + +++ addons/opensmppbox/gw/opensmppbox.c 2016-09-29 13:11:28.409256265 + @@ -2318,6 +2318,7 @@ octstr_get_cstr(item)); } gwlist_destroy(items, octstr_destroy_item); + octstr_destroy(receiver_shortcodes); }; /* consider now the 3 possibilities: */ @@ -2383,10 +2384,9 @@ } gwlist_destroy(items, octstr_destroy_item); octstr_destroy(shortcodes); +octstr_destroy(boxc_ids); } -octstr_destroy(smsc_id); -octstr_destroy(boxc_ids); -octstr_destroy(shortcodes); + octstr_destroy(smsc_id); } gwlist_destroy(list, NULL); -- С уважением, Денис Давыдов 2016-09-29 12:16 GMT+03:00 Davor Spasoski <davor.spaso...@onevip.mk>: > group = core > > dlr-storage = mysql > > … > > … > > … > > group = opensmppbox > > bearerbox-host = 127.0.0.1 > > bearerbox-port = 4001 > > opensmppbox-id = ex_one_smpp_clients > > opensmppbox-port = 3339 > > … > > our-system-id = exone > > smpp-logins = /vas/config/kannel/clients > > use-systemid-as-smsboxid = 1 > > timeout = 300 > > > > group = smsc-route > > smsbox-id = "vasgw" > > smsc-id = "vasgw;vasgw_OS" > > > > I also tried the last line with a single smsc-id and with > use-systemid-as-smsboxid = 1 or 0 > > > > *Davor * > > *From:* Rene Kluwen [mailto:rene.klu...@chimit.nl] > *Sent:* 29 September 2016 10:30 > > *To:* Davor Spasoski <davor.spaso...@onevip.mk> > *Cc:* users@kannel.org > *Subject:* RE: smsc-id > > > > What’s your config? > > > > *Van:* Davor Spasoski [mailto:davor.spaso...@onevip.mk > <davor.spaso...@onevip.mk>] > *Verzonden:* woensdag 28 september 2016 10:37 > *Aan:* Rene Kluwen <rene.klu...@chimit.nl> > *CC:* users@kannel.org > *Onderwerp:* RE: smsc-id > > > > And then setting the smsc-route properly results in opensmppbox crashing > like this: > > > > *** Error in `/vas/bin/opensmppbox': munmap_chunk(): invalid pointer: > 0x01f6f8a0 *** > > /lib/x86_64-linux-gnu/libc.so.6(+0x77725)[0x7fe249b6a725] > > /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1a8)[0x7fe249b76c18] > > …. > > *Davor * > > *From:* users [mailto:users-boun...@kannel.org <users-boun...@kannel.org>] > *On Behalf O
RE: smsc-id
group = core dlr-storage = mysql … … … group = opensmppbox bearerbox-host = 127.0.0.1 bearerbox-port = 4001 opensmppbox-id = ex_one_smpp_clients opensmppbox-port = 3339 … our-system-id = exone smpp-logins = /vas/config/kannel/clients use-systemid-as-smsboxid = 1 timeout = 300 group = smsc-route smsbox-id = "vasgw" smsc-id = "vasgw;vasgw_OS" I also tried the last line with a single smsc-id and with use-systemid-as-smsboxid = 1 or 0 Davor From: Rene Kluwen [mailto:rene.klu...@chimit.nl] Sent: 29 September 2016 10:30 To: Davor Spasoski <davor.spaso...@onevip.mk> Cc: users@kannel.org Subject: RE: smsc-id What’s your config? Van: Davor Spasoski [mailto:davor.spaso...@onevip.mk] Verzonden: woensdag 28 september 2016 10:37 Aan: Rene Kluwen <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>> CC: users@kannel.org<mailto:users@kannel.org> Onderwerp: RE: smsc-id And then setting the smsc-route properly results in opensmppbox crashing like this: *** Error in `/vas/bin/opensmppbox': munmap_chunk(): invalid pointer: 0x01f6f8a0 *** /lib/x86_64-linux-gnu/libc.so.6(+0x77725)[0x7fe249b6a725] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1a8)[0x7fe249b76c18] …. Davor From: users [mailto:users-boun...@kannel.org] On Behalf Of Davor Spasoski Sent: 25 September 2016 21:52 To: Rene Kluwen <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>> Cc: users@kannel.org<mailto:users@kannel.org> Subject: RE: smsc-id OK, I got-it. Smsbox-id will actually be populated with system-type or system-id. Hard to read those xml files :) Davor From: Davor Spasoski Sent: 25 September 2016 21:40 To: 'Rene Kluwen' <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>> Cc: users@kannel.org<mailto:users@kannel.org> Subject: RE: smsc-id Hi Rene, Thank you for your reply. The reason I missed the smsc-route is because I relied on a pdf version of the manual online and the whole group was missing there. Now I went throught the xml manual but still couldn’t find any system-id or system-type syntax under the smsc-route group. When I added something like: Group = sms-route Smsc-id = smsc1 System-id = vasgw or system-type = vasgw I got: ERROR: Group 'smsc-route' (or smsc-type) may not contain field 'system-type' I’ve downloaded the opensmppbox from svn co https://svn.kannel.org/opensmppbox/trunk What is the proper syntax for system-id or system-type directive under smsc-route? BR, Davor Spasoski M: + 389 75 400 608 e-mail: davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk> one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 Skopje | Macedonia From: Rene Kluwen [mailto:rene.klu...@chimit.nl] Sent: 24 September 2016 15:45 To: Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>> Cc: users@kannel.org<mailto:users@kannel.org> Subject: RE: smsc-id Check the opensmppbox user guide for group = smsc-route. You can either use system-id or system-type for that. This is also covered in that same manual. == Rene Van: Davor Spasoski [mailto:davor.spaso...@onevip.mk] Verzonden: donderdag 22 september 2016 10:06 Aan: rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl> Onderwerp: smsc-id Dear Rene, My apology for contacting you directly because I’ve previously posted a question on the user forum and also on the feature tracker on redmine.kannel.org. I don’t see any recent project activy lately, so I took the liberty to contact you. My setup is such that opensmppbox+kannel should act as a sort of transparent smpp proxy and pass system-id/password from one side to the other for a bunch of ESME. This is so, because our new SMSC host a) doesn’t allow direct access and b) has a pair of SMSC. To avoid client disruption, I will preserve the single ip and port of the old SMSC and assign-it to opensmppbox, which means I will not have the liberty to run multiple opensmppbox instances. On the bearerbox side I will connet to the SMSC pair as many times as the number of clients. That means that I will have 2 x ESME number smscs and ESME number of smsc-ids As is the current feature set of opensmppbox, I cannot assign smsc-id per client (system-id) entry in the clients.conf file and SMS from all ESME will be balanced across all smscs which is a big no in my case. I need certain system-ids to be routed to exactly the allowed smsc(s) and vice versa. Unfortunatelly, my programming knowledge is limited to php and touching the C code is risky for me. Would you like to at least point in which way to intervene in the code and I could find someone who knows C to write the actual code? Thanks for reading, I’m hoping on a response. BR, Davor Spasoski Disclaimer: one.Vip DOO Skopje This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-tran
RE: smsc-id
What’s your config? Van: Davor Spasoski [mailto:davor.spaso...@onevip.mk] Verzonden: woensdag 28 september 2016 10:37 Aan: Rene Kluwen <rene.klu...@chimit.nl> CC: users@kannel.org Onderwerp: RE: smsc-id And then setting the smsc-route properly results in opensmppbox crashing like this: *** Error in `/vas/bin/opensmppbox': munmap_chunk(): invalid pointer: 0x01f6f8a0 *** /lib/x86_64-linux-gnu/libc.so.6(+0x77725)[0x7fe249b6a725] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1a8)[0x7fe249b76c18] …. Davor From: users [mailto:users-boun...@kannel.org] On Behalf Of Davor Spasoski Sent: 25 September 2016 21:52 To: Rene Kluwen <rene.klu...@chimit.nl <mailto:rene.klu...@chimit.nl> > Cc: users@kannel.org <mailto:users@kannel.org> Subject: RE: smsc-id OK, I got-it. Smsbox-id will actually be populated with system-type or system-id. Hard to read those xml files :) Davor From: Davor Spasoski Sent: 25 September 2016 21:40 To: 'Rene Kluwen' <rene.klu...@chimit.nl <mailto:rene.klu...@chimit.nl> > Cc: users@kannel.org <mailto:users@kannel.org> Subject: RE: smsc-id Hi Rene, Thank you for your reply. The reason I missed the smsc-route is because I relied on a pdf version of the manual online and the whole group was missing there. Now I went throught the xml manual but still couldn’t find any system-id or system-type syntax under the smsc-route group. When I added something like: Group = sms-route Smsc-id = smsc1 System-id = vasgw or system-type = vasgw I got: ERROR: Group 'smsc-route' (or smsc-type) may not contain field 'system-type' I’ve downloaded the opensmppbox from svn co https://svn.kannel.org/opensmppbox/trunk What is the proper syntax for system-id or system-type directive under smsc-route? BR, Davor Spasoski M: + 389 75 400 608 e-mail: <mailto:davor.spaso...@onevip.mk> davor.spaso...@onevip.mk one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 Skopje | Macedonia From: Rene Kluwen [mailto:rene.klu...@chimit.nl] Sent: 24 September 2016 15:45 To: Davor Spasoski <davor.spaso...@onevip.mk <mailto:davor.spaso...@onevip.mk> > Cc: users@kannel.org <mailto:users@kannel.org> Subject: RE: smsc-id Check the opensmppbox user guide for group = smsc-route. You can either use system-id or system-type for that. This is also covered in that same manual. == Rene Van: Davor Spasoski [mailto:davor.spaso...@onevip.mk] Verzonden: donderdag 22 september 2016 10:06 Aan: rene.klu...@chimit.nl <mailto:rene.klu...@chimit.nl> Onderwerp: smsc-id Dear Rene, My apology for contacting you directly because I’ve previously posted a question on the user forum and also on the feature tracker on redmine.kannel.org. I don’t see any recent project activy lately, so I took the liberty to contact you. My setup is such that opensmppbox+kannel should act as a sort of transparent smpp proxy and pass system-id/password from one side to the other for a bunch of ESME. This is so, because our new SMSC host a) doesn’t allow direct access and b) has a pair of SMSC. To avoid client disruption, I will preserve the single ip and port of the old SMSC and assign-it to opensmppbox, which means I will not have the liberty to run multiple opensmppbox instances. On the bearerbox side I will connet to the SMSC pair as many times as the number of clients. That means that I will have 2 x ESME number smscs and ESME number of smsc-ids As is the current feature set of opensmppbox, I cannot assign smsc-id per client (system-id) entry in the clients.conf file and SMS from all ESME will be balanced across all smscs which is a big no in my case. I need certain system-ids to be routed to exactly the allowed smsc(s) and vice versa. Unfortunatelly, my programming knowledge is limited to php and touching the C code is risky for me. Would you like to at least point in which way to intervene in the code and I could find someone who knows C to write the actual code? Thanks for reading, I’m hoping on a response. BR, Davor Spasoski _ Disclaimer: one.Vip DOO Skopje This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. one.Vip DOO Skopje shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Please, do not print this e-mail unless it is necessary! Think about saving the environment! Напомена: оне.Вип ДОО Скопје Оваа електронска порака (вклучувајќи ги и прилозит
RE: smsc-id
And then setting the smsc-route properly results in opensmppbox crashing like this: *** Error in `/vas/bin/opensmppbox': munmap_chunk(): invalid pointer: 0x01f6f8a0 *** /lib/x86_64-linux-gnu/libc.so.6(+0x77725)[0x7fe249b6a725] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1a8)[0x7fe249b76c18] …. Davor From: users [mailto:users-boun...@kannel.org] On Behalf Of Davor Spasoski Sent: 25 September 2016 21:52 To: Rene Kluwen <rene.klu...@chimit.nl> Cc: users@kannel.org Subject: RE: smsc-id OK, I got-it. Smsbox-id will actually be populated with system-type or system-id. Hard to read those xml files :) Davor From: Davor Spasoski Sent: 25 September 2016 21:40 To: 'Rene Kluwen' <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>> Cc: users@kannel.org<mailto:users@kannel.org> Subject: RE: smsc-id Hi Rene, Thank you for your reply. The reason I missed the smsc-route is because I relied on a pdf version of the manual online and the whole group was missing there. Now I went throught the xml manual but still couldn’t find any system-id or system-type syntax under the smsc-route group. When I added something like: Group = sms-route Smsc-id = smsc1 System-id = vasgw or system-type = vasgw I got: ERROR: Group 'smsc-route' (or smsc-type) may not contain field 'system-type' I’ve downloaded the opensmppbox from svn co https://svn.kannel.org/opensmppbox/trunk What is the proper syntax for system-id or system-type directive under smsc-route? BR, Davor Spasoski M: + 389 75 400 608 e-mail: davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk> one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 Skopje | Macedonia From: Rene Kluwen [mailto:rene.klu...@chimit.nl] Sent: 24 September 2016 15:45 To: Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>> Cc: users@kannel.org<mailto:users@kannel.org> Subject: RE: smsc-id Check the opensmppbox user guide for group = smsc-route. You can either use system-id or system-type for that. This is also covered in that same manual. == Rene Van: Davor Spasoski [mailto:davor.spaso...@onevip.mk] Verzonden: donderdag 22 september 2016 10:06 Aan: rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl> Onderwerp: smsc-id Dear Rene, My apology for contacting you directly because I’ve previously posted a question on the user forum and also on the feature tracker on redmine.kannel.org. I don’t see any recent project activy lately, so I took the liberty to contact you. My setup is such that opensmppbox+kannel should act as a sort of transparent smpp proxy and pass system-id/password from one side to the other for a bunch of ESME. This is so, because our new SMSC host a) doesn’t allow direct access and b) has a pair of SMSC. To avoid client disruption, I will preserve the single ip and port of the old SMSC and assign-it to opensmppbox, which means I will not have the liberty to run multiple opensmppbox instances. On the bearerbox side I will connet to the SMSC pair as many times as the number of clients. That means that I will have 2 x ESME number smscs and ESME number of smsc-ids As is the current feature set of opensmppbox, I cannot assign smsc-id per client (system-id) entry in the clients.conf file and SMS from all ESME will be balanced across all smscs which is a big no in my case. I need certain system-ids to be routed to exactly the allowed smsc(s) and vice versa. Unfortunatelly, my programming knowledge is limited to php and touching the C code is risky for me. Would you like to at least point in which way to intervene in the code and I could find someone who knows C to write the actual code? Thanks for reading, I’m hoping on a response. BR, Davor Spasoski Disclaimer: one.Vip DOO Skopje This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. one.Vip DOO Skopje shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Please, do not print this e-mail unless it is necessary! Think about saving the environment! Напомена: оне.Вип ДОО Скопје Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и да ја избришете оригиналната порака и сите нејзини копии од Вашиот компјутерски систем.
RE: smsc-id
OK, I got-it. Smsbox-id will actually be populated with system-type or system-id. Hard to read those xml files :) Davor From: Davor Spasoski Sent: 25 September 2016 21:40 To: 'Rene Kluwen' <rene.klu...@chimit.nl> Cc: users@kannel.org Subject: RE: smsc-id Hi Rene, Thank you for your reply. The reason I missed the smsc-route is because I relied on a pdf version of the manual online and the whole group was missing there. Now I went throught the xml manual but still couldn’t find any system-id or system-type syntax under the smsc-route group. When I added something like: Group = sms-route Smsc-id = smsc1 System-id = vasgw or system-type = vasgw I got: ERROR: Group 'smsc-route' (or smsc-type) may not contain field 'system-type' I’ve downloaded the opensmppbox from svn co https://svn.kannel.org/opensmppbox/trunk What is the proper syntax for system-id or system-type directive under smsc-route? BR, Davor Spasoski M: + 389 75 400 608 e-mail: davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk> one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 Skopje | Macedonia From: Rene Kluwen [mailto:rene.klu...@chimit.nl] Sent: 24 September 2016 15:45 To: Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>> Cc: users@kannel.org<mailto:users@kannel.org> Subject: RE: smsc-id Check the opensmppbox user guide for group = smsc-route. You can either use system-id or system-type for that. This is also covered in that same manual. == Rene Van: Davor Spasoski [mailto:davor.spaso...@onevip.mk] Verzonden: donderdag 22 september 2016 10:06 Aan: rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl> Onderwerp: smsc-id Dear Rene, My apology for contacting you directly because I’ve previously posted a question on the user forum and also on the feature tracker on redmine.kannel.org. I don’t see any recent project activy lately, so I took the liberty to contact you. My setup is such that opensmppbox+kannel should act as a sort of transparent smpp proxy and pass system-id/password from one side to the other for a bunch of ESME. This is so, because our new SMSC host a) doesn’t allow direct access and b) has a pair of SMSC. To avoid client disruption, I will preserve the single ip and port of the old SMSC and assign-it to opensmppbox, which means I will not have the liberty to run multiple opensmppbox instances. On the bearerbox side I will connet to the SMSC pair as many times as the number of clients. That means that I will have 2 x ESME number smscs and ESME number of smsc-ids As is the current feature set of opensmppbox, I cannot assign smsc-id per client (system-id) entry in the clients.conf file and SMS from all ESME will be balanced across all smscs which is a big no in my case. I need certain system-ids to be routed to exactly the allowed smsc(s) and vice versa. Unfortunatelly, my programming knowledge is limited to php and touching the C code is risky for me. Would you like to at least point in which way to intervene in the code and I could find someone who knows C to write the actual code? Thanks for reading, I’m hoping on a response. BR, Davor Spasoski Disclaimer: one.Vip DOO Skopje This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. one.Vip DOO Skopje shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Please, do not print this e-mail unless it is necessary! Think about saving the environment! Напомена: оне.Вип ДОО Скопје Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и да ја избришете оригиналната порака и сите нејзини копии од Вашиот компјутерски систем. Секое неовластено користење на оваа порака во целост или делови од истата е строго забрането. Ве молиме да забележите дека електронските пораки се подложни на промени. оне.Вип ДОО Скопје не презема одговорност за несоодветно или нецелосно пренесување на информациите содржани во оваа комуникација, ниту пак за било какво задоцнување на приемот или оштетувања на вашиот систем. Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја природата! Disclaimer: one.Vip DOO Skopje This e-mail (including any
RE: smsc-id
Hi Rene, Thank you for your reply. The reason I missed the smsc-route is because I relied on a pdf version of the manual online and the whole group was missing there. Now I went throught the xml manual but still couldn’t find any system-id or system-type syntax under the smsc-route group. When I added something like: Group = sms-route Smsc-id = smsc1 System-id = vasgw or system-type = vasgw I got: ERROR: Group 'smsc-route' (or smsc-type) may not contain field 'system-type' I’ve downloaded the opensmppbox from svn co https://svn.kannel.org/opensmppbox/trunk What is the proper syntax for system-id or system-type directive under smsc-route? BR, Davor Spasoski M: + 389 75 400 608 e-mail: davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk> one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 Skopje | Macedonia From: Rene Kluwen [mailto:rene.klu...@chimit.nl] Sent: 24 September 2016 15:45 To: Davor Spasoski <davor.spaso...@onevip.mk> Cc: users@kannel.org Subject: RE: smsc-id Check the opensmppbox user guide for group = smsc-route. You can either use system-id or system-type for that. This is also covered in that same manual. == Rene Van: Davor Spasoski [mailto:davor.spaso...@onevip.mk] Verzonden: donderdag 22 september 2016 10:06 Aan: rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl> Onderwerp: smsc-id Dear Rene, My apology for contacting you directly because I’ve previously posted a question on the user forum and also on the feature tracker on redmine.kannel.org. I don’t see any recent project activy lately, so I took the liberty to contact you. My setup is such that opensmppbox+kannel should act as a sort of transparent smpp proxy and pass system-id/password from one side to the other for a bunch of ESME. This is so, because our new SMSC host a) doesn’t allow direct access and b) has a pair of SMSC. To avoid client disruption, I will preserve the single ip and port of the old SMSC and assign-it to opensmppbox, which means I will not have the liberty to run multiple opensmppbox instances. On the bearerbox side I will connet to the SMSC pair as many times as the number of clients. That means that I will have 2 x ESME number smscs and ESME number of smsc-ids As is the current feature set of opensmppbox, I cannot assign smsc-id per client (system-id) entry in the clients.conf file and SMS from all ESME will be balanced across all smscs which is a big no in my case. I need certain system-ids to be routed to exactly the allowed smsc(s) and vice versa. Unfortunatelly, my programming knowledge is limited to php and touching the C code is risky for me. Would you like to at least point in which way to intervene in the code and I could find someone who knows C to write the actual code? Thanks for reading, I’m hoping on a response. BR, Davor Spasoski Disclaimer: one.Vip DOO Skopje This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. one.Vip DOO Skopje shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Please, do not print this e-mail unless it is necessary! Think about saving the environment! Напомена: оне.Вип ДОО Скопје Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и да ја избришете оригиналната порака и сите нејзини копии од Вашиот компјутерски систем. Секое неовластено користење на оваа порака во целост или делови од истата е строго забрането. Ве молиме да забележите дека електронските пораки се подложни на промени. оне.Вип ДОО Скопје не презема одговорност за несоодветно или нецелосно пренесување на информациите содржани во оваа комуникација, ниту пак за било какво задоцнување на приемот или оштетувања на вашиот систем. Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја природата! Disclaimer: one.Vip DOO Skopje This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Any unauthorized use or dissemination of this message i
RE: smsc-id
Check the opensmppbox user guide for group = smsc-route. You can either use system-id or system-type for that. This is also covered in that same manual. == Rene Van: Davor Spasoski [mailto:davor.spaso...@onevip.mk] Verzonden: donderdag 22 september 2016 10:06 Aan: rene.klu...@chimit.nl Onderwerp: smsc-id Dear Rene, My apology for contacting you directly because I’ve previously posted a question on the user forum and also on the feature tracker on redmine.kannel.org. I don’t see any recent project activy lately, so I took the liberty to contact you. My setup is such that opensmppbox+kannel should act as a sort of transparent smpp proxy and pass system-id/password from one side to the other for a bunch of ESME. This is so, because our new SMSC host a) doesn’t allow direct access and b) has a pair of SMSC. To avoid client disruption, I will preserve the single ip and port of the old SMSC and assign-it to opensmppbox, which means I will not have the liberty to run multiple opensmppbox instances. On the bearerbox side I will connet to the SMSC pair as many times as the number of clients. That means that I will have 2 x ESME number smscs and ESME number of smsc-ids As is the current feature set of opensmppbox, I cannot assign smsc-id per client (system-id) entry in the clients.conf file and SMS from all ESME will be balanced across all smscs which is a big no in my case. I need certain system-ids to be routed to exactly the allowed smsc(s) and vice versa. Unfortunatelly, my programming knowledge is limited to php and touching the C code is risky for me. Would you like to at least point in which way to intervene in the code and I could find someone who knows C to write the actual code? Thanks for reading, I’m hoping on a response. BR, Davor Spasoski _ Disclaimer: one.Vip DOO Skopje This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. one.Vip DOO Skopje shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Please, do not print this e-mail unless it is necessary! Think about saving the environment! Напомена: оне.Вип ДОО Скопје Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и да ја избришете оригиналната порака и сите нејзини копии од Вашиот компјутерски систем. Секое неовластено користење на оваа порака во целост или делови од истата е строго забрането. Ве молиме да забележите дека електронските пораки се подложни на промени. оне.Вип ДОО Скопје не презема одговорност за несоодветно или нецелосно пренесување на информациите содржани во оваа комуникација, ниту пак за било какво задоцнување на приемот или оштетувања на вашиот систем. Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја природата!
Wildcards in smsc id
Hi Group, any one knows if wildcards can be used in allowed-smsc-id?, for example, having 3 smsc named modem1, modem2 and modem3 can be used: allowed-sms-id = modem*, this is to reroute traffic from modem1 to the other two when it's stoped, or any other suggestion?. Thanks for your help. Vinicio Cruz.
Re: Wildcards in smsc id
Hi You can use what I call virtual smsc along with allowed-smsc and denied-smsc. In your setup you can have something like: group=smsc smsc-id = modem1 allowed-smsc= modem1, group1, group3 ... group=smsc smsc-id = modem2 allowed-smsc= modem2, group1, group2 ... group=smsc smsc-id = modem3 allowed-smsc= modem3, group1, group2, group3 ... etc. Now when you want to send a sms to a specific modem you use: ...smsc=modemX... if you want to send a sms to either modem 2 or 3 you use ...smsc=group2... If you want to send a sms that will go through any modem you use ...smsc=group1... if you want to send a sms to either modem 1 or 3 you use ...smsc=group3... You don´t need to define virtuals smsc anywhere on the config file. Regards Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com On Fri, Aug 29, 2014 at 4:46 PM, Vinicio Cruz vinicio.c...@gmail.com wrote: Hi Group, any one knows if wildcards can be used in allowed-smsc-id?, for example, having 3 smsc named modem1, modem2 and modem3 can be used: allowed-sms-id = modem*, this is to reroute traffic from modem1 to the other two when it's stoped, or any other suggestion?. Thanks for your help. *Vinicio Cruz.*
Re: ERROR due to Delivery Reports from different smsc-id
Use the same smsc-id on all of them, but different allowed-smsc-id on each. That way the DLRs will all use the smsc-id, but you use the allowed-smsc-id to route your MTs. Also use smsc-admin-id so that you can start/stop/whatever each bind individually Regards On Thu, Apr 24, 2014 at 10:49 AM, Jeff Thorn j...@thorntechnologies.comwrote: Thanks for the response spamden. That is very unfortunate. We have a legitimate need to have different smsc-ids but have only one account. How feasible would it be to use meta data or some other way to match the sending smsc-id instead of the receiving smsc-id? If all else fails, what is the risk of matching the DLR on destination and timestamp alone? The reason we need multiple smsc-id is because we are routing interactive messages to binds that are less active since many of our other binds may have several thousand messages queued at any given time. If using multiple smsc-ids is not a valid approach, is there some other way to accomplish what we are trying to do. Perhaps the priority field is what we need? How does the priority field affect MT messages on a bind that already has several thousand messages queued for sending by kannel? Thanks! Jeff On Thu, Apr 24, 2014 at 3:23 AM, spameden spame...@gmail.com wrote: 2014-04-24 1:20 GMT+04:00 Jeff Thorn j...@thorntechnologies.com: I've searched the user groups for this issue and everyone says to use the same smsc-id. We specifically need different smsc-ids so our interactive messages can be delivered in real time and not get queued with our bulk messages. Only if you use same bind server and same login you need to use same smsc-id parameter. Because remote server doesn't know through which connection it should send DLR report. Is there anyway to ensure that Delivery Reports come back on the same smsc-id that the message was sent from? Otherwise, I don't understand why there is an option to specify different smsc-ids. It's always the same from which it was sent, just make sure you don't have same credentials / same server specified more than once. Thanks! On Wed, Apr 23, 2014 at 4:45 PM, Jeff Thorn j...@thorntechnologies.comwrote: We are seeing an increased number of error messages like the following: ERROR: SMPP[bind-b]: got DLR but could not find message or was not interested in it idxx dstxxx, type1 We have a number of binds setup to handle bulk messaging (which may queue in kannel) or interactive messaging (which is less frequent). I've noticed these errors occur when we receive the Delivery Report on one bind (bind-b), but the original MT was sent from a different bind (bind-a). In the DLR database table, the message with the same id and dst exists, but the smsc value is different (bind-a vs bind-b). Is there anyway to ensure that Delivery Reports come back on the same smsc-id that the message was sent from? Thanks! Jeff
Re: ERROR due to Delivery Reports from different smsc-id
Hi Juan, That is an interesting approach. Are you saying that if a bind has an smsc-id of bind-a but I add allowed-smsc-id with a value of bind-b then only messages that have the smsc=bind-b in the sendsms URL will get routed to that bind? It doesn't seem like that should work. Am I understanding your suggestion properly? Thanks! Jeff On Apr 26, 2014 10:26 AM, Juan Nin jua...@gmail.com wrote: Use the same smsc-id on all of them, but different allowed-smsc-id on each. That way the DLRs will all use the smsc-id, but you use the allowed-smsc-id to route your MTs. Also use smsc-admin-id so that you can start/stop/whatever each bind individually Regards On Thu, Apr 24, 2014 at 10:49 AM, Jeff Thorn j...@thorntechnologies.com wrote: Thanks for the response spamden. That is very unfortunate. We have a legitimate need to have different smsc-ids but have only one account. How feasible would it be to use meta data or some other way to match the sending smsc-id instead of the receiving smsc-id? If all else fails, what is the risk of matching the DLR on destination and timestamp alone? The reason we need multiple smsc-id is because we are routing interactive messages to binds that are less active since many of our other binds may have several thousand messages queued at any given time. If using multiple smsc-ids is not a valid approach, is there some other way to accomplish what we are trying to do. Perhaps the priority field is what we need? How does the priority field affect MT messages on a bind that already has several thousand messages queued for sending by kannel? Thanks! Jeff On Thu, Apr 24, 2014 at 3:23 AM, spameden spame...@gmail.com wrote: 2014-04-24 1:20 GMT+04:00 Jeff Thorn j...@thorntechnologies.com: I've searched the user groups for this issue and everyone says to use the same smsc-id. We specifically need different smsc-ids so our interactive messages can be delivered in real time and not get queued with our bulk messages. Only if you use same bind server and same login you need to use same smsc-id parameter. Because remote server doesn't know through which connection it should send DLR report. Is there anyway to ensure that Delivery Reports come back on the same smsc-id that the message was sent from? Otherwise, I don't understand why there is an option to specify different smsc-ids. It's always the same from which it was sent, just make sure you don't have same credentials / same server specified more than once. Thanks! On Wed, Apr 23, 2014 at 4:45 PM, Jeff Thorn j...@thorntechnologies.com wrote: We are seeing an increased number of error messages like the following: ERROR: SMPP[bind-b]: got DLR but could not find message or was not interested in it idxx dstxxx, type1 We have a number of binds setup to handle bulk messaging (which may queue in kannel) or interactive messaging (which is less frequent). I've noticed these errors occur when we receive the Delivery Report on one bind (bind-b), but the original MT was sent from a different bind (bind-a). In the DLR database table, the message with the same id and dst exists, but the smsc value is different (bind-a vs bind-b). Is there anyway to ensure that Delivery Reports come back on the same smsc-id that the message was sent from? Thanks! Jeff
Re: ERROR due to Delivery Reports from different smsc-id
Yes, you're understanding it correctly. So you can use bind-a as smsc-id for all the binds, and then use allowed-smsc-id like bind-b, bind-c, bind-d, etc on each and use those as smsc parameter for sending the MTs. DLRs will all use bind-a. Regards. On Sat, Apr 26, 2014 at 11:40 AM, Jeff Thorn j...@thorntechnologies.comwrote: Hi Juan, That is an interesting approach. Are you saying that if a bind has an smsc-id of bind-a but I add allowed-smsc-id with a value of bind-b then only messages that have the smsc=bind-b in the sendsms URL will get routed to that bind? It doesn't seem like that should work. Am I understanding your suggestion properly? Thanks! Jeff On Apr 26, 2014 10:26 AM, Juan Nin jua...@gmail.com wrote: Use the same smsc-id on all of them, but different allowed-smsc-id on each. That way the DLRs will all use the smsc-id, but you use the allowed-smsc-id to route your MTs. Also use smsc-admin-id so that you can start/stop/whatever each bind individually Regards On Thu, Apr 24, 2014 at 10:49 AM, Jeff Thorn j...@thorntechnologies.com wrote: Thanks for the response spamden. That is very unfortunate. We have a legitimate need to have different smsc-ids but have only one account. How feasible would it be to use meta data or some other way to match the sending smsc-id instead of the receiving smsc-id? If all else fails, what is the risk of matching the DLR on destination and timestamp alone? The reason we need multiple smsc-id is because we are routing interactive messages to binds that are less active since many of our other binds may have several thousand messages queued at any given time. If using multiple smsc-ids is not a valid approach, is there some other way to accomplish what we are trying to do. Perhaps the priority field is what we need? How does the priority field affect MT messages on a bind that already has several thousand messages queued for sending by kannel? Thanks! Jeff On Thu, Apr 24, 2014 at 3:23 AM, spameden spame...@gmail.com wrote: 2014-04-24 1:20 GMT+04:00 Jeff Thorn j...@thorntechnologies.com: I've searched the user groups for this issue and everyone says to use the same smsc-id. We specifically need different smsc-ids so our interactive messages can be delivered in real time and not get queued with our bulk messages. Only if you use same bind server and same login you need to use same smsc-id parameter. Because remote server doesn't know through which connection it should send DLR report. Is there anyway to ensure that Delivery Reports come back on the same smsc-id that the message was sent from? Otherwise, I don't understand why there is an option to specify different smsc-ids. It's always the same from which it was sent, just make sure you don't have same credentials / same server specified more than once. Thanks! On Wed, Apr 23, 2014 at 4:45 PM, Jeff Thorn j...@thorntechnologies.com wrote: We are seeing an increased number of error messages like the following: ERROR: SMPP[bind-b]: got DLR but could not find message or was not interested in it idxx dstxxx, type1 We have a number of binds setup to handle bulk messaging (which may queue in kannel) or interactive messaging (which is less frequent). I've noticed these errors occur when we receive the Delivery Report on one bind (bind-b), but the original MT was sent from a different bind (bind-a). In the DLR database table, the message with the same id and dst exists, but the smsc value is different (bind-a vs bind-b). Is there anyway to ensure that Delivery Reports come back on the same smsc-id that the message was sent from? Thanks! Jeff
Re: ERROR due to Delivery Reports from different smsc-id
2014-04-24 1:20 GMT+04:00 Jeff Thorn j...@thorntechnologies.com: I've searched the user groups for this issue and everyone says to use the same smsc-id. We specifically need different smsc-ids so our interactive messages can be delivered in real time and not get queued with our bulk messages. Only if you use same bind server and same login you need to use same smsc-id parameter. Because remote server doesn't know through which connection it should send DLR report. Is there anyway to ensure that Delivery Reports come back on the same smsc-id that the message was sent from? Otherwise, I don't understand why there is an option to specify different smsc-ids. It's always the same from which it was sent, just make sure you don't have same credentials / same server specified more than once. Thanks! On Wed, Apr 23, 2014 at 4:45 PM, Jeff Thorn j...@thorntechnologies.comwrote: We are seeing an increased number of error messages like the following: ERROR: SMPP[bind-b]: got DLR but could not find message or was not interested in it idxx dstxxx, type1 We have a number of binds setup to handle bulk messaging (which may queue in kannel) or interactive messaging (which is less frequent). I've noticed these errors occur when we receive the Delivery Report on one bind (bind-b), but the original MT was sent from a different bind (bind-a). In the DLR database table, the message with the same id and dst exists, but the smsc value is different (bind-a vs bind-b). Is there anyway to ensure that Delivery Reports come back on the same smsc-id that the message was sent from? Thanks! Jeff
Re: ERROR due to Delivery Reports from different smsc-id
Thanks for the response spamden. That is very unfortunate. We have a legitimate need to have different smsc-ids but have only one account. How feasible would it be to use meta data or some other way to match the sending smsc-id instead of the receiving smsc-id? If all else fails, what is the risk of matching the DLR on destination and timestamp alone? The reason we need multiple smsc-id is because we are routing interactive messages to binds that are less active since many of our other binds may have several thousand messages queued at any given time. If using multiple smsc-ids is not a valid approach, is there some other way to accomplish what we are trying to do. Perhaps the priority field is what we need? How does the priority field affect MT messages on a bind that already has several thousand messages queued for sending by kannel? Thanks! Jeff On Thu, Apr 24, 2014 at 3:23 AM, spameden spame...@gmail.com wrote: 2014-04-24 1:20 GMT+04:00 Jeff Thorn j...@thorntechnologies.com: I've searched the user groups for this issue and everyone says to use the same smsc-id. We specifically need different smsc-ids so our interactive messages can be delivered in real time and not get queued with our bulk messages. Only if you use same bind server and same login you need to use same smsc-id parameter. Because remote server doesn't know through which connection it should send DLR report. Is there anyway to ensure that Delivery Reports come back on the same smsc-id that the message was sent from? Otherwise, I don't understand why there is an option to specify different smsc-ids. It's always the same from which it was sent, just make sure you don't have same credentials / same server specified more than once. Thanks! On Wed, Apr 23, 2014 at 4:45 PM, Jeff Thorn j...@thorntechnologies.comwrote: We are seeing an increased number of error messages like the following: ERROR: SMPP[bind-b]: got DLR but could not find message or was not interested in it idxx dstxxx, type1 We have a number of binds setup to handle bulk messaging (which may queue in kannel) or interactive messaging (which is less frequent). I've noticed these errors occur when we receive the Delivery Report on one bind (bind-b), but the original MT was sent from a different bind (bind-a). In the DLR database table, the message with the same id and dst exists, but the smsc value is different (bind-a vs bind-b). Is there anyway to ensure that Delivery Reports come back on the same smsc-id that the message was sent from? Thanks! Jeff
ERROR due to Delivery Reports from different smsc-id
We are seeing an increased number of error messages like the following: ERROR: SMPP[bind-b]: got DLR but could not find message or was not interested in it idxx dstxxx, type1 We have a number of binds setup to handle bulk messaging (which may queue in kannel) or interactive messaging (which is less frequent). I've noticed these errors occur when we receive the Delivery Report on one bind (bind-b), but the original MT was sent from a different bind (bind-a). In the DLR database table, the message with the same id and dst exists, but the smsc value is different (bind-a vs bind-b). Is there anyway to ensure that Delivery Reports come back on the same smsc-id that the message was sent from? Thanks! Jeff
Re: ERROR due to Delivery Reports from different smsc-id
I've searched the user groups for this issue and everyone says to use the same smsc-id. We specifically need different smsc-ids so our interactive messages can be delivered in real time. On Wed, Apr 23, 2014 at 4:45 PM, Jeff Thorn j...@thorntechnologies.comwrote: We are seeing an increased number of error messages like the following: ERROR: SMPP[bind-b]: got DLR but could not find message or was not interested in it idxx dstxxx, type1 We have a number of binds setup to handle bulk messaging (which may queue in kannel) or interactive messaging (which is less frequent). I've noticed these errors occur when we receive the Delivery Report on one bind (bind-b), but the original MT was sent from a different bind (bind-a). In the DLR database table, the message with the same id and dst exists, but the smsc value is different (bind-a vs bind-b). Is there anyway to ensure that Delivery Reports come back on the same smsc-id that the message was sent from? Thanks! Jeff
Re: ERROR due to Delivery Reports from different smsc-id
I've searched the user groups for this issue and everyone says to use the same smsc-id. We specifically need different smsc-ids so our interactive messages can be delivered in real time and not get queued with our bulk messages. Is there anyway to ensure that Delivery Reports come back on the same smsc-id that the message was sent from? Otherwise, I don't understand why there is an option to specify different smsc-ids. Thanks! On Wed, Apr 23, 2014 at 4:45 PM, Jeff Thorn j...@thorntechnologies.comwrote: We are seeing an increased number of error messages like the following: ERROR: SMPP[bind-b]: got DLR but could not find message or was not interested in it idxx dstxxx, type1 We have a number of binds setup to handle bulk messaging (which may queue in kannel) or interactive messaging (which is less frequent). I've noticed these errors occur when we receive the Delivery Report on one bind (bind-b), but the original MT was sent from a different bind (bind-a). In the DLR database table, the message with the same id and dst exists, but the smsc value is different (bind-a vs bind-b). Is there anyway to ensure that Delivery Reports come back on the same smsc-id that the message was sent from? Thanks! Jeff
Re: routing sms using smsc-id not working
Hi Alejandro, I think you should use the following url, using the paramater smsc-id instead of smsc: http://xxx:xx/cgi-bin/sendsms? username=xxpassword=xxxto=+595981414913from=1244@3 binfo=CCOTItext=Cotizacion+del+diasmsc-id=tigo dlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3 If you do not choose any smsc, kannel will send the sms with a round robin algorythm. Regards. Pablo. 2013/11/26 Alejandro Mussi alemu...@gmail.com Hi, I have 2 smsc setup in kannel. When i send an sms i specified the smsc id in the url but kannel sometimes sends using the other smsc (it seems to choose randomly) Here is my http request for sending a message using smsc-id tigo but in some cases it sends using personal: http://xxx:xx/cgi-bin/sendsms?username=xxpassword=xxxto=+595981414913 from=1244@3binfo=CCOTItext=Cotizacion+del+diasmsc=tigo dlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3 Here my conf file group = smsc smsc = smpp host = xxx.xxx.xxx.xx port = 8089 receive-port = 8089 smsc-username = yyy smsc-password = yy system-type = VMA address-range = smsc-id = personal group = smsc smsc = smpp smsc-id = tigo host = xxx.xx.xxx.xx port = 5600 receive-port = 5600 smsc-username = yy smsc-password = yyy system-type = VMA address-range = Thanks -- - Alejandro Mussi Campos Cervera -- Pablo Gus
Re: routing sms using smsc-id not working
Hi Pablo, I have the same problem even changing the smsc paramter to smsc-id. In the kannel user-guide specified smsc as the parameter to use for defining the smsc-id. Best On Tue, Nov 26, 2013 at 11:19 AM, Pablo Gus pablo...@gmail.com wrote: Hi Alejandro, I think you should use the following url, using the paramater smsc-id instead of smsc: http://xxx:xx/cgi-bin/sendsms? username=xxpassword=xxxto=+595981414913from=1244@3 binfo=CCOTItext=Cotizacion+del+diasmsc-id=tigo dlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3 If you do not choose any smsc, kannel will send the sms with a round robin algorythm. Regards. Pablo. 2013/11/26 Alejandro Mussi alemu...@gmail.com Hi, I have 2 smsc setup in kannel. When i send an sms i specified the smsc id in the url but kannel sometimes sends using the other smsc (it seems to choose randomly) Here is my http request for sending a message using smsc-id tigo but in some cases it sends using personal: http://xxx:xx/cgi-bin/sendsms?username=xxpassword=xxxto=+595981414913 from=1244@3binfo=CCOTItext=Cotizacion+del+diasmsc=tigo dlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3 Here my conf file group = smsc smsc = smpp host = xxx.xxx.xxx.xx port = 8089 receive-port = 8089 smsc-username = yyy smsc-password = yy system-type = VMA address-range = smsc-id = personal group = smsc smsc = smpp smsc-id = tigo host = xxx.xx.xxx.xx port = 5600 receive-port = 5600 smsc-username = yy smsc-password = yyy system-type = VMA address-range = Thanks -- - Alejandro Mussi Campos Cervera -- Pablo Gus -- - Alejandro Mussi Campos Cervera
Re: routing sms using smsc-id not working
Hi You need to add allowed/denied smsc. on each group. Check documentation for details. Regards Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com On Tue, Nov 26, 2013 at 10:02 AM, Alejandro Mussi alemu...@gmail.com wrote: Hi Pablo, I have the same problem even changing the smsc paramter to smsc-id. In the kannel user-guide specified smsc as the parameter to use for defining the smsc-id. Best On Tue, Nov 26, 2013 at 11:19 AM, Pablo Gus pablo...@gmail.com wrote: Hi Alejandro, I think you should use the following url, using the paramater smsc-id instead of smsc: http://xxx:xx/cgi-bin/sendsms? username=xxpassword=xxxto=+595981414913from=1244@3binfo=CCOTItext=Cotizacion+del+diasmsc-id=tigodlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3 If you do not choose any smsc, kannel will send the sms with a round robin algorythm. Regards. Pablo. 2013/11/26 Alejandro Mussi alemu...@gmail.com Hi, I have 2 smsc setup in kannel. When i send an sms i specified the smsc id in the url but kannel sometimes sends using the other smsc (it seems to choose randomly) Here is my http request for sending a message using smsc-id tigo but in some cases it sends using personal: http://xxx:xx/cgi-bin/sendsms?username=xxpassword=xxxto=+595981414913from=1244@3binfo=CCOTItext=Cotizacion+del+diasmsc=tigodlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3 Here my conf file group = smsc smsc = smpp host = xxx.xxx.xxx.xx port = 8089 receive-port = 8089 smsc-username = yyy smsc-password = yy system-type = VMA address-range = smsc-id = personal group = smsc smsc = smpp smsc-id = tigo host = xxx.xx.xxx.xx port = 5600 receive-port = 5600 smsc-username = yy smsc-password = yyy system-type = VMA address-range = Thanks -- - Alejandro Mussi Campos Cervera -- Pablo Gus -- - Alejandro Mussi Campos Cervera
Re: routing sms using smsc-id not working
Solved. Thanks Alvaro On Tue, Nov 26, 2013 at 12:26 PM, Alvaro Cornejo cornejo.alv...@gmail.comwrote: Hi You need to add allowed/denied smsc. on each group. Check documentation for details. Regards Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com On Tue, Nov 26, 2013 at 10:02 AM, Alejandro Mussi alemu...@gmail.com wrote: Hi Pablo, I have the same problem even changing the smsc paramter to smsc-id. In the kannel user-guide specified smsc as the parameter to use for defining the smsc-id. Best On Tue, Nov 26, 2013 at 11:19 AM, Pablo Gus pablo...@gmail.com wrote: Hi Alejandro, I think you should use the following url, using the paramater smsc-id instead of smsc: http://xxx:xx/cgi-bin/sendsms? username=xxpassword=xxxto=+595981414913from=1244@3 binfo=CCOTItext=Cotizacion+del+diasmsc-id=tigodlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3 If you do not choose any smsc, kannel will send the sms with a round robin algorythm. Regards. Pablo. 2013/11/26 Alejandro Mussi alemu...@gmail.com Hi, I have 2 smsc setup in kannel. When i send an sms i specified the smsc id in the url but kannel sometimes sends using the other smsc (it seems to choose randomly) Here is my http request for sending a message using smsc-id tigo but in some cases it sends using personal: http://xxx:xx/cgi-bin/sendsms?username=xxpassword=xxxto= +595981414913from=1244@3 binfo=CCOTItext=Cotizacion+del+diasmsc=tigodlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3 Here my conf file group = smsc smsc = smpp host = xxx.xxx.xxx.xx port = 8089 receive-port = 8089 smsc-username = yyy smsc-password = yy system-type = VMA address-range = smsc-id = personal group = smsc smsc = smpp smsc-id = tigo host = xxx.xx.xxx.xx port = 5600 receive-port = 5600 smsc-username = yy smsc-password = yyy system-type = VMA address-range = Thanks -- - Alejandro Mussi Campos Cervera -- Pablo Gus -- - Alejandro Mussi Campos Cervera -- - Alejandro Mussi Campos Cervera
RE: SMSC-ID routing based on to/from on SMSBox?
The destination. From: users [mailto:users-boun...@kannel.org] On Behalf Of Porter, Kelvin Sent: dinsdag 12 november 2013 19:01 To: ha...@aeon.pk Cc: users@kannel.org Subject: RE: SMSC-ID routing based on to/from on SMSBox? Hi, I did some looking and it appears that I might be able to accomplish what I want using allowed- and/or denied-prefix. The description is a bit ambiguous though, these variables determines whether a SMS message can be sent through. The routing is unclear as to whether the prefix filtering is being applied to the sender or the receiver. I could look at the code, but does anyone know off-hand which number is being filtered? Thank you for the pointer. Regards, Kelvin R. Porter From: ha...@aeon.pk [mailto:ha...@aeon.pk] Sent: Tuesday, November 12, 2013 11:27 AM To: Porter, Kelvin Cc: users@kannel.org Subject: Re: SMSC-ID routing based on to/from on SMSBox? Have you tried allowed-smsc-id and denied-smsc-id parameters in group=smsc? On Tue, Nov 12, 2013 at 10:10 PM, Porter, Kelvin kelvin.por...@h3net.com wrote: Hi, The scenario is the following. I have customers that are sending HTTP requests to the SMSBox instance to initiate the sending of MT messages. Depending on the intended destination of those messages (i.e., the to/receiver number), I need to direct the message to one set of SMSC links or the other in the BearerBox. The application performing the HTTP requests does not have any way of determining the set of numbers that need to go to a particular SMSC. So, I am looking for a way to configure the SMSBox so that the SMSC is specified for certain MT destinations. In the opensmppbox, I would use the smsc-route option to set which SMSC was specified before it was sent to the bearerbox. I am looking for equivalent functionality. Have I overlooked something or is the functionality, not there? Thank you. Regards, Kelvin R. Porter From: ha...@aeon.pk [mailto:ha...@aeon.pk] Sent: Tuesday, November 12, 2013 10:48 AM To: Porter, Kelvin Cc: users@kannel.org Subject: Re: SMSC-ID routing based on to/from on SMSBox? Can you explain your scenario with an example please? Would be easier to understand what you need. On Mon, Nov 11, 2013 at 11:56 PM, Porter, Kelvin kelvin.por...@h3net.com wrote: Hi, I am writing to insure that I have not overlooked an option. In my application, I have a need to specify SMSC based on where the message is being sent to (the users will not specify the smsc in the HTTP request). Basically, I need to insure some MT destinations are treated differently that the others, independent of what is specified in the request. I have looked at the source and it does not appear that this functionality is implemented. Have I missed something? I am looking for something akin to the smsc-route option in the opensmppbox. I may attempt to splice in this code from the opensmppbox, if I must. Is there any interest in this functionality? Regards, Kelvin R. Porter
RE: SMSC-ID routing based on to/from on SMSBox?
Hi Stipe,
Thank you for the response. These two architectures give me some options,
until I arrive at a more permanent fix.
Regards,
Kelvin R. Porter
-Original Message-
From: Stipe Tolj [mailto:st...@kannel.org]
Sent: Wednesday, November 13, 2013 3:16 PM
To: Porter, Kelvin
Cc: users@kannel.org
Subject: Re: SMSC-ID routing based on to/from on SMSBox?
Am 11.11.2013 19:56, schrieb Porter, Kelvin:
Hi,
I am writing to insure that I have not overlooked an option. In my
application, I have a need to specify SMSC based on where the message
is being sent to (the users will not specify the smsc in the HTTP request).
Basically, I need to insure some MT destinations are treated
differently that the others, independent of what is specified in the
request. I have looked at the source and it does not appear that this
functionality is implemented. Have I missed something?
I am looking for something akin to the smsc-route option in the
opensmppbox. I may attempt to splice in this code from the
opensmppbox, if I must. Is there any interest in this functionality?
Hi Kelvin,
now, as far as I get you, you want some kind of man in the middle
process that is able to tag the MT with the corresponding smsc-id (that is then
routed for on the bearerbox level), while the external users
(ESMEs) are injecting the MTs in standard fashion way via the smsbox HTTP
sendsms interface, correct?
There are several ways to do this. Let me give you a glance of options:
a) HTTP bridging: means, in a communication chain diagram this:
users -HTTP- smsbox - bearerbox(SMSC HTTP) -HTTP- app -HTTP- smsbox
- bearerbox -SMPP/..- SMSC.
so, the users send the HTTP call, which is always routed (enforced) to a
smsc-id RELAY, which is a HTTP SMSC config that sends again the MT via HTTP to
an application layer, (call is routing layer if you want).
This logical entity can then do MNP (mobile number portability) lookups, decide
which SMSC is in charge to transport the MT, and then tag the MT again with
the correct smsc-id for the successing HTTP call to smsbox, which then get's
routed to the corresponding SMSC instance in bearerbox.
So, effectively you create a HTTP loop to a application layer that does the
routing decision, and then re-inject via smsbox.
b) smppbox bridging: means, in a communication chain diagram this:
users -HTTP- smsbox - bearerbox -SMPP- smppbox - bearerbox -SMPP/..- SMSC
in this case you can utilize the Kannel smppbox plugin API to call for
additional control flows, i.e. via a HTTP callback, or even via
implementation of own plugin logic into the smppbox to resolve the smsc-id you
want to route to.
Option a) is a bit of config mangling, especially if DLRs are involved.
Option b) is faster, but involves the licensing of the commercial Kannel SMPP
v5.0 server (smppbox).
Hope this gives some insight.
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: SMSC-ID routing based on to/from on SMSBox?
Can you explain your scenario with an example please? Would be easier to understand what you need. On Mon, Nov 11, 2013 at 11:56 PM, Porter, Kelvin kelvin.por...@h3net.comwrote: Hi, I am writing to insure that I have not overlooked an option. In my application, I have a need to specify SMSC based on where the message is being sent to (the users will not specify the smsc in the HTTP request). Basically, I need to insure some MT destinations are treated differently that the others, independent of what is specified in the request. I have looked at the source and it does not appear that this functionality is implemented. Have I missed something? I am looking for something akin to the “smsc-route” option in the opensmppbox. I may attempt to splice in this code from the opensmppbox, if I must. Is there any interest in this functionality? Regards, Kelvin R. Porter
RE: SMSC-ID routing based on to/from on SMSBox?
Hi, The scenario is the following... I have customers that are sending HTTP requests to the SMSBox instance to initiate the sending of MT messages. Depending on the intended destination of those messages (i.e., the to/receiver number), I need to direct the message to one set of SMSC links or the other in the BearerBox. The application performing the HTTP requests does not have any way of determining the set of numbers that need to go to a particular SMSC. So, I am looking for a way to configure the SMSBox so that the SMSC is specified for certain MT destinations. In the opensmppbox, I would use the smsc-route option to set which SMSC was specified before it was sent to the bearerbox. I am looking for equivalent functionality. Have I overlooked something or is the functionality, not there? Thank you. Regards, Kelvin R. Porter From: ha...@aeon.pk [mailto:ha...@aeon.pk] Sent: Tuesday, November 12, 2013 10:48 AM To: Porter, Kelvin Cc: users@kannel.org Subject: Re: SMSC-ID routing based on to/from on SMSBox? Can you explain your scenario with an example please? Would be easier to understand what you need. On Mon, Nov 11, 2013 at 11:56 PM, Porter, Kelvin kelvin.por...@h3net.commailto:kelvin.por...@h3net.com wrote: Hi, I am writing to insure that I have not overlooked an option. In my application, I have a need to specify SMSC based on where the message is being sent to (the users will not specify the smsc in the HTTP request). Basically, I need to insure some MT destinations are treated differently that the others, independent of what is specified in the request. I have looked at the source and it does not appear that this functionality is implemented. Have I missed something? I am looking for something akin to the smsc-route option in the opensmppbox. I may attempt to splice in this code from the opensmppbox, if I must. Is there any interest in this functionality? Regards, Kelvin R. Porter
Re: SMSC-ID routing based on to/from on SMSBox?
Have you tried allowed-smsc-id and denied-smsc-id parameters in group=smsc? On Tue, Nov 12, 2013 at 10:10 PM, Porter, Kelvin kelvin.por...@h3net.comwrote: Hi, The scenario is the following… I have customers that are sending HTTP requests to the SMSBox instance to initiate the sending of MT messages. Depending on the intended destination of those messages (i.e., the to/receiver number), I need to direct the message to one set of SMSC links or the other in the BearerBox. The application performing the HTTP requests does not have any way of determining the set of numbers that need to go to a particular SMSC. So, I am looking for a way to configure the SMSBox so that the SMSC is specified for certain MT destinations. In the opensmppbox, I would use the smsc-route option to set which SMSC was specified before it was sent to the bearerbox. I am looking for equivalent functionality. Have I overlooked something or is the functionality, not there? Thank you. Regards, Kelvin R. Porter *From:* ha...@aeon.pk [mailto:ha...@aeon.pk] *Sent:* Tuesday, November 12, 2013 10:48 AM *To:* Porter, Kelvin *Cc:* users@kannel.org *Subject:* Re: SMSC-ID routing based on to/from on SMSBox? Can you explain your scenario with an example please? Would be easier to understand what you need. On Mon, Nov 11, 2013 at 11:56 PM, Porter, Kelvin kelvin.por...@h3net.com wrote: Hi, I am writing to insure that I have not overlooked an option. In my application, I have a need to specify SMSC based on where the message is being sent to (the users will not specify the smsc in the HTTP request). Basically, I need to insure some MT destinations are treated differently that the others, independent of what is specified in the request. I have looked at the source and it does not appear that this functionality is implemented. Have I missed something? I am looking for something akin to the “smsc-route” option in the opensmppbox. I may attempt to splice in this code from the opensmppbox, if I must. Is there any interest in this functionality? Regards, Kelvin R. Porter
RE: SMSC-ID routing based on to/from on SMSBox?
Hi, I did some looking and it appears that I might be able to accomplish what I want using allowed- and/or denied-prefix. The description is a bit ambiguous though, these variables determines whether a SMS message can be sent through. The routing is unclear as to whether the prefix filtering is being applied to the sender or the receiver. I could look at the code, but does anyone know off-hand which number is being filtered? Thank you for the pointer. Regards, Kelvin R. Porter From: ha...@aeon.pk [mailto:ha...@aeon.pk] Sent: Tuesday, November 12, 2013 11:27 AM To: Porter, Kelvin Cc: users@kannel.org Subject: Re: SMSC-ID routing based on to/from on SMSBox? Have you tried allowed-smsc-id and denied-smsc-id parameters in group=smsc? On Tue, Nov 12, 2013 at 10:10 PM, Porter, Kelvin kelvin.por...@h3net.commailto:kelvin.por...@h3net.com wrote: Hi, The scenario is the following... I have customers that are sending HTTP requests to the SMSBox instance to initiate the sending of MT messages. Depending on the intended destination of those messages (i.e., the to/receiver number), I need to direct the message to one set of SMSC links or the other in the BearerBox. The application performing the HTTP requests does not have any way of determining the set of numbers that need to go to a particular SMSC. So, I am looking for a way to configure the SMSBox so that the SMSC is specified for certain MT destinations. In the opensmppbox, I would use the smsc-route option to set which SMSC was specified before it was sent to the bearerbox. I am looking for equivalent functionality. Have I overlooked something or is the functionality, not there? Thank you. Regards, Kelvin R. Porter From: ha...@aeon.pkmailto:ha...@aeon.pk [mailto:ha...@aeon.pkmailto:ha...@aeon.pk] Sent: Tuesday, November 12, 2013 10:48 AM To: Porter, Kelvin Cc: users@kannel.orgmailto:users@kannel.org Subject: Re: SMSC-ID routing based on to/from on SMSBox? Can you explain your scenario with an example please? Would be easier to understand what you need. On Mon, Nov 11, 2013 at 11:56 PM, Porter, Kelvin kelvin.por...@h3net.commailto:kelvin.por...@h3net.com wrote: Hi, I am writing to insure that I have not overlooked an option. In my application, I have a need to specify SMSC based on where the message is being sent to (the users will not specify the smsc in the HTTP request). Basically, I need to insure some MT destinations are treated differently that the others, independent of what is specified in the request. I have looked at the source and it does not appear that this functionality is implemented. Have I missed something? I am looking for something akin to the smsc-route option in the opensmppbox. I may attempt to splice in this code from the opensmppbox, if I must. Is there any interest in this functionality? Regards, Kelvin R. Porter
Re: SMSC-ID routing based on to/from on SMSBox?
I used it long time ago. Cannot recall how exactly I did that. But you need some sort of REGEX combination to route SMS to certain SMSCs, and then putting allowed/denied parameters in place as well. On Tue, Nov 12, 2013 at 11:01 PM, Porter, Kelvin kelvin.por...@h3net.comwrote: Hi, I did some looking and it appears that I might be able to accomplish what I want using allowed- and/or denied-prefix. The description is a bit ambiguous though, these variables determines whether a SMS message can be “sent through”. The routing is unclear as to whether the prefix filtering is being applied to the sender or the receiver. I could look at the code, but does anyone know off-hand which number is being filtered? Thank you for the pointer. Regards, Kelvin R. Porter *From:* ha...@aeon.pk [mailto:ha...@aeon.pk] *Sent:* Tuesday, November 12, 2013 11:27 AM *To:* Porter, Kelvin *Cc:* users@kannel.org *Subject:* Re: SMSC-ID routing based on to/from on SMSBox? Have you tried allowed-smsc-id and denied-smsc-id parameters in group=smsc? On Tue, Nov 12, 2013 at 10:10 PM, Porter, Kelvin kelvin.por...@h3net.com wrote: Hi, The scenario is the following… I have customers that are sending HTTP requests to the SMSBox instance to initiate the sending of MT messages. Depending on the intended destination of those messages (i.e., the to/receiver number), I need to direct the message to one set of SMSC links or the other in the BearerBox. The application performing the HTTP requests does not have any way of determining the set of numbers that need to go to a particular SMSC. So, I am looking for a way to configure the SMSBox so that the SMSC is specified for certain MT destinations. In the opensmppbox, I would use the smsc-route option to set which SMSC was specified before it was sent to the bearerbox. I am looking for equivalent functionality. Have I overlooked something or is the functionality, not there? Thank you. Regards, Kelvin R. Porter *From:* ha...@aeon.pk [mailto:ha...@aeon.pk] *Sent:* Tuesday, November 12, 2013 10:48 AM *To:* Porter, Kelvin *Cc:* users@kannel.org *Subject:* Re: SMSC-ID routing based on to/from on SMSBox? Can you explain your scenario with an example please? Would be easier to understand what you need. On Mon, Nov 11, 2013 at 11:56 PM, Porter, Kelvin kelvin.por...@h3net.com wrote: Hi, I am writing to insure that I have not overlooked an option. In my application, I have a need to specify SMSC based on where the message is being sent to (the users will not specify the smsc in the HTTP request). Basically, I need to insure some MT destinations are treated differently that the others, independent of what is specified in the request. I have looked at the source and it does not appear that this functionality is implemented. Have I missed something? I am looking for something akin to the “smsc-route” option in the opensmppbox. I may attempt to splice in this code from the opensmppbox, if I must. Is there any interest in this functionality? Regards, Kelvin R. Porter
RE: SMSC-ID routing based on to/from on SMSBox?
Use forced-smsc in group=sendsms-user Sent from Samsung Mobile Original message From: ha...@aeon.pk Date:12/11/2013 11:09 PM (GMT+05:00) To: Porter, Kelvin Cc: users@kannel.org Subject: Re: SMSC-ID routing based on to/from on SMSBox? I used it long time ago. Cannot recall how exactly I did that. But you need some sort of REGEX combination to route SMS to certain SMSCs, and then putting allowed/denied parameters in place as well. On Tue, Nov 12, 2013 at 11:01 PM, Porter, Kelvin kelvin.por...@h3net.commailto:kelvin.por...@h3net.com wrote: Hi, I did some looking and it appears that I might be able to accomplish what I want using allowed- and/or denied-prefix. The description is a bit ambiguous though, these variables determines whether a SMS message can be “sent through”. The routing is unclear as to whether the prefix filtering is being applied to the sender or the receiver. I could look at the code, but does anyone know off-hand which number is being filtered? Thank you for the pointer. Regards, Kelvin R. Porter From: ha...@aeon.pkmailto:ha...@aeon.pk [mailto:ha...@aeon.pkmailto:ha...@aeon.pk] Sent: Tuesday, November 12, 2013 11:27 AM To: Porter, Kelvin Cc: users@kannel.orgmailto:users@kannel.org Subject: Re: SMSC-ID routing based on to/from on SMSBox? Have you tried allowed-smsc-id and denied-smsc-id parameters in group=smsc? On Tue, Nov 12, 2013 at 10:10 PM, Porter, Kelvin kelvin.por...@h3net.commailto:kelvin.por...@h3net.com wrote: Hi, The scenario is the following… I have customers that are sending HTTP requests to the SMSBox instance to initiate the sending of MT messages. Depending on the intended destination of those messages (i.e., the to/receiver number), I need to direct the message to one set of SMSC links or the other in the BearerBox. The application performing the HTTP requests does not have any way of determining the set of numbers that need to go to a particular SMSC. So, I am looking for a way to configure the SMSBox so that the SMSC is specified for certain MT destinations. In the opensmppbox, I would use the smsc-route option to set which SMSC was specified before it was sent to the bearerbox. I am looking for equivalent functionality. Have I overlooked something or is the functionality, not there? Thank you. Regards, Kelvin R. Porter From: ha...@aeon.pkmailto:ha...@aeon.pk [mailto:ha...@aeon.pkmailto:ha...@aeon.pk] Sent: Tuesday, November 12, 2013 10:48 AM To: Porter, Kelvin Cc: users@kannel.orgmailto:users@kannel.org Subject: Re: SMSC-ID routing based on to/from on SMSBox? Can you explain your scenario with an example please? Would be easier to understand what you need. On Mon, Nov 11, 2013 at 11:56 PM, Porter, Kelvin kelvin.por...@h3net.commailto:kelvin.por...@h3net.com wrote: Hi, I am writing to insure that I have not overlooked an option. In my application, I have a need to specify SMSC based on where the message is being sent to (the users will not specify the smsc in the HTTP request). Basically, I need to insure some MT destinations are treated differently that the others, independent of what is specified in the request. I have looked at the source and it does not appear that this functionality is implemented. Have I missed something? I am looking for something akin to the “smsc-route” option in the opensmppbox. I may attempt to splice in this code from the opensmppbox, if I must. Is there any interest in this functionality? Regards, Kelvin R. Porter
SMSC-ID routing based on to/from on SMSBox?
Hi, I am writing to insure that I have not overlooked an option. In my application, I have a need to specify SMSC based on where the message is being sent to (the users will not specify the smsc in the HTTP request). Basically, I need to insure some MT destinations are treated differently that the others, independent of what is specified in the request. I have looked at the source and it does not appear that this functionality is implemented. Have I missed something? I am looking for something akin to the smsc-route option in the opensmppbox. I may attempt to splice in this code from the opensmppbox, if I must. Is there any interest in this functionality? Regards, Kelvin R. Porter
DLR rerouting for smsc id Nokia 5800 XpressMusic disabled.
I am getting this error in bearerbox.What is its mean? Please tell me how to get rid of it. DLR rerouting for smsc id Nokia 5800 XpressMusic disabled. -- Thank you !! amritpalpathak.blogspot.com
RE: Behavior of multiple binds with the same smsc-id
Look for smsc2_rout() in gw/bb_smscconn.c. == Rene -Original Message- From: Garth Patil [mailto:garthpa...@gmail.com] Sent: Friday, 27 May, 2011 05:33 To: Rene Kluwen Cc: Juan Nin; Users mailing list Subject: Re: Behavior of multiple binds with the same smsc-id Thanks Rene. Can you point me to the part of the code that does this? On Thu, May 26, 2011 at 2:02 PM, Rene Kluwen rene.klu...@chimit.nl wrote: Yes, it will load balance. But as far as I recall, not in a round robin fashion. Messages will be sent to the smsc with the least messages in queue. Which will always be the first one, if load is low. == Rene It will load balance. I believe it does it on a round robin fashion On Thursday, May 26, 2011, Garth Patil garthpa...@gmail.com wrote: Hi All, I have a question I was unable to reconcile from the documentation regarding the behavior of multiple binds with the same smsc-id. I have 2 pairs of TX an RX binds, with each pair connected to different data centers of the same operator. If I assign the same smsc-id to all 4 binds, what is the behavior of kannel when I send an SMS that specifies that smsc-id? Does it choose one of the TX binds at random, or load balance between the two? Thanks, Garth smime.p7s Description: S/MIME cryptographic signature
Behavior of multiple binds with the same smsc-id
Hi All, I have a question I was unable to reconcile from the documentation regarding the behavior of multiple binds with the same smsc-id. I have 2 pairs of TX an RX binds, with each pair connected to different data centers of the same operator. If I assign the same smsc-id to all 4 binds, what is the behavior of kannel when I send an SMS that specifies that smsc-id? Does it choose one of the TX binds at random, or load balance between the two? Thanks, Garth
Re: Behavior of multiple binds with the same smsc-id
It will load balance. I believe it does it on a round robin fashion On Thursday, May 26, 2011, Garth Patil garthpa...@gmail.com wrote: Hi All, I have a question I was unable to reconcile from the documentation regarding the behavior of multiple binds with the same smsc-id. I have 2 pairs of TX an RX binds, with each pair connected to different data centers of the same operator. If I assign the same smsc-id to all 4 binds, what is the behavior of kannel when I send an SMS that specifies that smsc-id? Does it choose one of the TX binds at random, or load balance between the two? Thanks, Garth
Re: Behavior of multiple binds with the same smsc-id
Yes, it will load balance. But as far as I recall, not in a round robin fashion. Messages will be sent to the smsc with the least messages in queue. Which will always be the first one, if load is low. == Rene It will load balance. I believe it does it on a round robin fashion On Thursday, May 26, 2011, Garth Patil garthpa...@gmail.com wrote: Hi All, I have a question I was unable to reconcile from the documentation regarding the behavior of multiple binds with the same smsc-id. I have 2 pairs of TX an RX binds, with each pair connected to different data centers of the same operator. If I assign the same smsc-id to all 4 binds, what is the behavior of kannel when I send an SMS that specifies that smsc-id? Does it choose one of the TX binds at random, or load balance between the two? Thanks, Garth
Re: Behavior of multiple binds with the same smsc-id
You're right! On Thursday, May 26, 2011, Rene Kluwen rene.klu...@chimit.nl wrote: Yes, it will load balance. But as far as I recall, not in a round robin fashion. Messages will be sent to the smsc with the least messages in queue. Which will always be the first one, if load is low. == Rene It will load balance. I believe it does it on a round robin fashion On Thursday, May 26, 2011, Garth Patil garthpa...@gmail.com wrote: Hi All, I have a question I was unable to reconcile from the documentation regarding the behavior of multiple binds with the same smsc-id. I have 2 pairs of TX an RX binds, with each pair connected to different data centers of the same operator. If I assign the same smsc-id to all 4 binds, what is the behavior of kannel when I send an SMS that specifies that smsc-id? Does it choose one of the TX binds at random, or load balance between the two? Thanks, Garth
Re: DLR rerouting for smsc id some name disabled.
Thanks for the answer Nikos, I don't completely understand if I need to do a smsc retouting or not. What I need is to store the DLR in the MySQL database... and for some reason my dlr table is empty... for some reason my configuration or something else is not allowing or is not indicating to do it... SELECT count(*) FROM dlr; count(*) --- 0 Aldo Zavala Mobile (760).556.5050 24/7(760).890.4221 _ From: Nikos Balkanas [mailto:nbalka...@gmail.com] To: us...@vm1.kannel.org, Aldo Zavala [mailto:a...@cleartalk.net] Sent: Wed, 27 Apr 2011 20:06:00 -0700 Subject: Re: DLR rerouting for smsc id some name disabled. Hi, This is related with smsc retouting. If you have this enabled then DLRs are rerouted as well. Bad warning, you can safely ignore. BR, Nikos - Original Message - From: Aldo Zavala To: users@kannel.org Sent: Thursday, April 28, 2011 2:38 AM Subject: DLR rerouting for smsc id some name disabled. Sorry if somebody might get this message twice but I posted it 14 hours ago and I still don't see it in the user's Digest. Hi, I was tying to google this and still don't find anything definitive, what are the causes of these messages in the bearerbox.log? [0] INFO: DLR rerouting for smsc id some name disabled. Note: I am trying to setup DLR using mysql method and still no success =( any help will be really appreciated! Aldo Zavala
Re: How can we choose SMSC-ID in sqlbox,
Clarification: As Rene states, use allowed-smsc-id and denied-smsc-id in group smsc in kannel.conf. Otherwise bb tries to load balnce between available SMScs. BR, Nikos - Original Message - From: Rene Kluwen To: 'Anshu Sah' ; 'users' Sent: Sunday, October 03, 2010 11:19 PM Subject: RE: How can we choose SMSC-ID in sqlbox, Try using allowed-smsc-id in your group = smsc From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Anshu Sah Sent: Sunday, 03 October, 2010 21:30 To: users Subject: How can we choose SMSC-ID in sqlbox, Hello team, I am trying to use sqlbox, but that is randomly selecting One of my 3 SMSCs, Even i insert column smsc_id into table send_sms, It doesn't effect to working of sqlbox plz suggest. Regards Anshu Sah
Re: EMI DLR uniqueness, smsc-id/timestamp problem
Hi, This is a known issue with DLRs. Ts is supposed to be a unique foreign-id, not a timestamp, at least with SMPP. Some time ago a patch was provided to include also destination number into DLR matching. However, that clashed with existing SMScs, which do not report destination numbers in their DLRs, so i guess never made it to CVS. Maybe this patch needs to be configurable in each SMSc. BR, Nikos - Original Message - From: Luis Tiago Rico To: users@kannel.org Sent: Tuesday, May 04, 2010 9:19 PM Subject: EMI DLR uniqueness, smsc-id/timestamp problem Hi to all, I'm using Kannel 1.4.3 and I'm having this problem with some switched/mismatch delivery reports! It happens when I send several MT to the same SMSC at the same time, using a EMI connection... Well, from what I got, when a DLR arrives, Kannel only takes in account the SMSC ID and the Timestamp. This causes a loose of uniqueness, since only timestamp and smsc-id are used as unique id (no destination number). 2010-05-04 16:54:26 [18405] [12] DEBUG: EMI2[68959-TMN]: emi2 parsing packet: ^B02/00368/O/53/68959/962834401/040510165418/1/107/040510165422/3//4120737561206D656E736167656D206461732031363A35343A31382064652031302D30352D3034207061726120303033353139363238333434303120666F69206775617264616461206E6F2043656E74726F206465204D656E736167656E7320646120544D4E2E204D6F7469766F3A2054656C656D6F76656C206465736C696761646F20282020323729/46^C 2010-05-04 16:54:26 [18405] [12] DEBUG: DLR[pgsql]: Looking for DLR smsc=68959-TMN, ts=040510165418, dst=962834401, type=4 2010-05-04 16:54:26 [18405] [12] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM dlr WHERE smsc='68959-TMN' AND ts='040510165418' LIMIT 1; So, if two or more messages have the same timestamp, it's not guaranteed that the arrived DLR's are matched against the correct DLR entry on database (and then the problem spreads, as the dlr_url are wrong, etc, etc). Correct me if I'm wrong but from my research on the mailing list I found this problem was a old known one and there is/was a patch for it (adding the destination number to the queries)! As I was reading a bit more on the mailing list, I found that the problem was solved in the after releases... Well it was a bit wired because in my log files the query only takes in account the mentioned parameters... Reading a bit more I found that for some reason the patch was not included in the latest release (see http://www.mail-archive.com/users@kannel.org/msg19454.html)! Sincerely I got a bit confused here with these patches included/not included in the releases So my questions are: Is this patch the way to solve the problem or there is something that I'm missing here? Why this patch was not included/forgotten in the latest kannel release (1.4.3)? Where can I find this patch and how to install it (just copy files / compile kannel) ? Many thanks in advance, Luis Rico
FW: EMI DLR uniqueness, smsc-id/timestamp problem
Hi Nikos, Thank you for your reply. I was already guessing why the patch was not included Never the less, I will download the src code from cvs, and apply the patch to produce my release I will have to change it a bit more, because some of my smsc dont send the country code prefix on destination numbers, like I send on the MT, so I need to include them in dlr search. I could put a LIKE %destination condition on the query, but I dont want to slow down performance What do you think? As you say, it will be great to include on the smsc configuration some property that if set would include the destination number on the dlr search query (or something like that). BR, Luis Rico From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: quarta-feira, 5 de Maio de 2010 10:57 To: Luis Tiago Rico; us...@vm1.kannel.org Subject: Re: EMI DLR uniqueness, smsc-id/timestamp problem Hi, This is a known issue with DLRs. Ts is supposed to be a unique foreign-id, not a timestamp, at least with SMPP. Some time ago a patch was provided to include also destination number into DLR matching. However, that clashed with existing SMScs, which do not report destination numbers in their DLRs, so i guess never made it to CVS. Maybe this patch needs to be configurable in each SMSc. BR, Nikos - Original Message - From: Luís Tiago Rico To: users@kannel.org Sent: Tuesday, May 04, 2010 9:19 PM Subject: EMI DLR uniqueness, smsc-id/timestamp problem Hi to all, I'm using Kannel 1.4.3 and I'm having this problem with some switched/mismatch delivery reports! It happens when I send several MT to the same SMSC at the same time, using a EMI connection... Well, from what I got, when a DLR arrives, Kannel only takes in account the SMSC ID and the Timestamp. This causes a loose of uniqueness, since only timestamp and smsc-id are used as unique id (no destination number). 2010-05-04 16:54:26 [18405] [12] DEBUG: EMI2[68959-TMN]: emi2 parsing packet: ^B02/00368/O/53/68959/962834401/040510165418/1/107/040510165422 /3//4120737561206D656E736167656D206461732031363A35343A31382064652031302D3035 2D3034207061726120303033353139363238333434303120666F69206775617264616461206E 6F2043656E74726F206465204D656E736167656E7320646120544D4E2E204D6F7469766F3A20 54656C656D6F76656C206465736C696761646F20282020323729/46^C 2010-05-04 16:54:26 [18405] [12] DEBUG: DLR[pgsql]: Looking for DLR smsc=68959-TMN, ts=040510165418, dst=962834401, type=4 2010-05-04 16:54:26 [18405] [12] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM dlr WHERE smsc='68959-TMN' AND ts='040510165418' LIMIT 1; So, if two or more messages have the same timestamp, it's not guaranteed that the arrived DLR's are matched against the correct DLR entry on database (and then the problem spreads, as the dlr_url are wrong, etc, etc). Correct me if I'm wrong but from my research on the mailing list I found this problem was a old known one and there is/was a patch for it (adding the destination number to the queries)! As I was reading a bit more on the mailing list, I found that the problem was solved in the after releases... Well it was a bit wired because in my log files the query only takes in account the mentioned parameters... Reading a bit more I found that for some reason the patch was not included in the latest release (see http://www.mail-archive.com/users@kannel.org/msg19454.html)! Sincerely I got a bit confused here with these patches included/not included in the releases So my questions are: Is this patch the way to solve the problem or there is something that I'm missing here? Why this patch was not included/forgotten in the latest kannel release (1.4.3)? Where can I find this patch and how to install it (just copy files / compile kannel) ? Many thanks in advance, Luis Rico
Re: EMI DLR uniqueness, smsc-id/timestamp problem
Hi, Since you do not seem shy to go through the code, why don't you try making the patch configurable? As far as prefices go, look into the unified-prefix variable in configuration. That way kannel will strip off the extra prefix and do an exact match. BR, Nikos - Original Message - From: Luis Tiago Rico To: us...@vm1.kannel.org Sent: Wednesday, May 05, 2010 5:02 PM Subject: FW: EMI DLR uniqueness, smsc-id/timestamp problem Hi Nikos, Thank you for your reply. I was already guessing why the patch was not included… Never the less, I will download the src code from cvs, and apply the patch to produce my release… I will have to change it a bit more, because some of my smsc don’t send the country code prefix on destination numbers, like I send on the MT, so I need to include them in dlr search. I could put a “LIKE %destination” condition on the query, but I don’t want to slow down performance… What do you think? As you say, it will be great to include on the smsc configuration some property that if set would include the destination number on the dlr search query (or something like that). BR, Luis Rico From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: quarta-feira, 5 de Maio de 2010 10:57 To: Luis Tiago Rico; us...@vm1.kannel.org Subject: Re: EMI DLR uniqueness, smsc-id/timestamp problem Hi, This is a known issue with DLRs. Ts is supposed to be a unique foreign-id, not a timestamp, at least with SMPP. Some time ago a patch was provided to include also destination number into DLR matching. However, that clashed with existing SMScs, which do not report destination numbers in their DLRs, so i guess never made it to CVS. Maybe this patch needs to be configurable in each SMSc. BR, Nikos - Original Message - From: Luνs Tiago Rico To: users@kannel.org Sent: Tuesday, May 04, 2010 9:19 PM Subject: EMI DLR uniqueness, smsc-id/timestamp problem Hi to all, I'm using Kannel 1.4.3 and I'm having this problem with some switched/mismatch delivery reports! It happens when I send several MT to the same SMSC at the same time, using a EMI connection... Well, from what I got, when a DLR arrives, Kannel only takes in account the SMSC ID and the Timestamp. This causes a loose of uniqueness, since only timestamp and smsc-id are used as unique id (no destination number). 2010-05-04 16:54:26 [18405] [12] DEBUG: EMI2[68959-TMN]: emi2 parsing packet: ^B02/00368/O/53/68959/962834401/040510165418/1/107/040510165422/3//4120737561206D656E736167656D206461732031363A35343A31382064652031302D30352D3034207061726120303033353139363238333434303120666F69206775617264616461206E6F2043656E74726F206465204D656E736167656E7320646120544D4E2E204D6F7469766F3A2054656C656D6F76656C206465736C696761646F20282020323729/46^C 2010-05-04 16:54:26 [18405] [12] DEBUG: DLR[pgsql]: Looking for DLR smsc=68959-TMN, ts=040510165418, dst=962834401, type=4 2010-05-04 16:54:26 [18405] [12] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM dlr WHERE smsc='68959-TMN' AND ts='040510165418' LIMIT 1; So, if two or more messages have the same timestamp, it's not guaranteed that the arrived DLR's are matched against the correct DLR entry on database (and then the problem spreads, as the dlr_url are wrong, etc, etc). Correct me if I'm wrong but from my research on the mailing list I found this problem was a old known one and there is/was a patch for it (adding the destination number to the queries)! As I was reading a bit more on the mailing list, I found that the problem was solved in the after releases... Well it was a bit wired because in my log files the query only takes in account the mentioned parameters... Reading a bit more I found that for some reason the patch was not included in the latest release (see http://www.mail-archive.com/users@kannel.org/msg19454.html)! Sincerely I got a bit confused here with these patches included/not included in the releases So my questions are: Is this patch the way to solve the problem or there is something that I'm missing here? Why this patch was not included/forgotten in the latest kannel release (1.4.3)? Where can I find this patch and how to install it (just copy files / compile kannel) ? Many thanks in advance, Luis Rico
RE: EMI DLR uniqueness, smsc-id/timestamp problem
Hi again Nikos, Thanks for the kick reply. Well let’s see if got time to do all that… Do you think unified-prefix configuration also works on received DLR destination number? I was looking exactly that on the manual and nothing mention about DLR, only MT and MO! BR, Luis Rico From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: quarta-feira, 5 de Maio de 2010 15:10 To: Luis Tiago Rico; us...@vm1.kannel.org Subject: Re: EMI DLR uniqueness, smsc-id/timestamp problem Hi, Since you do not seem shy to go through the code, why don't you try making the patch configurable? As far as prefices go, look into the unified-prefix variable in configuration. That way kannel will strip off the extra prefix and do an exact match. BR, Nikos - Original Message - From: Luís Tiago Rico mailto:lti...@present-technologies.com To: us...@vm1.kannel.org Sent: Wednesday, May 05, 2010 5:02 PM Subject: FW: EMI DLR uniqueness, smsc-id/timestamp problem Hi Nikos, Thank you for your reply. I was already guessing why the patch was not included… Never the less, I will download the src code from cvs, and apply the patch to produce my release… I will have to change it a bit more, because some of my smsc don’t send the country code prefix on destination numbers, like I send on the MT, so I need to include them in dlr search. I could put a “LIKE %destination” condition on the query, but I don’t want to slow down performance… What do you think? As you say, it will be great to include on the smsc configuration some property that if set would include the destination number on the dlr search query (or something like that). BR, Luis Rico From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: quarta-feira, 5 de Maio de 2010 10:57 To: Luis Tiago Rico; us...@vm1.kannel.org Subject: Re: EMI DLR uniqueness, smsc-id/timestamp problem Hi, This is a known issue with DLRs. Ts is supposed to be a unique foreign-id, not a timestamp, at least with SMPP. Some time ago a patch was provided to include also destination number into DLR matching. However, that clashed with existing SMScs, which do not report destination numbers in their DLRs, so i guess never made it to CVS. Maybe this patch needs to be configurable in each SMSc. BR, Nikos - Original Message - From: Luνs Tiago Rico To: users@kannel.org Sent: Tuesday, May 04, 2010 9:19 PM Subject: EMI DLR uniqueness, smsc-id/timestamp problem Hi to all, I'm using Kannel 1.4.3 and I'm having this problem with some switched/mismatch delivery reports! It happens when I send several MT to the same SMSC at the same time, using a EMI connection... Well, from what I got, when a DLR arrives, Kannel only takes in account the SMSC ID and the Timestamp. This causes a loose of uniqueness, since only timestamp and smsc-id are used as unique id (no destination number). 2010-05-04 16:54:26 [18405] [12] DEBUG: EMI2[68959-TMN]: emi2 parsing packet: ^B02/00368/O/53/68959/962834401/040510165418/1/107/040510165422 /3//4120737561206D656E736167656D206461732031363A35343A31382064652031302D3035 2D3034207061726120303033353139363238333434303120666F69206775617264616461206E 6F2043656E74726F206465204D656E736167656E7320646120544D4E2E204D6F7469766F3A20 54656C656D6F76656C206465736C696761646F20282020323729/46^C 2010-05-04 16:54:26 [18405] [12] DEBUG: DLR[pgsql]: Looking for DLR smsc=68959-TMN, ts=040510165418, dst=962834401, type=4 2010-05-04 16:54:26 [18405] [12] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM dlr WHERE smsc='68959-TMN' AND ts='040510165418' LIMIT 1; So, if two or more messages have the same timestamp, it's not guaranteed that the arrived DLR's are matched against the correct DLR entry on database (and then the problem spreads, as the dlr_url are wrong, etc, etc). Correct me if I'm wrong but from my research on the mailing list I found this problem was a old known one and there is/was a patch for it (adding the destination number to the queries)! As I was reading a bit more on the mailing list, I found that the problem was solved in the after releases... Well it was a bit wired because in my log files the query only takes in account the mentioned parameters... Reading a bit more I found that for some reason the patch was not included in the latest release (see http://www.mail-archive.com/users@kannel.org/msg19454.html)! Sincerely I got a bit confused here with these patches included/not included in the releases So my questions are: Is this patch the way to solve the problem or there is something that I'm missing here? Why this patch was not included/forgotten in the latest kannel release (1.4. 3)? Where can I find this patch and how to install it (just copy files / compile kannel) ? Many thanks in advance, Luis Rico
Re: EMI DLR uniqueness, smsc-id/timestamp problem
But...You mentioned that some of your smscs don't send it. That's why I proposed it. Otherwise it could be another configuration task, this time per smsc. It is more efficient to truncate it in the code than in the database. BR, Nikos - Original Message - From: Luis Tiago Rico To: 'Nikos Balkanas' ; us...@vm1.kannel.org Sent: Wednesday, May 05, 2010 5:56 PM Subject: RE: EMI DLR uniqueness, smsc-id/timestamp problem Hi again Nikos, Thanks for the kick reply. Well let΅―s see if got time to do all that΅ Do you think unified-prefix configuration also works on received DLR destination number? I was looking exactly that on the manual and nothing mention about DLR, only MT and MO! BR, Luis Rico From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: quarta-feira, 5 de Maio de 2010 15:10 To: Luis Tiago Rico; us...@vm1.kannel.org Subject: Re: EMI DLR uniqueness, smsc-id/timestamp problem Hi, Since you do not seem shy to go through the code, why don't you try making the patch configurable? As far as prefices go, look into the unified-prefix variable in configuration. That way kannel will strip off the extra prefix and do an exact match. BR, Nikos - Original Message - From: Lu¨�s Tiago Rico To: us...@vm1.kannel.org Sent: Wednesday, May 05, 2010 5:02 PM Subject: FW: EMI DLR uniqueness, smsc-id/timestamp problem Hi Nikos, Thank you for your reply. I was already guessing why the patch was not included΅ Never the less, I will download the src code from cvs, and apply the patch to produce my release΅ I will have to change it a bit more, because some of my smsc don΅―t send the country code prefix on destination numbers, like I send on the MT, so I need to include them in dlr search. I could put a ΅°LIKE %destination΅± condition on the query, but I don΅―t want to slow down performance΅ What do you think? As you say, it will be great to include on the smsc configuration some property that if set would include the destination number on the dlr search query (or something like that). BR, Luis Rico From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: quarta-feira, 5 de Maio de 2010 10:57 To: Luis Tiago Rico; us...@vm1.kannel.org Subject: Re: EMI DLR uniqueness, smsc-id/timestamp problem Hi, This is a known issue with DLRs. Ts is supposed to be a unique foreign-id, not a timestamp, at least with SMPP. Some time ago a patch was provided to include also destination number into DLR matching. However, that clashed with existing SMScs, which do not report destination numbers in their DLRs, so i guess never made it to CVS. Maybe this patch needs to be configurable in each SMSc. BR, Nikos - Original Message - From: Lu¦Νs Tiago Rico To: users@kannel.org Sent: Tuesday, May 04, 2010 9:19 PM Subject: EMI DLR uniqueness, smsc-id/timestamp problem Hi to all, I'm using Kannel 1.4.3 and I'm having this problem with some switched/mismatch delivery reports! It happens when I send several MT to the same SMSC at the same time, using a EMI connection... Well, from what I got, when a DLR arrives, Kannel only takes in account the SMSC ID and the Timestamp. This causes a loose of uniqueness, since only timestamp and smsc-id are used as unique id (no destination number). 2010-05-04 16:54:26 [18405] [12] DEBUG: EMI2[68959-TMN]: emi2 parsing packet: ^B02/00368/O/53/68959/962834401/040510165418/1/107/040510165422/3//4120737561206D656E736167656D206461732031363A35343A31382064652031302D30352D3034207061726120303033353139363238333434303120666F69206775617264616461206E6F2043656E74726F206465204D656E736167656E7320646120544D4E2E204D6F7469766F3A2054656C656D6F76656C206465736C696761646F20282020323729/46^C 2010-05-04 16:54:26 [18405] [12] DEBUG: DLR[pgsql]: Looking for DLR smsc=68959-TMN, ts=040510165418, dst=962834401, type=4 2010-05-04 16:54:26 [18405] [12] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM dlr WHERE smsc='68959-TMN' AND ts='040510165418' LIMIT 1; So, if two or more messages have the same timestamp, it's not guaranteed that the arrived DLR's are matched against the correct DLR entry on database (and then the problem spreads, as the dlr_url are wrong, etc, etc). Correct me if I'm wrong but from my research on the mailing list I found this problem was a old known one and there is/was a patch for it (adding the destination number to the queries)! As I was reading a bit more on the mailing list, I found that the problem was solved in the after releases... Well it was a bit wired because in my log files the query only takes in account the mentioned parameters... Reading a bit more I found that for some reason the patch was not included in the latest release (see http://www.mail-archive.com/users@kannel.org/msg19454.html)! Sincerely I got a bit confused here with these patches included/not included in the releases So my questions are: Is this patch the way to solve the problem or there is something that I'm missing here? Why this patch
RE: EMI DLR uniqueness, smsc-id/timestamp problem
Hi again Nikos, Sorry if I was miss understood. The problem is I send a MT to the smsc with the prefix, and the smsc returns a dlr with destination without the prefix! So I have entry on dlr DB with prefix and my query has to reflect that. Again I agree with you with some kind of dlr-unified-prefix configuration per smsc. My big problem here is where to start changing the code for adding new configurations, has I opened the project and I feel like a cow watching to a palace :) ...Seems I have to lose some hours of sleep! Feel free to do any comments! BR, Luis Rico PS: I think this thread is about to go to dev... -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: quarta-feira, 5 de Maio de 2010 16:14 To: Luis Tiago Rico; us...@vm1.kannel.org Subject: Re: EMI DLR uniqueness, smsc-id/timestamp problem But...You mentioned that some of your smscs don't send it. That's why I proposed it. Otherwise it could be another configuration task, this time per smsc. It is more efficient to truncate it in the code than in the database. BR, Nikos - Original Message - From: Luis Tiago Rico To: 'Nikos Balkanas' ; us...@vm1.kannel.org Sent: Wednesday, May 05, 2010 5:56 PM Subject: RE: EMI DLR uniqueness, smsc-id/timestamp problem Hi again Nikos, Thanks for the kick reply. Well let΅―s see if got time to do all that΅ Do you think unified-prefix configuration also works on received DLR destination number? I was looking exactly that on the manual and nothing mention about DLR, only MT and MO! BR, Luis Rico From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: quarta-feira, 5 de Maio de 2010 15:10 To: Luis Tiago Rico; us...@vm1.kannel.org Subject: Re: EMI DLR uniqueness, smsc-id/timestamp problem Hi, Since you do not seem shy to go through the code, why don't you try making the patch configurable? As far as prefices go, look into the unified-prefix variable in configuration. That way kannel will strip off the extra prefix and do an exact match. BR, Nikos - Original Message - From: Lu¨s Tiago Rico To: us...@vm1.kannel.org Sent: Wednesday, May 05, 2010 5:02 PM Subject: FW: EMI DLR uniqueness, smsc-id/timestamp problem Hi Nikos, Thank you for your reply. I was already guessing why the patch was not included΅ Never the less, I will download the src code from cvs, and apply the patch to produce my release΅ I will have to change it a bit more, because some of my smsc don΅―t send the country code prefix on destination numbers, like I send on the MT, so I need to include them in dlr search. I could put a ΅°LIKE %destination΅± condition on the query, but I don΅―t want to slow down performance΅ What do you think? As you say, it will be great to include on the smsc configuration some property that if set would include the destination number on the dlr search query (or something like that). BR, Luis Rico From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: quarta-feira, 5 de Maio de 2010 10:57 To: Luis Tiago Rico; us...@vm1.kannel.org Subject: Re: EMI DLR uniqueness, smsc-id/timestamp problem Hi, This is a known issue with DLRs. Ts is supposed to be a unique foreign-id, not a timestamp, at least with SMPP. Some time ago a patch was provided to include also destination number into DLR matching. However, that clashed with existing SMScs, which do not report destination numbers in their DLRs, so i guess never made it to CVS. Maybe this patch needs to be configurable in each SMSc. BR, Nikos - Original Message - From: Lu¦Νs Tiago Rico To: users@kannel.org Sent: Tuesday, May 04, 2010 9:19 PM Subject: EMI DLR uniqueness, smsc-id/timestamp problem Hi to all, I'm using Kannel 1.4.3 and I'm having this problem with some switched/mismatch delivery reports! It happens when I send several MT to the same SMSC at the same time, using a EMI connection... Well, from what I got, when a DLR arrives, Kannel only takes in account the SMSC ID and the Timestamp. This causes a loose of uniqueness, since only timestamp and smsc-id are used as unique id (no destination number). 2010-05-04 16:54:26 [18405] [12] DEBUG: EMI2[68959-TMN]: emi2 parsing packet: ^B02/00368/O/53/68959/962834401/040510165418/1/107/040510165422/3//4120737561206D656E736167656D206461732031363A35343A31382064652031302D30352D3034207061726120303033353139363238333434303120666F69206775617264616461206E6F2043656E74726F206465204D656E736167656E7320646120544D4E2E204D6F7469766F3A2054656C656D6F76656C206465736C696761646F20282020323729/46^C 2010-05-04 16:54:26 [18405] [12] DEBUG: DLR[pgsql]: Looking for DLR smsc=68959-TMN, ts=040510165418, dst=962834401, type=4 2010-05-04 16:54:26 [18405] [12] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM dlr WHERE smsc='68959-TMN' AND ts='040510165418' LIMIT 1; So, if two or more messages have the same timestamp, it's not guaranteed that the arrived DLR's are matched against the correct DLR entry on database
EMI DLR uniqueness, smsc-id/timestamp problem
Hi to all, I'm using Kannel 1.4.3 and I'm having this problem with some switched/mismatch delivery reports! It happens when I send several MT to the same SMSC at the same time, using a EMI connection... Well, from what I got, when a DLR arrives, Kannel only takes in account the SMSC ID and the Timestamp. This causes a loose of uniqueness, since only timestamp and smsc-id are used as unique id (no destination number). 2010-05-04 16:54:26 [18405] [12] DEBUG: EMI2[68959-TMN]: emi2 parsing packet: ^B02/00368/O/53/68959/962834401/040510165418/1/107/040510165422/3//4120737561206D656E736167656D206461732031363A35343A31382064652031302D30352D3034207061726120303033353139363238333434303120666F69206775617264616461206E6F2043656E74726F206465204D656E736167656E7320646120544D4E2E204D6F7469766F3A2054656C656D6F76656C206465736C696761646F20282020323729/46^C 2010-05-04 16:54:26 [18405] [12] DEBUG: DLR[pgsql]: Looking for DLR smsc=68959-TMN, ts=040510165418, dst=962834401, type=4 2010-05-04 16:54:26 [18405] [12] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM dlr WHERE smsc='68959-TMN' AND ts='040510165418' LIMIT 1; So, if two or more messages have the same timestamp, it's not guaranteed that the arrived DLR's are matched against the correct DLR entry on database (and then the problem spreads, as the dlr_url are wrong, etc, etc). Correct me if I'm wrong but from my research on the mailing list I found this problem was a old known one and there is/was a patch for it (adding the destination number to the queries)! As I was reading a bit more on the mailing list, I found that the problem was solved in the after releases... Well it was a bit wired because in my log files the query only takes in account the mentioned parameters... Reading a bit more I found that for some reason the patch was not included in the latest release (see http://www.mail-archive.com/users@kannel.org/msg19454.html)! Sincerely I got a bit confused here with these patches included/not included in the releases So my questions are: Is this patch the way to solve the problem or there is something that I'm missing here? Why this patch was not included/forgotten in the latest kannel release (1.4.3)? Where can I find this patch and how to install it (just copy files / compile kannel) ? Many thanks in advance, Luis Rico
smsc-id forwarding between several kannels
Hi What I want to have is: The message commes to the kannel network in kannel1 with smsc = 1, it forwadrs the message to a 3rd kannel smsc, through a 2nd kannel but want to have kannel 3 know that the message entered into the system through kannel1/smsc1 and not from kannel2/smsc2 that is the smsc that delivered the message to kannel3/smsc3 sms -- [Kannel SMSC id 1] -- [Kannel SMSC id 2] -- [Kannel SMSC id 3] As per the user guide, I'm supposed to use %i or %I (What is the difference?) but in my tests, kannel3/smsc3 always receve the smsc origin as kannel2/smsc2 instead of kannel1/smsc1. Regards Alvaro
2 connections and use of allowed-smsc-id preferred-smsc-id
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
Re: 2 connections and use of allowed-smsc-id preferred-smsc-id
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
DLR rerouting for smsc id my_route disabled: how to enable?
Hi, my request is already in the subject. When I start the bearerbox I can see that message and I think this is the problem why I didn't receive delivery report. Does anybody know how to enable it? Thank You!
Re: DLR rerouting for smsc id my_route disabled: how to enable?
Hai, did you get any error message while starting bearerbox. mail us your log (which shows problem). Then only people can able to help you.regards,PrasadOn 5/3/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi,my request is already in the subject.When I start the bearerbox I can see that message and I think this is theproblem why I didn't receive delivery report.Does anybody know how to enable it?Thank You! -- Thanks,Prasad KavuriSoftware ConsultantMobile Lifestyle BerhadUnit F10 Block 3 (2320)Century Square63000 CyberjayaMalaysia.Tel: +60 3 8318 6691 Fax:+60 3 8318 7760HP: +60 12 927 4711
Re: Wrong smsc-id used for submit_sm
You need to specify some of the parameters denied-smsc-id / allowed-smsc-id / preferred-smsc-id at smsc config level. More info in the User's Guide ;-) On Tuesday 16 August 2005 13:35, Konstantin Vayner wrote: Hi List, Here's my problem.. I have several links up in my setup - some of them SMPP , some EMI2 When i submit an MT to sendsms (over http), i specify smsc-id to be used for sending. (by smsc= uri parameter) However, in some cases (it does not happen all the time), the real smsc used to send the message (that, i can see in bearerbox.log) is different. I am not sure if that it's entirely correct, but as far as i can see this substitution happens when smsc-id i use is EMI2. (maybe i did not notice this on other links though) For example, i submit msg with smsc=orange_ro_1353 , and it's going out through smsc-id mobileway_uk .. (both are configured properly and deliver messages both ways, the substitution does not happen on every such msg) Question is... why can this thing happen, and how can i prevent kannel from doing that? For what it's worth, if the smsc i requested is down and msg cannot be sent through it, i prefer such message to be dropped rather than being attempted to deliver through other link (as every link i have is limited for delivery to its own destination only). Regards, Konstantin P.S. My configuration (relevant parts of it :) ) OS: Fedora Core 2 Kannel: kannel-1.3.2-3.1.fc2.fr (useragent: Kannel/1.3.2-mblox) ^^ kannel is binary distribution that comes with fedora core2 kannel.conf (partial): group = core admin-port = 13000 smsbox-port = 13001 wapbox-port = 13002 admin-password = bar status-password = foo log-file = /var/log/kannel/bearerbox.log access-log = /var/log/kannel/bearerbox-access.log log-level = 0 admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 # SMSC SMPP group = smsc smsc = smpp smsc-id = mobileway_uk_orange host = xxx.xxx.xxx.xxx port = transceiver-mode = true smsc-username = smsc-password = system-type = VMA address-range = my-number = enquire-link-interval = 120 reconnect-delay = 30 source-addr-ton = 5 source-addr-npi = 0 source-addr-autodetect = false # SMSC UCP group = smsc smsc = emi smsc-id = orange_ro_1351 host = xxx.xxx.xxx.xxx port = smsc-username = smsc-password = my-number = 1351 keepalive = 55 receive-port = idle-timeout = 30 # SMSBOX SETUP group = smsbox bearerbox-host = localhost #smsbox-id = smsbox1 sendsms-port = #global-sender = 123 log-file = /var/log/kannel/smsbox.log access-log = /var/log/kannel/smsbox-access.log log-level = 0 # SEND-SMS USERS group = sendsms-user username = password = user-deny-ip = *.*.*.* user-allow-ip = 127.0.0.1 default-smsc = # ^^ what is this value used for? is it unused if i specify smsc-id on request? # smsc-id i have here is neither mobileway_uk_orange nor orange_ro_1351 ... # Forward everything to VAST group = sms-service name = vast keyword = default get-url = http://vast-host/kannel/mo?from=%qto=%Qtext=%audh=%ubinary=%bsmsc=%it s=%t max-messages = 0 ### note that there are more smsc's exist there, skipped some of them because of similarity / irrelevancy ### end of kannel.conf Request made to kannel: /cgi-bin/sendsms?user=pass=from=1351to=%2B40744813571text=%01%0 6%04%03%AE%81%EA%02%05%6A%00%45%C6%0b%03http://v4.appcell.com/imsc/units/kis sfmro/kiss_content/kiss_content.sms?sid=3dd3528d%00%08%01%03World+Soccer+Man ager+2005%00%01%01udh=%06%05%04%0B%84%23%F0smsc=orange_ro_1351 bearerbox.log: 2005-08-16 15:25:32 [6408] [7] DEBUG: SMPP[mobileway_uk_orange]: Manually forced source addr ton = 5, source add npi = 0 2005-08-16 15:25:32 [6408] [7] DEBUG: SMPP[mobileway_uk_orange]: Sending PDU: 2005-08-16 15:25:32 [6408] [7] DEBUG: SMPP PDU 0x91741f8 dump: 2005-08-16 15:25:32 [6408] [7] DEBUG: type_name: submit_sm 2005-08-16 15:25:32 [6408] [7] DEBUG: command_id: 4 = 0x0004 2005-08-16 15:25:32 [6408] [7] DEBUG: command_status: 0 = 0x 2005-08-16 15:25:32 [6408] [7] DEBUG: sequence_number: 2713 = 0x0a99 2005-08-16 15:25:32 [6408] [7] DEBUG: service_type: NULL 2005-08-16 15:25:32 [6408] [7] DEBUG: source_addr_ton: 5 = 0x0005 2005-08-16 15:25:32 [6408] [7] DEBUG: source_addr_npi: 0 = 0x 2005-08-16 15:25:32 [6408] [7] DEBUG: source_addr: 1351 2005-08-16 15:25:32 [6408] [7] DEBUG: dest_addr_ton: 1 = 0x0001 2005-08-16 15:25:32 [6408] [7] DEBUG: dest_addr_npi: 1 = 0x0001 2005-08-16 15:25:32 [6408] [7] DEBUG: destination_addr: 40744813571 2005-08-16 15:25:32 [6408] [7] DEBUG: esm_class: 67 = 0x0043 2005-08-16 15:25:32 [6408] [7] DEBUG: protocol_id: 0 = 0x 2005-08-16 15:25:32 [6408] [7] DEBUG: priority_flag: 0 = 0x 2005-08-16 15:25:32 [6408] [7] DEBUG: schedule_delivery_time: NULL 2005-08-16 15
Wrong smsc-id used for submit_sm
Hi List, Here's my problem.. I have several links up in my setup - some of them SMPP , some EMI2 When i submit an MT to sendsms (over http), i specify smsc-id to be used for sending. (by smsc= uri parameter) However, in some cases (it does not happen all the time), the real smsc used to send the message (that, i can see in bearerbox.log) is different. I am not sure if that it's entirely correct, but as far as i can see this substitution happens when smsc-id i use is EMI2. (maybe i did not notice this on other links though) For example, i submit msg with smsc=orange_ro_1353 , and it's going out through smsc-id mobileway_uk .. (both are configured properly and deliver messages both ways, the substitution does not happen on every such msg) Question is... why can this thing happen, and how can i prevent kannel from doing that? For what it's worth, if the smsc i requested is down and msg cannot be sent through it, i prefer such message to be dropped rather than being attempted to deliver through other link (as every link i have is limited for delivery to its own destination only). Regards, Konstantin P.S. My configuration (relevant parts of it :) ) OS: Fedora Core 2 Kannel: kannel-1.3.2-3.1.fc2.fr (useragent: Kannel/1.3.2-mblox) ^^ kannel is binary distribution that comes with fedora core2 kannel.conf (partial): group = core admin-port = 13000 smsbox-port = 13001 wapbox-port = 13002 admin-password = bar status-password = foo log-file = /var/log/kannel/bearerbox.log access-log = /var/log/kannel/bearerbox-access.log log-level = 0 admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 # SMSC SMPP group = smsc smsc = smpp smsc-id = mobileway_uk_orange host = xxx.xxx.xxx.xxx port = transceiver-mode = true smsc-username = smsc-password = system-type = VMA address-range = my-number = enquire-link-interval = 120 reconnect-delay = 30 source-addr-ton = 5 source-addr-npi = 0 source-addr-autodetect = false # SMSC UCP group = smsc smsc = emi smsc-id = orange_ro_1351 host = xxx.xxx.xxx.xxx port = smsc-username = smsc-password = my-number = 1351 keepalive = 55 receive-port = idle-timeout = 30 # SMSBOX SETUP group = smsbox bearerbox-host = localhost #smsbox-id = smsbox1 sendsms-port = #global-sender = 123 log-file = /var/log/kannel/smsbox.log access-log = /var/log/kannel/smsbox-access.log log-level = 0 # SEND-SMS USERS group = sendsms-user username = password = user-deny-ip = *.*.*.* user-allow-ip = 127.0.0.1 default-smsc = # ^^ what is this value used for? is it unused if i specify smsc-id on request? # smsc-id i have here is neither mobileway_uk_orange nor orange_ro_1351 ... # Forward everything to VAST group = sms-service name = vast keyword = default get-url = http://vast-host/kannel/mo?from=%qto=%Qtext=%audh=%ubinary=%bsmsc=%its=%t max-messages = 0 ### note that there are more smsc's exist there, skipped some of them because of similarity / irrelevancy ### end of kannel.conf Request made to kannel: /cgi-bin/sendsms?user=pass=from=1351to=%2B40744813571text=%01%06%04%03%AE%81%EA%02%05%6A%00%45%C6%0b%03http://v4.appcell.com/imsc/units/kissfmro/kiss_content/kiss_content.sms?sid=3dd3528d%00%08%01%03World+Soccer+Manager+2005%00%01%01udh=%06%05%04%0B%84%23%F0smsc=orange_ro_1351 bearerbox.log: 2005-08-16 15:25:32 [6408] [7] DEBUG: SMPP[mobileway_uk_orange]: Manually forced source addr ton = 5, source add npi = 0 2005-08-16 15:25:32 [6408] [7] DEBUG: SMPP[mobileway_uk_orange]: Sending PDU: 2005-08-16 15:25:32 [6408] [7] DEBUG: SMPP PDU 0x91741f8 dump: 2005-08-16 15:25:32 [6408] [7] DEBUG: type_name: submit_sm 2005-08-16 15:25:32 [6408] [7] DEBUG: command_id: 4 = 0x0004 2005-08-16 15:25:32 [6408] [7] DEBUG: command_status: 0 = 0x 2005-08-16 15:25:32 [6408] [7] DEBUG: sequence_number: 2713 = 0x0a99 2005-08-16 15:25:32 [6408] [7] DEBUG: service_type: NULL 2005-08-16 15:25:32 [6408] [7] DEBUG: source_addr_ton: 5 = 0x0005 2005-08-16 15:25:32 [6408] [7] DEBUG: source_addr_npi: 0 = 0x 2005-08-16 15:25:32 [6408] [7] DEBUG: source_addr: 1351 2005-08-16 15:25:32 [6408] [7] DEBUG: dest_addr_ton: 1 = 0x0001 2005-08-16 15:25:32 [6408] [7] DEBUG: dest_addr_npi: 1 = 0x0001 2005-08-16 15:25:32 [6408] [7] DEBUG: destination_addr: 40744813571 2005-08-16 15:25:32 [6408] [7] DEBUG: esm_class: 67 = 0x0043 2005-08-16 15:25:32 [6408] [7] DEBUG: protocol_id: 0 = 0x 2005-08-16 15:25:32 [6408] [7] DEBUG: priority_flag: 0 = 0x 2005-08-16 15:25:32 [6408] [7] DEBUG: schedule_delivery_time: NULL 2005-08-16 15:25:32 [6408] [7] DEBUG: validity_period: NULL 2005-08-16 15:25:32 [6408] [7] DEBUG: registered_delivery: 0 = 0x 2005-08-16 15:25:32 [6408] [7] DEBUG: replace_if_present_flag: 0 = 0x 2005-08-16 15:25:32 [6408] [7] DEBUG: data_coding: 4 = 0x0004 2005-08-16 15:25:32 [6408] [7] DEBUG: sm_default_msg_id: 0
Map message to smsc-id
Hi, a couple of days before i asked for a way to send concatenated messages over the same virtual smsc (smsc = at). If there is no such built-in functionality i have to do something on my own. I have to decide where i route messages. My solution is that the decision for the smsc can be made by looking at the last byte of the receiver number so that every SMS to the same recipient uses the same smsc. Here is a example (receiver number ending with a 1 or 2 will be sent over SMSC1, ending with a 3 or 4 will be sent over SMSC2 and so on. the concatenated sms will use the same gsm-modem because the last byte is the same and the message will be routed to the same smsc): [...] 01234567891 - SMSC1 01234567892 - SMSC1 01234567893 - SMSC2 01234567894 - SMSC2 [...] Now my question: Is there a way to map a message to a virtual smsc? If so i can write a script which decides where to route the sms an map it to the matching smsc-id in kannel. __ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201
bearerbox failover to second smsc (the old favourites of allowed-smsc-id, etc)
Hi, I thought I'd configured my test kannel config such that in the event that a connection to an smpp server went dead (smsc-id=smpp2 below) then sms sends would get re-posted via the second smsc (smsc-id=TEST411 below, which is actually just a call to sendsms over to another bearerbox server). This seems to work fine, I thought a combination of allowed-smsc-id, preferred-smsc-id and forced-smsc would do the trick, and indeed it does to a point - if smpp2 went dead, we started going over TEST411 instead. Problem was, once smpp2 came back, we still kept sending over TEST411. I had to restart bearerbox/smsbox to get it working over smpp2 again. Would be very grateful for suggestions. # CORE GROUP # group = core admin-port = 13000 smsbox-port = 13001 admin-password = xxx log-level = 1 log-file = /home/sc/logs/kannel.log access-log = /home/sc/logs/sms.log access-log-format = %t %l [SMSC:%i] [to:%P] [%L:%b] box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 store-file = /tmp/kannel.store dlr-storage = mysql # includes # #SQL DLR Group group = mysql-connection id = dlrdb host = sovcluster1 mysql-username = xx mysql-password = xxx database = xxx # mysql fields defined group = dlr-db id = dlrdb table = dlr field-smsc = smsc field-timestamp = ts field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxc # SMSC SMPP ### group = smsc smsc = smpp smsc-id = smpp2 allowed-smsc-id = smpp2 preferred-smsc-id = smpp2 host = xxx.xxx.xxx.xxx port = xxx receive-port = xxx smsc-username = xxx smsc-password = xxx system-type = MT msg-id-type = 0x01 group = smsc smsc = http smsc-id = TEST411 system-type = kannel smsc-username = xxx smsc-password = xxx port = 13015 send-url = http://xxx:13013/cgi-bin/sendsms; # SMSBOX SETUP group = smsbox bearerbox-host = xxx sendsms-port = 13013 global-sender = +xxx log-level = 1 log-file = /home/sc/logs/smsbox.log # SEND-SMS USERS ## group = sendsms-user username = xxx password = xxx forced-smsc = smpp2 _ Stay in touch with absent friends - get MSN Messenger http://www.msn.co.uk/messenger
please help with denied-smsc-id/forced-smsc/accepted-smsc confusion
Hello, I'm really struggling to get to grips with kannel support for multiple smsc-id. All I'm trying to do is a) support connections to 2 different smpp ports b) in event that both are down, use an http smsc to simply re-post the SMS to another kannel instance on another server (test411), with its own smpp config c) make sure DLR get routed back to the smsc-id that sent the SMS My kannel.conf below - would REALLY appreciate any help ! # CORE GROUP # group = core admin-port = 13000 smsbox-port = 13001 admin-password = xxx log-file = /tmp/kannel.log access-log = /tmp/access.log log-level = 3 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 store-file = /tmp/kannel.store dlr-storage = mysql # includes # #include = sc_mysqldlr.conf #SQL DLR Group group = mysql-connection id = dlrdb host = devdb1 mysql-username = sc mysql-password = xx database = scdev1 # mysql fields defined group = dlr-db id = dlrdb table = dlr field-smsc = smsc field-timestamp = ts field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxc # SMSC SMPP ### group = smsc smsc = smpp smsc-id = smpp1 denied-smsc-id = smpp2;smpp3;smpp4 host = xxx.yyy.zzz.zzz port = 9000 receive-port = 9000 smsc-username = xx smsc-password = yy system-type = MT msg-id-type = 0x01 # SMSC SMPP ### group = smsc smsc = smpp smsc-id = smpp2 denied-smsc-id = smpp1;smpp3;smpp4 host = xxx.yyy.zzz.xxx port = 9000 receive-port = 9000 smsc-username = xx smsc-password = yy system-type = MT msg-id-type = 0x01 group = smsc smsc = http smsc-id = TEST411 system-type = kannel smsc-username = sc smsc-password = port = 13015 send-url = http://test411:13013/cgi-bin/sendsms; # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-port = 13013 global-sender = +x #sendsms-chars = 0123456789 +- log-file = /tmp/smsbox.log log-level = 3 #access-log = /tmp/access.log # SEND-SMS USERS ## group = sendsms-user username = sc password = k3nn3l forced-smsc = smpp1 group = sendsms-user username = sc password = k3nn3l forced-smsc = smpp2 # SERVICES group = sms-service accepted-smsc = smpp1 keyword = nop text = smpp1 service group = sms-service accepted-smsc = smpp2 keyword = nop text = smpp2 service group = sms-service accepted-smsc = TEST411 keyword = nop text = TEST411 service # DEFAULT SERVICE # group = sms-service keyword = default text = No service specified _ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger
SMS routing based on smsc-id does not work properly.
Dear, Sirs! Sorry for I have two different SMSC(one is SMPP-based, another one is HTTP-based ) in configuration file and have some problems with routing. I want to route reply to the same SMSC, which receive request. I make configuration as in documentation http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN4033 but it does not work properly. CONFIG: group = core admin-port = smsbox-port = log-file = kannel.log log-level = 0 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 access-log = access.log store-file = kannel.store # SMSC CONNECTIONS group = smsc smsc = smpp smsc-id = SMSC1 denied-smsc-id = SMSC2 transceiver-mode = 1 host = SMPP SMSC IP Addr port = smsc-username = user smsc-password = pass system-type = VMA group = smsc smsc = http smsc-id = SMSC2 denied-smsc-id = SMSC1 system-type = kannel smsc-username = user smsc-password = pass port = send-url = http://XXX.XXX.XX/sms; connect-allow-ip = HTTP SMSC IP # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-chars = 0123456789 +- log-file = smsbox.log log-level = 0 access-log = access.log group = sms-service keyword = default name = test1 max-messages = 10 concatenation = false allowed-receiver-prefix = accepted-smsc = SMSC1 split-chars = omit-empty = true text = TEST1 group = sms-service keyword = default name = test2 max-messages = 10 concatenation = false allowed-receiver-prefix = accepted-smsc = SMSC2 split-chars = omit-empty = true text = TEST2 If I send sms request from SMSC1, kannel send reply back via SMSC2, but if i send sms request from SMSC2, kannel sends reply back via SMSC2 too. Then i set config block of SMSC2 above SMSC1. And if I send sms request from SMSC1, kannel sends reply back via SMSC1, but if i send sms request from SMSC2 kannel send reply back via SMSC1 too. Only if i set routing based on allowed-prefix in my config, then all work fine. But kannel users guide shows than i can do routing based on smsc-id, denied-smsc-id, accepted-smsc params. What i do wrong? Thank you beforehand. -- Best regards, Roman.
