SMS Server Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release includes only resolved issues.
This release contains the following resolved issues:
SMS Server now uses the full volume of segments for outbound (mobile terminated) messages, as follows:
- Without segmentation and reassembling: 160 7-bit codes, 140 8-bit codes, or 70 16-bit codes
- With segmentation and reassembling (and 6-byte User Data Header): 153 7-bit codes, 134 8-bit codes, or 67 16-bit codes
Chat sessions now display negative responses from the SMSC. If SMS Server receives an error code from the SMSC, or if it fails to send an outbound (mobile terminated) message for some other reason, it does the following:
- Logs these dedicated messages (which may be used for alerts) in the log file:
- 42125 Std <message source> failed execution of request to channel... <message content>
- 42711 Std <message source> system message posted to chat... <message content>
- Sends one of the following session messages to the active chat session. This message appears in the transcript as a message from the end customer.
- [SYSTEM MESSAGE] Message to the customer was not delivered. Error 920, 'lost connection with channel <channel-name>'
- [SYSTEM MESSAGE] Message to the customer was not delivered. Error 920, 'rejected by channel <channel-name>'
No special procedure is required to upgrade to release 18.104.22.168.