Parse the xser field and check for the udh type of service (01). Then
look in the udh data
for catenated message identifier (00)...
/Christian
Bruno David Rodrigues wrote:
I think we should catenate them in smsc_* code as we want to move
the splitting from smsbox to smsc_* too.
BTW: in emi2,
I've asked for permission to use Zellsoft's premises (Copenhagen) and
got it (It's not a lot of space, but at least it is free..). I guess we
have place for 10-20 people. (How many active developers are there?). If
someone has an alternative, I am very open...
- persons who would like to
- important items to be discussed.
- Releases of kannel.
I you watch the users mailing list, you know that a lot of people is
still using the 1.0.3 version, not knowing the state it is in. A lot of
bugs have been found in this version, but was never corrected. Actually,
I think everybody
You have have to do this in each protocol implementation or what?? - I
don't like this. I don't
see why this have to be done like that. No matter what character set an
smsc is using, a message should be no more than 160 septets gsm encoded.
Then you could convert to the relevant characterset
