Additional case, field ts in dlr table value will also the same as sql_id in sqlbox. The problem is when we send MT, the SMSC will expect the MT foreign-id should be match with the MO foreign-id (many telco do this, unless it is a bulk MT with no MO a.k.a push). And also when the DLR comes it will comes with the good foreign-id as the result Kannel will never found any. Please CMIIW. Thanks.
On Sep 12, 2013, at 9:57 AM, Willy Mularto <[email protected]> wrote: > Hi Rene, > I just review sqlbox_mysql.c and found something > > Msg *mysql_fetch_msg() > { > ... > msg->sms.foreign_id = octstr_null_create(row[0]); > … > } > > int mysql_fetch_msg_list(List *qlist, long limit) > { > … > msg->sms.foreign_id = octstr_null_create(row[0]); > … > } > > Confusing me, since foreign_id should be row[27] > > And after did POC I found if we insert our own foreign_id value then SQLBox > will over ride it with sql_id value. And the funny thing is binfo is also got > sql_id value Is it a bug? > > > > On Aug 22, 2013, at 5:20 PM, Rene Kluwen <[email protected]> wrote: > >> This is a request to all beloved sqlbox users. >> >> I am looking for experiences with the recently updated version (with >> multi-record selects). Is this an improvement? >> I want to know, especially if you are sending high volumes of traffic. >> >> Also I am looking for people that are willing to sponsor updating the other >> sqlbox drivers (postgres, mssql, oracle, etc.). >> >> == Rene >> >> >
