Yes - saw that..
That's the consolation prize.. :)
 
I need to strip off the extra stuff and I'll have the hex message_id. Any ideas out there on the quickest way to do that? ;)
 
 
----- Original Message -----
Sent: Thursday, June 26, 2003 6:39 PM
Subject: [-] Re: non standard message_id breaks DLR


On Donnerstag, Juni 26, 2003, at 06:40 Uhr, Alexander Malysh wrote:

Hi Nisan,

I believe, you have not undestand the issue...
Very long is not a problem for kannel, the problem is, that message_id
received in submit_sm is not the same as in delivery receipt later. Just look
this example:
submit_sm -> submit_sm_resp -> msg_id = 02/00/b9637bb4/11353872920997
but in delivery receipt:
message_id = 3110304692

This is definit. not allowed! Because message id in delivery receipt is only
the part of message id from submit_sm_resp. You can't convert it in any form
generic for all SMSCs.

the id b9637bb4 is the hex value of 3110304692. Did you notice that?


Andreas Fink
Global Networks Switzerland AG

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

Reply via email to