- IMGate only supports Store and Forward message delivery mode.
- The incoming SMS message size is limited to 160 (Latin) characters or 70 (non-Latin) characters. The size for incoming multipart SMS message with a User Data Header (UDH) information is limited to 153 (Latin) characters or 63 (non-Latin) characters for each SMS part.
- IMGate sends messages longer than 254 (Latin) characters or 127 (non-Latin) characters using the message_payload TLV parameter for SUBMIT_SM operations.
- IMGate receives/sends messages one at a time using the submit_sm operation. The submit_sm_multi operation is not supported.
- IMGate uses the registered_delivery option (that is enabled in the service policy for an SMPP vendor connection) to request a delivery report for the SMS message being submitted. The query_sm operation is not supported.
- IMGate sends accounting requests to charge users for SMS delivery upon receiving the SUBMIT_SM_RESP response message.
- IMGate cannot cancel a pending delivery of a previously submitted message. The cancel_sm operation is not supported.
- IMGate cannot replace a previously submitted message that is pending delivery. The replace_sm operation is not supported.
- Based on the matched domain service policy, IMGate receives a routing list for further SMS message processing and delivery. IMGate sends/resends the SMS message only to the first available vendor from the routing list. According to the error code that the vendor sends in their response, IMGate either resends the SMS message (temporary error code) or discontinues resending it (permanent error code). For more details, see
Handling Undelivered SMS Messages. Routing the SMS messages to the other vendors within the routing list is not supported. Let’s say the routing list for the main domain service policy (higher priority) includes vendors A and B. The routing list for the secondary domain service policy includes vendors C and D. When vendor A fails to deliver an SMS message IMGate will send it to vendor C, since vendor C is the first available vendor for the secondary domain service policy.
- End users can send and receive messages only by using their account ID numbers. They can assign aliases to their main numbers and successfully use them for calls. Messaging from aliases is not supported.
Was this article helpful?