General FAQ's

Although many of us have smartphones, not everybody does. Also some people don't want to use apps because they may have to pay for it and some free apps are of varying quality. Finally, not all apps are available for every type of mobile phone or their operating system.

SMS Technology generally is safer than internet dependent communication platforms (eg. e-mails). sendQuick operates independently from the internet and can integrated with your preferred enterprise application, or as a standalone solution, to enable 2-way messaging more effectively and more securely.

According to The Economist, while an email maybe read within 48 hours upon its delivery, SMSes are read within 20 minutes on average. SMSes also has a higher open-read rate than emails. From a business and technical perspective, this could mean time-critical advantage gained if using SMSes to enable remedial actions. sendQuick appliances can integrate with existing enterprise applications to extend messaging capability, or serve as a standalone system by itself. Therefore you benefit by having higher ROI, and lower TCO, increased agility and better workflow management.

If you have a pre-existing customer contact list and it is saved in CSV (comma separated values) format, you can simply upload it and have sendQuick appliance use it to send out. However if you are intending to reuse that same list over a few times, you can upload it to the sendQuick appliances address book for repeated use.

sendQuick appliances can average 6 to 8 messages per modem per minute. You can increase the number of modems to better load balance the message delivery capability between them to improve the message throughput

sendQuick appliances can help your business become agile since ...

a) we support SMTP (Email), HTTP Post, FTP, ODBC access for integration with applications

b) we support SNMP Trap, Syslog and Email for IT and Network Monitoring and Alerts

c) we support RADIUS-compliant SSL VPN for 2 Factor Authentication

 

sendQuick appliances can be scaled up to the use of 32 modems and it can perform auto load-balancing.

Selected sendQuick appliances can operate in a Active-Active Clustering mode to ensure zero-downtime implementation.

While we cannot guarantee any modem’s compatibility for use with sendQuick appliances, there is however a high chance of success when deploying with serial modems using RS232

Technical FAQ's

We are current use Maestro (Rs232 and USB) and Robustel (RS232 & USB) for sendQuick. Robustel updated that future models will combine RS232 and USB into one (maestro already combine).

Each modem uses 2 ports in sendQuick box. Modem is connected to sendQuick via a Y cable as shown below. Bottom of Y cable goes to the modem, and the top 2 goes to 2 ports in sendQuick server. Each sendQuick box has 4 ports. This means that each sendQuick can support up to 2 modems. USB hub is needed when there are 2 or more modems being used. Our current USB hub has 7 ports. It is recommended to use an external power source for the USB hub. Drawing power from sendQuick may affect the life of the sendQuick box.

It’s only applicable for sendQuick Entera. Fax interface card needs to be installed into sendQuick port.
For outgoing fax notification, customer can send email to “fax-<phonenumber>@sendquick IP address”, with PDF attachment. sendQuick will convert PDF file and send out fax message. Customer can also send via HTTP Post*, however, email to fax is the most common method.
For incoming fax, sendQuick will send out email with fax as PDF attachment. sendQuick can only send to one common email address.
*If customer is sending via HTTP Post, sendQuick can also send out a fax cover. Customer will need to specify the URL for sendQuick to grab the HTML file to send out.

It’s only applicable for sendQuick Entera. Voice card needs to be installed into sendQuick port. Customer sends pre-recorded voice file via HTTP post to sendQuick.

Connect a monitor and keyboard to sendQuick server, Press ALT+F3, follow instructions on the screen

Go to “Modem Status” page. If modem is detected, this page will show the modem IMEI and SMSC number found from the SIM card

When modem LED is not blinking it is either PIN numberis present or SIM is not working/ activated.
Do the following check:

• Remove SIM and modem from USB/modem
• Put SIM into normal phone
• Make sure there is no PIN. If there is PIN, remove PINand set phone to disable PIN
• Try to make a call or send SMS with SIM in the phone

Connect monitor and keyboard to system. Find the IP address in the IP routing table on the screen

Connect monitor and keyboard to system

• Press ALT+F4
• You will see the login page
• Enter default username (admin) and password (sqroot)
• Change the IP, Netmask and Gateway IP address

  • Connect monitor to system
  • Check for any error message on screen
  • Press the LCD button, check for any reaction from LCD. If there is no reaction, system may hang.
  • Check LAN connection to sendQuick, if there is any LED lighton LAN port
  • Go to "Backup & Diagnostic
  • Use SMTP Server connectivity to test SMTP connection

