SEMA OISD Deliver SM issue

Dear all,

    I ran into trouble with a carrier using Sema SMSC Version G8.1 OIS 
v5.8. Actually this Sema SMSC is sending Deliver SM commands to Kannel 
containing more than one SM. As a result Kannel rejects this command and 
closes the connection to the SMSC

This is an example of a Deliver SM command containing four SMs that 
Kannel rejected.
2007-12-14 19:08:07 [8625] [23] INFO: OISD[sema] logged in.
2007-12-14 19:08:21 [8625] [23] ERROR: OISD[sema]: wrong packet
2007-12-14 19:08:21 [8625] [23] DEBUG: Octet string at 0x81ae3a8:
2007-12-14 19:08:21 [8625] [23] DEBUG:   len:  289
2007-12-14 19:08:21 [8625] [23] DEBUG:   size: 1024
2007-12-14 19:08:21 [8625] [23] DEBUG:   immutable: 0
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 44 b1 d5 28 00 09 37 00 
47 00 07 42 44 30 30 30   D..(..7.G..BD000
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 30 30 00 00 00 00 0d 39 
31 34 38 36 39 38 35 38   00.....914869858
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 32 32 35 31 00 00 02 0d 
0c 05 0a 03 00 06 04 62   2251...........b
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 30 17 0c 06 03 30 37 31 
32 31 34 31 34 33 37 33   0....07121414373
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 39 35 32 30 37 31 32 31 
34 31 34 33 37 33 39 35   9520712141437395
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 32 4c 40 4e 4f 00 09 00 
00 3c 00 07 42 44 30 30   2L@NO....<..BD00
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 30 30 30 b6 02 5f d3 0d 
39 31 34 38 36 36 38 39   000.._..91486689
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 39 31 30 38 33 00 00 00 
01 01 2b 30 37 31 32 31   91083.....+07121
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 34 31 34 34 31 34 33 35 
32 30 37 31 32 31 34 31   4144143520712141
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 34 34 31 34 33 35 32 47 
8c 45 a5 00 09 00 00 3b   4414352G.E.....;
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 00 07 42 44 30 30 30 30 
30 46 c7 63 4e 0d 39 31   ..BD00000F.cN.91
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 34 38 36 39 34 30 30 38 
39 33 34 00 00 00 00 00   48694008934.....
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 30 37 31 32 31 34 31 34 
33 37 33 34 35 32 30 37   0712141437345207
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 31 32 31 34 31 34 33 37 
33 34 35 32 42 c0 01 78   121414373452B..x
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 00 09 00 00 3b 00 07 42 
44 30 30 30 30 30 49 46   ....;..BD00000IF
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: fb 1b 0d 39 31 34 38 36 
36 30 36 38 30 32 32 38   ...9148660680228
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 00 00 00 00 00 30 37 31 
32 31 34 31 34 33 39 32   .....07121414392
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 38 35 32 30 37 31 32 31 
34 31 34 33 39 32 38 35   8520712141439285
2007-12-14 19:08:21 [8625] [23] DEBUG:   data: 
32                                                2
2007-12-14 19:08:21 [8625] [23] DEBUG: Octet string dump ends.

According to this carrier API specification the SMSC can open up to ten 
transactions to SME without waiting to receive a Deliver SM Result. Is 
Kannel SEMA OISD implemantation incompatible with this sort of operation?

Regards