Our CVT trial continues. We are investigating connectivity improvements based on the tool's usage so far. Thank you for your help in testing our diagnostic tools. It provides us with valuable information to continue enhancing the tools that you use.

Additionally, I was informed this morning that the Avaya Diagnostic Portal and many of the Avaya web tools are down this morning. The IT team is working on restoring service, and I will send out an update once things are back to normal.

As always, please continue to send me feedback on what you require and what we can do to make supporting Avaya products easier for you.

Additionally, I was informed this morning that the Avaya Diagnostic Portal and many of the Avaya web tools are down this morning. The IT team is working on restoring service, and I will send out an update once things are back to normal.

The Avaya Diagnostic Portal along with Config Validate Tool are all back up and running. Thank you to all for your patience while service was being restored.

As AOS Backbone Engineer, I came across the CVT when searching for info on a new, managed account that came into our vertical. Account was turned over lacking information on configs and we did not have the luxury of time to spend putting it together. The first issue i came across was rather large from my perspective but may not be an issue for most and realize also I may not fall into the intended audience for the tool. However, i wanted to ask and find out:

Currently, The CVT only allows input for requests utilizing Customer FL/Sold To. Can we utilize SEIDs in place of sold to numbers or is there a plan for this capability? I would assume the Sold Tos/FLs are correlated into SEIDs anyways in the software, but wasnt sure. As a service employee, reach is pretty far away from the processes that I know to utilize Sold to's. Obtaining them can be a challenge as we speak SEID, not FL.

Great concept, very well executed..

I am Hopeful it will extend to allow for search input other than FL, but understanding if not.

As AOS Backbone Engineer, I came across the CVT when searching for info on a new, managed account that came into our vertical. Account was turned over lacking information on configs and we did not have the luxury of time to spend putting it together. The first issue i came across was rather large from my perspective but may not be an issue for most and realize also I may not fall into the intended audience for the tool. However, i wanted to ask and find out:

Currently, The CVT only allows input for requests utilizing Customer FL/Sold To. Can we utilize SEIDs in place of sold to numbers or is there a plan for this capability? I would assume the Sold Tos/FLs are correlated into SEIDs anyways in the software, but wasnt sure. As a service employee, reach is pretty far away from the processes that I know to utilize Sold to's. Obtaining them can be a challenge as we speak SEID, not FL.

Great concept, very well executed..

I am Hopeful it will extend to allow for search input other than FL, but understanding if not.

Great suggestion! I have started looking into making the initial selection available either by SEID or FL. I have added it to our feature tracking list.

As AOS Backbone Engineer, I came across the CVT when searching for info on a new, managed account that came into our vertical. Account was turned over lacking information on configs and we did not have the luxury of time to spend putting it together. The first issue i came across was rather large from my perspective but may not be an issue for most and realize also I may not fall into the intended audience for the tool. However, i wanted to ask and find out:

Currently, The CVT only allows input for requests utilizing Customer FL/Sold To. Can we utilize SEIDs in place of sold to numbers or is there a plan for this capability? I would assume the Sold Tos/FLs are correlated into SEIDs anyways in the software, but wasnt sure. As a service employee, reach is pretty far away from the processes that I know to utilize Sold to's. Obtaining them can be a challenge as we speak SEID, not FL.

Great concept, very well executed..

I am Hopeful it will extend to allow for search input other than FL, but understanding if not.

You asked, and we deliver. The ability to enter an SEID directly is now live! Here is a screen capture of what the selection screen looks like:

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.