While using the Kaisa platform sometimes you may come across a specific error message that can be confusing or perhaps too ambiguous to troubleshoot. In this article, we will cover some of the most common errors you may come across and explain what they mean so you know what the next steps should be. 

Some common errors you may come across when using some of our solutions:

"Blacklisted IP" 

A blacklisted IP is a request coming from an IP address that exists in a library of malicious or reported IPs (every request to Kaisa is checked against these lists to verify if the request needs to be rejected if coming from a known to be malicious IP address). 
 

"Blocked IP"
A blocked IP request is a request that is rejected because the IP address has reached a cap of requests in a predetermined amount of time. In order to prevent bot traffic or crawlers from creating unnecessary sessions and number requests, IP addresses may get temporarily blocked if we receive too many requests from a single IP in a short period of time.

"Blocked User Agent"

This block occurs when agents request an excessive volume of number requests for customers using our DNCS API solution. If a visitor/IP address requests too many numbers, we will block further requests for some time.

"DNCS number cap has been hit"

Most Kaisa customers will have a maximum amount of dynamic numbers that can be used simultaneously at any given time. This number cap, or dynamic number ceiling, has usually been previously agreed upon in your contract with Kaisa, and you will see this error from our backend whenever a request for a dynamic number fails because the cap has been reached. To know more about your number cap or how to help with this, you can always contact support@kaisa.io

If this error appears it's due to the phone number that you are providing not using the correct format. E164 is a common international standard for telephone numbers that we and most providers and suppliers will use. Numbers in this format can have a maximum of fifteen digits and are written as follows: [+][country code][subscriber number including area code]. An example of how this should look can be seen below:

Please note that no spaces should be present in the E164 number

"Answering number is not allowed"

You may see this error when trying to add a telephone number in our platform. Each account and organisation in Kaisa has certain types of numbers included in their agreement, and these can determine what type of numbers you may receive from us but also what numbers we can connect to. These specific categories can be for example Kaisa numbers or mobile numbers, that may or may not be included in your agreement with Kaisa. For any questions about categories or which ones are available to you, feel free to ask us on support@kaisa.io

"Kaisa number not available" or "Freespee number not available"
This error may occur when no Kaisa number is available for the area that you have specified at that moment, when trying to create a number with our API or requesting a specific dialling code. Occasionally a specific area code may be temporarily unavailable if demand is high, but rest assured we are always making new numbers available when needed.

"a valid resource must be specified"

This error will appear when querying our API and not using one of the existing resources. To know what resources you can use (essentially what you can query our API for), you can see a full section dedicated to this here.

"could not add subcust"

Our dynamic number solution (whether javascript or DNCS API) will create subaccounts automatically with requests for dynamic numbers, if the custnr value sent in the request (the identifier you have chosen for the account) doesn't exist. Sometimes this error may show up if there was a problem with the request itself and our system tried but couldn't create an account, typically because the custnr, custemail or the custname sent for the account are invalid or exceed the character limit in our system (45 characters for the custnr, 60 characters for the custname and for the custemail there is a 150 character limit, it has to include '@' and if there’s a list of emails, all emails need to be valid). If the custemail is unknown for the account, please leave this field empty.

"custnr does not exist"

The custnr is an identifier for an account provided by the customer (when the account was created manually, or when it was created automatically by our DNCS API or javascript solutions. This error indicates the custnr value used in the request doesn't match any of the values in your account. The custnr has to be a unique value inside the master account (but can be a duplicate in other master accounts).