Tagged: Hi Nishit, just a quick catch up will be somtime helping you when possible, will decide on next week.
-
AuthorPosts
-
we are closing here now can you please make sure there is no junk notifications comming please be careful with every steps you do. Ppl saying there are junk notifications coming every 2 seconds or so again…
Cheers
Hello Mark,
yes, it is sanbox notification.
Hello Mark,
I passed a inquiry fro the support team.
Message:
—————————————————————–
Hello Team,This is the status for tnOrder on sanbox :{“status”:”Success”,”statusCode”:”200″} , but not getting order list on sanbox inteliquent portal. This is the timestap of the order (2024-09-26 08:05:08)
Thanks
————————————
Hello Nishit thank you for your replies, and message to support, do you think you can finish this job?
If so when we are going to start receiving valuable numbers?Can you please also sent #12880 instruction to site admin and your measures to prevent unauthorized numbers purchase.
CheersHi Nishit we are closing here will catch up in about 48 hours.
Hello Mark,
I did make nanotel api on live .I will send instruction by Monday for admin.
Hi Nishit thanks for your update will monitor how NanoTel will start picking numbers now, also we have noted the Voip projects stopped taking numbers from Inteliquent for some reason we can see multiple database connection errors, i hope it is not conflicting again.
Hello Nishit we do not know when you have enabled live mode but we can see that NanoTel got 6666 number notification says as number found but when we checked on Inteliquent the number was actually purchased which is good but why notifications are incorrect? – We have been working on this job for already a month!
Also i have requested to let you know that we have checked and found that Ineloquent released the following numbers
503.503.7000-799 and 503.503.6000-6999 but NanoTel could only captured 6666. So the question is where are 6000, 7000, и 7777 numbers? – which means all these numbers have been captured by our competitors and we have got only one 6666 – have you checked all your codes? Are you still working on it? we just trying to understand why we missed all other numbers and only captured one?Also could you please let us know if you enabled NPA-NXX search as well?
CheersHello Mark,
Whenever you are getting number found it means number purchased. There is no other thing to do on this portal like (notify or reserved).
For your point about released number i think we missed 3 number here like (503.503.7000,503.503.7777, 503.503.6000). Can you please confirm if i am right.
Hi Nishit we hope you have had a good weekend,
thank you for your message, please make the notification looking correct if the number purchased let it say number purchased instead.For the missing numbers , yes we can confirm that we have been still missing numbers. The site admin notified us that there had been two blocks of numbers released 503.503.6 and 503.503.7 and there were following numbers in these new blocks 6000, 6666, 7000, 7777. Nano Tel got 6666 and the rest of the numbers had been purchased by an other user.
If your script is fully functioning then it looks that we missing few seconds if other numbers being taken by other competitor.
Today we haven’t seen any single notification from NanoTel yet.
Hi Nishit we are closing here now Monday US time usually multiple numbers blogs being released hoping we will get some numbers purchased.
also please do not forget the following:
1) Set up a tracker on NanoTel project
2) Please answer if you have enabled non wildcard rules entries for NPA-NXX
3) Let us know your reply on server speed (what do you think on this)
4) Your #12880 instruction for site Admin.
5) and last but not least we are still waiting when your script start capturing valuable numbers (as described in the job) as we still missing from Ineloquent.Cheers
Hello Mark,
1) Set up a tracker on NanoTel project
->i did it , you can check.
2) Please answer if you have enabled non wildcard rules entries for NPA-NXXI
I am not getting your point here.5) and last but not least we are still waiting when your script start capturing valuable numbers (as described in the job) as we still missing from Ineloquent.
I have completed my script, we are loosing our number because execution time , I am sure other competitor are also loosing some number.However i will see if i can do anything.Hello Nishit thank you for your reply, for your #12894:
1) Thank you
2) We were wondering if we can create a non wildcard rule we tried to create couple rules today and it seems it is enabled.
3) Let us know your reply on server speed (what do you think on this) you have comented that voip server speed was not too great so we are still awaiting for your reply comment regarding NanoTel host.
4) Your #12880 instruction for site Admin. Still waiting for that.
5) Thanks for your: “I have completed my script, we are loosing our number because execution time , I am sure other competitor are also loosing some number. However i will see if i can do anything” – this is a main factor of the whole job so we are looking forward when we start receiving desired numbers, so far we still loosing a LOT of numbers and here are some report for you below:MONDAY (US TIME) there had been released a lot of numbers we can see that NanoTel has captured 406.405.7000 but we loose 7777. By the way again the notification from NanoTel is wrong and still says number found but it has been purchased so please make sure that notification comes correct if it is purchased then notification should say Number has been purchased.
Now Inteliquent is is biggest teleecom provider. Inteliquent have been requesting millions numbers and their release multiple blocks at a time. One block at a time can contain 100 numbers 50 and 50 from this 100 Nano Tel have purchased only 1 number 7000. So we think the reason why this 7000 has been purchased it is just a coincidence rather than a rule as we want it to be as we lost big amount of valuable numbers. If your script could allow us to buy 50 numbers ending with 000 plus 7000 then we would see good progress.
Thus can you please send us your API call request that has purchased 7000 number so we can have a look at that, site admins themselves already started examine API library as we are doing this job for toooooo long. We believe your API code requests too many parameters such as Trunk group and other options but site admins believe that API requests can be shorter and that’s how our competitor does it this way and capturing all valuble numbers but us only one or two.
Later we found that NanoTel found an other number 4444.
TOTAL:
Voip 941.390.1111 and 941.390.2222
NanoTel 4444 and 7000but we still missing best numbers as 7777, 8888
also we lost these 941.390.0000,1000,2000,4000.
So please resolve this all above. To make requests more efficent please reduce API parapeters requests site admin belives that we do not have to requett othre options to make our API calls faster.Also feel free to add every 1 second API calls – now we have every 2 sec but from what you have done so far it does not help much.
Please let us know if any issues.Also just letting you know that company approved my holiday and im going to be away from next week so someone from the team will be on some extra support hours for your time zone.
Cheers
- This reply was modified 2 months, 3 weeks ago by Mark Hanson.
Hello Nishit we are closing here, will catch up with you in about 24 hours.
CheersHello Mark,
Nanotel is only for wildcard and also only for purchase , if i will make reserve and notify functionality integration then it will take more execution time and we might loose more number. That’s why i was not suppose to make reserve and notify functionality here.
You can consider my above paragraph as a instruction also .
For API execution code you can find it from (/app/Http/Controllers/AdminNumberRulesController.php)
Can you please confirm me what will be maximum entry on nanotel. I am thinking to run cron for all entry with different path, what do you think ?
- This reply was modified 2 months, 3 weeks ago by Nishit Shan.
-
AuthorPosts
- You must be logged in to reply to this topic.