Dear Sir,
You are absolutely correct, but the logic is implemented in smppbox
for providing multiple smsc and also
bearerbox setting is not to be changed.
My application communicates with smppbox and smppbox in turn
communicates with bearerbox.
Regards,
Ramesh Helaiya
On Monday 30 June 2014 01:18 PM, spameden wrote:
2014-06-30 10:53 GMT+04:00 Ramesh G. Helaiya <ram...@routesms.in
<mailto:ram...@routesms.in>>:
Dear Sir,
The option which u have provided is a not what I am looking for.
Let me give an example of the same with format of access,
below is what the process flow must be
2014-06-30 12:12:48 FAILED Send SMS [SMSC:smpp_g1] [SVC:xxxxx]
[ACT:smpp] [BINF:] [from:tester] [to:1111111111]
[FID:192.168.200.12] [UUID:7079fab9-c8bf-4ee0-b607-6ece3bb82180]
[flags:-1:0:-1:0:3] [msg:158:test fall back] [udh:0:]
2014-06-30 12:12:48 Receive DLR [SMSC:smpp_g1] [SVC:xxxxx] [ACT:]
[BINF:] [from:1111111111] [to:tester] [FID:192.168.200.12]
[UUID:7079fab9-c8bf-4ee0-b607-6ece3bb82180] [flags:-1:-1:-1:-1:16]
[msg:73:NACK/0x00000a/Invalid Source Address] [udh:0:]
[boxid:vmIndia] [meta-data:]
2014-06-30 12:12:48 Sent SMS [SMSC:smpp_g2] [SVC:xxxxx] [ACT:smpp]
[BINF:] [from:tester] [to:1111111111] [FID:1914063012173074600]
[UUID:7079fab9-c8bf-4ee0-b607-6ece3bb82180] [flags:-1:0:-1:0:3]
[msg:158:test fall back] [udh:0:]
where smsc smpp_g1 if fails the message with NACK then it
should be retried with other smsc as in above case smpp_g2.
Bearerbox already provides the functionality for smppbox to
provided multiple smsc ";" separated.
but the problem is bbox sends messages to both gateway rather
than sending message to first gateway and in case of NACK it must
be retried with other gateway
You should do this on your application level. E.g. get status and
resend through other SMSC if there is NACK status.
Regards
On Saturday 28 June 2014 02:55 PM, spameden wrote:
2014-06-28 2:44 GMT+04:00 Ramesh G. Helaiya <ram...@routesms.in
<mailto:ram...@routesms.in>>:
Dear Team,
How can we implement Fall Back SMSC Option in bearerbox.
When one SMSC is rejecting the Message with NACK, the
message must be retried with other SMSC.
There is no such option here.
You can implement yourself a simple check via monit/nagios/zabbix
or any other monitoring system or simple bash script to switch
smsc via kannel's admin interface command by checking web
interface again if SMSC is still up.
e.g. you check with lynx http://localhost:13000/status page and
grep if smsc is still up if not, you just add needed smsc with:
lynx http://localhost:13000/add-smsc?smsc=XXX&password=XXXX
Regards,
RGH
