Notification Settings

[Andrey]

#12941

there should be one API key i think that belongs to NanoTel, but you can also see voip that auto purchases numbers so it works there and for some reason do not work for NanoTel. You can check numbers at any time not necessarily at midnight we sometime see the numbers in different times so you can capture which number is going reserved.

We also check over weekend if your new code works and let you now afterwards.
To inteliquent you can explain them that we have to manually purchasing numbers as the auto purchase is not working and we have to manually buy them to not miss.

I think once you got the number you can screen shot it and send it to Inteliquent and we also check if any changes and update you.

Kind regards Andrey

[Andrey]

#12943

Hello Nishit we have been monitoring your new updates over weekends and found the following: We have recived only one notification message and there was no any other notifications so we decided to log in to the inteliquent and check that number but wen we logged in we found more numbers than one: See screen shot attached. https://webmaklay.com/wp-content/uploads/2024/10/MNUM.jpg

So now it is even worse we can not see which numbers are there and they still going to reservation so we need manually purchase them.

What we though is – if you create an entry with last 123, 456 or 789 numbers. Just make quantity minimum so it will capture such numbers and we see them we know it is for support. Next time when we purchasing numbers we leave them untouched so you can get involve inteliquent team to have a look at this issue and suggest what kind of bug it is and hopefully they address you a resolution for that.

Kind regards Andrey

• This reply was modified 1 month, 1 week ago by Andrey.
• This reply was modified 1 month, 1 week ago by Andrey.

[Nishit Shan]

#12946

Hello Andrey,

I made chnages in code and got mail of these below listed number:
2185512000,
2184028000,
2185419000,
7155669999,
6086087777,
6086088888,
5204164444,
3204174444,
3202424444,
7156535555

I have printed in mail to see if the number is being reserved or not and got the number is being reserved as reserved: 1.

Can you please confirm if these number got auto purchased.

[Andrey]

#12947

Hi Nishit sure will ask administrator to check if numbers purchased and get back to you. I can see the numbers being repeating again in notification but let us check if the numbers purchasing and then look at number repeating issue

[Nishit Shan]

#12948

Hello Andrey,

for two number i got this (Duplicate TNs detected:[6086087000, 6086088000]) message from the API and these two number has not been purchase and i can see it on reserved number list.

When i asked inteliquent support team about this then he said the number is not been reserved and trying to purchase that’s why getting this response, But if the number is not being reserved then how i can see in our reserved number list on inteliquent portal.

About the API key specific reserved number list, support team said they are not providing facility to fetch reserved number on the basis of API key. So it is being hard to purchase number after reserving.I am looking for the solution .

[Andrey]

#12952

Hi Nishit I’ve read your #12948 by the look on it there are some misunderstanding going on within ineliquent, unless there is a bug on Inteliquent. I have also checked with project admin and they said that after some time they could finally see those numbers that we could not see https://webmaklay.com/wp-content/uploads/2024/10/FNDNUMB.jpg.

Not sure what’s going on. Surprisingly Monday more numbers should be released by the telecom but NanoTel and Voip admins missing about 313 notifications! We continue checking and later the day we received some notification on Voip https://webmaklay.com/wp-content/uploads/2024/10/VOipots.jpg

Well there is definitely something going wrong with notifications and we hoping you can find resolution for this. NanoTEl team can not work without proper notification system.

Please let me know if there is a bug from Inteliquent side and if you find it will address it to the Inteliquent ppl.
Kind regards Andrey

[Nishit Shan]

#12953

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.

[Andrey]

#12956

Hello Nishit that has been a good research and discussion with Inteliquent it does worth more knowledge.
I have got your message and spoken to Voip and NanoTel administration and found our the following that we suppose to use different IDs for both Voip and NanoTel projects. If not then we must review our codding then as it should be all different.

If you login to Inteliquent (using Voip Inteliquent Access) then you can click admin and there – see all users list i will provide links to this here: https://portal.inteliquent.com/CustomerPortal/userList.htm and find different users there Voip and Nano Tel and if you click on any of them you will see all the access details which are also different and unique https://webmaklay.com/wp-content/uploads/2024/10/int1.jpg. Each account has to have unique username different email and etc.

You can also click on API KEYS and find API keys and see different API keys on that page which are also different. Please see this page here https://portal.inteliquent.com/CustomerPortal/apiKeyDetails.htm.

So the question is what do you use for your API calls userDetail there should be different parameters there and not linked to one an other so that should stop the conflict behavior. All API Keys, API secret, user all are different.

——————————————

An other question is that in API calls there is a “wireless” parameter which is set to NO and this is right, the question is if we enable it on Inteliquent will that make any difference for our numbers searching / purchasing improvement?

Your are going good with your communication with Inteliquent we appreciate it and hoping you can fix it soon, we also decided to increase your balance a little bit as our humble thank you for your great work.
Kind regards Andrey

[Nishit Shan]

#12958

Please find: #post-12957

[Nishit Shan]

#12957

Hello Andrey,

Please check these both screenshot (https://ibb.co/JdX2ydx , https://ibb.co/3R2SdtX) order screenshot is with different user id . You can notice the data is same for both, it means the storing point for both is same. In this case when i do fetch reserved number and purchase them then the voip reserved number will also be purchased.Read this line from support team (Suppose you reserve a TN x, if you try to reserve the same TN x you will be able to do it). It means we can reserve already reserved number if we have same storing point for all user and because of this we are reserving already reserved number . Because of the entry on Voip we are reserving it from voip and because of same types of entry we are reserving the reserved number from nanotel also. Because of all these process code are facing duplicate tn order and also the reason we are getting same notification many time on mail.

I only have two solution for this problem:

1. Make a complete different account with different storing point.
2. Remove Reserve number concept from everywhere (Currently it is on voip).

[Andrey]

#12960

Hi Nishit thank you for your thoughts, could you please clarify these two screen shots in #12957, different user do you mean both Voip and NanoTel keep the record in one NanoTel account? one account is a NanoTel or Voip we have created different users with different APIs what do you mean one storing point?

[Nishit Shan]

#12961

Hello Andrey,

You can see in the screenshot for both different user, there is same order list for both user. It means the number is being stored at same place for both user.Where the number or any detail is being stored is storing point.

[Andrey]

#12962

Oh i see so both accounts under one root company name? let me talk to the nano tel admin and get back to you.

[Nishit Shan]

#12963

Hello Andrey,

I am getting error message (Your password needs to be updated. Please check your email to reset it.) on inteliquent login.

[Andrey]

#12966

done!

[Author]

Posts