[Nishit Shan]

in reply to: Voip Repair 24 #12697

Hello Mark,

Currently i am working one newly added task so i did not get time to look on wildcard. I will inform about any needed up gradation or anything after completing port out task on user site also.

[Nishit Shan]

in reply to: Voip Repair 24 #12696

Hello Mark,

I was aware about this, that’s why i asked you to contact with support team and you did but they are giving same API method which i am already using in code.
If admin wants real time data then site will be very slow loading.

[Nishit Shan]

in reply to: Voip Repair 24 #12693

Hello Mark,

See the task description

__________________________________________________
Please upgrade existing port out Voip table to more modern look and more efficient functionally.
Please check Inteliquent portout table here and make Voip port out looking close to Inteliquent interface. Please ensure that site admin can track all recent portouts with maximum information break down. Please make sure the Voip portout table has got reliable data and easy to operate.
___________________________________________________________________________

There is only four line task description so i did what i get.

[Nishit Shan]

in reply to: Voip Repair 24 #12691

Hello Mark,

My above message for API was about the response of support team , Our code is using same API which they suggested for.
Good news is that now we are getting all the updated port out list as inteliquent but site speed is still same.
I have made changes on admin port out table and added all the functionality inteliquent have on there page, You can now ask admin to test. If they want to changes existing table design also then they have to give template for the new design otherwise Port out table task is now been completed.

[Nishit Shan]

in reply to: Voip Repair 24 #12689

Hello Mark,

I checked the Support team response for the API and they are naming the same API which i already using.
You know the what the problem is here, First i have to get list of port out data by calling API(orderList) then calling Another APi(orderDetail) to get the portout detail one by one using order number.
The main resaon of long time loading is calling APi(orderDetail) for every order and i don’t think support team can do anything in it.

I made some changes in port out page and integrated export numbers and export orders functionality as it is in inteliquent.You can check and give your feedback as soon as possible, Because i want all the task should be tested as i finish any task.

[Nishit Shan]

in reply to: Voip Repair 24 #12685

Hello Mark,

Send this below message to the Support Team:

————————————————————————————————————
Is there any api url where i can get all these listed detail from one place. Currently i am getting all these detail from multiple interconnected API and it is making web page too slow.If there is any thing i can do to speed up web page loading please suggest.

port_number, pon, submit_date, desired_due_date, confirm_due_date, port_status, tn_quantity, tn_quantity, streetNum, streetName, tn, rateCenter, province, endUser, authName, accountNum, tnStatus, portOutPin, portDt, postalCode, city, streetType
————————————————————————————————————
Mark, you are also free to advise me if you have any idea or input for it.

• This reply was modified 7 months, 3 weeks ago by Nishit Shan.

[Nishit Shan]

in reply to: Voip Repair 24 #12684

Hello Mark,

Check this link for screenshot (https://ibb.co/FhMsb9p). There is a normal entry for end with 8888 it is not wildcard entry. The reason behind getting 1000 number is not wildcard.

[Nishit Shan]

in reply to: Voip Repair 24 #12682

Hello Mark,

I am checking the code for wilcard issue.
How is it possible the same code behave different for different execution time ? If it once worked it should work every time. But i will check the code if there is some issue. Can you please ask for some entry for wildcard so i can also test by adding from my side.

I did fixed the limit 10 digits for the wilcard.

• This reply was modified 7 months, 3 weeks ago by Nishit Shan.

[Nishit Shan]

in reply to: Voip Repair 24 #12678

Hello Mark,

I was started working on new job that’s why i sent you the error code for API response so i can get reason and do fix them.
Currently i am going to work on export functionality like we have on inteliquent.

• This reply was modified 7 months, 3 weeks ago by Nishit Shan.

[Nishit Shan]

in reply to: Voip Repair 24 #12676

Hello Mark,

Thanks for post#12674.
Every thing is ok and safe for now.
There is heavy rain fall in my city that’s why.

[Nishit Shan]

in reply to: Voip Repair 24 #12675

Hello Mark,

Say thanks to support team for API, I think now it is working .

[Nishit Shan]

in reply to: Voip Repair 24 #12672

Hello Mark,

See my city condition right now

https://portal.voip.us/public/temp/WhatsApp%20Image%202024-08-27%20at%2011.32.52.jpeg

• This reply was modified 7 months, 3 weeks ago by Nishit Shan.

[Nishit Shan]

in reply to: Voip Repair 24 #12670

Hello Mark,

check this link :(https://portal.voip.us/public/temp/errorresponse.txt)

[Nishit Shan]

in reply to: Voip Repair 24 #12664

Hello Mark

This link https://portal.inteliquent.com/CustomerPortal/caseSummary.htm you provided is not accessible on my end.
screen-shot: https://ibb.co/tX27tRS

I am not getting your “we are looking on Inteliquent portout table it shows webhook address poiting to voip?” line.

Yesterday i was working on EN site for bug fixing so i did not get time to look on new added task, I will see to day and tell you about the progress.

[Nishit Shan]

in reply to: Voip Repair 24 #12666

Hello Mark,

Do you want same look and functionality as inteliquent for port out upgrade ?
Can you please be specific about your need?

[Author]

Posts