----- Original Message ----- From: "Bruno David Rodrigues" <[EMAIL PROTECTED]> To: "Tim Kehres" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, January 14, 2002 3:49 AM Subject: Re: Doing things easier - discussion
> > I might be very well missing a few basic things here as I'm just getting > > familiar with the code and operations, however, from my preliminary tests, > > it would seem that while messages are indeed split, they are not done in a > > way that makes it possible for the MS to be able to automatically > > re-assemble the original message. Is this the intent in the code, or am > I > > doing something wrong here? In the meantime I'll continue to dig though > > the code to better understand how the headers are constructed and used.... > > :-) :-) > > If you say concatenation=1 and max-messages=4 (or something else), kannel > will > split the message and add the correct udh concatenation field, so the mobile > will > recover the full message. Yeah, I found the problem on this end. For starters, I was using the 1.03 code, which appears to be broken in this regard (at least on my RedHat 7.1 environment). In addition, I took the User Guide (1.03) a bit too literally and repeated the misspelling (concetenation) on page 47, which of course the code would not deal with. I believe that this is fixed in the current documents. Also things work well once I ran the 1.1.5 code. :-) > But that depends on the mobile. Nokia 6210 always say "message 1/n", > ericsson > T39 and nokia 9210, for example, could join the 4 splitted messages in one As not all the Nokia phones will do reassembly (8250 for example), I'm using an older 3310 for this purpose. One thing that I did notice however is that if I receive long (concatenated) messages from another Nokia phone (say another 3310), I get only one indication of a new message. With Kannel, I'll get a separate notification for each component. If I'm reading the first segment when the next one comes in, the phone notifies me that it is appending to the message. While in the end, all works well, the experience by the mobile user is different. Any ideas on why this might be? Thanks and Best Regards, -- Tim
