[Nishit Shan]

in reply to: Notification Settings #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.

[Nishit Shan]

in reply to: Notification Settings #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).

[Nishit Shan]

in reply to: Notification Settings #12958

Please find: #post-12957

[Nishit Shan]

in reply to: Notification Settings #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.

[Nishit Shan]

in reply to: Notification Settings #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 .

[Nishit Shan]

in reply to: Notification Settings #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.

[Nishit Shan]

in reply to: Notification Settings #12940

Hello Andrey,

“I guess the best way will be is to see when Nanotel notification come and say this number is purchased then login to Inteliquent and see that number is actually sitting at orders reserved directory and then Inteliquent support can track it and guide you properly.”
My Point => i can do it, but the time we are getting notification of number purchased it is our midnight . There is a problem in doing it because of time Zone and distance.

I have asked something to the support team and if teh API work like i am wishing it should work, then i can purchase all number, My Idea is we will fetch all the reserved number then system will purchased it one by one, Since we have time of 4 hour after number reservation then we can do it.But there is one problem in doing it , that’s why i cantacted to know from the support team point.As you also know we have two API key one is working on VOIP and One is For Nanotel. I want to know if the nanotel API key will give all the reserved number including voip and nanotel.
My message to support team:
——————————————
I need to know one more thing, I have two API key detail with same user and i am using (https://services.inteliquent.com/Services/2.0.0/tnReservedList) to get tnReservedList. Then how it will get the list like (it will get only number which have been reserved with the matching API key or it will give all reserved number which is for users).
—————————————–

[Nishit Shan]

in reply to: Notification Settings #12938

Hello Andrey,

I need to know the current feedback about the number purchase.

“i have old code and will make as it was”=> Means i have the code which i chnaged yesterday and will set the same code if new changes doesn’t work.

For your point about is inteliquent support team help: Some of his point making me confused because i sent then two number which i got from the nanotel notification email (5078575555,3203085555) and you informed me that the number is being reserved but not purchased. But support team is saying the number were not in an available status, if the number were not in an available status then how i got it in our list and even in notification ,do the API provide reserved number also.
One more point he said that “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”.What it mean ? I can not place order within minutes.

Also please give the feedback about today’s number purchasing status, like how many number you got or how many you missed.

[Nishit Shan]

in reply to: Notification Settings #12936

Hello Andrey,

I found an unwanted result during testing on sandbox account and i also shared it with support team.
___________________________________________________
{status:Duplicate TNs detected:[2029884658, 2029884659, 2029884665, 2029884667, 2029884691, 2029884693, 2029884699, 2029884704, 2029905628, 2029905675],statusCode:413}
____________________________________________________
I made some big changes in current code, please monitor the behaviour of new code and give your feedback.
Sorry, but you may loose your number if the code doesn’t work. However i have old code and will make as it was.

The Current code worked on sandbox and mail was also not repeating the number.

[Nishit Shan]

in reply to: Notification Settings #12933

Hello Andrey,

Sorry, but there is not number in reserve number list . Please check the screen-shot (https://ibb.co/ZMvF928). It is being hard for me to track actual activity because of different timezone and also i have to trust on my code because same code is working on sandbox account.

However i am looking for reason behind the mail and purchasing bug.

[Nishit Shan]

in reply to: Notification Settings #12931

Hello Andrey,

I am waiting for actual number admin purchased manually.I also made changes in order process , can you confirm if it is now working .

[Nishit Shan]

in reply to: Notification Settings #12929

Hello Andrey,

Can you please share 3 or 4 number which you have purchased manually, support team is asking for TN number Example and i need 3 or 4 tn number .

For the Email Repeating , i noticed it is because of number purchasing problem.And for the trunk group i will try to order without trunk group.

[Nishit Shan]

in reply to: Notification Settings #12925

Hello Andrey,

I passed a messaged to the Support team for the help:
_______________________________________________________________________
I am reserving number using tnInventory api with reserve:y flag and it is working , but when i try to place order it using tnOrder then it is not ordering even i am getting status success. But same code for tnOrder on sanbox is working perfectly.

Please check below code structure:

$postData = [
“privateKey” => “hH5_APRI8TzKqwOq9XOVrEFcsU_J”,
“tnOrder” => [
“tnList” => [
“tnItem” => [
“tn” => $number[‘telephoneNumber’],
“trunkGroup” => “ATLNGAQSNAN_1790”,
“endUser” => [
“name” => ‘Voip_us’
],
“tnFeature” => [
“callerId” => [
“cnamDip” => $number[‘cnamAllowed’] === ‘Y’ ? ‘Y’ : ‘N’
],
]
]
]
]
];

$port_in_url = ‘https://services.inteliquent.com/Services/2.0.0/tnOrder’;
$response = Http::withToken($token_id)
->withHeaders([
‘Content-Type’ => ‘application/json’,
‘charset’ => ‘UTF-8’,
])
->timeout(1000)
->post($port_in_url, $postData);
————————————————————————

Because this same above code is working perfectly on sandbox account and not working on real account.

[Nishit Shan]

in reply to: Notification Settings #12923

Hello Andrey,

I will update you once i complete and fix the reservation but not purchasing bug.

for your point where you are not able to purchase or reserve 2222,3333 , there is a mistake in admin entry on nanotel. I already informed Mark that on this dashboard only there should be wilcard’s entry and i can see there is normal entry for 2222 and 3333 instead of wildcard. Can you please ask admin to change entry from normal to wilcard.

[Nishit Shan]

in reply to: Notification Settings #12919

Hello Andrey,

I am good , How are you doing ?
Do you mean not a single number is being auto-purchased or some number is being auto-purchased ?

[Author]

Posts