[Andrey]

in reply to: Notification Settings CRSM #13144

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.

[Andrey]

in reply to: Notification Settings CRSM #13142

Hello Nishit we have tested your work,
and aslo asked Ineliquent lady to check API calls for us and as she confirmed the API calls have not been reduced please read her email attached: – https://webmaklay.com/wp-content/uploads/2024/11/intlg-1.jpg

Also we tested NanoTel- Wirelss and added 5555 and 6666 as we seen them on Wirelss data base but NanoTel – Wirelss not being downloaded it for some reason.
Can you please check and fix it?

Kind regards Andrey

[Andrey]

in reply to: Notification Settings CRSM #13140

ok thank you Noshit will test it with admin, i hope we wont loose numbers on NanoTel

[Andrey]

in reply to: Notification Settings CRSM #13138

🙂 come on Nishit you are not dumb you are good professional :)!

[Andrey]

in reply to: Notification Settings CRSM #13136

Hello Nishit we have created an API for this site and it is Nano_crms please use that as life. Please let me know if you have done anything from #13129 and #13132.

Kind regards Andrey 🙂

[Andrey]

in reply to: Notification Settings CRSM #13134

Hello Nishit there should be Nano_crms

[Andrey]

in reply to: Notification Settings CRSM #13132

Hello Nishit thank you for your reply, i have had an other discussion with the team from Voip administration and i think i could assured them that you are doing great job. There was a huge problem for them of loosing numbers from telecommunicators and you could resolve this issue at your best performance and now NanoTel gets desired numbers in a good order.

You have done a great work Nishit we just need to find a gold middle between these two issues one of them resolved and team getting good numbers and all of us appreciate that brilliant work you did. This issue arrived from Inteliquent they can see that numbers being taken but they do not want so many API calls from our account as and we need to accept their arguments and satisfy their request without losing our numbers purchasing benefits.

So voip administration have more trust in your and allowed us to turn NanoTel- Wirelss work turn on to life production mode. So you can now please change NanoTel-Wirelss job to live but please be carefull it captures numbers not too aggressive and please make sure that there is no any potentials of purcasing unwanted numbers as it will cause a HUGE problems for the site admins as Wirelss numbers are very expensive to pay for junk numbers and plus can be big conflict between our customers and telecomunicators. We do not need it to be happends as it will affect our development and servicing tasks.

So long story short:

A. please check all this API issues so we can resolve them as it complained in here https://webmaklay.com/wp-content/uploads/2024/11/intl2.jpg.

B. Please check that there is no notification duplicating scenarios happening as i mentioned to you in #13129 clause 3.

C. Please check that when customer does any changes on voip or nanotel and saves any rules it does saves properly and if we reload the page it still works and saves. Also notification popups when edding or rule creatiion done the message comes up The notification has been saved succesfuly! Customers very nervious when they click save and nothing happening.

For me,
i will ask site admins to check NanoTel- Wirelss job and get all funds released so we can start checking Portout changes and pay for all jobs and go ahead!

Have a great weekend.
Kind regards Andrey

[Andrey]

in reply to: Notification Settings CRSM #13129

Hello Nishit, we have had a loong catch up with project administrations and they declined our offer to switch NanoTel-Wireless on life.

The reasons for that are:
1. We have recived an othre email from Inteliquent you can read this here: https://webmaklay.com/wp-content/uploads/2024/11/intl2.jpg
2. Voip team have been trying to reduce API calls by to changing some chron timings on voip and nanotel. When they change rules on voip and change 6 hours to 12 hours then click SAVE – firstly they can not see any popup message saying changes saved and secondly the rule timing change does not work. We can see that 6 hours changed to 12 but when we refresh the page it shows back 6 hours and this functionality does not work we must to fix it asap as this directly affecting all Inteliquent API calls on NanoTel and we could not reduce API calls as i mentioned in 1).
3. The worse case scenario we noted that when we change anything on voip timing or remove unwanted rules these automaticly creating a rule on NanoTel portal. So what ever work we have done on Voip now you can open NanoTel Notification Rules and see more rules auto generated on NanoTel. We had only few rules on NanoTel for auto purcase and now if you open NanoTel portal you will see almost two pages of unwanted rules because this system bug.

We belive that beause of this it sends more and more requests to Inteliquent and Voip administration worring very much that Intyeliquent will ban them for these bit errors.

Nishit i have spoken with some developers they say that there are too many script copining between Voip and Nanotel which is why system cross multiply and cross duplicate all rules between Voip and NanoTel, this is very risky and we having problems now with Inteliquent.

Please fix it all ASAP it is very serious and also check NanoTel Whirelss if anything similar codded on it before e have got permission to go ahead and continue with this job.
Kind regards Andrey

[Andrey]

in reply to: Notification Settings CRSM #13127

Sure will do, thank You!

[Andrey]

in reply to: Notification Settings CRSM #13125

Got you Nishit i have send site admin request for permission if we can go life and let you know once i got reply from them.

For our next work we may need to think about reducing API calls to Ineloquent as their warn nanotel and Voip administration. THey have already removed repeating rules and notifications from both NanoTel and Voip and now we need to think somthing from our side to reduce API calls to Inteliquent and Peerless.

Please read this warning message from telecomunicator. – https://webmaklay.com/wp-content/uploads/2024/11/intlg.jpg
My thoughts were to create a code so each rule can stop cron calls after purcase.

For example if we’ve got a Notification Rule with 8888 for example that sends request calls every minute but if this rule captured a number 8888 then code pause this cron job for selected period of time for example 15 minutes or 2 hours (admin can control that time frame) which after 8888 notifications resume its cron jobs as set 1 min or other.

This above functionality should reduce API calls from customers sites to Inteliquent and protects them from furthre warnings. Please let me know what do you think about it as you probably have a better idea.

Will wait for site admin permition for life change API from sand box to life allow them to test it again if no issues pay for this job. Then test Port out if all good also pay for Port out job and start new work.

I can see some archive works sitting in the pool from Mark for some reason he requesting an othre developer for some jobs incuding file downloads job. Could you please advice why it is so is it because you can not do it or any other reasons?

Regards Andrey

[Andrey]

in reply to: Notification Settings CRSM #13120

Hello Nishit thank you for your message,
Notifications looking good to me, i think i would change the title in Nanotel notifications instad of Nanotel.In i would leave NanoTel and for wireless notifications i would put NanoTel – Wireless.

Could you please confirm if the NanoTel Wireless is now live or still sandbox?
Kind regards Andrey

[Andrey]

in reply to: Notification Settings CRSM #13117

Hello Nishit feedback from the site admin:
1) please change NANO CMRS to NANO Wireless everywhere
2) We tried to put number search as 2277 and code found this number very quickly.
3) However we used 1 minute chrone and changed to 10 minutes but notifications still coming every minute and this is wrong.
4) Please also make notification messages coming to the email nocely looking so it is easy to detect what notification comes from NanoTel In and when comes from NANO Wireless
Kind regards Andrey

[Andrey]

in reply to: Notification Settings CRSM #13115

Nishit could you please improve the look of wifi notification messages as it look not realy good 😉
https://webmaklay.com/wp-content/uploads/2024/11/SRCM.jpg

[Andrey]

in reply to: Notification Settings CRSM #13113

Ok will tell nanotel admin to check and add possible combinations for testing

[Andrey]

in reply to: Notification Settings CRSM #13111

Hello Nishit any news?

[Author]

Posts