Dear all,
I've ran into a couple of error from which I'm not sure if it's a bug or misuse from my side. I'm sending messages larger than 160 characters spanning 2 to 3 messages concatenated into 1 message. To make this work, I use these parameters: max-messages = 6 concatenation = true In general my messages went out without any problem but sometimes messages generated errors and they didn't arrive at the destination. These were the errors I encountered in the log file using a Siemens M20 (No Debug information unfortunately) 2008-06-13 16:51:37 [2926] [7] ERROR: AT2[/dev/ttyS0]: CMS ERROR: +CMS ERROR: 304 2008-06-13 16:51:37 [2926] [7] ERROR: AT2[/dev/ttyS0]: CMS ERROR: Invalid PDU mode parameter (304) 2008-06-13 16:51:38 [2926] [7] ERROR: AT2[/dev/ttyS0]: CMS ERROR: +CMS ERROR: 304 2008-06-13 16:51:38 [2926] [7] ERROR: AT2[/dev/ttyS0]: CMS ERROR: Invalid PDU mode parameter (304) 2008-06-13 16:51:38 [2926] [7] ERROR: AT2[/dev/ttyS0]: CMS ERROR: +CMS ERROR: 304 These ware the errors I encountered in the log file using a Siemens TC 63 2009-01-06 10:36:50 [19479] [9] DEBUG: boxc_receiver: sms received 2009-01-06 10:36:50 [19479] [9] DEBUG: new split_parts created 0x81b3710 2009-01-06 10:36:50 [19479] [9] DEBUG: send_msg: sending msg to box: <127.0.0.1> 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: TP-Validity-Period: 24.0 hours 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: --> AT+CMGS=69^M 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: <-- > 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: send command status: 1 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: --> 0051000B912394552107F00000A73F050003000202D8611D0C16B3C166B6DA0C26A3E514 0A6AB2D92A368B41DD382C67B F41F6B29CFC66A7ED611D0C3693D16E381A8E369BC5 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: --> ^Z 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: <-- > 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: <-- ERROR 2009-01-06 10:36:52 [19479] [7] ERROR: AT2[/dev/ttyS0]: Generic error: ERROR 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: send command status: -1 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: --> AT+CMGS=69^M 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: <-- > 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: send command status: 1 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: --> 0051000B912394552107F00000A73F050003000202D8611D0C16B3C166B6DA0C26A3E514 0A6AB2D92A368B41DD382C67B F41F6B29CFC66A7ED611D0C3693D16E381A8E369BC5 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: --> ^Z 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: <-- > 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: <-- ERROR 2009-01-06 10:36:52 [19479] [7] ERROR: AT2[/dev/ttyS0]: Generic error: ERROR 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: send command status: -1 2009-01-06 10:36:52 [19479] [7] DEBUG: AT2[/dev/ttyS0]: --> AT+CMGS=69^M 2009-01-06 10:36:53 [19479] [7] DEBUG: AT2[/dev/ttyS0]: <-- > 2009-01-06 10:36:53 [19479] [7] DEBUG: AT2[/dev/ttyS0]: send command status: 1 2009-01-06 10:36:53 [19479] [7] DEBUG: AT2[/dev/ttyS0]: --> 0051000B912394552107F00000A73F050003000202D8611D0C16B3C166B6DA0C26A3E514 0A6AB2D92A368B41DD382C67B F41F6B29CFC66A7ED611D0C3693D16E381A8E369BC5 2009-01-06 10:36:53 [19479] [7] DEBUG: AT2[/dev/ttyS0]: --> ^Z 2009-01-06 10:36:53 [19479] [7] DEBUG: AT2[/dev/ttyS0]: <-- > 2009-01-06 10:36:53 [19479] [7] DEBUG: AT2[/dev/ttyS0]: <-- ERROR 2009-01-06 10:36:53 [19479] [7] ERROR: AT2[/dev/ttyS0]: Generic error: ERROR 2009-01-06 10:36:53 [19479] [7] DEBUG: AT2[/dev/ttyS0]: send command status: -1 2009-01-06 10:36:53 [19479] [7] DEBUG: Set split msg status to 3 2009-01-06 10:36:53 [19479] [7] DEBUG: AT2[/dev/ttyS0]: TP-Validity-Period: 24.0 hours 2009-01-06 10:36:53 [19479] [7] DEBUG: AT2[/dev/ttyS0]: --> AT+CMGS=154^M 2009-01-06 10:36:53 [19479] [7] DEBUG: AT2[/dev/ttyS0]: <-- > 2009-01-06 10:36:53 [19479] [7] DEBUG: AT2[/dev/ttyS0]: send command status: 1 2009-01-06 10:36:53 [19479] [7] DEBUG: AT2[/dev/ttyS0]: --> 0051000B912394552107F00000A7A00500030002018ACD6210F4768FC36C3648FEA687E9 E9B75BA750149BC5608B387CB 6AED6A10E9E7ED3E5A0BBFC2D2EB37530180D67CBCD60B21B0C8653288ACD62B0451C3E5 BC4EA54377ECBDD65763A0C9A8FD1F2F7785DD6C160B45CEC36B3C96E37182EA650149BC 560CBF99CB69C D4A9AEEA2697CD2185829A6CB6AA531D5C1E2697CB7090F8BD4EBBC3 2009-01-06 10:36:53 [19479] [7] DEBUG: AT2[/dev/ttyS0]: --> ^Z 2009-01-06 10:36:58 [19479] [7] DEBUG: AT2[/dev/ttyS0]: <-- > 2009-01-06 10:36:58 [19479] [7] DEBUG: AT2[/dev/ttyS0]: <-- +CMGS: 122 2009-01-06 10:36:58 [19479] [7] DEBUG: AT2[/dev/ttyS0]: <-- OK 2009-01-06 10:36:58 [19479] [7] DEBUG: AT2[/dev/ttyS0]: send command status: 0 2009-01-06 10:36:58 [19479] [7] DEBUG: Parts of concatenated message failed. The messages generating the above mentioned erros had following structure: (I replaced the content for privacy reasons) X being capitalized alphanumeric values x being alphanumeric values 0 being numeric values . is unchanged : is unchanged - is unchanged There is a \n (carriage return) between each line. Failing message: ###Start Message#### XXXX xxxxxx xxxxxxxx: XXXX-XXX-XXX:xxxx xxxxxxxxxx:0000000000000 XXXX-XXX-XXX:xxx xxxxxxxxxxxx:0000000000000 XXXX-XXX-XXX:xxx xxxxxxx:0000000000000 XXX-XX:xxxxx xxxxxx:0000000000000 XXX-XXXX:xxxxxx xxx:0000000000000 ###EndMessage#### Working message: ###Start Message#### XXXX xxxxxx xxxxxxxx: . XXXX-XXX-XXX:xxxx xxxxxxxxxx:0000000000000 . XXXX-XXX-XXX:xxx xxxxxxxxxxxx:0000000000000 . XXXX-XXX-XXX:xxx xxxxxxx:0000000000000 . XXX-XX:xxxxx xxxxxx:0000000000000 . XXX-XXXX:xxxxxx xxx:0000000000000 ###EndMessage#### When replacing the \n (carriage returns) with a ".\n" (a dot and carriage return the problem was solved and the messages arrived without a problem or error) I'm using Kannel 1.4.1 compiled on Suse Linux. Unfortunately I can't confirm if the problem can also be reproduced on version 1.4.2 I hope this information is helpful to someone. Cheers, Jelle S.
