yes unique dlr-url per MT message NOTE: the your request bellow is wrong
the request to the cgi-bin/send-sms should be as usual , just the value of the dlr-rul should be urlencoded unique dlrurl ... fixed request based on the one bellow http://147.120.203.99:17018/cgi-bin/sendsms?username=a&password=a&to=67436&from=990&text=test+msg&dlr-mask=31&mclass=0&dlr-url=http%3A%2F%2Flocalhost%2Fdlr.pgsql.php%3FsmscID%3D%25i%26dlr%3D%25d%26answer%3D%25A%26to%3D%25p%26from%3D%25P%26ts%3D%25T%26smsID%3D07fceb25372fcc4cb847c7099008500e%26charset%3D%25C%26kannel_id%3D%25I"; -----Original Message----- From: Tharanga [EMAIL PROTECTED] Sent: 11 ??? 2008 ?. To: seik Subject:smsc message ID > Hi seik, > iam having the same problem. actually what u mean by unique dlr-url per > message ? > is it means when i sending i need to use a uniquq url for every message. > http://147.120.203.99:17018/cgi-bin/sendsms?username=a&password=a&to=67436&f > rom=990&text=test msg&dlr-mask=31&mclass=0&smsID=345677" > many thanks, > Tharanga > ----- Original Message ----- > From: "seik" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Tuesday, June 10, 2008 1:20 AM > Subject: Re: smsc message ID >> you do not need the smsc id >> >> all you need is to set YOUR unique dlr-url per MT message >> >> to achieve that, add in the dlr-url something like >> >> MysmsID=6be1268d3d7d99e6ec99e9138e77d6ea >> make sure the value of the MysmsID sould is unique >> and use it to trace the status of the MT message. >> >> the db based dlr queue has nothing to do with the delivery reports per > message ... >> it just saves the queue in a db, to avoid loss of data in case of OS crash > ... >> >> example of dlr-url: >> > "http://localhost/dlr.pgsql.php?smscID=%i&dlr=%d&answer=%A&to=%p&from=%P&ts= > %T&smsID=07fceb25372fcc4cb847c7099008500e&charset=%C&kannel_id=%I" >> >> resulting dlr-url: >> >> 127.0.0.1 - - [09/Jun/2008:22:45:37 +0300] "GET > /dlr.pgsql.php?smscID=mtel&dlr=8&answer=ACK%2F&to=%2B359111111111&from=1916& > ts=1213040737&smsID=nonfd9c1ff6b66bc510c785ffac6fb0b754&charset=ISO-8859-1&k > annel_id=a890dfe9-72a9-48db-b98d-cd7c533c5958 HTTP/1.1" 200 1 "-" > "Kannel/cvs-20070627" >> 127.0.0.1 - - [09/Jun/2008:22:45:45 +0300] "GET > /dlr.pgsql.php?smscID=mtel&dlr=1&answer=id%3A0302419579+sub%3A001+dlvrd%3A00 > 1+submit+date%3A0806092245+done+date%3A0806092245+stat%3ADELIVRD+err%3A000+t > ext%3ABlagodarim+Vi+za+Vas&to=%2B359111111111&from=1916&ts=1213040745&smsID= > nonfd9c1ff6b66bc510c785ffac6fb0b754&charset=ISO-8859-1&kannel_id=41e9cd46-90 > ad-4014-b08f-91d152fd0388 HTTP/1.1" 200 1 "-" "Kannel/cvs-20070627" >> >> i think you will deal from here >> >> >> >> >> -----Original Message----- >> From: [email protected] [EMAIL PROTECTED] >> Sent: 09 ??? 2008 ?. >> To: seik >> Subject:smsc message ID >> >> > Hello everybody, >> >> >> > I am currently working on getting delivery receipts on my dlr-url. >> >> > When I query the sendsms cgi-bin interface : >> > > http://localhost/cgi-bin/sendsms?user=username&pass=password&from=xxxxxxx&to > =xxxxxxxxxxx&smsc=mysmsc&text=some+text&mclass=1&dlr-mask=31&dlr-url=http%3A > %2F%2Flocalhost%2Fdlr.php%3Fid%3DArdn6lE4%26state%3D%25d%26smsid%3D%25I >> >> > dlr-url looking like that: >> >> > http://localhost/dlr.php?id=Ardn6l&state=%d&smsid=%I >> >> > The %I only gives me the "internal" message ID kannel generated. >> >> > I would like the actual (aggregator) smsc message ID >> >> > On a side not, I am using a pgsql dlr queue, and I can see my message ID >> > being stored into the ts (timestamp) field. >> >> > Thank you for your help, >> >> > Eric >> >> >> >> >> >> >> >>
