[Mark Hanson]

in reply to: EN Repairs 22 #10288

Hello NIshit thank you for your #10287, can you input a condition so it detects PIN and display it as other orders? Although we believe since you find the cause it will be easy for you to find a resolution for it. Please just let us know when you resolved that so we can test again.

All these errors in this job just holding our back to go ahead with some other improvement tasks so hoping we can fix them all soon.

for #10286 – than you for updates will check these.

For #10282 – we have tried to order trough API -order #21889 but in the order there was no carrier recorded could you please check why it has not recorded a carrier? Please feel free to see the order https://excellentnumbers.com/admin/index.php?ToDo=viewOrders&orderId=21889
Please note we have already added Carrier to this order but when the order come we could see a notice “No Carrier found” we believe you still be able to track the issue.

Cheers

[Mark Hanson]

in reply to: EN Repairs 22 #10285

sure no probs!

[Mark Hanson]

in reply to: EN Repairs 22 #10283

Hello Nishit thank you for your updates will check the API ordering and gat back to you, and wait for your manual orders updates.

Would you also advice on where we are on these now so we can check something else:

Numbers Bulk Edid – RAFed
Import Numbers From File – RAFed

Back End Errors
a) – RAFed
b)
c) – RAFed
d) – RAFed
e) – RAFed
f) – RAFed
g) – RAFed
h)
l) – I made changes regarding this automatic pin generation.
m)
n) – RAFed

Front End Errors
a) –
b) – Rectified
c) –
d) –
e) –
f) –
g) –
h) –
l) –

Improvements

a) –
b) –
c) –

Cheers

[Mark Hanson]

in reply to: EN Repairs 22 #10281

Hello Nishit thank you for your messages,
for your #10279 –

as you now now when creating manual orders on EN, site admin adds some numbers from EN inventory and some from outside. Those from outside – are real phone numbers but they are not on EN inventory and when we add them manulay the system do create the order on EN with this number but site admin manually adds these “out side’ numbers onto telinta so they can be activatable.

Probably those numbers that are on ENB have got a kinda ID that outside numbers do not have and when number gets activated such parameters as Pin, Services, and we found other orders with Carrier info got missing.
So please check if you can find the problem and fix it for us.

for #10280 –
Yes, please feel free to create an order trough API for vanity number, hopefully this will help you to track and detect the problem. Please try to find the cheapest Vanity number to proceed.

Cheers

[Mark Hanson]

in reply to: EN Repairs 22 #10278

Hi Nishit thank you for your reply and updates,
for #10264 we have tested and unfortunately the pin still not being generated while customers ordering trough API is it possible to fix it?

thank you for #10276
looking forward for more updates.
Cheers

[Mark Hanson]

in reply to: EN Repairs 22 #10275

Hello Nishit haven’t heard from you long time, are you alright there?
Cheers

[Mark Hanson]

in reply to: EN Repairs 22 #10274

Hello Nishit, hope you have had a good weekend,
Would you please advice how many tasks left for both BackEnd and Front End, do not worry about Front End Errors(b) we reported to site admin and it seems that they can not find this issue anymore.

You now have updated Backend(h) in task so you can now have a look at that too.
Cheers

[Mark Hanson]

in reply to: EN Repairs 22 #10272

Hello Nishit thank you for your updates, yes we have reported to the site admin about Front End Errors(b) and can not get any more details on this. The team is still searching for a place where this event took place and if found repot back to you if any more details.

At the meantime we shall skip this task and let us go ahead with other errors.
Cheers

[Mark Hanson]

in reply to: EN Repairs 22 #10270

Hello Nishit, for Backend(h) in #10249. we finally got some more information from the EN site admin. As a result we have added more clarity to Backend(h) task. Please read it again and it should be looking much better to understand.

Thank you for your patience with this.
Cheers

[Mark Hanson]

in reply to: EN Repairs 22 #10268

Hello Nishit thank you for your messages,

We have been checking your API investigated issue and resolution regarding vanity numbers if it was the case and the problem resolved finance happy to add more funds to this job to appreciate your time finding and resolving this issue.

