[Nishit Shan]

in reply to: Custom Features #11324

Hello Mark,

Thank you for information on “Voip Repairs 23”

Work in progress for DID number’s listing and DID numbers Advance searching.

[Nishit Shan]

in reply to: Custom Features #11321

Hello Mark,

Thank you reply.

I am making changes for Api request for advance search and found that we can not use all fields for search numbers from advance search form to send search request to telinta API. We can use NPA, NXX, LINE, State and Note to search from Telinta API.
Here is the link of request field list for Telinta API (https://prev.portaone.com/docs/PortaBilling_API.html#GetAccountListRequest)

[Nishit Shan]

in reply to: Custom Features #11318

In addition
The user current functionality is showing the numbers tables only for the Activated numbers and its settings.
So as per your instruction on #11316 (c)&(d) also have to make the same listing and setting functionality for Pending and DID Numbers. And it will take much time and effort to develop such functionality like current listing of active numbers from user-home page for Pending and DID Numbers.

• This reply was modified 2 years, 3 months ago by Nishit Shan.

[Nishit Shan]

in reply to: Custom Features #11317

Hello Mark,

Thank you for this update,

I am currently working on Advance search functionality changes from Intelinqent to Telinta. Should any fields will mandatory for the advance search?
And I will also change the color of Return Values window selection.

[Nishit Shan]

in reply to: Custom Features #11313

Hello Mark,

Thanks for update, Now this will be the change on while search functionality into custom search Task for API side/Back-end requests.

And as instructed for Phone Numbers(https://ibb.co/7py4y35) tab the advance search form always will be open while page load.
And
How can we determine the the Number is on pending status? because fro account list API request there is no field where we can say API to provide only pending Numbers into response.

• This reply was modified 2 years, 3 months ago by Nishit Shan.

[Nishit Shan]

in reply to: Custom Features #11307

correction for #11306

I sent the time and budget to the finance and they said the budget is low as per effort and time spending for tasks.

[Nishit Shan]

in reply to: Custom Features #11306

Hello Mark,

Thank you for update. changes has made for this please review it and if any changes then update me.

Some comments our finance department :

I sent the time and budget to the finance and they said the budget is low as per afford and time spending for tasks.

[Nishit Shan]

in reply to: Custom Features #11303

Hello Mark,

1) Made changes for the Advance search Task. But it gives limited numbers of detail about searched TN.
like
{
“tn”: ‘TN’,
“trunkGroup”: “ATLNGAQSNAN_1790”,
“lata”: “920”,
“rateCenter”: “WALLINGFD”,
“locName”: “WALLINGFD”,
“province”: “CT”,
“tnStatus”: “Pending”,
“cnamDip”: “N”
}
and this will limits us to make functionality for ‘Return value’ field.(https://ibb.co/Rjw0FqQ)
2) And for pagination while we jump on big numbers like when we are on page 1 and if we jump directly to the list page then it gives error (‘{“statusCode”:”414″,”status”:”Large result set without searchId detected. Please contact support team for assistance.”}’). The response provides us searchId but there is no any instruction where we can add the searchId for pagination into request.

[Nishit Shan]

in reply to: Custom Features #11299

Hello Mark,

I added the link on Active Numbers. and changes functionality to open the Active numbers list for click on Active numbers link without refreshing the page.

And working on Assigned numbers inteliquent APi for searching Assigned numbers for Advance search.

[Nishit Shan]

in reply to: Custom Features #11289

Hello Mark,

Firstly, I focused on Voip Repairs 23 task and it’s issue. From tomorrow i will focused on Custom Features.

• This reply was modified 2 years, 3 months ago by Nishit Shan.

[Nishit Shan]

in reply to: Voip Repairs 23 #11288

Hello Mark,

Added progress bar for the port-in functionality.

[Nishit Shan]

in reply to: Voip Repairs 23 #11255

Hello Mark,

Thank you for update.

Just one more question for Port In task – do we have a page where voip customers can see they port in processed numbers? —> No

Checking possibility of loding progressbar.

[Nishit Shan]

in reply to: Voip Repairs 23 #11252

Hello Mark,

Currently the we are getting data of user on User-home page so the telinta connectivity is currently working.

And yes the portin functionality is now working.

[Nishit Shan]

in reply to: Voip Repairs 23 #11250

I just said this as possibility,

And i did not know how the old login page works, as i did not worked on any telinta side login functionality. as i checked code and i found the telita API authentication is working with login id and API token. And the Error is related to the user ID and Password.

[Nishit Shan]

in reply to: Voip Repairs 23 #11248

No, It is not Telinta side error but it is some kind of spam login attempt through old login and password.

But our login functionality is working through API token.

[Author]

Posts