Yes, I saw it in the debug log, thank you.
The only thing I did not know if it is generated by kannel or by an external 
smsc (Thank you Nikos).
To answer the question below: the same ids are coming from one smsc when there 
is huge amount of SMs sent to it.

Regarding to Nicos's answer the problem must be found at smsc side.

Thanks again guys!

Bye,
Gabor

-----Original Message-----
From: Nikos Balkanas [mailto:[email protected]] 
Sent: Thursday, March 11, 2010 6:26 AM
To: sangprabv
Cc: Maros Gabor EB_HU; [email protected]
Subject: Re: Duplicated FID (foreign_id)

Correction:

Kannel always searches DLR by SMSc, FID and MSISDN ;-)

BR,
Nikos
----- Original Message ----- 
From: "sangprabv" <[email protected]>
To: "Nikos Balkanas" <[email protected]>
Cc: "Gabor Maros" <[email protected]>; <[email protected]>
Sent: Thursday, March 11, 2010 3:10 AM
Subject: Re: Duplicated FID (foreign_id)


Does the duplicated FID happened on the same MSISDN? If not then it's not an 
issue, since Kannel always search DLR by MSISDN and FID.



sangprabv
[email protected]


On Mar 11, 2010, at 1:26 AM, Nikos Balkanas wrote:

> Hi,
>
> Each smsc is generating its own unique ID called foreign ID (FID). This 
> should be unique per SMSc according to the protocol. This is notified to 
> kannel in the submit_sm_resp PDU (assuming SMPP) sent by the SMSc and 
> kannel correlates that to its message id.
>
> For the different FID formats refer to message-type in User's Guide.
>
> BR,
> Nikos
> ----- Original Message ----- From: "Gabor Maros" 
> <[email protected]>
> To: <[email protected]>
> Sent: Wednesday, March 10, 2010 8:03 PM
> Subject: Duplicated FID (foreign_id)
>
>
>>
>> Hi,
>>
>> can anybody tell me how is FID generated or on which side.
>> I ask it because I have a problem: in access.log there are different
>> messages that have the same PIDs, and I need to know where I should 
>> search
>> the problem (on kannel side, or on my sms provider's side).
>>
>> Thanks!
>> -- 
>> View this message in context: 
>> http://old.nabble.com/Duplicated-FID-%28foreign_id%29-tp27853586p27853586.html
>> Sent from the Kannel - User mailing list archive at Nabble.com.
>>
>
>

____________________________________________________________________________________________________
Ez az e-mail és az összes hozzá tartozó csatolt melléklet titkos és/vagy 
jogilag, szakmailag vagy más módon védett információt tartalmazhat. Amennyiben 
nem Ön a levél címzettje akkor a levél tartalmának közlése, reprodukálása, 
másolása, vagy egyéb más úton történő terjesztése, felhasználása szigorúan 
tilos. Amennyiben tévedésből kapta meg ezt az üzenetet kérjük azonnal értesítse 
az üzenet küldőjét. Az Erste Bank Hungary Nyrt. (EBH) nem vállal felelősséget 
az információ teljes és pontos - címzett(ek)hez történő - eljuttatásáért, 
valamint semmilyen késésért, kapcsolat megszakadásból eredő hibáért, vagy az 
információ felhasználásából vagy annak megbízhatatlanságából eredő kárért.

Az üzenetek EBH-n kívüli küldője vagy címzettje tudomásul veszi és hozzájárul, 
hogy az üzenetekhez más banki alkalmazott is hozzáférhet az EBH folytonos 
munkamenetének biztosítása érdekében.


This e-mail and any attached files are confidential and/or covered by legal, 
professional or other privilege. If you are not the addressee, any disclosure, 
reproduction, copying, distribution, or other dissemination or use of this 
communication is strictly prohibited. If you have received this transmission in 
error please notify Erste Bank Hungary Nyrt. (EBH) immediately. EBH does not 
accept liability for the correct and complete transmission of the information, 
nor for any delay or interruption of the transmission, nor for damages arising 
from the use of or reliance on the information.

The sender or recipient of these messages agrees that they may be read by other 
EBH employees than the official recipient or sender in order to ensure the 
continuity of work-related activities and allow supervision thereof.

____________________________________________________________________________________________________


Reply via email to