[Nishit Shan]

in reply to: Search Improvnement #14302

Hello Andrey,

I am looking for post #14296, i will update you once i finish or find need to update you.

[Nishit Shan]

in reply to: Search Improvnement #14299

Hello Andrey,

I have checked my and and find there is no difference in the code for 6666 and 9999, if 6666 is working then 9999 for should also work.

• This reply was modified 1 month ago by Nishit Shan.

[Nishit Shan]

in reply to: Search Improvnement #14293

Hello Andrey,

I noticed you sent me a message, but it disappeared. Can you confirm if you deleted it, because it is no longer available?

[Nishit Shan]

in reply to: Search Improvnement #14292

Hello Andrey,

There is being some problem in our side , that’s why i am not able to update you . Yesterday i was updating the full system for the problem fixing. Now everything is fine and working.

Update: I am not currently working on number search as it was completed from my side, If there is still any issues please know me.

Sorry for inconvenience !

[Nishit Shan]

in reply to: Search Improvnement #14288

Hello Andrey,

Please check the link for screenshot (https://ibb.co/1Scz3y2), I made improvement for this list.

[Nishit Shan]

in reply to: Search Improvnement #14285

In addition to my above message, I also want to let you know that I have completed all the improvements I had planned to do from my side.

[Nishit Shan]

in reply to: Search Improvnement #14284

Hello Andrey,

I am working on number serach cron functionality. Can you please confirm about any improvement on number search

[Nishit Shan]

in reply to: Search Improvnement #14280

Hello Andrey,

Everything will continue to work as it was previously. The only change is that the cron job will now run twice and execute two different function scripts separately. This approach removes the dependency on a single function, helping to reduce the overall execution time and allowing the second script to run without delay.

For example, consider a list of wildcard entries. Currently, all wildcard entries are processed through a single function for number reservation. In the updated code, each entry will be handled by a separate individual function. This ensures that one entry doesn’t have to wait for the previous one to finish, thereby improving performance and efficiency.

I hope you understand my point.

[Nishit Shan]

in reply to: Search Improvnement #14278

Hello Andrey,

It’s source code addition.

[Nishit Shan]

in reply to: Search Improvnement #14276

Hello Andrey,

Yes, you are right. We already have individual cron jobs for ******8888, ******9999, ******7777, and *****000, and I am repeating the same by creating another cron job for each of them. That’s why I’m asking if the admin wants to add more patterns, should we also create individual cron jobs for those as well?

[Nishit Shan]

in reply to: Search Improvnement #14274

Hello Andrey,

I have set individual cron jobs for ******8888, ******9999, ******7777, and *****000. Could you please ask the admin if they want individual cron jobs for any other wildcard entries? If so, I will set them up.

[Nishit Shan]

in reply to: Search Improvnement #14272

Hello Andrey,

I am still working on the number search, but I noticed that the purchased number has started working now.

[Nishit Shan]

in reply to: Search Improvnement #14268

Hello Andrey,

Maybe yes, but it should only affect the notification (email).

[Nishit Shan]

in reply to: Search Improvnement #14264

Hello Andrey,

I just want to know if the service provider (Inteliquent) has made any changes to their policies, structure, or anything else that could affect our number purchasing system. Could you please investigate this for me?

[Nishit Shan]

in reply to: Search Improvnement #14263

Hello Andrey,

Thanks for your message, I was saying to check Inteliquent dashboard to check reserve number list and see if there is number being reserved for *******000 format.

[Author]

Posts