Home Forums NanoTel Notification Settings Reply To: Notification Settings

Nishit Shan
Participant
Post count: 1116

Hello Andrey,

Sorry, but i was confuse and not able to find the exact reason behind the error. Now after a discussion with support team and there message (You can read below):
—————————————————————————————–
1. We do not allow fetching back the TNs that were reserved with only a particular API key.
You will get back all the TNs that are reserved on the customer account, irrespective of what API key was used to reserve them.
2. Also, for you second query – we show from our logs that you were sending the tnOrder request with the same set of TNs every minute. As the request contained a large number of TNs, the order was still being built and in the meantime you were entering the next order in the very next minute. Hence, the error Duplicate TNs detected.
3. I noticed from our logs that the TN 6086087000 has been included twice in your payload
——————————————————————————————

Now what i think is reason behind all these problem is the same userDetail for voip and nanotel on inteliquent.
They also added a point that the reason behind the duplicate TNs is that we are sending continues request to the inteliquent APi for order purchase .So our idea was to send request to purchase number every second or every two second will not work.

My Solution: I think we should make other account on inteliquent with different user detail and then within a single loop we can reserve all number in our system and after that we can call the place order by getting reserved number list from our inteliquent account.
To be honest i think API provider (Inteliquent) is a big player in this industry and they built there system very cleverly. Because i asked them can we get reserved number on the basis of the API token which i provided for reserve, then he said they are not providing this type of facility.