Re: non standard message_id breaks DLR

On Thursday 26 June 2003 18:05, David Tully wrote: > Hi! > > > The middle bit of the submit_sm_resp is the message_id - 'b9637bb4' out of > '02/00/b9637bb4/11353872920997' > The rest is junk - the last number is the destination number. Interesting, I've just noticed that I get a similar problem wi

MMS notification --nokia

Hi, SI can be delivered to Nokia6650. But MMS notification can't be recognised by Nokia6650.Two short messages are used for one MMS notification. First short message: --SMPP header 00bd 0004 000f 0002 0134 3530 0001 0138 3631 3338 3035 3534 3030 3033 0043 0400

Re: [-] Re: non standard message_id breaks DLR

On Donnerstag, Juni 26, 2003, at 11:30 Uhr, David Tully wrote: 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? ;)     ask your SMPP link supplier to conform to the SMPP

Re: [-] Re: non standard message_id breaks DLR

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 - From: Andreas Fink To: Alexander Malysh Cc: [EMAIL PROTECTED] S

Re: non standard message_id breaks DLR

Am Donnerstag, 26. Juni 2003 19:39 schrieb Andreas Fink: > 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 i

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: submi

Re: non standard message_id breaks DLR

hi At 06:40 PM 6/26/03 +0200, Alexander Malysh wrote: Hi Nisan, I believe, you have not undestand the issue... yes, sorry.. my patch is for another message_id issue. I have seen this same behaviour, allthough the provider failed many of our other tests, so never made it to actual live usage N

Re: non standard message_id breaks DLR

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/1135387292099

Re: non standard message_id breaks DLR

Hi At 01:12 PM 6/26/03 +0200, Alexander Malysh wrote: Hi David, strange... I have not never seen such message_id! One think i can say, SMSC is s we have.. (No provider names mentioned) and yes they are real flaky..Although this is a valid msg_id albeit very long. NULTERMINATED(message_id

Re: non standard message_id breaks DLR

Alexander Malysh wrote: > > Hi David, > > strange... > > I have not never seen such message_id! One think i can say, SMSC is s > buggy! It's not allowed to get one message id in submit_sm_resp and another > one or part of them in delivery receipt. I would propose, you contact your > operator

Re: non standard message_id breaks DLR

Hi David, strange... I have not never seen such message_id! One think i can say, SMSC is s buggy! It's not allowed to get one message id in submit_sm_resp and another one or part of them in delivery receipt. I would propose, you contact your operator and give him a hint to look in SMPP spe

non standard message_id breaks DLR

Hi! I'm getting back a strange (non-standard?) message_id in submit_sm_resp Alexander - sorry for assuming it was a DLR problem! :) 2003-06-25 12:31:56 [6] DEBUG: type_name: submit_sm_resp 2003-06-25 12:31:56 [6] DEBUG: command_id: 2147483652 = 0x8004 2003-06-25 12:31:56 [6] DEBUG: co