Re: problem with routing sms to proper smsc
Hi, Rerouting is something else. Your question is obviously about routing. Please post detailed bb logs from startup, leading up to the problem. Probably smscs are inactive, i.e. have not started up. BR, Nikos - Original Message - From: "Pawel Bunko" To: Sent: Wednesday, December 16, 2009 9:19 AM Subject: problem with routing sms to proper smsc Hello, I configured 4 modems of 2 gsm operators: group = smsc smsc = at smsc-id = GS2ModemEra14 modemtype = telit device = rawtcp host = 172.16.82.194 port = 15014 speed = 9600 pin = 5047 keepalive = 5 max-error-count = 5 log-file = "/opt/kannel/GS2ModemEra14.log" log-level = 0 sim-buffering = true preferred-smsc-id="GS2ModemEra14;GS2ModemEra15" allowed-smsc-id="GS2ModemEra14;GS2ModemEra15" group = smsc smsc = at smsc-id = GS2ModemEra15 modemtype = telit device = rawtcp host = 172.16.82.194 port = 15015 speed = 9600 pin = 8321 keepalive = 5 max-error-count = 5 log-file = "/opt/kannel/GS2ModemEra15.log" log-level = 0 sim-buffering = true preferred-smsc-id="GS2ModemEra14;GS2ModemEra15" allowed-smsc-id="GS2ModemEra14;GS2ModemEra15" group = smsc smsc = at smsc-id = GS2ModemPlus07 modemtype = telit device = rawtcp host = 172.16.82.194 port = 15007 speed = 9600 pin = 8856 keepalive = 5 max-error-count = 5 log-file = "/opt/kannel/GS2ModemPlus07.log" log-level = 0 sim-buffering = true preferred-smsc-id="GS2ModemPlus07;GS2ModemPlus08" allowed-smsc-id="GS2ModemPlus07;GS2ModemPlus08" group = smsc smsc = at smsc-id = GS2ModemPlus08 modemtype = telit device = rawtcp host = 172.16.82.194 port = 15008 speed = 9600 pin = 7282 keepalive = 5 max-error-count = 5 log-file = "/opt/kannel/GS2ModemPlus08.log" log-level = 0 sim-buffering = true preferred-smsc-id="GS2ModemPlus07;GS2ModemPlus08" allowed-smsc-id="GS2ModemPlus07;GS2ModemPlus08" # SEND-SMS USERS group = sendsms-user username = GS2ModemEra14 password = GS2ModemEra14 group = sendsms-user username = GS2ModemEra15 password = GS2ModemEra15 group = sendsms-user username = GS2ModemPlus07 password = GS2ModemPlus07 group = sendsms-user username = GS2ModemPlus08 password = GS2ModemPlus08 and when I try to send sms with sendsms: url looks like this: http://172.16.160.82:13013/cgi-bin/sendsms?username=GS2ModemEra14&password=GS2ModemEra14&from=&to=xxx&text=test&smsc-id=GS2ModemEra14&dlr-mask =31&coding=0&validity=1440 bearbox logs looks like this: 2009-12-16 08:02:48 [11165] [12] DEBUG: boxc_receiver: sms received 2009-12-16 08:02:48 [11165] [12] WARNING: Cannot find SMSCConn for message to , rejected. 2009-12-16 08:02:48 [11165] [12] WARNING: Message rejected by bearerbox, no router! According to the user's guide this sendsms request with that configuration should reroute sms to GS2ModemEra14 or GS2ModemEra15 smsc http://172.16.160.82:13013/cgi-bin/sendsms?username=GS2ModemPlus08&password=GS2ModemPlus08&from=&to=xxx&text=test&smsc-id=GS2ModemPlus08&dlr-mask =31&coding=0&validity=1440 this sms should be rerouted to GS2ModemPlus08 or GS2ModemPlus07 smsc why those sms were rejected? when I leave only preferred-smsc-id list for each modem everything working fine but I think that rerouting wouldn't work as I wish what is wrong? thanks for your help Pawel
Re: problem with routing sms to proper smsc
Nikos Balkanas pisze: Hi, Rerouting is something else. Your question is obviously about routing. Please post detailed bb logs from startup, leading up to the problem. Probably smscs are inactive, i.e. have not started up. I was talking about routing all smsc were active when I added forced-smsc = to every send-sms users group like this # SEND-SMS USERS group = sendsms-user username = GS2ModemEra14 password = GS2ModemEra14 forced-smsc = GS2ModemEra14 group = sendsms-user username = GS2ModemEra15 password = GS2ModemEra15 forced-smsc = GS2ModemEra15 group = sendsms-user username = GS2ModemPlus07 password = GS2ModemPlus07 forced-smsc = GS2ModemPlus07 group = sendsms-user username = GS2ModemPlus08 password = GS2ModemPlus08 forced-smsc = GS2ModemPlus08 routing starts working and when I try to send sms with sendsms: url looks like this: http://172.16.160.82:13013/cgi-bin/sendsms?username=GS2ModemEra14&password=GS2ModemEra14&from=&to=xxx&text=test&smsc-id=GS2ModemEra14&dlr-mask =31&coding=0&validity=1440 but it is strange why forced-smsc is necessary if smsc-id parameter was pass in sendsms url? bearbox logs looks like this: 2009-12-16 08:02:48 [11165] [12] DEBUG: boxc_receiver: sms received 2009-12-16 08:02:48 [11165] [12] WARNING: Cannot find SMSCConn for message to , rejected. 2009-12-16 08:02:48 [11165] [12] WARNING: Message rejected by bearerbox, no router! According to the user's guide this sendsms request with that configuration should reroute sms to GS2ModemEra14 or GS2ModemEra15 smsc http://172.16.160.82:13013/cgi-bin/sendsms?username=GS2ModemPlus08&password=GS2ModemPlus08&from=&to=xxx&text=test&smsc-id=GS2ModemPlus08&dlr-mask =31&coding=0&validity=1440 this sms should be rerouted to GS2ModemPlus08 or GS2ModemPlus07 smsc why those sms were rejected? when I leave only preferred-smsc-id list for each modem everything working fine but I think that rerouting wouldn't work as I wish what is wrong? thanks for your help Pawel -- Paweł Buńko Starszy Programista Dział Budowy Oprogramowania Systemów Zarządzania Biuro Rozwoju Produktu tel. +48 22 61 16 729; 502 477 791 fax. +48 22 61 09 143 mail: p.bu...@autoguard.pl; www.autoguard.pl AutoGuard S.A. z siedzibą w Warszawie (04-128), ul. Omulewska 27. Spółka wpisana do Krajowego Rejestru Sądowego w Sądzie Rejonowym dla m. st. Warszawy w Warszawie, XIII Wydział Gospodarczy Krajowego Rejestru Sądowego pod nr KRS 287629. Kapitał akcyjny: 1.059.000,00 zł (w pełni opłacony), NIP 113-22-19-747, REGON 016284203. Klauzula poufności: Ta wiadomość może zawierać informacje poufne. Jeżeli nie jesteś adresatem wiadomości (i/albo otrzymałeś ją omyłkowo), prosimy poinformować nadawcę oraz ją usunąć. Wszelkie kopiowanie, ujawnianie lub dalsze przekazywanie materiałów zawartych w tej wiadomości elektronicznej jest zabronione. Disclaimer: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Re: problem with routing sms to proper smsc
That's because you have a typo. You should use: &smsc= in your URL instead of: &smsc-id= BR, Nikos - Original Message - From: "Pawel Bunko" To: "Nikos Balkanas" Cc: Sent: Wednesday, December 16, 2009 1:27 PM Subject: Re: problem with routing sms to proper smsc Nikos Balkanas pisze: Hi, Rerouting is something else. Your question is obviously about routing. Please post detailed bb logs from startup, leading up to the problem. Probably smscs are inactive, i.e. have not started up. I was talking about routing all smsc were active when I added forced-smsc = to every send-sms users group like this # SEND-SMS USERS group = sendsms-user username = GS2ModemEra14 password = GS2ModemEra14 forced-smsc = GS2ModemEra14 group = sendsms-user username = GS2ModemEra15 password = GS2ModemEra15 forced-smsc = GS2ModemEra15 group = sendsms-user username = GS2ModemPlus07 password = GS2ModemPlus07 forced-smsc = GS2ModemPlus07 group = sendsms-user username = GS2ModemPlus08 password = GS2ModemPlus08 forced-smsc = GS2ModemPlus08 routing starts working and when I try to send sms with sendsms: url looks like this: http://172.16.160.82:13013/cgi-bin/sendsms?username=GS2ModemEra14&password=GS2ModemEra14&from=&to=xxx&text=test&smsc-id=GS2ModemEra14&dlr-mask =31&coding=0&validity=1440 but it is strange why forced-smsc is necessary if smsc-id parameter was pass in sendsms url? bearbox logs looks like this: 2009-12-16 08:02:48 [11165] [12] DEBUG: boxc_receiver: sms received 2009-12-16 08:02:48 [11165] [12] WARNING: Cannot find SMSCConn for message to , rejected. 2009-12-16 08:02:48 [11165] [12] WARNING: Message rejected by bearerbox, no router! According to the user's guide this sendsms request with that configuration should reroute sms to GS2ModemEra14 or GS2ModemEra15 smsc http://172.16.160.82:13013/cgi-bin/sendsms?username=GS2ModemPlus08&password=GS2ModemPlus08&from=&to=xxx&text=test&smsc-id=GS2ModemPlus08&dlr-mask =31&coding=0&validity=1440 this sms should be rerouted to GS2ModemPlus08 or GS2ModemPlus07 smsc why those sms were rejected? when I leave only preferred-smsc-id list for each modem everything working fine but I think that rerouting wouldn't work as I wish what is wrong? thanks for your help Pawel -- Paweł Buńko Starszy Programista Dział Budowy Oprogramowania Systemów Zarządzania Biuro Rozwoju Produktu tel. +48 22 61 16 729; 502 477 791 fax. +48 22 61 09 143 mail: p.bu...@autoguard.pl; www.autoguard.pl AutoGuard S.A. z siedzibą w Warszawie (04-128), ul. Omulewska 27. Spółka wpisana do Krajowego Rejestru Sądowego w Sądzie Rejonowym dla m. st. Warszawy w Warszawie, XIII Wydział Gospodarczy Krajowego Rejestru Sądowego pod nr KRS 287629. Kapitał akcyjny: 1.059.000,00 zł (w pełni opłacony), NIP 113-22-19-747, REGON 016284203. Klauzula poufności: Ta wiadomość może zawierać informacje poufne. Jeżeli nie jesteś adresatem wiadomości (i/albo otrzymałeś ją omyłkowo), prosimy poinformować nadawcę oraz ją usunąć. Wszelkie kopiowanie, ujawnianie lub dalsze przekazywanie materiałów zawartych w tej wiadomości elektronicznej jest zabronione. Disclaimer: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Re: problem with routing sms to proper smsc
Nikos Balkanas pisze: That's because you have a typo. You should use: &smsc= in your URL instead of: &smsc-id= thanks a lot :) stupid mistake BR, Nikos - Original Message - From: "Pawel Bunko" To: "Nikos Balkanas" Cc: Sent: Wednesday, December 16, 2009 1:27 PM Subject: Re: problem with routing sms to proper smsc Nikos Balkanas pisze: Hi, Rerouting is something else. Your question is obviously about routing. Please post detailed bb logs from startup, leading up to the problem. Probably smscs are inactive, i.e. have not started up. I was talking about routing all smsc were active when I added forced-smsc = to every send-sms users group like this # SEND-SMS USERS group = sendsms-user username = GS2ModemEra14 password = GS2ModemEra14 forced-smsc = GS2ModemEra14 group = sendsms-user username = GS2ModemEra15 password = GS2ModemEra15 forced-smsc = GS2ModemEra15 group = sendsms-user username = GS2ModemPlus07 password = GS2ModemPlus07 forced-smsc = GS2ModemPlus07 group = sendsms-user username = GS2ModemPlus08 password = GS2ModemPlus08 forced-smsc = GS2ModemPlus08 routing starts working and when I try to send sms with sendsms: url looks like this: http://172.16.160.82:13013/cgi-bin/sendsms?username=GS2ModemEra14&password=GS2ModemEra14&from=&to=xxx&text=test&smsc-id=GS2ModemEra14&dlr-mask =31&coding=0&validity=1440 but it is strange why forced-smsc is necessary if smsc-id parameter was pass in sendsms url? bearbox logs looks like this: 2009-12-16 08:02:48 [11165] [12] DEBUG: boxc_receiver: sms received 2009-12-16 08:02:48 [11165] [12] WARNING: Cannot find SMSCConn for message to , rejected. 2009-12-16 08:02:48 [11165] [12] WARNING: Message rejected by bearerbox, no router! According to the user's guide this sendsms request with that configuration should reroute sms to GS2ModemEra14 or GS2ModemEra15 smsc http://172.16.160.82:13013/cgi-bin/sendsms?username=GS2ModemPlus08&password=GS2ModemPlus08&from=&to=xxx&text=test&smsc-id=GS2ModemPlus08&dlr-mask =31&coding=0&validity=1440 this sms should be rerouted to GS2ModemPlus08 or GS2ModemPlus07 smsc why those sms were rejected? when I leave only preferred-smsc-id list for each modem everything working fine but I think that rerouting wouldn't work as I wish what is wrong? thanks for your help Pawel -- PaweΕ‚ BuΕ„ko Starszy Programista DziaΕ‚ Budowy Oprogramowania SystemΓ³w ZarzΔ…dzania Biuro Rozwoju Produktu tel. +48 22 61 16 729; 502 477 791 fax. +48 22 61 09 143 mail: p.bu...@autoguard.pl; www.autoguard.pl AutoGuard S.A. z siedzibΔ… w Warszawie (04-128), ul. Omulewska 27. SpΓ³Ε‚ka wpisana do Krajowego Rejestru SΔ…dowego w SΔ…dzie Rejonowym dla m. st. Warszawy w Warszawie, XIII WydziaΕ‚ Gospodarczy Krajowego Rejestru SΔ…dowego pod nr KRS 287629. KapitaΕ‚ akcyjny: 1.059.000,00 zΕ‚ (w peΕ‚ni opΕ‚acony), NIP 113-22-19-747, REGON 016284203. Klauzula poufnoΕ›ci: Ta wiadomoΕ›Δ‡ moΕΌe zawieraΔ‡ informacje poufne. JeΕΌeli nie jesteΕ› adresatem wiadomoΕ›ci (i/albo otrzymaΕ‚eΕ› jΔ… omyΕ‚kowo), prosimy poinformowaΔ‡ nadawcΔ™ oraz jΔ… usunΔ…Δ‡. Wszelkie kopiowanie, ujawnianie lub dalsze przekazywanie materiaΕ‚Γ³w zawartych w tej wiadomoΕ›ci elektronicznej jest zabronione. Disclaimer: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. -- Paweł Buńko Starszy Programista Dział Budowy Oprogramowania Systemów Zarządzania Biuro Rozwoju Produktu tel. +48 22 61 16 729; 502 477 791 fax. +48 22 61 09 143 mail: p.bu...@autoguard.pl; www.autoguard.pl AutoGuard S.A. z siedzibą w Warszawie (04-128), ul. Omulewska 27. Spółka wpisana do Krajowego Rejestru Sądowego w Sądzie Rejonowym dla m. st. Warszawy w Warszawie, XIII Wydział Gospodarczy Krajowego Rejestru Sądowego pod nr KRS 287629. Kapitał akcyjny: 1.059.000,00 zł (w pełni opłacony), NIP 113-22-19-747, REGON 016284203. Klauzula poufności: Ta wiadomość może zawierać informacje poufne. Jeżeli nie jesteś adresatem wiadomości (i/albo otrzymałeś ją omyłkowo), prosimy poinformować nadawcę oraz ją usunąć. Wszelkie kopiowanie, ujawnianie lub dalsze przekazywanie materiałów zawartych w tej wiadomości elektronicznej jest zabronione. Disclaimer: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
