On Thursday 10 November 2005 12:22, Alexander Malysh wrote: > sorry but it seems we make workarounds for buggy SMSC. I'm -1 for this > patch. They must fix SMSC instead of adding some workarounds where those > don't belong to. Priority has _nothing_ todo with receiver and udh. > Instead SMSC devels should read spec properly (EMI 4.0, GSM 03.38, GSM > 03.40). There is not sign of catenated msgs ordering. > > And second thing: why in hell they try to reasseble the msg? it's a > handset job...
We had a similar problem with a client where the SMSC was assembling the message. We didn't have an ordering problem but there was a bug in one of the target handsets that caused it to crash when the SAR header was put before the NBS header, and the SMSC was rearranging the UDH IEs and causing the crash (which was initially blamed on us, of course :-). We never got them to stop doing that and the quoted reason is that they track SAR messages for billing purposes - they bill the user differently for SAR messages then for normal messages. -- Oded