Use Telnet 25 where IP is the sendQuick IP address. If TCP port 25 is open, and it shows: “220 sendquick.messenger ESMTP”, this means sendQuick is ready to receive email

 

  • Go to "Usage Logs & Report"> SMS Outbox
  • Enable Delivery Report in "SMS System Setup"
  • System will be record the date and time when SMS has been successfully delivered to destination mobile phone

Go to “Usage Logs & Report” > SMS Inbox

  • Go to "Backup & Diagnostic"
  • reat system diagnostic file[Start] and download file
  • Send file to us

Cloud FAQ's

The servers are hosted at Singapore telco-grade, MTCS-certified data centres.

To a certain extent. sendQuick ASP and WebOTP /Captive Portal can be integrated with sendQuick and Sqoope appliances. In fact, sendQuick ASP can be integrated with hosted Sqoope, and sendQuick WebOTP / Captive Portal can be integrated with hosted Sqoope.

Service availability: 24 x 7, excluding planned maintenance.

Server availability: at least 99.5% uptime, excluding planned downtime.

For the problem(s) reported, Talariax Pte Ltd will response within the required response time and support the issues as reported. The support (service level) is 24x7 hours response via emails (support@talariax.com) and phone calls (+65 6280 2881 during office hours – i.e. Monday to Friday, excluding Public Holidays from 9.30am to 5.30pm).  A mobile number (+65 9694 6237) will be provided for support after-office phone calls to continue provide service support on 24x7 basis.

TalariaX Cloud offers purchase options such as e-store and e-submission of signed application form. As for payment methods accepted, they include PayPal, credit cards, GIRO, cheque and bank transfer.

Yes but only for certain services (e.g. Clouvera and sendQuick ASP SMS pre-buy packages and the credits top-up) for now.

Yes, TalariaX Cloud has a primary and backup servers running in parallel at 2 different local telco-grade data centres with the redirecting being configured on application’s end for load balancing and high availability (HA) purposes, thereby minimising downtime in the event of outage.

Within one working week upon receipt of completed application form or order form (for e-store).

There are features for the users to utilize to adhere to PDPA regulations. However, it is the users who need to do their due diligence before using TalariaX Cloud services to reach out to the recipients.

This is a SMS technology limitation across the board which may result in some special characters turning from ASCII Text into Unicode characters and affect the eventual SMS count and billing to the customer. Hence, to overcome this limitation, the user will either type into the message box manually or copy and paste to "notepad" and then replicate that actions to the message box from "notepad".

No. The closest recommended model that support this function would be sendQuick Avera appliance.

Yes, if the telco operator fails to deliver SMS, TalariaX Cloud will use alternative telco links to conduct immediate retry.

 

There is no limit on the number of messages allowed for sending is imposed unless the SMS credits are used up for pre-paid account.

No limit imposed, unlimited users supported.

The SendQuick ASP HTTP(S) API is provided the interface to send SMS by using HTTP(S) method (POST or GET). The 2 types of send SMS approaches:

  • Batch SMS send which is sending same SMS message content to multiple mobile numbers with single HTTP request.
  • Single SMS send which is sending one SMS message to one mobile number with single HTTP request.

Customer need to subscribe an account with TalariaX Cloud for sending SMS via the HTTP API and choose the SMS quota package (pre-paid) or set to unlimited SMS quota (post-paid) based on the estimated volume of outgoing SMS required. Besides, the customer may register the application IP Address with TalariaX Cloud to ensure only the approved application is allowed to send SMS from the subscribed account.

The Status shows outcome of the sent message(s). If it is Y, it means that SendQuickASP has already sent out the message from the gateway. If it is N, it means that SendQuickASP has not sent out the message from the gateway. Then, if it is NEW, it means that the message is new to SendQuickASP, queuing up to be processed the soonest possible.

The Delivered Status shows an acknowledgement of the sent message(s) directly from the telecom operators. Some of the possible words seen can be as followed: Delivered – the message has been delivered by the telecom operator to recipient, Sent / Accepted – the telecom operator has received/accepted the sent message from SendQuickASP gateway, Undelivered – the message has not been delivered by telecom operator or [blank] – the telecom operator has not come back to TalariaX Cloud on the delivery status to relay in the SendQuickASP system and it does not necessary mean the recipient has not received the message physically.

