Hi there.
The application will operate as a gateway between a number of different
SMSCs of different operators for both MO and MT.
I would expect to have a msg-id in every incoming (to the application) SMS
as well as some msg-id clashes.
I'd like to create a DB (probably either Oracle or Postgres) for storage and
for statistics and would then need a two-way access: one with (really)
unique IDs to the application and one with SMSC-related IDs.
If I could unify the IDs with a unique numbering, I would then get an
advance in my architecture.
I hope I've been clearer as I'm not English native speaker.

2008/9/8 Christian Jensen <[EMAIL PROTECTED]>

>  What will you do with the id once you get it? Describe your scenario
> better.
>
> ------------------------------
> From: regme please <[EMAIL PROTECTED]>
> Sent: September 8, 2008 7:57 AM
> To: Alejandro Guerrieri <[EMAIL PROTECTED]>
> Cc: [email protected] <[email protected]>
> Subject: Re: Trivial (maybe) questions
>
>  Hi,
> I have been unclear, I presume.
> I mean, isn't there any msg-id when I receive an SMS from an external SMSC
> (a real one I mean)?
> Who is in charge for creating such an ID in a complete chain (handlset,
> MSC, SMSC, gateway and the way back)?
> How is this ID handled in respect to all other message entities' IDs?
>
> I have not enough background on the technicalities of 2G/3G and some
> reference for study would also be greatly appreciated.
>
> Muchas gracias. :-)
>
> 2008/9/8 Alejandro Guerrieri <[EMAIL PROTECTED]>
>
>> The message-id's are created from an uuid implementation (system function
>> that creates unique id's based on a microsecond timestamp and some random
>> factors to achieve uniqueness).
>>
>> Afaik, there's no way to re-define it without patching the code.
>>
>> Hope it helps,
>>
>> Alex
>>
>>
>> On Mon, Sep 8, 2008 at 11:29 AM, regme please <[EMAIL PROTECTED]>wrote:
>>
>>> Who is in charge for assigning a message-ID to each SMS?
>>> Am I allowed in Kannel to somehow re-define it?
>>>
>>> Thanks for the patience.
>>>
>>> RMP.
>>>
>>
>>
>

Reply via email to