-
AuthorPosts
-
Hi Nishit NanoTel- Wirelss – does not work the numbers not being captured can you please advice why it is not working?
For NanoTel API calls can you please cound how many API calls come from both Voip and NanoTell, probably 12 calls per sec comes from both projects.
Hello Andrey,
May you please confirm from inteliquent if they have released any number with our active entry format for wireless crsm, Then i will check my code also.
- This reply was modified 1 week ago by Nishit Shan.
We know that there are numbers realeased there and you can see it from Inteliquent and see the numbers but our system not capturing them. If you think your code tag different format you can see on Inteliquent and sand box how the numbers look like. If in doubt you can text them on support i will ask administration too how the phone format suppose to look like.
Can you please also count how many API calls being sent per sec or min from both Voip and NAnoTel we will check with Inteliquent as well
Hello Nishit how is all going any updates,
i have spoken with admin they suggest us the following.There is a parameter in Inteliquent saying : Is the number wireless and by default it may stay as NO but we may need to change it as YES. this one you can try as we still not getting any numbers from NanoTel – Wirelss.
How about API calls have you counted how many API calls we sent from both sites any othre thoughts how we can reduce API calls?
Also have you changed on a duplicate issue?
Kind regards AndreyHello Andrey,
As per admin’s suggestion i already did it ( “wireless” => “Y”,). I am wondering how it is working with sandbox account and not with live .BTW i am looking for the possible reason behind it.
About API calls: I have checked the log and it is calling as it should call and for the purchase , reserve and notify only one api is calling for each voip and nanotel.
The same API call count depends on numbers of entry we have, Like we have 20 entry for purchase then API will called 20 times.There is no more delicacy issues now.
Hello Andrey,
I found a catch inside nanotel wireless code, The reason we are loosing the number is time interval.
What we have to do is to remove interval because of interval we are loosing number and other’s getting the number.
I have sent a question to the support team :
_______________________________________________________________________________________________________________
Hello Team,I am working on Wireless number with tnInventory api , Here i want if i once notified about any number then again this number should not come in my API’s inventory list. I there Any for it ?
Good catch Nishit hoping the answer will come soon and we can finish this job!
Thank you!
🙂Hello Nishit how is all going any news from support and other repairs?
Could you please also let me know if you can work December in case if you planning any holidays?
Kind regards AndreyHello Andrey,
Sadly i didn’t have any reply from the support team.
I will be working on December there is no holiday officially.
- This reply was modified 5 days, 1 hour ago by Nishit Shan.
Hello Nishit thank you for your updates, thats all good while we wating could you please check duplicating issue mentioned earlier and API calls reductions unless you have already fixed that..
Kind regards Andrey 😉
Hello Nishit is there any updates?
Hello Andrey,
There is update that there is no update from the support team.
I already fixed duplicating issue and also made some changes for API call , I am not sure the changes will work or not.If it works and get no complain from the Inteliquent then i will complete the changes and it will take time.
Hello Nishit thank you for your message, well i’ve started thinking maybe they not understood your question? I will try to get it touch with site administration about possible job closure if support not reply.
Hello Andrey,
May be Support team not understood my question but even then they should ask me to clarify the point.
Hello Nishit you are right, in your #13161 but i think they start replying to you something as we can see some correspondence coming trough.
As discussed in #13160 i have contacted site administration and found some more comments for us to check and repair.
1. There have been wireless numbers notifications coming trough with Number Found message but site admin set auto purchase. So it sounds that site admin set an auto purchase for wireless numbers but system not purchasing numbers.
2. When new rules / notifications created they seemed to be not working as well. Site administrator set a rule for 2222 for every 12 hours but haven’t received any notifications. However they checked with ineloquent account and saw that 2222 numbers are available in the ineloquent system but no notifications received.
Could you please check that Nishit?
Kind regards Andrey -
AuthorPosts
- You must be logged in to reply to this topic.