NO, there is NOT such functionality, Reason: it has to be implemented at the SMSC side ...
I refer the following scheme kannel_receives_MO -> sql_injection_with_Rule_on_insert -> sql_inject_MT_with_same_MO_Unique_id -> \ kannel_sends_MT_with_DLR_id_equal_to_Unique_id -> kannel_receives_ACK/DLR then kannel_receives_MO_REPLY -> sql_injection_with_Rule_on_insert in fact the Rule_on_Insert does the trick, it performs checks on the incoming MO content, for specific rules, like: 1. existence of previously received MO from the same MSISDN to the same shortcode with particular text, 2. existence of previously sent MT with positive DLR status with particular text, 3. additional rules per service description as time periods limiting the response timeout. we pre define the services in SQL arrays and rules on insert_update, used by sqlbox, its possible for PostgreSQL and Oracle. -----Original Message----- From: [] Sent: 21 Юли 2008 г. To: seik Subject:Message ID > 2008/7/21 seik <[EMAIL PROTECTED]>: >> use the MO kannel_ID, or create your OWN unique ID as unique DLR id for each >> MT. >> >> then its simple sql to match them >> >> in case you use sqlbox and pgsql/oracle it is not so complicated task, >> dont know for sqlbox backed by mysql >> >> we went a bit further and patched the sqlbox in a view to inject some >> additional data >> like our unique ID in a view to match MT-MO traffic and to control the MT/MO >> ratio > Ok, I admit I've never used sqlbox > From what you have written, the MT messages sent from Kannel should be > marked with a unique > DLR id, sent to the SMSC and delivered to the subscriber. When the > subscriber sends reply MO > message, the SMSC attaches the same unique ID and sends the data to > Kannel. Right? > What additional data is sent to the SMSC for this purpose? > Some SMPP optional parameters? > BR, Jovan
