Required features

Messaging features that increase the cost of sending a message may be dropped in favor of least-cost routing. By setting the required features parameter you can prevent features being dropped by making them mandatory for message delivery to occur. You can, for instance, prevent the dropping of a sender ID by setting this parameter.

Setting the required features bitmask

For certain message features like binary, Unicode, concatenation and UDH, we always set the appropriate required feature value for you. This parameter is set using a combined decimal number to refer to the additional required features.

The decimal value that refers to a particular message type feature is listed in the table below:

For example:

32 + 512 = 544 – Numeric sender ID and flash SMS both required. The value you would set to ensure that flash and numeric sender ID are both supported would therefore be 544.

To ensure that delivery acknowledgment and alphanumeric IDs are supported you would use the value 8240 (16 + 32 + 8192).

You can view the Parameters list page to see the name of the parameter for the API you are using.