The polling interval is the frequency (in seconds), of polling message QUEUE. This setting helps you manage any probable stress on message QUEUE. Usual recommended setting is 2-5 seconds. The window size is more relevant for Asynchronous request between ESME and SMSC and defines the max number of allowed number of unacknowledged transactions. It helps to regulate throttling by […]
Why is there a time difference in SMS Delivery reports compared to the actual time of delivery in handset?
The delivery time of SMS shown in reports is as received from upstream Gateway, which may differ from gateway to gateway received on real time, so there might be some time difference in report.
You can change your password from Login page. If you forgot your password and are unable to log in, click on Click here to reset your password. One password reset link will be sent via email.
Usually for single SMS, character length is 160 characters. If you type more than 160 characters then the SMS will get split in to multiple SMS as per the SMPP standards. While Available maximum character length in iTextWeb is Simple Text: 1200 characters, Unicode: 530 characters.
Previous reports will be available in the Reporting section. date wise summary report is also visible by entering the dates in the custom range.
Every system has a defined session time, if no activity is done for that defined time, the session will get automatically expires, and thus the iTextWeb / iTextBlaze user will get logged out from its respective account. If the SPAM Validation is active for any respective account and if the system detects any SPAM words, […]
Our application is designed supports Normal, Flash, Unicode SMS. Unicode SMS also know as language SMS such as Hindi,Urdu,Arabic, Thai etc. Unicode Flash is not supported widely across the globe. Kindly check the documents provided by your Telecom operator for details. In certain countries Normal message as encoded as Latin-2 instead of default 7 bit […]
Why messages with special characters i.e. (&, *, @, $) are not delivered in a readable format on some mobile screens?
Special characters such as &, *, @, $ etc has different values in GSM 7 bit encoding. You need to check the character en-coding supported by your SMSC. Some SMSC uses ISO 8859-2 Latin character set instead of GSM7 bit. In case of mismatch of character encoding, such special characters in message may not appear properly on […]
Few countries have regulatory requirement to differentiate between promotional and transactional SMS. Since it is country specific requirement, its not available by default. However same can configured based on client requirement. SMPP Gateway time limit can also be implemented in such scenario. Any messages queued after the stipulated timing window are queued automatically for next day […]