Maybe I'm wrong, but it seems it is not storable in the DB! 2008/9/9 Alejandro Guerrieri <[EMAIL PROTECTED]>
> Wouldn't the smsc-id and internal message id suffice? > > > On Tue, Sep 9, 2008 at 12:09 PM, regme please <[EMAIL PROTECTED]>wrote: > >> Hi again. >> >> The point here is that in order to track messages coming from different >> sources, I'd need to know (that is store in the DB) the original msg-id >> along with the source. >> What I understand is that the original msg-id is "overwritten" with an >> internal one without the possibility to store it. >> Would please anyone there confirm this and provide any hint about this >> topic? >> >> Thanks. >> >> 2008/9/8 regme please <[EMAIL PROTECTED]> >> >> 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. >>>>> >>>> >>>> >>> >> >
