Re: Routing to multiple SMSCs OPENSMPP
Hi Gorki, As they say, there are many ways of skinning a cat. That's the beauty of this craft. Use whatever suits you best or makes a logic. Thanks, Davor Sent from my iPad On Jul 29, 2017, at 4:33 AM, Gorki Alfaro <gork...@gmail.com> wrote: Davor Thanks a lot, it was really helpful. Also I would like to share another solution that I found, and is using to SMSC with the same name, Here you have the config files ---excerpt opensmppbox.conf group = core dlr-storage = mysql group = opensmppbox opensmppbox-id =mysmppbox log-level = 0 log-file = /var/log/kannel/opensmppbox.log our-system-id = testsmpp use-systemid-as-smsboxid = true route-to-smsc = smppgwgeneric # see sample smpplogins.txt smpp-logins = "/etc/kannel/smpplogins.txt" kannel.conf #- # CORE.. #- # SMSC CONNECTIONS #SMSC 1 group = smsc smsc-id = smppgwgeneric smsc = smpp host =x.x.x.x port = 5019 smsc-username = xxx smsc-password = xx allowed-prefix = "5019;+5019" preferred-prefix = "5019;+5019" allowed-smsc-id = smppgwgeneric msg-id-type = 0x01 #SMSC 2 group = smsc smsc-username = xxx smsc-password = xx smsc-id = smppgwgeneric smsc = smpp host = X.X.X.X port = 4201 allowed-prefix = "5013;+5013;5018;+5018" preferred-prefix = "5013;+5013;5018;+5018" allowed-smsc-id = smppgwgeneric msg-id-type = 0x01 Hope could be helpful for someone else. Regards, Gorki 2017-07-27 9:46 GMT-06:00 Davor Spasoski <davor.spaso...@onevip.mk>: Follow-up configuration: group = smsc smsc = smpp smsc-id = "SMSC1" allowed-smsc-id = "SMSC1;SMSC2" allowed-receiver-prefix = prefix1,prefix3 group = smsc smsc = smpp smsc-id = "SMSC2" allowed-smsc-id = "SMSC1;SMSC2" allowed-receiver-prefix = prefix2,prefix3 ……… Opensmppbox group = smsc-route smsc-id = SMSC1 smsbox-id = SMSC1 With the above, kannel will load-share between SMSC12 and SMSC2 for prefix3 and will use SMSC1-only for prefix1 and SMSC2-only for prefix2. If you on top of this want to have a preferred SMSC for prefix3 instead of load sharing, just add preferred-smsc-id = SMSC1 in the SMSC1 configuration. Good luck! Davor Spasoski From: users [mailto:users-bounces@kannel.org] On Behalf Of Davor Spasoski Sent: Wednesday, July 26, 2017 10:35 PM To: Gorki Alfaro <gork...@gmail.com> Cc: users@kannel.org Subject: Re: Routing to multiple SMSCs OPENSMPP The smscs do not necessarily have to have same-ids. Same smsc-ids are used when you want to load balance the traffic among two or more smscs. Use two id. It is important that smsc1 should allow smsc2 and vice versa. I can't be much verbose now, as I'm writing from my handy. I'll have access to a computer tomorrow afternoon. Until then, read the userguide and experiment. Davor On Jul 26, 2017, at 6:24 PM, Gorki Alfaro <gork...@gmail.com> wrote: Hi Davor, thanks for your help. I understand that in the opensmppbox config I have to set the variable route-to-smsc to a specific smsc-id and then in the kannel configuration file set two o more group = smsc with the same id (here use the variables allowed-smsc-id and allowed-prefix) ? Can you provide an example? Thanks in advance Gorki 2017-07-26 1:35 GMT-06:00 Davor Spasoski <davor.spaso...@onevip.mk>: Hi, Try using the allowed-smsc-id and allowed-prefix of the SMSC group set of variables. Davor Spasoski From: users [mailto:users-bounces@kannel.org] On Behalf Of Gorki Alfaro Sent: Wednesday, July 26, 2017 5:47 AM To: users@kannel.org Subject: Routing to multiple SMSCs OPENSMPP Hello my friends Does anyone solve this situation? I have clients connecting to me through SMPP connections who needs to send messages to more than one SMSC however OPENSMPP configuration only allows one SMSC (variable route-to-smsc) . The question is: How can I redirect messages to different SMSC based on the destination number? Thanks in advance Gorki 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: Routing to multiple SMSCs OPENSMPP
Davor Thanks a lot, it was really helpful. Also I would like to share another solution that I found, and is using to SMSC with the same name, Here you have the config files ---excerpt *opensmppbox.conf* group = core dlr-storage = mysql group = opensmppbox opensmppbox-id =mysmppbox log-level = 0 log-file = /var/log/kannel/opensmppbox.log our-system-id = testsmpp use-systemid-as-smsboxid = true *route-to-smsc = smppgwgeneric* # see sample smpplogins.txt smpp-logins = "/etc/kannel/smpplogins.txt" *kannel.conf* #- # CORE.. #- # SMSC CONNECTIONS #SMSC 1 group = smsc *smsc-id = smppgwgeneric* smsc = smpp host =x.x.x.x port = 5019 smsc-username = xxx smsc-password = xx allowed-prefix = "5019;+5019" preferred-prefix = "5019;+5019" allowed-smsc-id = smppgwgeneric msg-id-type = 0x01 #SMSC 2 group = smsc smsc-username = xxx smsc-password = xx *smsc-id = smppgwgeneric* smsc = smpp host = X.X.X.X port = 4201 allowed-prefix = "5013;+5013;5018;+5018" preferred-prefix = "5013;+5013;5018;+5018" allowed-smsc-id = smppgwgeneric msg-id-type = 0x01 Hope could be helpful for someone else. Regards, Gorki 2017-07-27 9:46 GMT-06:00 Davor Spasoski : > Follow-up configuration: > > > > group = smsc > > smsc = smpp > > smsc-id = "SMSC1" > > allowed-smsc-id = "SMSC1;SMSC2" > > allowed-receiver-prefix = prefix1,prefix3 > > > > group = smsc > > smsc = smpp > > smsc-id = "SMSC2" > > allowed-smsc-id = "SMSC1;SMSC2" > > allowed-receiver-prefix = prefix2,prefix3 > > > > ……… > > > > Opensmppbox > > group = smsc-route > > smsc-id = SMSC1 > > smsbox-id = SMSC1 > > > > With the above, kannel will load-share between SMSC12 and SMSC2 for > prefix3 and will use SMSC1-only for prefix1 and SMSC2-only for prefix2. If > you on top of this want to have a preferred SMSC for prefix3 instead of > load sharing, just add preferred-smsc-id = SMSC1 in the SMSC1 configuration. > > > > Good luck! > > > > *Davor Spasoski* > > > > *From:* users [mailto:users-boun...@kannel.org] *On Behalf Of *Davor > Spasoski > *Sent:* Wednesday, July 26, 2017 10:35 PM > *To:* Gorki Alfaro > *Cc:* users@kannel.org > *Subject:* Re: Routing to multiple SMSCs OPENSMPP > > > > The smscs do not necessarily have to have same-ids. Same smsc-ids are used > when you want to load balance the traffic among two or more smscs. > > Use two id. It is important that smsc1 should allow smsc2 and vice versa. > I can't be much verbose now, as I'm writing from my handy. I'll have access > to a computer tomorrow afternoon. Until then, read the userguide and > experiment. > > > > Davor > > > On Jul 26, 2017, at 6:24 PM, Gorki Alfaro wrote: > > Hi Davor, thanks for your help. > > > > I understand that in the opensmppbox config I have to set the variable* > route-to-smsc* to a specific smsc-id and then in the kannel configuration > file set two o more group = smsc with the same id (here use the variables > allowed-smsc-id > and allowed-prefix) ? > > Can you provide an example? > > > > > > Thanks in advance > > Gorki > > > > > > > > 2017-07-26 1:35 GMT-06:00 Davor Spasoski : > > Hi, > > > > Try using the allowed-smsc-id and allowed-prefix of the SMSC group set of > variables. > > > > *Davor Spasoski* > > *From:* users [mailto:users-boun...@kannel.org] *On Behalf Of *Gorki > Alfaro > *Sent:* Wednesday, July 26, 2017 5:47 AM > *To:* users@kannel.org > *Subject:* Routing to multiple SMSCs OPENSMPP > > > > Hello my friends > > > > Does anyone solve this situation? I have clients connecting to me > through SMPP connections who needs to send messages to more than one SMSC > however OPENSMPP configuration only allows one SMSC > (variable route-to-smsc) . > > The question is: How can I redirect messages to different SMSC based on > the destination number? > > > > Thanks in advance > > > > Gorki > > > > > -- > > > 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
RE: Routing to multiple SMSCs OPENSMPP
Follow-up configuration: group = smsc smsc = smpp smsc-id = "SMSC1" allowed-smsc-id = "SMSC1;SMSC2" allowed-receiver-prefix = prefix1,prefix3 group = smsc smsc = smpp smsc-id = "SMSC2" allowed-smsc-id = "SMSC1;SMSC2" allowed-receiver-prefix = prefix2,prefix3 ……… Opensmppbox group = smsc-route smsc-id = SMSC1 smsbox-id = SMSC1 With the above, kannel will load-share between SMSC12 and SMSC2 for prefix3 and will use SMSC1-only for prefix1 and SMSC2-only for prefix2. If you on top of this want to have a preferred SMSC for prefix3 instead of load sharing, just add preferred-smsc-id = SMSC1 in the SMSC1 configuration. Good luck! Davor Spasoski From: users [mailto:users-boun...@kannel.org] On Behalf Of Davor Spasoski Sent: Wednesday, July 26, 2017 10:35 PM To: Gorki Alfaro Cc: users@kannel.org Subject: Re: Routing to multiple SMSCs OPENSMPP The smscs do not necessarily have to have same-ids. Same smsc-ids are used when you want to load balance the traffic among two or more smscs. Use two id. It is important that smsc1 should allow smsc2 and vice versa. I can't be much verbose now, as I'm writing from my handy. I'll have access to a computer tomorrow afternoon. Until then, read the userguide and experiment. Davor On Jul 26, 2017, at 6:24 PM, Gorki Alfaro mailto:gork...@gmail.com>> wrote: Hi Davor, thanks for your help. I understand that in the opensmppbox config I have to set the variable route-to-smsc to a specific smsc-id and then in the kannel configuration file set two o more group = smsc with the same id (here use the variables allowed-smsc-id and allowed-prefix) ? Can you provide an example? Thanks in advance Gorki 2017-07-26 1:35 GMT-06:00 Davor Spasoski mailto:davor.spaso...@onevip.mk>>: Hi, Try using the allowed-smsc-id and allowed-prefix of the SMSC group set of variables. Davor Spasoski From: users [mailto:users-boun...@kannel.org<mailto:users-boun...@kannel.org>] On Behalf Of Gorki Alfaro Sent: Wednesday, July 26, 2017 5:47 AM To: users@kannel.org<mailto:users@kannel.org> Subject: Routing to multiple SMSCs OPENSMPP Hello my friends Does anyone solve this situation? I have clients connecting to me through SMPP connections who needs to send messages to more than one SMSC however OPENSMPP configuration only allows one SMSC (variable route-to-smsc) . The question is: How can I redirect messages to different SMSC based on the destination number? Thanks in advance Gorki 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 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 nec
Re: Routing to multiple SMSCs OPENSMPP
The smscs do not necessarily have to have same-ids. Same smsc-ids are used when you want to load balance the traffic among two or more smscs. Use two id. It is important that smsc1 should allow smsc2 and vice versa. I can't be much verbose now, as I'm writing from my handy. I'll have access to a computer tomorrow afternoon. Until then, read the userguide and experiment. Davor On Jul 26, 2017, at 6:24 PM, Gorki Alfaro <gork...@gmail.com> wrote: Hi Davor, thanks for your help. I understand that in the opensmppbox config I have to set the variable route-to-smsc to a specific smsc-id and then in the kannel configuration file set two o more group = smsc with the same id (here use the variables allowed-smsc-id and allowed-prefix) ? Can you provide an example? Thanks in advance Gorki 2017-07-26 1:35 GMT-06:00 Davor Spasoski <davor.spaso...@onevip.mk>: Hi, Try using the allowed-smsc-id and allowed-prefix of the SMSC group set of variables. Davor Spasoski From: users [mailto:users-bounces@kannel.org] On Behalf Of Gorki Alfaro Sent: Wednesday, July 26, 2017 5:47 AM To: users@kannel.org Subject: Routing to multiple SMSCs OPENSMPP Hello my friends Does anyone solve this situation? I have clients connecting to me through SMPP connections who needs to send messages to more than one SMSC however OPENSMPP configuration only allows one SMSC (variable route-to-smsc) . The question is: How can I redirect messages to different SMSC based on the destination number? Thanks in advance Gorki 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 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: Routing to multiple SMSCs OPENSMPP
Hi Davor, thanks for your help. I understand that in the opensmppbox config I have to set the variable *route-to-smsc* to a specific smsc-id and then in the kannel configuration file set two o more group = smsc with the same id (here use the variables allowed-smsc-id and allowed-prefix) ? Can you provide an example? Thanks in advance Gorki 2017-07-26 1:35 GMT-06:00 Davor Spasoski : > Hi, > > > > Try using the allowed-smsc-id and allowed-prefix of the SMSC group set of > variables. > > > > *Davor Spasoski* > > *From:* users [mailto:users-boun...@kannel.org] *On Behalf Of *Gorki > Alfaro > *Sent:* Wednesday, July 26, 2017 5:47 AM > *To:* users@kannel.org > *Subject:* Routing to multiple SMSCs OPENSMPP > > > > Hello my friends > > > > Does anyone solve this situation? I have clients connecting to me > through SMPP connections who needs to send messages to more than one SMSC > however OPENSMPP configuration only allows one SMSC > (variable route-to-smsc) . > > The question is: How can I redirect messages to different SMSC based on > the destination number? > > > > Thanks in advance > > > > Gorki > > > > -- > > 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: Routing to multiple SMSCs OPENSMPP
Hi, Try using the allowed-smsc-id and allowed-prefix of the SMSC group set of variables. Davor Spasoski From: users [mailto:users-boun...@kannel.org] On Behalf Of Gorki Alfaro Sent: Wednesday, July 26, 2017 5:47 AM To: users@kannel.org Subject: Routing to multiple SMSCs OPENSMPP Hello my friends Does anyone solve this situation? I have clients connecting to me through SMPP connections who needs to send messages to more than one SMSC however OPENSMPP configuration only allows one SMSC (variable route-to-smsc) . The question is: How can I redirect messages to different SMSC based on the destination number? Thanks in advance Gorki 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! Напомена: оне.Вип ДОО Скопје Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и да ја избришете оригиналната порака и сите нејзини копии од Вашиот компјутерски систем. Секое неовластено користење на оваа порака во целост или делови од истата е строго забрането. Ве молиме да забележите дека електронските пораки се подложни на промени. оне.Вип ДОО Скопје не презема одговорност за несоодветно или нецелосно пренесување на информациите содржани во оваа комуникација, ниту пак за било какво задоцнување на приемот или оштетувања на вашиот систем. Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја природата!
Routing to multiple SMSCs OPENSMPP
Hello my friends Does anyone solve this situation? I have clients connecting to me through SMPP connections who needs to send messages to more than one SMSC however OPENSMPP configuration only allows one SMSC (variable route-to-smsc) . The question is: How can I redirect messages to different SMSC based on the destination number? Thanks in advance Gorki
Fwd: opensmppbox multiple smscs
my current configuration files are attached. my problem is that I cannot have more than one opensmppboxs but I have to make suer that reply for MO should be routed to same smsc from which MO has been received. I don't know how to configure that. currently i use route-to-smsc = A to route sms(MO)from ESME to smsc and to route sms(MT)from smsc to ESME group = smsbox-route smsbox-id = opensmpp smsc-id = A what if i have 5 smscs and one opensmppbox please help -- Forwarded message -- From: Hasnain Qureshi Date: Tue, Oct 11, 2011 at 12:03 PM Subject: opensmppbox multiple smscs To: users@kannel.org Hi all, I have currently established this setup. ESME==>opensmppbox==>kannel(bearer box)==> SMSC I currently have one smsc, I am using route-to-smsc in opensmppbox configuration file to route MT sms from opensmppbox to smsc and smsbox-route in kannel configuration file to route MO to opensmppbox and then to ESME. Now I have to add 4 other smsc(total of 5) from different Network Operator but I can't have more than one opemsmppbox. I have to make sure that reply from ESME should be routed to the same smsc from which sms is received. I can not use some thing based on prefixes because there is Mobile Number Portibility. Please guide me in this matter. Hasnain kannel.conf Description: Binary data opensmpp.conf Description: Binary data
opensmppbox multiple smscs
Hi all, I have currently established this setup. ESME==>opensmppbox==>kannel(bearer box)==> SMSC I currently have one smsc, I am using route-to-smsc in opensmppbox configuration file to route MT sms from opensmppbox to smsc and smsbox-route in kannel configuration file to route MO to opensmppbox and then to ESME. Now I have to add 4 other smsc(total of 5) from different Network Operator but I can't have more than one opemsmppbox. I have to make sure that reply from ESME should be routed to the same smsc from which sms is received. I can not use some thing based on prefixes because there is Mobile Number Portibility. Please guide me in this matter. Hasnain
Re: Antwort: Wap Push : global-sender parameter for multiple SMSCs
Sorry for the spam, forgot to give the reference for the pap spec: http://www.wapforum.org/DTD/pap_2.0.dtd BR, Nikos - Original Message - From: "Nikos Balkanas" To: "Nick Mee" ; Cc: Sent: Wednesday, April 13, 2011 11:05 AM Subject: Re: Antwort: Wap Push : global-sender parameter for multiple SMSCs my-number might work. You could also start 2 wapbox instances, each one with a different global sender. Lastly there is a element in PAP specification, where you specify sender address and name, but I am not sure if wapbox supports it. Try them, and let us know. BR, Nikos - Original Message - From: stefan.allem...@css.ch To: Nick Mee Cc: us...@vm1.kannel.org ; users-boun...@vm1.kannel.org Sent: Wednesday, April 13, 2011 10:56 AM Subject: Antwort: Wap Push : global-sender parameter for multiple SMSCs I think you can use my-number = "123456" in each smsc section (group = smsc) Stefan Von:Nick Mee An:us...@vm1.kannel.org Datum:13.04.2011 09:35 Betreff:Wap Push : global-sender parameter for multiple SMSCs Gesendet von:users-boun...@vm1.kannel.org Hi User List Im trying to configure Kannel to allow WAP Pushes to two different SMSCs. My problem is - they each require a different originating number (global-sender parameter in the ppg group). Is there a way of specifying the originating number for each WAP Push (similar to the 'from' parameter in sendsms)? This is my config file ... group = core admin-port = ... admin-password = aaa status-password = aaa admin-deny-ip = "*.*.*.*" admin-allow-ip = "127.0.0.1" smsbox-port = 13001 wapbox-port = 13002 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" wdp-interface-name = "*" log-file = "/var/log/kannel/bearerbox.log" log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = "aaa" smsc-password = aaa system-type = 'VMA' address-range = "" msg-id-type = 0 throughput = 30 smsc-id = smsc1 allowed-smsc-id = "smsc1" log-file = "/var/log/kannel/smsc1.log" log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = "aaa" smsc-password = aaa system-type = 'VMA' address-range = "" msg-id-type = 0 throughput = 30 smsc-id = smsc2 allowed-smsc-id = "smsc2" log-file = "/var/log/kannel/smsc2.log" log-level = 0 group = wapbox bearerbox-host = 127.0.0.1 log-file = "/var/log/kannel/wapbox.log" log-level = 0 syslog-level = none group = smsbox smsbox-id = smsbox1 bearerbox-host = localhost sendsms-port = 13131 sendsms-chars = "0123456789 " access-log = "/var/log/kannel/access.log" log-file = "/var/log/kannel/smsbox.log" log-level = 0 group = smsbox-route smsbox-id = smsbox1 smsc-ids = "smsc1;smsc2" group = ppg ppg-url = /wappush ppg-port = 8080 service-name = ppg ppg-smsbox-id = smsbox1 concurrent-pushes = 100 users = 1024 global-sender = 12345 trusted-pi = false ppg-allow-ip = ... group = wap-push-user wap-push-user = pushtest ppg-username = zzz ppg-password = zzz allow-ip = ... group = sms-service keyword = default max-messages = 0 get-url = "http://."; group = sendsms-user username = xxx password = xxx forced-smsc = smsc1 group = sendsms-user username = yyy password = yyy forced-smsc = smsc2 -- Der Inhalt dieses E-Mails ist streng vertraulich und moglicherweise gesetzlich besonders geschutzt. Dieses E-Mail ist nur fur den Adressaten bestimmt. Wenn Sie nicht der beabsichtigte Empfanger sind, ist es Ihnen nicht gestattet und stellt moglicherweise einen Gesetzesverstoss dar, dieses E-Mail zu kopieren, zu verbreiten oder anderweitig zu verwenden. In diesem Fall sollten Sie uns so schnell wie moglich benachrichtigen und dieses E-Mail loschen. Le contenu de ce courriel est strictement confidentiel et probablement legalement protege. Il n'est adresse qu'aux destinataires mentionnes. Si vous n'en faites pas partie, vous n'avez pas l'autorisation de le copier, ni de le diffuser, ni meme de le destiner a un autre usage - ce qui dans chaque cas peut en effet constituer une infraction a la loi. Dans ce cas, vous devriez nous en informer immediatement et effacer ce courriel. Il contenuto del presente messaggio elettronico e da considerare di massima riservatezza e possibilmente e protetto in modo particolare dalla legge. La presente e-mail e riservata alla sola attenzione della persona destinataria. Se lei non e la persona che avrebbe dovuto ricevere la e-mail, non le e permesso e possibilmente rappresenta una violazione della legge, copiare la presente e-mail, diffonderla o utilizzarla in qualsiasi altro modo. In questo caso lei dovrebbe informarci al piu presto possibile e cancellare la presente e-mail.
Re: Antwort: Wap Push : global-sender parameter for multiple SMSCs
my-number might work. You could also start 2 wapbox instances, each one with a different global sender. Lastly there is a element in PAP specification, where you specify sender address and name, but I am not sure if wapbox supports it. Try them, and let us know. BR, Nikos - Original Message - From: stefan.allem...@css.ch To: Nick Mee Cc: us...@vm1.kannel.org ; users-boun...@vm1.kannel.org Sent: Wednesday, April 13, 2011 10:56 AM Subject: Antwort: Wap Push : global-sender parameter for multiple SMSCs I think you can use my-number = "123456" in each smsc section (group = smsc) Stefan Von:Nick Mee An:us...@vm1.kannel.org Datum:13.04.2011 09:35 Betreff:Wap Push : global-sender parameter for multiple SMSCs Gesendet von:users-boun...@vm1.kannel.org Hi User List Im trying to configure Kannel to allow WAP Pushes to two different SMSCs. My problem is - they each require a different originating number (global-sender parameter in the ppg group). Is there a way of specifying the originating number for each WAP Push (similar to the 'from' parameter in sendsms)? This is my config file ... group = core admin-port = ... admin-password = aaa status-password = aaa admin-deny-ip = "*.*.*.*" admin-allow-ip = "127.0.0.1" smsbox-port = 13001 wapbox-port = 13002 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" wdp-interface-name = "*" log-file = "/var/log/kannel/bearerbox.log" log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = "aaa" smsc-password = aaa system-type = 'VMA' address-range = "" msg-id-type = 0 throughput = 30 smsc-id = smsc1 allowed-smsc-id = "smsc1" log-file = "/var/log/kannel/smsc1.log" log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = "aaa" smsc-password = aaa system-type = 'VMA' address-range = "" msg-id-type = 0 throughput = 30 smsc-id = smsc2 allowed-smsc-id = "smsc2" log-file = "/var/log/kannel/smsc2.log" log-level = 0 group = wapbox bearerbox-host = 127.0.0.1 log-file = "/var/log/kannel/wapbox.log" log-level = 0 syslog-level = none group = smsbox smsbox-id = smsbox1 bearerbox-host = localhost sendsms-port = 13131 sendsms-chars = "0123456789 " access-log = "/var/log/kannel/access.log" log-file = "/var/log/kannel/smsbox.log" log-level = 0 group = smsbox-route smsbox-id = smsbox1 smsc-ids = "smsc1;smsc2" group = ppg ppg-url = /wappush ppg-port = 8080 service-name = ppg ppg-smsbox-id = smsbox1 concurrent-pushes = 100 users = 1024 global-sender = 12345 trusted-pi = false ppg-allow-ip = ... group = wap-push-user wap-push-user = pushtest ppg-username = zzz ppg-password = zzz allow-ip = ... group = sms-service keyword = default max-messages = 0 get-url = "http://."; group = sendsms-user username = xxx password = xxx forced-smsc = smsc1 group = sendsms-user username = yyy password = yyy forced-smsc = smsc2 -- Der Inhalt dieses E-Mails ist streng vertraulich und moglicherweise gesetzlich besonders geschutzt. Dieses E-Mail ist nur fur den Adressaten bestimmt. Wenn Sie nicht der beabsichtigte Empfanger sind, ist es Ihnen nicht gestattet und stellt moglicherweise einen Gesetzesverstoss dar, dieses E-Mail zu kopieren, zu verbreiten oder anderweitig zu verwenden. In diesem Fall sollten Sie uns so schnell wie moglich benachrichtigen und dieses E-Mail loschen. Le contenu de ce courriel est strictement confidentiel et probablement legalement protege. Il n'est adresse qu'aux destinataires mentionnes. Si vous n'en faites pas partie, vous n'avez pas l'autorisation de le copier, ni de le diffuser, ni meme de le destiner a un autre usage - ce qui dans chaque cas peut en effet constituer une infraction a la loi. Dans ce cas, vous devriez nous en informer immediatement et effacer ce courriel. Il contenuto del presente messaggio elettronico e da considerare di massima riservatezza e possibilmente e protetto in modo particolare dalla legge. La presente e-mail e riservata alla sola attenzione della persona destinataria. Se lei non e la persona che avrebbe dovuto ricevere la e-mail, non le e permesso e possibilmente rappresenta una violazione della legge, copiare la presente e-mail, diffonderla o utilizzarla in qualsiasi altro modo. In questo caso lei dovrebbe informarci al piu presto possibile e cancellare la presente e-mail.
Antwort: Wap Push : global-sender parameter for multiple SMSCs
I think you can use my-number = "123456" in each smsc section (group = smsc) Stefan Von:Nick Mee An: us...@vm1.kannel.org Datum: 13.04.2011 09:35 Betreff:Wap Push : global-sender parameter for multiple SMSCs Gesendet von: users-boun...@vm1.kannel.org Hi User List Im trying to configure Kannel to allow WAP Pushes to two different SMSCs. My problem is - they each require a different originating number (global-sender parameter in the ppg group). Is there a way of specifying the originating number for each WAP Push (similar to the 'from' parameter in sendsms)? This is my config file ... group = core admin-port = ... admin-password = aaa status-password = aaa admin-deny-ip = "*.*.*.*" admin-allow-ip = "127.0.0.1" smsbox-port = 13001 wapbox-port = 13002 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" wdp-interface-name = "*" log-file = "/var/log/kannel/bearerbox.log" log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = "aaa" smsc-password = aaa system-type = 'VMA' address-range = "" msg-id-type = 0 throughput = 30 smsc-id = smsc1 allowed-smsc-id = "smsc1" log-file = "/var/log/kannel/smsc1.log" log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = "aaa" smsc-password = aaa system-type = 'VMA' address-range = "" msg-id-type = 0 throughput = 30 smsc-id = smsc2 allowed-smsc-id = "smsc2" log-file = "/var/log/kannel/smsc2.log" log-level = 0 group = wapbox bearerbox-host = 127.0.0.1 log-file = "/var/log/kannel/wapbox.log" log-level = 0 syslog-level = none group = smsbox smsbox-id = smsbox1 bearerbox-host = localhost sendsms-port = 13131 sendsms-chars = "0123456789 " access-log = "/var/log/kannel/access.log" log-file = "/var/log/kannel/smsbox.log" log-level = 0 group = smsbox-route smsbox-id = smsbox1 smsc-ids = "smsc1;smsc2" group = ppg ppg-url = /wappush ppg-port = 8080 service-name = ppg ppg-smsbox-id = smsbox1 concurrent-pushes = 100 users = 1024 global-sender = 12345 trusted-pi = false ppg-allow-ip = ... group = wap-push-user wap-push-user = pushtest ppg-username = zzz ppg-password = zzz allow-ip = ... group = sms-service keyword = default max-messages = 0 get-url = "http://."; group = sendsms-user username = xxx password = xxx forced-smsc = smsc1 group = sendsms-user username = yyy password = yyy forced-smsc = smsc2 -- Der Inhalt dieses E-Mails ist streng vertraulich und möglicherweise gesetzlich besonders geschützt. Dieses E-Mail ist nur für den Adressaten bestimmt. Wenn Sie nicht der beabsichtigte Empfänger sind, ist es Ihnen nicht gestattet und stellt möglicherweise einen Gesetzesverstoss dar, dieses E-Mail zu kopieren, zu verbreiten oder anderweitig zu verwenden. In diesem Fall sollten Sie uns so schnell wie möglich benachrichtigen und dieses E-Mail löschen. Le contenu de ce courriel est strictement confidentiel et probablement légalement protégé. Il n'est adressé qu'aux destinataires mentionnés. Si vous n'en faites pas partie, vous n'avez pas l'autorisation de le copier, ni de le diffuser, ni même de le destiner à un autre usage - ce qui dans chaque cas peut en effet constituer une infraction à la loi. Dans ce cas, vous devriez nous en informer immédiatement et effacer ce courriel. Il contenuto del presente messaggio elettronico è da considerare di massima riservatezza e possibilmente è protetto in modo particolare dalla legge. La presente e-mail è riservata alla sola attenzione della persona destinataria. Se lei non è la persona che avrebbe dovuto ricevere la e-mail, non le è permesso e possibilmente rappresenta una violazione della legge, copiare la presente e-mail, diffonderla o utilizzarla in qualsiasi altro modo. In questo caso lei dovrebbe informarci al più presto possibile e cancellare la presente e-mail.
Wap Push : global-sender parameter for multiple SMSCs
Hi User List Im trying to configure Kannel to allow WAP Pushes to two different SMSCs. My problem is - they each require a different originating number (global-sender parameter in the ppg group). Is there a way of specifying the originating number for each WAP Push (similar to the 'from' parameter in sendsms)? This is my config file ... group = core admin-port = ... admin-password = aaa status-password = aaa admin-deny-ip = "*.*.*.*" admin-allow-ip = "127.0.0.1" smsbox-port = 13001 wapbox-port = 13002 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" wdp-interface-name = "*" log-file = "/var/log/kannel/bearerbox.log" log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = "aaa" smsc-password = aaa system-type = 'VMA' address-range = "" msg-id-type = 0 throughput = 30 smsc-id = smsc1 allowed-smsc-id = "smsc1" log-file = "/var/log/kannel/smsc1.log" log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = "aaa" smsc-password = aaa system-type = 'VMA' address-range = "" msg-id-type = 0 throughput = 30 smsc-id = smsc2 allowed-smsc-id = "smsc2" log-file = "/var/log/kannel/smsc2.log" log-level = 0 group = wapbox bearerbox-host = 127.0.0.1 log-file = "/var/log/kannel/wapbox.log" log-level = 0 syslog-level = none group = smsbox smsbox-id = smsbox1 bearerbox-host = localhost sendsms-port = 13131 sendsms-chars = "0123456789 " access-log = "/var/log/kannel/access.log" log-file = "/var/log/kannel/smsbox.log" log-level = 0 group = smsbox-route smsbox-id = smsbox1 smsc-ids = "smsc1;smsc2" group = ppg ppg-url = /wappush ppg-port = 8080 service-name = ppg ppg-smsbox-id = smsbox1 concurrent-pushes = 100 users = 1024 global-sender = 12345 trusted-pi = false ppg-allow-ip = ... group = wap-push-user wap-push-user = pushtest ppg-username = zzz ppg-password = zzz allow-ip = ... group = sms-service keyword = default max-messages = 0 get-url = "http://."; group = sendsms-user username = xxx password = xxx forced-smsc = smsc1 group = sendsms-user username = yyy password = yyy forced-smsc = smsc2
Re: Mixing the SMS delivery between multiple SMSCs randomly
My problem is resolved. Sorry for wasting your valuable time. There is a typo mistakes at one place in my original configuration file.By concept it should work fine, So i audited the config from scratch, and found the problem. I struggled for 3 days, so posted to our group with frustration.Please ignore my request. Thank You- SG --- On Tue, 19/10/10, SG wrote: From: SG Subject: Mixing the SMS delivery between multiple SMSCs randomly To: users@kannel.org Date: Tuesday, 19 October, 2010, 6:23 AM Hi Group I am facing one different problem.I have configured 3 SMSC groups in kannel.conf file and 3 separate SMS users for each SMSC.I have configured DENIED SMSC list in SMSC groups and forced SMSC in SMS USER groups. But when i did HTML post with one SMSC user and pass word like belowhttp://192.168.3.111:4/cgi-bin/sendsms?username=user1&password=pass1_#$&charset=ISO-8859-1&to=155&smsc=SMSC1&from=5&concatenation=true&account=1_2_34_57&dlr-mask=31&text=Test+Message It is supposed to deliver through SMSC1, but strangely it is delivering through random SMSC 1 or 2 or 3 I am using 1-November-2010 Kannel source I have searched a lot in internet and old emails bit did not find my answer. Please help me. Lot of thanks in Advance.-SG I am sending my configuration sample here. #SMSC GROUPS#group = smscsmsc = smppsmsc-id = SMSC1denied-smsc-id= SMSC2;SMSC3log-level = 1log-file = "/home/kannel/log/SMSC1.log"reconnect-delay = 10host = gateway.z.netport = 9900transceiver-mode = truesmsc-username = ""smsc-password = "pass"system-type = "VMA"enquire-link-interval = 30max-pending-submits = 10reconnect-delay = 10connection-timeout = 0wait-ack = 60wait-ack-expire = 0x00 group = smscsmsc = smppsmsc-id = SMSC2denied-smsc-id= SMSC1;SMSC3log-level = 1log-file = "/home/kannel/log/SMSC2.log"reconnect-delay = 10host = gateway.z2.netport = 9900transceiver-mode = truesmsc-username = "222"smsc-password = "pass"system-type = "VMA"enquire-link-interval = 30max-pending-submits = 10reconnect-delay = 10connection-timeout = 0wait-ack = 60wait-ack-expire = 0x00 group = smscsmsc = smppsmsc-id = SMSC3denied-smsc-id= SMSC1;SMSC2log-level = 1log-file = "/home/kannel/log/SMSC3.log"reconnect-delay = 10host = gateway.z3.netport = 9900transceiver-mode = truesmsc-username = ""smsc-password = "pass"system-type = "VMA"enquire-link-interval = 30max-pending-submits = 10reconnect-delay = 10connection-timeout = 0wait-ack = 60wait-ack-expire = 0x00 #SMSC USERS#group = sendsms-userusername = user1password = pass1_#$name = SMSUSER1concatenation= truemax-messages = 10forced-smsc = SMSC1 group = sendsms-userusername = user2password = pass2_#$name = SMSUSER2concatenation= truemax-messages = 10forced-smsc = SMSC2 group = sendsms-userusername = user3password = pass3_#$name = SMSUSER3concatenation= truemax-messages = 10forced-smsc = SMSC3 # END ###
Mixing the SMS delivery between multiple SMSCs randomly
Hi Group I am facing one different problem.I have configured 3 SMSC groups in kannel.conf file and 3 separate SMS users for each SMSC.I have configured DENIED SMSC list in SMSC groups and forced SMSC in SMS USER groups. But when i did HTML post with one SMSC user and pass word like belowhttp://192.168.3.111:4/cgi-bin/sendsms?username=user1&password=pass1_#$&charset=ISO-8859-1&to=155&smsc=SMSC1&from=5&concatenation=true&account=1_2_34_57&dlr-mask=31&text=Test+Message It is supposed to deliver through SMSC1, but strangely it is delivering through random SMSC 1 or 2 or 3 I am using 1-November-2010 Kannel source I have searched a lot in internet and old emails bit did not find my answer. Please help me. Lot of thanks in Advance.-SG I am sending my configuration sample here. #SMSC GROUPS#group = smscsmsc = smppsmsc-id = SMSC1denied-smsc-id= SMSC2;SMSC3log-level = 1log-file = "/home/kannel/log/SMSC1.log"reconnect-delay = 10host = gateway.z.netport = 9900transceiver-mode = truesmsc-username = ""smsc-password = "pass"system-type = "VMA"enquire-link-interval = 30max-pending-submits = 10reconnect-delay = 10connection-timeout = 0wait-ack = 60wait-ack-expire = 0x00 group = smscsmsc = smppsmsc-id = SMSC2denied-smsc-id= SMSC1;SMSC3log-level = 1log-file = "/home/kannel/log/SMSC2.log"reconnect-delay = 10host = gateway.z2.netport = 9900transceiver-mode = truesmsc-username = "222"smsc-password = "pass"system-type = "VMA"enquire-link-interval = 30max-pending-submits = 10reconnect-delay = 10connection-timeout = 0wait-ack = 60wait-ack-expire = 0x00 group = smscsmsc = smppsmsc-id = SMSC3denied-smsc-id= SMSC1;SMSC2log-level = 1log-file = "/home/kannel/log/SMSC3.log"reconnect-delay = 10host = gateway.z3.netport = 9900transceiver-mode = truesmsc-username = ""smsc-password = "pass"system-type = "VMA"enquire-link-interval = 30max-pending-submits = 10reconnect-delay = 10connection-timeout = 0wait-ack = 60wait-ack-expire = 0x00 #SMSC USERS#group = sendsms-userusername = user1password = pass1_#$name = SMSUSER1concatenation= truemax-messages = 10forced-smsc = SMSC1 group = sendsms-userusername = user2password = pass2_#$name = SMSUSER2concatenation= truemax-messages = 10forced-smsc = SMSC2 group = sendsms-userusername = user3password = pass3_#$name = SMSUSER3concatenation= truemax-messages = 10forced-smsc = SMSC3 # END ###
multiple smscs
hi all, just wanted to confirm i've got it right here... i've got two smsc groups, to different smpp servers. i've tried blocking access to one and then the other using my firewall and it seems messages still get out (although dlr's weren't coming back... perhaps they always come from the same server?) anyway the most important thing is that messages get out ... so am i right in assuming that if you include multiple smsc groups in your kannel config, and then you don't specify an smsc id in your send-sms call, that if one of those connections goes down it will use the other one automatically? cheers iain
RES: multiple smscs
Here it is (I erased the secret stuff): group = smsc smsc-id = opt3344 smsc = emi denied-smsc-id = "vdf3344;tmn3344" host = port = smsc-username = smsc-password = my-number = 3344 keepalive = 30 idle-timeout = 60 flow-control = 1 window = 100 group = sendsms-user username = password = max-messages = 3 concatenation = true user-deny-ip = "*.*.*.*" user-allow-ip = denied-prefix-regex=^(\+351)?(91|96) forced-smsc = opt3344 group = smsc smsc-id = vdf3344 smsc = emi denied-smsc-id = "opt3344;tmn3344" host = port = smsc-username = smsc-password = my-number = 3344 keepalive = 30 idle-timeout = 60 flow-control = 1 window = 100 group = smsc smsc-id = tmn3344 smsc = emi denied-smsc-id = "opt3344;vdf3344" host = port = my-number = 3344 keepalive = 30 idle-timeout = 60 flow-control = 1 window = 100 group = sendsms-user username = password = max-messages = 3 concatenation = true user-deny-ip = "*.*.*.*" user-allow-ip = forced-smsc = vdf3344 allowed-prefix-regex =^(\+351)?91 group = sendsms-user username = password = max-messages = 3 concatenation = true user-deny-ip = "*.*.*.*" user-allow-ip = forced-smsc = tmn3344 allowed-prefix-regex =^(\+351)?96 I had the allowed-smsc-id, but because I got the following message from the logs, I droped it. 2007-04-27 15:25:08 [19502] [0] WARNING: Both 'allowed-smsc-id' and 'denied-smsc-id' set, deny-list automatically ignored I've also been playing around with the prefixes, but they don't seem to matter. Thanks, Gabriel Lühers Graça [EMAIL PROTECTED] -Mensagem original- De: Rodrigo Cremaschi [mailto:[EMAIL PROTECTED] Enviada em: sexta-feira, 27 de Abril de 2007 12:05 Para: Gabriel Luhers Graca Cc: users@kannel.org Assunto: Re: multiple smscs Hi Gabriel, post your config file, please. Are you using sms-push mechanism to reply to the MO messages? In this case, the INFO line is normal, as you are setting max-messages = 0. Your script is responsible for specifying the outgoing SMSC. When you use multiple SMSCs, you have to allow the desired SMSC and deny the others, as Davy said, like this: # SMSC ONE group = smsc smsc = smpp smsc-id = ONE allowed-smsc-id = "ONE" denied-smsc-id = "TWO", "THREE" ... # SMSC TWO group = smsc smsc = smpp smsc-id = TWO allowed-smsc-id = "TWO" denied-smsc-id = "ONE", "THREE" ... etc. Regards, Rodrigo Cremaschi. On 4/27/07, Gabriel Luhers Graca <[EMAIL PROTECTED]> wrote: > I did as you suggested, Chan, but my SMSs are always being sent to the same > SMSC. It seems like the allowed-prefix is simply ignored. But the > denied-smsc-id is not, because the logs show this: > > 2007-04-27 14:14:56 [10761] [5] INFO: No reply sent, denied. > > How does kannel decide who gets the request? > > Thanks, > > Gabriel Lühers Graça > [EMAIL PROTECTED] > > -Mensagem original- > De: Davy Chan [mailto:[EMAIL PROTECTED] > Enviada em: terça-feira, 24 de Abril de 2007 1:30 > Para: Gabriel Luhers Graca > Cc: users@kannel.org > Assunto: Re: multiple smscs > > **>Subject: multiple smscs > **>Date: Mon, 23 Apr 2007 11:32:25 -0300 > **>Message-ID: <[EMAIL PROTECTED]> > **>From: "Gabriel Luhers Graca" <[EMAIL PROTECTED]> > **>To: > **> > **>Hello, > **> > **> I'm trying to configure multiple SMSCs without success. > **> > **> The sms-services are identical for all 3 of my SMSCs, but I need to > **> be able to choose which one sends back the reply using the number. > **> The actually just have to go back to the same SMSC they came from. > **> > **> One operator handles all numbers that start with 91, another all > **> that start with 96 and a third the remainder. > **> > **> I've tried the following: > **> > **>group = smsc > **>smsc-id = xxx3344 > **>smsc = emi > **>allowed-smsc-id = xxx3344 > **>host = 10.xxx.yyy.zzz > **>port = ppp > **>my-number = 3344 > **>keepalive = 30 > **>idle-timeout = 60 > **>flow-control = 1 > **>window = 100 > **> > **>group = sendsms-user > **>username = jdoe > **>password = secret > **>max-messages = 3 > **>concatenation = true > **>user-deny-ip = "*.*.*.*" > **>user-allow-ip = "127.0.0.1; 10.xxx.yyy.zzz" > **>forced-smsc = xxx3344 > **>allowed-prefix = "96" > **> > **> > **> I thought "allowed-prefix" would make all requests from numbers starting > with 96 be channeled to this SMSC, but that didn't happen. > **> > **> How does one configure this? > > "allowed-smsc-id" establishes that a particular smsc entry is willing > to accept SMS for a specific smsc smsc-id name. > > What you want to do is to limit the list of smsc-id that can use the > smsc. You should also add a "denied-smsci-id" that lists all the > smsc-id's that are forbidden to use that smsc. > > See ya... > > d.c. > >
Re: multiple smscs
Hi Gabriel, post your config file, please. Are you using sms-push mechanism to reply to the MO messages? In this case, the INFO line is normal, as you are setting max-messages = 0. Your script is responsible for specifying the outgoing SMSC. When you use multiple SMSCs, you have to allow the desired SMSC and deny the others, as Davy said, like this: # SMSC ONE group = smsc smsc = smpp smsc-id = ONE allowed-smsc-id = "ONE" denied-smsc-id = "TWO", "THREE" ... # SMSC TWO group = smsc smsc = smpp smsc-id = TWO allowed-smsc-id = "TWO" denied-smsc-id = "ONE", "THREE" ... etc. Regards, Rodrigo Cremaschi. On 4/27/07, Gabriel Luhers Graca <[EMAIL PROTECTED]> wrote: I did as you suggested, Chan, but my SMSs are always being sent to the same SMSC. It seems like the allowed-prefix is simply ignored. But the denied-smsc-id is not, because the logs show this: 2007-04-27 14:14:56 [10761] [5] INFO: No reply sent, denied. How does kannel decide who gets the request? Thanks, Gabriel Lühers Graça [EMAIL PROTECTED] -Mensagem original- De: Davy Chan [mailto:[EMAIL PROTECTED] Enviada em: terça-feira, 24 de Abril de 2007 1:30 Para: Gabriel Luhers Graca Cc: users@kannel.org Assunto: Re: multiple smscs **>Subject: multiple smscs **>Date: Mon, 23 Apr 2007 11:32:25 -0300 **>Message-ID: <[EMAIL PROTECTED]> **>From: "Gabriel Luhers Graca" <[EMAIL PROTECTED]> **>To: **> **>Hello, **> **> I'm trying to configure multiple SMSCs without success. **> **> The sms-services are identical for all 3 of my SMSCs, but I need to **> be able to choose which one sends back the reply using the number. **> The actually just have to go back to the same SMSC they came from. **> **> One operator handles all numbers that start with 91, another all **> that start with 96 and a third the remainder. **> **> I've tried the following: **> **>group = smsc **>smsc-id = xxx3344 **>smsc = emi **>allowed-smsc-id = xxx3344 **>host = 10.xxx.yyy.zzz **>port = ppp **>my-number = 3344 **>keepalive = 30 **>idle-timeout = 60 **>flow-control = 1 **>window = 100 **> **>group = sendsms-user **>username = jdoe **>password = secret **>max-messages = 3 **>concatenation = true **>user-deny-ip = "*.*.*.*" **>user-allow-ip = "127.0.0.1; 10.xxx.yyy.zzz" **>forced-smsc = xxx3344 **>allowed-prefix = "96" **> **> **> I thought "allowed-prefix" would make all requests from numbers starting with 96 be channeled to this SMSC, but that didn't happen. **> **> How does one configure this? "allowed-smsc-id" establishes that a particular smsc entry is willing to accept SMS for a specific smsc smsc-id name. What you want to do is to limit the list of smsc-id that can use the smsc. You should also add a "denied-smsci-id" that lists all the smsc-id's that are forbidden to use that smsc. See ya... d.c.
RES: multiple smscs
I did as you suggested, Chan, but my SMSs are always being sent to the same SMSC. It seems like the allowed-prefix is simply ignored. But the denied-smsc-id is not, because the logs show this: 2007-04-27 14:14:56 [10761] [5] INFO: No reply sent, denied. How does kannel decide who gets the request? Thanks, Gabriel Lühers Graça [EMAIL PROTECTED] -Mensagem original- De: Davy Chan [mailto:[EMAIL PROTECTED] Enviada em: terça-feira, 24 de Abril de 2007 1:30 Para: Gabriel Luhers Graca Cc: users@kannel.org Assunto: Re: multiple smscs **>Subject: multiple smscs **>Date: Mon, 23 Apr 2007 11:32:25 -0300 **>Message-ID: <[EMAIL PROTECTED]> **>From: "Gabriel Luhers Graca" <[EMAIL PROTECTED]> **>To: **> **>Hello, **> **> I'm trying to configure multiple SMSCs without success. **> **> The sms-services are identical for all 3 of my SMSCs, but I need to **> be able to choose which one sends back the reply using the number. **> The actually just have to go back to the same SMSC they came from. **> **> One operator handles all numbers that start with 91, another all **> that start with 96 and a third the remainder. **> **> I've tried the following: **> **>group = smsc **>smsc-id = xxx3344 **>smsc = emi **>allowed-smsc-id = xxx3344 **>host = 10.xxx.yyy.zzz **>port = ppp **>my-number = 3344 **>keepalive = 30 **>idle-timeout = 60 **>flow-control = 1 **>window = 100 **> **>group = sendsms-user **>username = jdoe **>password = secret **>max-messages = 3 **>concatenation = true **>user-deny-ip = "*.*.*.*" **>user-allow-ip = "127.0.0.1; 10.xxx.yyy.zzz" **>forced-smsc = xxx3344 **>allowed-prefix = "96" **> **> **> I thought "allowed-prefix" would make all requests from numbers starting with 96 be channeled to this SMSC, but that didn't happen. **> **> How does one configure this? "allowed-smsc-id" establishes that a particular smsc entry is willing to accept SMS for a specific smsc smsc-id name. What you want to do is to limit the list of smsc-id that can use the smsc. You should also add a "denied-smsci-id" that lists all the smsc-id's that are forbidden to use that smsc. See ya... d.c.
Re: multiple smscs
**>Subject: multiple smscs **>Date: Mon, 23 Apr 2007 11:32:25 -0300 **>Message-ID: <[EMAIL PROTECTED]> **>From: "Gabriel Luhers Graca" <[EMAIL PROTECTED]> **>To: **> **>Hello, **> **> I'm trying to configure multiple SMSCs without success. **> **> The sms-services are identical for all 3 of my SMSCs, but I need to **> be able to choose which one sends back the reply using the number. **> The actually just have to go back to the same SMSC they came from. **> **> One operator handles all numbers that start with 91, another all **> that start with 96 and a third the remainder. **> **> I've tried the following: **> **>group = smsc **>smsc-id = xxx3344 **>smsc = emi **>allowed-smsc-id = xxx3344 **>host = 10.xxx.yyy.zzz **>port = ppp **>my-number = 3344 **>keepalive = 30 **>idle-timeout = 60 **>flow-control = 1 **>window = 100 **> **>group = sendsms-user **>username = jdoe **>password = secret **>max-messages = 3 **>concatenation = true **>user-deny-ip = "*.*.*.*" **>user-allow-ip = "127.0.0.1; 10.xxx.yyy.zzz" **>forced-smsc = xxx3344 **>allowed-prefix = "96" **> **> **> I thought "allowed-prefix" would make all requests from numbers starting with 96 be channeled to this SMSC, but that didn't happen. **> **> How does one configure this? "allowed-smsc-id" establishes that a particular smsc entry is willing to accept SMS for a specific smsc smsc-id name. What you want to do is to limit the list of smsc-id that can use the smsc. You should also add a "denied-smsci-id" that lists all the smsc-id's that are forbidden to use that smsc. See ya... d.c.
multiple smscs
Hello, I'm trying to configure multiple SMSCs without success. The sms-services are identical for all 3 of my SMSCs, but I need to be able to choose which one sends back the reply using the number. The actually just have to go back to the same SMSC they came from. One operator handles all numbers that start with 91, another all that start with 96 and a third the remainder. I've tried the following: group = smsc smsc-id = xxx3344 smsc = emi allowed-smsc-id = xxx3344 host = 10.xxx.yyy.zzz port = ppp my-number = 3344 keepalive = 30 idle-timeout = 60 flow-control = 1 window = 100 group = sendsms-user username = jdoe password = secret max-messages = 3 concatenation = true user-deny-ip = "*.*.*.*" user-allow-ip = "127.0.0.1; 10.xxx.yyy.zzz" forced-smsc = xxx3344 allowed-prefix = "96" I thought "allowed-prefix" would make all requests from numbers starting with 96 be channeled to this SMSC, but that didn't happen. How does one configure this? Thanks, Gabriel Lühers Graça [EMAIL PROTECTED]
missrouted DLR on multiple SMSCs with 1.4.0
List, I have 1.4.0 configured with multiple SMSCs, why the DLR missrouted so many times.How to avoid it? I have enabled denied-smsc, allowed-smsc directives but no work. Many thanks for replies. Regards Willy
RE: SMPP - Selecting MT Connection From Multiple SMSCs
you can try passing additional parameter &smsc= in your sendsms url -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Neil Mukerji Sent: Thursday, March 25, 2004 10:00 PM To: [EMAIL PROTECTED] Subject: SMPP - Selecting MT Connection From Multiple SMSCs Hi, I've got a connections to Multiple SMSCs as I need to listen for MO on all of them, plus I use some for Premium sending and others for standard sending. When I send an SMS message (via HTTP sendsms-user), it currently randomly selects which SMSC to send from. Clearly I need to find a way of making this precise, not random. The manual states: The communication link between bearerbox and smsbox has been designed for the purpose of load-balancing via random assignment. Which means, bearerbox holds all smsc connections and passes inbound message to one of the connected smsboxes. So you have a determined route for outbound messages, but no determinated route for inbound messages. Where is this determined route for outbound messages? Seems random to me. I tried setting "forced-smsc =" but this doesn't help. Any suggestions, or do I need to run a separate instance of bearerbox for each connection? That'd be a right pain.. Neil Mukerji Technical Manager Sign-Up.to [EMAIL PROTECTED] www.sign-up.to 0845 644 4184
SMPP - Selecting MT Connection From Multiple SMSCs
Title: SMPP - Selecting MT Connection From Multiple SMSCs Hi, I've got a connections to Multiple SMSCs as I need to listen for MO on all of them, plus I use some for Premium sending and others for standard sending. When I send an SMS message (via HTTP sendsms-user), it currently randomly selects which SMSC to send from. Clearly I need to find a way of making this precise, not random. The manual states: The communication link between bearerbox and smsbox has been designed for the purpose of load-balancing via random assignment. Which means, bearerbox holds all smsc connections and passes inbound message to one of the connected smsboxes. So you have a determined route for outbound messages, but no determinated route for inbound messages. Where is this determined route for outbound messages? Seems random to me. I tried setting "forced-smsc =" but this doesn't help. Any suggestions, or do I need to run a separate instance of bearerbox for each connection? That'd be a right pain…. Neil Mukerji Technical Manager Sign-Up.to [EMAIL PROTECTED] www.sign-up.to 0845 644 4184
RE: Using Multiple SMSCs
Hi Reza, Many thanks for your answer, following your description bellow, what I get is the following, kannel will receive incomming messages from Operator1 subs (destination Operator2 subs) and will send them to http://myhost/myapp and it has to push them using the second connection (Operator2), we did this and worked. But this is not exactly what was we were looking for, we were looking for kannel to make the routing between operators without any external application. We installed the kannel 1.3.1 and in the documentation was the smsbox routing, and it seems that it matches with what we are looking for. We would like to know if someone has worked with this and can bring us some help. Best Regards Oscar Flores -Original Message- From: Reza Anwar [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 18, 2004 10:27 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Using Multiple SMSCs Hi Oscar, I'm currently connecting to two SMS-Cs at two different operators. What you have to do is to define a group = smsc for each SMS-C you want to connect to (I'm using one group = smsbox). In your case it might go something like this: group = smsc smsc-id = operator1 allowed-smsc-id = operator1 smsc = smpp interface-version = 34 . . . group = smsc smsc-id = operator2 allowed-smsc-id = operator2 smsc = smpp interface-version = 34 . . . Then you have to set up group = sendsms-user since you would like to push the message from one SMS-C to the other, so: group = sendsms-user username = foo1 password = bar1 forced-smsc = operator1 . . . group = sendsms-user username = foo2 password = bar2 forced-smsc = operator2 . . . If you don't want a subscriber at operator1 receive a reply when he/she sends a message, make sure you set max-messages=0 at the group = sms-service setting: group = sms-service keyword = default name = service1 accepted-smsc = operator1 url = "http://yourhost/yourapp"; max-messages = 0 . . . group = sms-service keyword = default name = service2 accepted-smsc = operator2 url = "http://yourhost/yourapp"; max-messages = 0 . . . Make you app catch the message from an SMS-C and then push it using http://yourhost:sendsms-port/cgi-bin/sendsms?username=sendsms_username_o f_other_smsc&password=sendsms_password_of_other_smsc&to=dest_msisdn&text =yaddayaddayadda. Hope this helps, --Reza Oscar Flores wrote: >Hi kannel users, > >In my company we have a project to interconnect different SMSCs and We >want to use the kannel gateway to do this. > >The idea is to connect SMSCs from different mobile operators, let's >suppose two operators, kannel will be connected to both SMSCs using SMPP >3.4. And when subs from operator1 sends messages to subs from operator2 >kannel will receive the messages from SMSC1 and send them to SMSC2 and >in the other way too. > >We have reviewed the documentation and did some test but we weren't able >to make this work. Would you like to give us some help, How we do have >to make the configuration, do we need one smsbox for each operator? > >Many Thanks and Best Regards > >Oscar Flores > > > > > > >
Re: Using Multiple SMSCs
Hi Oscar, I'm currently connecting to two SMS-Cs at two different operators. What you have to do is to define a group = smsc for each SMS-C you want to connect to (I'm using one group = smsbox). In your case it might go something like this: group = smsc smsc-id = operator1 allowed-smsc-id = operator1 smsc = smpp interface-version = 34 . . . group = smsc smsc-id = operator2 allowed-smsc-id = operator2 smsc = smpp interface-version = 34 . . . Then you have to set up group = sendsms-user since you would like to push the message from one SMS-C to the other, so: group = sendsms-user username = foo1 password = bar1 forced-smsc = operator1 . . . group = sendsms-user username = foo2 password = bar2 forced-smsc = operator2 . . . If you don't want a subscriber at operator1 receive a reply when he/she sends a message, make sure you set max-messages=0 at the group = sms-service setting: group = sms-service keyword = default name = service1 accepted-smsc = operator1 url = "http://yourhost/yourapp"; max-messages = 0 . . . group = sms-service keyword = default name = service2 accepted-smsc = operator2 url = "http://yourhost/yourapp"; max-messages = 0 . . . Make you app catch the message from an SMS-C and then push it using http://yourhost:sendsms-port/cgi-bin/sendsms?username=sendsms_username_of_other_smsc&password=sendsms_password_of_other_smsc&to=dest_msisdn&text=yaddayaddayadda. Hope this helps, --Reza Oscar Flores wrote: Hi kannel users, In my company we have a project to interconnect different SMSCs and We want to use the kannel gateway to do this. The idea is to connect SMSCs from different mobile operators, let's suppose two operators, kannel will be connected to both SMSCs using SMPP 3.4. And when subs from operator1 sends messages to subs from operator2 kannel will receive the messages from SMSC1 and send them to SMSC2 and in the other way too. We have reviewed the documentation and did some test but we weren't able to make this work. Would you like to give us some help, How we do have to make the configuration, do we need one smsbox for each operator? Many Thanks and Best Regards Oscar Flores
Using Multiple SMSCs
Hi kannel users, In my company we have a project to interconnect different SMSCs and We want to use the kannel gateway to do this. The idea is to connect SMSCs from different mobile operators, let's suppose two operators, kannel will be connected to both SMSCs using SMPP 3.4. And when subs from operator1 sends messages to subs from operator2 kannel will receive the messages from SMSC1 and send them to SMSC2 and in the other way too. We have reviewed the documentation and did some test but we weren't able to make this work. Would you like to give us some help, How we do have to make the configuration, do we need one smsbox for each operator? Many Thanks and Best Regards Oscar Flores
Routing WAP Push messages with multiple smscs
Dear All, I've searched the list and couldn't find any mention of this before, so here we go: I have kannel running on a box with 2 smscs configured, a gsm modem and an smpp gateway. I want the GSM modem to be used for incoming SMS messages only, and for all outgoing messages to go via the SMPP host. I have this working fine for text based SMS, but I can't figure out how to set it up for the PPG on kannel. I'm using the PAP facility to initiate WAP push messages and they are always routed via the gsm modem. Is there a quick & easy way to get the PPG to use a nominated SMSC ? Thanks, Jon.
