HI, SMPP CONNECTION CONFIG SETTINGS FOR TX & RX SEPARATELY.
###TX:: group=smsc smsc=smpp smsc-id=SMSC1 allowed-smsc-id=SMSC1 port = 9999 host = host.ip.address smsc-username = smppout smsc-password = smppout system-type = "" interface-version = 0x34 inquire-link-interval = 60 ###RX:: group=smsc smsc=smpp smsc-id=SMSC1 allowed-smsc-id=SMSC1 receive-port = 9999 host = host.ip.address smsc-username = smppout smsc-password = smppout system-type = "" interface-version = 0x34 inquire-link-interval = 60 *Rajeev Krishna* Operations Manager Krishnas Software Technologies www.krishnasoft.in mobile :+91 888 5815 888 Sales :+91 888 5813 888 Support :+91 888 5817 888 On Fri, Nov 7, 2014 at 6:44 PM, Pablo Gus <pablo...@gmail.com> wrote: > Thanks for the answers, > > Alvaro, every time when the error occurs the SMSC connections seem to be > UP and running (at least, there is no disconnection). We have 3 SMSC and > each one have a smsc-id and a allowed-smsc configuration like the following: > > group=smsc > smsc=smpp > smsc-id=SMSC1 > allowed-smsc-id=SMSC1 > ... [more config] > > group=smsc > smsc=smpp > smsc-id=SMSC2 > allowed-smsc-id=SMSC2 > ... [more config] > > group=smsc > smsc=smpp > smsc-id=SMSC3 > allowed-smsc-id=SMSC3 > ... [more config] > > So in this case I do not think it is a misconfiguration error because > there is no ambiguity with the allowed SMSCs, also when we send SMS to > kannel we always indicate a valid SMSC-ID. If you see some error here, > please let me know. > > Rajeev, do you have some example to configurate Rx and Tx separately? > > Also I checked the kannel page and I see that the 1.4.4 version is out. > May be this version has a fix for this bug that you mentioned with the > transceiver mode. Maybe we must go to 1.4.4 instead of 1.5.0. What do you > think about this? > > Thanks again! > > Regards, > Pablo. > > 2014-11-07 4:57 GMT-02:00 RK Krishnas <r...@krishnasoft.in>: > > Hi Every one, >> >> Problem may be you might have connected in transceiver mode. There is a >> bug we noticed that when ever there is a reconnection of single session in >> transceiver mode, the rx connects but the tx wont connect. So Initially try >> with tx & rx seperately. Let me know the working. >> We faced same issue for 3 months & solved it by 2 seperate sessions of tx >> & rx. >> >> >> >> *Rajeev Krishna* >> >> Operations Manager >> Krishnas Software Technologies >> www.krishnasoft.in >> mobile :+91 888 5815 888 >> Sales :+91 888 5813 888 >> Support :+91 888 5817 888 >> >> On Fri, Nov 7, 2014 at 2:17 AM, Alvaro Cornejo <cornejo.alv...@gmail.com> >> wrote: >> >>> Hi >>> >>> This usually means kannel does not find a smsc available to route the >>> sms to. >>> >>> - Check that your connections are all up and that they don't disconnect. >>> - Check that you sent the messages with the correct smsc-id. You might >>> have some messages routed a non existent route or have denied/allowed smsc >>> misconfigured >>> >>> Regards >>> >>> Alvaro >>> >>> >>> >>> >>> |-----------------------------------------------------------------------------------------------------------------| >>> Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier >>> celular y Nextel >>> en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via >>> SMS y GPRS online >>> Visitenos en www.perusms.com >>> >>> On Thu, Nov 6, 2014 at 2:43 PM, Pablo Gus <pablo...@gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> We are having some issues with Kannel v1.5.0. At some moment the >>>> application is not able to send more messages, it can receive but it can't >>>> send more SMS. >>>> >>>> Tracing some info in the log we can see the following behaviour: >>>> >>>> kannel.log >>>> >>>> 2014-11-06 14:22:13 [20038] [1] DEBUG: HTTP: Destroying HTTPClient for >>>> `127.0.0.1'. >>>> 2014-11-06 14:22:19 [20038] [14] DEBUG: send_msg: sending msg to box: >>>> <127.0.0.1> >>>> 2014-11-06 14:22:19 [20038] [14] DEBUG: boxc_sender: sent message to >>>> <127.0.0.1> >>>> 2014-11-06 14:22:19 [20038] [13] DEBUG: boxc_receiver: got ack >>>> 2014-11-06 14:22:19 [20038] [13] DEBUG: boxc_receiver: sms received >>>> 2014-11-06 14:22:19 [20038] [13] DEBUG: send_msg: sending msg to box: >>>> <127.0.0.1> >>>> 2014-11-06 14:22:19 [20038] [12] DEBUG: sms_router: handling message >>>> (0x7f4344001670 vs 0x7f4344001670) >>>> 2014-11-06 14:22:19 [20038] [12] DEBUG: Routing failed, re-queued. >>>> 2014-11-06 14:22:19 [20038] [12] DEBUG: sms_router: handling message >>>> (0x7f4344001670 vs 0x7f4344001670) >>>> 2014-11-06 14:22:19 [20038] [12] DEBUG: Routing failed, re-queued. >>>> 2014-11-06 14:22:19 [20038] [12] DEBUG: sms_router: time to sleep 30.00 >>>> secs. >>>> 2014-11-06 14:22:19 [20038] [12] DEBUG: sms_router: gwlist_len = 1 >>>> 2014-11-06 14:22:19 [20038] [12] DEBUG: sms_router: handling message >>>> (0x7f4344001670 vs 0x7f4344001670) >>>> 2014-11-06 14:22:19 [20038] [12] DEBUG: Routing failed, re-queued. >>>> 2014-11-06 14:22:19 [20038] [12] DEBUG: sms_router: handling message >>>> (0x7f4344001670 vs 0x7f4344001670) >>>> 2014-11-06 14:22:19 [20038] [12] DEBUG: Routing failed, re-queued. >>>> 2014-11-06 14:22:19 [20038] [12] DEBUG: sms_router: time to sleep 30.00 >>>> secs. >>>> >>>> sms-box.log >>>> >>>> 2014-11-06 14:22:19 [20091] [3] DEBUG: Stored UUID >>>> 5b62ad94-02ea-446e-8fa3-32a3cee3fc0e >>>> 2014-11-06 14:22:19 [20091] [3] DEBUG: message length 147, sending 1 >>>> messages >>>> 2014-11-06 14:22:19 [20091] [3] DEBUG: Status: 202 Answer: <Sent.> >>>> 2014-11-06 14:22:19 [20091] [3] DEBUG: Delayed reply - wait for >>>> bearerbox >>>> >>>> Since the moment in which kannel gives "routing failed" error, the >>>> send-sms service for a particular SMSC stops working and we must restart >>>> that SMSC to operate again correctly. >>>> >>>> I will appreciate any contribution to this issue. >>>> >>>> Thanks in advance. >>>> >>>> Regards, >>>> Pablo. >>>> >>> >>> >> > > > -- > Pablo Gus >
