Re: splitting messages

"Jeetendra Singh" <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <04f101c3679e$6d625380$6f37a8c0@js>
The reference number should not be confused with message id. A same reference number in UDH of multiple short messages identify them as part of same long message, so in such a case you will have same reference number in all segments of a long message whereas every such segment shall be assigned a unique message id.

Also in this case, ETSI GSM Specs 3.40 clearly define that "Each concatenated short message contains a reference number which together with the originating address and Service Centre address allows the receiving entity to discriminate between concatenated short messages sent from different originating SMEs and/or SCs."

Also I couldnt understand what purpose it would solve to send op logo with different originators? 

-Jeetendra

----- Original Message ----- 
  From: DILWORTH MICHAEL 
  To: [email protected] 
  Sent: Wednesday, August 20, 2003 7:07 PM
  Subject: RE: splitting messages


  well there is a sort of message id inside the udh ..its the concatenated short message reference number ,.. there is no need to use the short number

  mike

  -----Original Message-----
  From: Konstantin Vayner [mailto:[email protected]]
  Sent: Wednesday, August 20, 2003 4:35 PM
  To: [email protected]
  Subject: Re: splitting messages


  of course smsc won't complain about it...
  every message for smsc is separate, it does not try to reassemble 
  messages , it just sends the parts which are actually totally separate 
  short messages;
  reassembling of messages is made on phone itself, and i am 99% sure that 
  what you are trying to do can't be done;
  phone just assumes it got first part of one thing and second part of 
  another thing; while the originators differ it would mean that two 
  different originators sent their messages, though none of them delivered 
  both parts;
  that is because there is actually no message id inside the udh...

  So, theoretically, [i did not try this actually] one would be able to 
  send two operator logos to one phone and (with some unpredictable delays 
  that happen during delivery) get both logos broken (mixed) on the phone...

  DILWORTH MICHAEL wrote:

  >hi
  >
  >the phones tested on are 7650 and 3650 and 7110 none work. yes the SMSCs and kannel all say it went ok.. but the phone doesnt get it.
  >
  >:(
  >
  >mike
  >-----Original Message-----
  >From: Stipe Tolj [mailto:[email protected]]
  >Sent: Wednesday, August 20, 2003 4:16 PM
  >To: DILWORTH MICHAEL
  >Cc: [email protected]
  >Subject: Re: splitting messages
  >
  >
  >  
  >
  >>I have a little issue here I hope someone can shed some light on.
  >>
  >>what i want to do is to split a binary message (operator logo) and
  >>send it to a mobile.  simple..yes, but i want to sent it using 2
  >>different froms. it doesnt seem to work.  it works ok if i use the
  >>same from.
  >>
  >>Please find here the sample (nokia operator logo with udh ) and my
  >>debugs.  sorry its quite long
  >>    
  >>
  >
  >seeing your SMPP PDUs at least the SMSC does not complain about it,
  >right?!
  >
  >So it's the phone that actually does not accept an concatenated SMS
  >from different source addresses.
  >
  >It is subject that the phone may use the source address as identifying
  >qualifier when re-assembling the message on the device.
  >
  >I never tried to send concatenated messages with different source
  >addresses, but I would suppose that it is the phone that breaks the
  >acceptance here.
  >
  >Stipe
  >
  >[email protected]
  >-------------------------------------------------------------------
  >Wapme Systems AG
  >
  >Vogelsanger Weg 80
  >40470 Düsseldorf
  >
  >Tel: +49-211-74845-0
  >Fax: +49-211-74845-299
  >
  >E-Mail: [email protected]
  >Internet: http://www.wapme-systems.de
  >-------------------------------------------------------------------
  >wapme.net - wherever you are
  >
  >
  >  
  >
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.