Hi all, I'm quite new to this so please bear with me. I've configured my SMPP component with the following properties.
bridgeErrorHandler: ERROR dataCoding: 8 encoding: UTF-16 splittingPolicy: ACCEPT However, when I send a message over 70 chars, the SMSC server requests it because the message is over 140 octets. My expectation is that, since splittingPolicy = ACCEPT, the SMPP server would split the original message into however many messages under 140 bytes are required so these could be accepted by the SMSC. Am I missing something in the configuration or is my expectation incorrect? Some other info: - Messages under 70 chars are accepted. - I can't find anything useful in the logs. - I've tried setting splittingPolicy = REJECT but instead of stopping any messages over 140 octets, the message is still sent to, and rejected by, the SMSC. - I haven't done much testing with other encodings combinations as some of the messages will contain Thai characters and this is the only encoding supported by the SMSC provider. Thanks in advance, Tommy O'Donnell This email is intended for the person or company named and access by anyone else is unauthorised. If you are not the person or company named, please delete this email and notify the sender. The information in this email, including any attachments, may be confidential or legally privileged and its unauthorised disclosure, copying, distribution or use is prohibited and may be unlawful. This email has been sent from MDS Global Ltd, a registered company incorporated in England and Wales with registered number 02263085 . The registered office is The Point, 410 Birchwood Boulevard, Warrington, Cheshire WA3 7WD. MDS Global Ltd may monitor email traffic data and also the content of email for the purposes of security, ensure compliance with company policies and staff training.
