Re[2]: smpp dlr problem

Jury Cherepanov <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Organization HighTech
Message-ID <[email protected]>
Hello Andreas,

Tuesday, May 06, 2003, 7:56:43 PM, you wrote:


AF> On Dienstag, Mai 6, 2003, at 06:07  Uhr, Andrea Viscovich wrote:

>>> Thinking that DLR is based on "message_id" reply contents must include
>>> Message ID, but in your way sms service provider make response with
>>> out any standart contents of message_id, that your problem this
>>> message_id field, make full dump of recieved PDU.
>>
>> Hi Juri,
>> I don't undesrtand.
>> thre message_id field is the ts field:
>> creating the dlr I have:
>> Adding DLR smsc=SMPP:xxx.xxx.xxx.xxx:2775/2775:futuress:VMA, 
>> ts=2976249,
>> src=Visco, dst=+39347zzzzzzz, mask=31, boxc=smsboxA
>>
>> Searching the dlr 20 min after i got:
>> Looking for DLR smsc=SMPP:xxx.xxx.xxx.xxx:2775/2775:futuress:VMA,
>> ts=0002976249, dst=Visco, type=1
>>
>> the ts is the same or 0002976249<>2976249?

AF> this is NOT the same. Its alphanumeric in some cases.
>>
AF> Andreas Fink
AF> Global Networks Switzerland AG

AF> ------------------------------------------------------------------
AF> Tel: +41-61-6666333  Fax: +41-61-6666334   Mobile: +41-79-2457333
AF> Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland
AF> Web: http://www.global-networks.ch/      [email protected]
AF> ------------------------------------------------------------------

In starting there was message_id = NULL. And error was unable find
with message_id.

There may be some or with exchange numbers (src <=> dest) or some with
alphanumeric search in dlr storrage.



---------------------------------------------------------
Jury Cherepanov
System Developer (Technical Director) , HIGH TECHNOLOGIES
Turaidas 2a, Riga, Latvia
Phone +371-9633398
mailto:[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.