how to SMS que management
hi i am using kannel 1.4.3.i asking few question as given below: 1) how to manage the que using kannel.if any parametrs required ?? 2) how many sms traffix will be supported by kannel. 3) how to improve performance of kannel.
[no subject]
hi i am using kannel 1.4.3.i asking few question as given below: 1) how to manage the que using kannel.if any parametrs required ?? 2) how many sms traffix will be supported by kannel. 3) how to improve performance of kannel.
Re: Not ACKed message !
So how do you run them? 3 different bearerboxes connected to the same smsc with the same credentials? No wonder it doesn't work. What are you trying to do? BR, Nikos - Original Message - From: Mohammed Saleem To: Nikos Balkanas Cc: users@kannel.org Sent: Saturday, November 27, 2010 8:37 PM Subject: Re: Not ACKed message ! Hi Nikos, Here is my conf file for the SMPP conn # # XXX SMPP Connection Configurations # group=smsc smsc=smpp smsc-id=XXX allowed-smsc-id=XXX preferred-smsc-id=XXX log-file="/storage01/instance01/log/xxx01.log" log-level=0 reconnect-delay=5 max-sms-octets=140 # # SMPP Specific Variables # host=10.20.20.101 port=31110 # 0x02 - just carry on waiting (given that the wait-ack should never expire this is the must accurate) # A message is resent if the acknowledge from SMSC takes more than this time. Defaults to 60 seconds. transceiver-mode=true receive-port=0 smsc-username=** smsc-password=** system-type=SMPP service-type=1 interface-version="34" enquire-link-interval=58 source-addr-ton=0 source-addr-npi=5 source-addr-autodetect=no dest-addr-ton=1 dest-addr-npi=1 bind-addr-ton=1 bind-addr-npi=1 msg-id-type=0 connection-timeout=300 validityperiod=1440 I have also another 2 files with the same configurations, with only a difference in the log file, so total are three connections with the same smsc-id Thanks in advance :) Best Regards, Mohammed M I Sleem http://www.abusleem.net http://www.freakle.com - The Search Freak http://www.colorle.com - color your Google search 2010/11/27 Nikos Balkanas Hi, Please post your configuration. BR, Nikos - Original Message - From: Mohammed Saleem To: users@kannel.org Sent: Saturday, November 27, 2010 7:15 PM Subject: Not ACKed message ! Dear Kannelers I had a not ACKed MT 2010-11-27 13:03:35 [6563] [17] WARNING: SMPP[SMSCID_XX]: Not ACKED message found, will retransmit. SENT<103>sec. ago, SEQ<124720>, Ξ’ DST<+> I know this is normal, but I have 2 questions: (1) How can I know the reason why the message wan't ACKed? (2) How can I prevent bb from resending the MT? I have configured the SMSC connection to connect/reconnect when a message is not ACKed: # wait-ack-expire: Defines what kind of action should be taken if the ack of a message expires. The options for this value are: # 0x00 - disconnect/reconnect (default)Ξ’ # 0x01 - as is now, re-queue, but this could potentially result in the msg arriving twice # 0x02 - just carry on waiting (given that the wait-ack should never expire this is the must accurate) I haven't configured the wait-ack-expire so the default action is to connect/reconnect, I am not sure if this variables covers my case NOTE: sometimes when I get this WARNING another WARNING follows it tells that the SMPP is sending wring sequence number NOTE: I have balanced connection (3 connections) configured in kannel that have the same smsc-id Any opinion would be highly appreciated, thanks Best Regards, Mohammed M I Sleem http://www.abusleem.net http://www.freakle.com - The Search Freak http://www.colorle.com - color your Google search
Bearerbox DEBUG mode logs
Hi, I seem to be unable to get the DEBUG logs from bearerbox in any file, although I have set the log level to be 0 in the config files. The command I use to start services is: bearerbox -v 0 -D "/usr/smsc/logs" -F "/usr/smsc/logs/bbox-debug.log" -V 0 /usr/smsc/config/bbox.conf However, bbox-debug.log does not contain anything other than initial INFO level messages at the start of bearerbox. Can someone help me out as how to get the bearerbox logs? Regards, Hamza
Re: Not ACKed message !
Hi Nikos, Here is my conf file for the SMPP conn # # XXX SMPP Connection Configurations # group=smsc smsc=smpp smsc-id=XXX allowed-smsc-id=XXX preferred-smsc-id=XXX log-file="/storage01/instance01/log/xxx01.log" log-level=0 reconnect-delay=5 max-sms-octets=140 # # SMPP Specific Variables # host=10.20.20.101 port=31110 # 0x02 - just carry on waiting (given that the wait-ack should never expire this is the must accurate) # A message is resent if the acknowledge from SMSC takes more than this time. Defaults to 60 seconds. transceiver-mode=true receive-port=0 smsc-username=** smsc-password=** system-type=SMPP service-type=1 interface-version="34" enquire-link-interval=58 source-addr-ton=0 source-addr-npi=5 source-addr-autodetect=no dest-addr-ton=1 dest-addr-npi=1 bind-addr-ton=1 bind-addr-npi=1 msg-id-type=0 connection-timeout=300 validityperiod=1440 I have also another 2 files with the same configurations, with only a difference in the log file, so total are three connections with the same smsc-id Thanks in advance :) Best Regards, Mohammed M I Sleem http://www.abusleem.net http://www.freakle.com - The Search Freak http://www.colorle.com - color your Google search 2010/11/27 Nikos Balkanas > Hi, > > Please post your configuration. > > BR, > Nikos > - Original Message - From: Mohammed Saleem > To: users@kannel.org > Sent: Saturday, November 27, 2010 7:15 PM > Subject: Not ACKed message ! > > > > > Dear Kannelers > > I had a not ACKed MT > > 2010-11-27 13:03:35 [6563] [17] WARNING: SMPP[SMSCID_XX]: Not ACKED message > found, will retransmit. SENT<103>sec. ago, SEQ<124720>, > Β DST<+> > > > > I know this is normal, but I have 2 questions: > > (1) How can I know the reason why the message wan't ACKed? > > (2) How can I prevent bb from resending the MT? I have configured the SMSC > connection to connect/reconnect when a message is not ACKed: > > # wait-ack-expire: Defines what kind of action should be taken if the ack > of a message expires. The options for this value are: > # 0x00 - disconnect/reconnect (default)Β > > # 0x01 - as is now, re-queue, but this could potentially result in the msg > arriving twice > # 0x02 - just carry on waiting (given that the wait-ack should never expire > this is the must accurate) > > I haven't configured the wait-ack-expire so the default action is to > connect/reconnect, I am not sure if this variables covers my case > > NOTE: sometimes when I get this WARNING another WARNING follows it tells > that the SMPP is sending wring sequence number > NOTE: I have balanced connection (3 connections) configured in kannel that > have the same smsc-id > > > Any opinion would be highly appreciated, thanks > > > > > > > > Best Regards, > Mohammed M I Sleem > http://www.abusleem.net > > http://www.freakle.com - The Search Freak > > http://www.colorle.com - color your Google search >
Re: Not ACKed message !
Hi, Please post your configuration. BR, Nikos - Original Message - From: Mohammed Saleem To: users@kannel.org Sent: Saturday, November 27, 2010 7:15 PM Subject: Not ACKed message ! Dear Kannelers I had a not ACKed MT 2010-11-27 13:03:35 [6563] [17] WARNING: SMPP[SMSCID_XX]: Not ACKED message found, will retransmit. SENT<103>sec. ago, SEQ<124720>, Β DST<+> I know this is normal, but I have 2 questions: (1) How can I know the reason why the message wan't ACKed? (2) How can I prevent bb from resending the MT? I have configured the SMSC connection to connect/reconnect when a message is not ACKed: # wait-ack-expire: Defines what kind of action should be taken if the ack of a message expires. The options for this value are: # 0x00 - disconnect/reconnect (default)Β # 0x01 - as is now, re-queue, but this could potentially result in the msg arriving twice # 0x02 - just carry on waiting (given that the wait-ack should never expire this is the must accurate) I haven't configured the wait-ack-expire so the default action is to connect/reconnect, I am not sure if this variables covers my case NOTE: sometimes when I get this WARNING another WARNING follows it tells that the SMPP is sending wring sequence number NOTE: I have balanced connection (3 connections) configured in kannel that have the same smsc-id Any opinion would be highly appreciated, thanks Best Regards, Mohammed M I Sleem http://www.abusleem.net http://www.freakle.com - The Search Freak http://www.colorle.com - color your Google search
Not ACKed message !
Dear Kannelers I had a not ACKed MT 2010-11-27 13:03:35 [6563] [17] WARNING: SMPP[SMSCID_XX]: Not ACKED message found, will retransmit. SENT<103>sec. ago, SEQ<124720>, DST<+> I know this is normal, but I have 2 questions: (1) How can I know the reason why the message wan't ACKed? (2) How can I prevent bb from resending the MT? I have configured the SMSC connection to connect/reconnect when a message is not ACKed: # wait-ack-expire: Defines what kind of action should be taken if the ack of a message expires. The options for this value are: # 0x00 - disconnect/reconnect (default) # 0x01 - as is now, re-queue, but this could potentially result in the msg arriving twice # 0x02 - just carry on waiting (given that the wait-ack should never expire this is the must accurate) I haven't configured the *wait-ack-expire* so the default action is to connect/reconnect, I am not sure if this variables covers my case NOTE: sometimes when I get this WARNING another WARNING follows it tells that the SMPP is sending wring sequence number NOTE: I have balanced connection (3 connections) configured in kannel that have the same smsc-id Any opinion would be highly appreciated, thanks Best Regards, Mohammed M I Sleem http://www.abusleem.net http://www.freakle.com - The Search Freak http://www.colorle.com - color your Google search
