Alexander Malysh wrote:
Hi,
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.
yep, agree'ing here to Alex's position. Mainly this was because of my +0 voting.
Actually it may be more -0 ;)
@Enver: can you please check what vendor this specific EMI SMSC is? If it is a
non standard vendor, hence, home-brewed, then you should force them to obey the
specs.
We really don't want to add workarrounds for bugs of other people's software,
that's why specs are for.
Sounds drastic, but it has to be programatic, otherwise we're the one to blame,
since we do everything, but not the clean words of the spec.
I didn't find any specific things regarding ordering of concatenated (hence udh
included) messages in EMI. If you can state that this is an anomaly of Kannel,
we'll fix it.
Stipe
mailto:stolj_{at}_wapme-group.de
-------------------------------------------------------------------
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
-------------------------------------------------------------------
