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! Напомена: оне.Вип ДОО Скопје Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и да ја избришете оригиналната порака и сите нејзини копии од Вашиот компјутерски систем. Секое неовластено користење на оваа порака во целост или делови од истата е строго забрането. Ве молиме да забележите дека електронските пораки се подложни на промени. оне.Вип ДОО Скопје не презема одговорност за несоодветно или нецелосно пренесување на информациите содржани во оваа комуникација, ниту пак за било какво задоцнување на приемот или оштетувања на вашиот систем. Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја природата!
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