By default, the SMS logs will be stored in the hosted servers for around 180-days but it is configurable upon request.

Keyword is defined as the first word in the incoming (received) SMS message. The keyword management is used to configure the routing and functions of the incoming SMS message. This is useful to convert and direct the incoming SMS to different supported formats (e.g. email, HTTP Post) to integrate to different backend applications, allowing data collation into backend applications automatically.

sendQuick allows keywords being unique and consists of alphanumeric characters (up to 15 characters) without space/special characters.

  • The incoming SMS will be converted to emails, and sent to these email addresses listed
  • The incoming SMS will be redirected to the mobile numbers listed
  • The incoming SMS will be converted to any of the supporting APIs and sent to the requested URL listed
  • Incoming SMS may trigger an auto-reply SMS / an auto-email send-out push

Direct connection via Local Link means working with the local telcos, i.e. SMS messages do not leave Singapore shores for the full delivery. It can be in the form of Shared / Dedicated Short Codes (5-digit numbers), Shared/Dedicated Long Codes or Caller ID.

Direct connection via International Link means working with the overseas aggregators, i.e. SMS messages (be they be sent to Singapore mobile numbers or non-Singapore numbers) do leave and route back to Singapore shores for the full delivery. It is usually in the form of Caller ID or long codes.

If only the SMS were to fail to successfully pass through the SMS gateway, then there is no SMS charge to customer.

Yes, so long as the SMS passes through the SMS gateway successfully.

The mechanics in sending is that messages flow via the mobile operators’ SMSCs from an enterprise (a business entity).

  • Mobile Terminated (MT) message: outgoing SMS to mobile phone
  • Mobile Originated (MO) message: incoming SMS from mobile phone

When a message is delivered by a Short Message service centre (SMSC), it will return a Delivery Status and the reason of failure, if any, to the organization.

The organization can choose either one of the following to deliver their messages:

(1) Directly connected to one telco operator but some may be undelivered because no single mobile operator can reach every operator, or

(2) Directly connected to several mobile operators but it is complex and challenging to manage.

Most organizations would not select option (1), and incur the cost of managing each mobile operator and negotiating the business terms cum technical integrations. Rather, organizations will implement option (2) by engaging an aggregator who can provide the most cost-effective, yet efficient way to deliver message anywhere, anytime while covering all complexities involved.

TalariaX Cloud is one of the leading mobile messaging value-add service providers who offers 2 ways to send message in general – either via a web user interface (UI) or an API.  A web UI requires no development but an API usually requires some basic integration effort to enable external system to be integrated to send messages.

No, SMS delivery cannot be guaranteed as telco operator does not provide 100% guaranteed SMS delivery too. For SMS delivery, TalariaX Cloud only guarantees on SMS server availability of at least 99.5% uptime, excluding scheduled downtime. Nevertheless, TalariaX Cloud is able to provide the option of hybrid messaging that ensures guaranteed message delivery.

Number masking refers to the name given by the sender in the sender field in an outgoing SMS message. It is restricted to only up to 11 alpha-numeric characters without any special character and does not allow a recipient to reply back unless a SIM mobile number is provided in the given name and/or message content sent.

Sending and receiving throughput of SMS via direct connection: at least 2-3SMS/second.

Receiving via modem hosting: 20 SMS/second.

Yes, this function is supported with character set encoding ASCII Text (ISO-8859-1) for English and Malay languages, and UTF-8 (Unicode) for all other languages or a mix of English/Malay and other languages.

To standardize the storing of alphanumeric characters, the American Standard Code for Information Interchange (ASCII) was created. It defined a unique binary 7-bits number for each storable character to support the numbers from 0-9, the upper/lower case English alphabet (a-z, A-Z), and some special characters like ! $ + - ( ) @ < > .

Because the limited character sets in ASCII Text and its non-compatibility in multilingual environments, the Unicode Consortium developed the Unicode Standard. The Unicode Standard covers (almost) all the characters, punctuations, and symbols in the world.

By industry standard, a standard SMS message in ASCII Text (ISO-8859-1) is 160 characters and in UTF-8 (Unicode) is 70 characters.

As for each concatenated (long) SMS message, one SMS count in ASCII Text (ISO-8859-1) and UTF-8 (Unicode) contains 153 characters and 67 characters respectively.