Guest
2007-05-09T10:41:03Z
Are multipart long SMS message supported?
Support
2007-05-09T10:43:56Z
To send messages longer that 160 character the IntelliSoftware gateway can send multipart messages. Each message part can contain 153 characters. Most handset will assemble the individual message part back into one message for display. You will be charged one message credit for each multipart message part.

Multipart message are controlled by the gateway's MaxConCat setting. A MaxConCat setting of 1 will only send 1 message part (max length 160 characters), MaxConCat setting of 2 will send upto 2 messages parts (max length 306 characters).

You can configure the default MaxConCat setting for the Email and HTTP interfaces in the Preference section of your account.

To change the maximum size, login into your account and click on the 'Preferences' link. In the 'Message Concatenation' section, change the 'Default Max. Msg. Parts' from 1 to a number from 2-10.

Here are some example settings:

1 - 160 characters max - 1 credit per recipient
2 - 306 characters max - 2 credits per recipient
3 - 459 characters max - 3 credits per recipient
4 - 612 characters max - 4 credits per recipient

When multipart messages are used, each message part can contain only 153 characters. Additional credits will be used to send each message part.


If you are using any of the API interfaces then you are able to override the MaxConCat setting on a per submission basis:

HTTP Interface - maxconcat field
COM Interface - MaxConCatMsgs property
.Net Interface - MaxConCatMsgs property
Guest
2007-11-16T02:54:23Z
Could you clarify the number of allowed characters for Unicode encoded messages and if they can be concated and if they honor the maxconcat= HTTP field. Also what is the character limit for WAP push messages?

Thanks
Support
2007-11-16T09:06:05Z
Unicode messages sizes:

Please note multipart/long Unicode is not currently support by our gateway (04/04/08).


WAP Push message sizes:

Our gateway will only send one SMS message per submission. Therefore a WAP PUSH message is charged at 1 credit.

An INVALID_REQUEST will result if the submitted text and href parameters would require 2 SMS messages to be sent. As a guide, the href and text parameters combined should not exceed 114 characters (assuming href starts with 'http://www.' )