Hi
If I do remember well, kannel uses a combination of ts, destination and
smsc to search for the dlr.
You might want to check code to be sure.
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, Jun 25, 2015 at 4:48 PM, Michael Epstein <mepst...@callfire.com>
wrote:
> Hi Alvaro,
>
> Thanks for the quick informative reply.
>
> this is the table in question:
>
> KANNEL [kannel] ON kannel> describe dlr;
>
> +-------------+--------------+------+-----+-------------------+-----------------------------+
> | Field | Type | Null | Key | Default |
> Extra |
>
> +-------------+--------------+------+-----+-------------------+-----------------------------+
> | dt | timestamp | NO | MUL | CURRENT_TIMESTAMP | on update
> CURRENT_TIMESTAMP |
> | smsc | varchar(40) | YES | MUL | NULL
> | |
> | ts | varchar(40) | YES | | NULL
> | |
> | destination | varchar(40) | YES | | NULL
> | |
> | source | varchar(40) | YES | | NULL
> | |
> | service | varchar(40) | YES | | NULL
> | |
> | url | varchar(255) | YES | | NULL
> | |
> | mask | int(10) | YES | | NULL
> | |
> | status | int(10) | YES | | NULL
> | |
> | boxc | varchar(40) | YES | | NULL
> | |
>
> +-------------+--------------+------+-----+-------------------+-----------------------------+
> 10 rows in set (0.01 sec)
>
> the insert is logged as:
>
> sql: INSERT INTO `dlr` (`smsc`, `ts`, `source`, `destination`, `service`,
> `url`, `mask`, `boxc`, `status`) VALUES (?, ?, ?, ?, ?, ?, ?, ?, 0)
>
> I don't see an explicit key.
>
> is there some sort compound key based on the smsc, ts, source and
> destination?
>
> We actually have two dbs one for each instance now but it is causing
> problems when a DLRs are sent back from a particular carrier to the wrong
> bind. So this is a work around.
>
> I am thinking it will be ok as long as the clocks are in sync since the ts
> is needed.
>
> Thanks again,
> Mike
>
>
> On 6/25/15 2:27 PM, Alvaro Cornejo wrote:
>
> Hi
>
> Yes as long as you have enough connections and HW capacity.
>
> Entries on each record will have it own key id set therefore it is
> pretty unlikely you will have different kannel instance share the same id
> set keys.
>
> The drown back will be that both instances will need to read all the
> table for checking dlrs. You can however use same database but different
> tables for each kannel instance.
>
> 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, Jun 25, 2015 at 3:12 PM, Michael Epstein <mepst...@callfire.com>
> wrote:
>
>> Hi Everyone,
>>
>> I was wondering if multiple kannel instances on different hosts can share
>> a mysql database for DLR storage?
>>
>> Any help would be greatly appreciated.
>>
>> Thanks,
>> Mike
>>
>>
>
>