For #10266 – thank you for your conclusion will send this to planning and finance to create a job for this request.
For #10267 – the device was iphone please check if it is looking good on iphones.

Cheers

[Mark Hanson]

in reply to: EN Repairs 22 #10265

Hello Nishit thank you for your updates and investigation, good job if it is now working will confirm you here.
Would you please also advice regarding the site admin suggestion to create API tools manager so we can discuss it with finince?

Will check this soon and get back to you.
Cheers

[Mark Hanson]

in reply to: EN Repairs 22 #10263

Hello Nishit thank you for your updates and checking API library,
in #10261 could you please advice if you fixed the issue with the user account/auth key balance?

We have also received a detailed message from EN site admins regarding API work flow please read it below so it may help you to locate the problem.

============================= MESSAGE FROM EN SITE ADMIN STARTS ===============================

The API workflow.
We assuming and rely on your API development that customers uses our API code to display EN numbers on their websites so EN numbers can be purchase from our resellers web source.

All resellers have got their own auth.key

So our reseller’s buyers find EN numbers on each resellers websites then purchase this number on their website and then some resellers manually visiting EN site, finding number that’s been purchased on their website on EN numbers stock and obtain this number using their EN store credit.

In this case orders being generated as usual and our re sellers activate such numbers from their customers’ front end numbers activation page.

However, we have got a re seller whose developers automated such ( Reseller Web – EN Web) purchase process and this numbers showing on EN system as activated and some of them not activated. Those numbers that are not activated EN admin attempts manual activation in this case it generates new client on Telinta but for some reason (most of the time) it does not create a pin code ( not sure if it is missing a code or API calls) and this is why we can not see pincodes in our orders.

On the same note on EN orders such orders do not display service information (you said it has been fixed but it was not) please check.
Also when EN developer started working on EN Repairs we also noted that such orders started missing carrier lookup information, so please fix it.

Summarizing your API flow
The API provide multiple information to our re sellers who can choose which parameters to display and which not but we can not see any data and can not control this API functionality as there is no any API management interface where we could restrict/ allow/ add which information to display and which re seller. It would be also great to see some traceability about what’s been happening trough this API transaction flow, user names, clients, IP, web URL, time etc. Please advice if it is possible to achieve.

============================= END OF THE EN ADMINS MESSAGE ==========================================

Please note last part ( Summarizing your API flow )of the message above and let us know if we can do it for them so we will request new Job for this task.

We also waiting for additional information regarding your Backend(h) in #10249.

for: BTW I am moving on to fronted error for now and #10262 – thank you
Cheers

[Mark Hanson]

in reply to: EN Repairs 22 #10260

Hello Nishit thank you for your question which is very good one, we have forwarded your question to the site admin for more details and get back to you once received more information.

On EN.net suppose to be a API sample code for our remote customers and if it is nit working probably there is something wrong in this entire API library as it should work on EN. net testing page please try to inspect it so the API library is actually functioning. If you meet any issues that will cause you to recode API library please let us know so we could re budget your labor ours.

We also waiting for additional information regarding your Backend(h) in #10249.
Awaiting reply from site admins.

Please keep us updated if any other questions arise about other tasks in bot back end and frond end repair errors.
Cheers

[Mark Hanson]

in reply to: EN Repairs 22 #10254

Hello Nishit for

Back End Errors
L) I made changes regarding this automatic pin generation.
unfortunately it does not work and still when ppl ordering numbers trough EN API library there is no PIN showing up,

Please see screen shot below.
https://webmaklay.com/wp-content/uploads/2023/02/IMG-8e1581d01cc4ded501aee935aaf59b0f-V.jpg

Cheers

[Mark Hanson]

in reply to: EN Repairs 22 #10252

Yes Nishit sorry i forgot to say that we have send your question to the site admins, we are waiting for their reply and get back to you soon.
Meanwhile you can look at an othre tasks to fix.
Cheers

[Author]

Posts