Notification Settings CRSM

[Andrey]

#13127

Sure will do, thank You!

[Andrey]

#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

[Nishit Shan]

#13130

Hello Andrey,

I have fixed both point 1 and point 2 bug, But i want to know is it possible that the voip credential have access to some other one because i have noted a function which i don’t think is written by me. However i have fixed the bug related to your point 1 and 2.

I will suggest you to not make any entry with cron duration less then one minute. I think because we have only purchase system for voip and nanotel , we will catch all number provided by the inteliquent administrator.

[Nishit Shan]

#13131

Hello Andrey,

There was also a functionality i have added after discussion with mark, that functionality was to continues call for api to purchase or reserve the number so admin can not miss any number.Because cron directly doesn’t provide functionality to call a job repeatedly less than one minutes of time interval , we have had to make custom function to call the API repeatedly. Now i am removing that functionality from the code.

[Andrey]

#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

[Nishit Shan]

#13133

Hello Andrey,

Can you please confirm from admin which API key I use from this list (https://ibb.co/vkj07bd)

[Andrey]

#13134

Hello Nishit there should be Nano_crms

[Nishit Shan]

#13135

Hello Andrey,

I am on Nano_crms dashboard but there are also multiple key for API
Check the link : https://ibb.co/3CYdSv6

[Andrey]

#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 🙂

[Nishit Shan]

#13137

Hello Andrey,

Oh, sorry my bad, I dumb thinking you are taking about Nano_crms is new portal instead of thinking that it is name of API.

[Andrey]

#13138

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

[Nishit Shan]

#13139

Hello Andrey,

I have sifted the nanotel crsm on live, ask admin to test carefully. Currently i have deactivated all the entries from nanotel csrm dasboard.

[Andrey]

#13140

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

[Andrey]

#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

[Nishit Shan]

#13143

Hello Andrey,

I have seen the mail text from the intelligent, but there is one thing we should always aware about that we need to purchase maximum desired number as much as we can . The error or reason behind the continues call of api is , because we don’t want to loss the important number so i have to call the API continuously.
As the lady said , she is saying the inteliquent release number once a week or when they have blocks of number . But how we will know which day and which time they are releasing the number , because we are not being notified or any event . If we get any event or anything then we can set our API call on event.

However it needs a deep research to reduce the API call , Because we can not and should not denies there point . 12 call in one second from one url is too much and it increase the server load and it can also cause serve crash.

I am not getting your second point “NanoTel – Wirelss not being downloaded”, Can you please explain it again for me.

[Author]

Posts