Home › Forums › NT-CRSM › Notification Settings CRSM › Reply To: Notification Settings CRSM
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