Hi, Wow! I think I see some looping going on here...
Where is your message originating from? MO or MT? Assuming MT originating on Box 2. It is sending a URL to bearerbox port 13125 where http SMSc is listening for SMS clients. That is SMS clients, not HTTP clients. Are you sure that this does what you think it does? Let's assume that this works. Then you try a push from BOX1 to BOX2. Don't you need to pass some parameters in the URL? Like SMS, from, to, meta-data? If you did and assume that you kept your somekeyword around, it would propably sent right back to BOX 1 and so on... I am sure this is not what you want to do, so why don't you tell us about it? BR, Nikos ----- Original Message ----- From: Ishtiaq Ahmed To: [email protected] Sent: Thursday, February 12, 2009 5:43 PM Subject: Kannel to Kannel Meta-Data problem hi Guyz, Been working over the forwarding of the SMS from one Kannel to another Kannel, using the kannel http smsc .... here are the configs KANNEL BOX 1 group = smsc smsc = http smsc-id = SomeNetwork system-type = kannel smsc-username = ooober smsc-password = ooober send-url = "http://KANNELBOX2:13131/cgi-bin/sendsms"; connect-allow-ip = *.*.*.* port = 13125 allowed-smsc-id = SomeNetwork group = sms-service keyword-regex = somekeyword max-messages = 0 accepted-smsc= SomeNetwork get-url = "http://SERVER:8080/applicationcontext/receivemsg.htm?sender=%p&text=%a&shortcode=%P&operatorId=%o&price=%O&smscid=%i&meta-data=%D"; KANNEL BOX 2 group = sms-service keyword-regex = somekeyword max-messages = 0 #GET URL to send messages to APPLICATION get-url = "http://KANNELBOX1:13125/sms?username=ooober&password=ooober&from=%p&to=%P&text=%a&meta-data=%D"; accepted-smsc = SomeNetwork Everything is fine.... But Kannel Box 1 while sending the message to SERVER does not send meta-data tag with it.... %D has no value... Regards, Ishtiaq Ahmed
