[Nishit Shan]

in reply to: Maseter Port Out PIN #13891

Hello Andrey,

All job inside this task page is not yet been completed “Master Port Out PIN and Bulk Edit Numbers Improvment” still have to do.

With your permission i am going to look into both of these task , i will let you know if there will be any questions or confusion.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13888

Hello Andrey,

I want to ask if there is any task listed which should i prioritise or should i go in flow ?

[Nishit Shan]

in reply to: Maseter Port Out PIN #13881

Hello Andrey,
Additionally, users cannot include “-” in the brand name, as the system automatically removes hyphens when searching the brand name in the database.

I’ve updated the brand name to “Matching NPA NXX (305.305 etc)” and added one number — (254) 254-0000 — under the “TEXAS”, “Matching NPA NXX (305.305 etc)”, and its original “New Number” brand. The number now appears in the product listings of all three brands.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13879

Hello Andrey,

Thank you for your feedback.

I reviewed the issue and noticed that the brand not is not matching the expected NPA/NXX format (e.g., 305.305). This appears to be due to the brand name containing a “/” character. Since the system uses the brand name as a URL parameter, “/” is not allowed in the brand name.

I’m currently looking into resolving the issue by updating the brand name.

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

[Nishit Shan]

in reply to: Maseter Port Out PIN #13877

Hello Andrey,

I have fixed the reserve button issue.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13875

Hello Andrey,

Can you please confirm if admin have tested “Top Categories – Widget Sync” , because i need to complete it’s coding if it is correct.

During the initial development of this site, CSS was not as advanced as it is today, and media queries were either not widely adopted or unavailable. This could be one of the reasons behind some of the design limitations we’re observing now. Over the past 3–4 years, web technologies have evolved significantly, which means that some older code may still function, while other parts might no longer perform as expected. That said, I’ll definitely review the current state of the site, but it’s important to keep this context in mind as we assess the design.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13872

Hello Andrey,

I have reviewed the API code and also tested providing all numbers through the getAllNumbers API request. Below is my input accordingly:

As you know, we already have the following APIs available:

getMillionNumbers

getRepeaterNumbers

getDoubleRepeaterNumbers

getVanityNumbers

getX00-X000

getTollFreeNumbers

getXY0-0000

getX00-Y000

getXYY-YYYY

These APIs allow users to fetch their preferred types of numbers. While we can provide access to all numbers through the getAllNumbers API, doing so would place a heavy load on our server, potentially leading to a server crash. Even if the server successfully handles the request, the response time will be significantly delayed, which could result in a timeout error for the API user.

Considering we have over 90,000 numbers in our database, returning all of them in a single request is neither practical nor advisable. For this reason, I currently limit the getAllNumbers API response to 500 numbers at a time.

Our documentation includes detailed explanations of each API’s request and response structure. However, if an API user requires specific data not covered by the existing APIs, we are open to creating a new, dedicated API for that purpose.

Although we already offer APIs to fetch specific number types like Repeater and Million numbers, I am open to discussing any new ideas or suggestions you may have—especially if they align with customer needs.

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

[Nishit Shan]

in reply to: Maseter Port Out PIN #13871

Hello Andrey,

Can you please confirm site speed is now ok, because you are saying me to go ahead with APi . So should i look forward for site speed or API.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13866

Hello Andrey,

Can you please confirm, if there is any changes on server side because i have noticed an strange thing. The ftp which was not working from a long time is now working.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13865

Hello Andrey,

I will check that reason and get back to you , although today i was not working on EN because i was looking on API and looking for the solution as per your need. I have some comment about it , which i will mention in few hours in next message.

I will check site speed and fixed it.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13862

Hello Andrey,

Since I was in the middle of ongoing work, I haven’t had the chance to fully investigate the issue with the “Reserve” button yet. However, I have confirmed that it is not related to our previous changes regarding the amount display. I will look into the issue and apply a fix accordingly.

Meanwhile, I have completed the code for the “Top Categories – Widget Sync” feature. Please review and test it. Once I receive your feedback,Then only i will finalise and wrap up the the code on my end.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13859

Hello Andrey,

I have checked the api code and there is no issues, to prevent site speed issues i have default limit of 500 and therefor you might not getting all number with the “Million Numbers” and “Repeaters”. Although there is seperate API for all the specific number brand. getMillionNumbers, getRepeaterNumbers, getDoubleRepeaterNumbers, getVanityNumbers, getX00-X000, getTollFreeNumbers, getXY0-0000,getX00-Y000, getXYY-YYYY is our different API , so customer can user these API to get there desired number insted of calling getAllNumbers APi.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13858

Hello Andrey,

I have made changes about amount display on home page, there was problem after login before login is was displaying correctly.it was displaying correctly before login so i was thinking it is working and this confusion taken my my time otherwise it was a quick error.
Now i am going to check API bug and then will update you about it .

[Nishit Shan]

in reply to: Maseter Port Out PIN #13854

Hello Andrey,

please find post-13853

[Nishit Shan]

in reply to: Maseter Port Out PIN #13853

Hello Andrey,

I will check customer’s complain about API and home page’s price display issue and then i will get back to you as soon as possible.

[Author]

Posts