Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Simulation Node List when adding VoIP Site

Please order the simulation node list in alphabetical order when adding a VoIP site.

When you have 5000+ nodes - it's very time consuming trying to find the node in a list that is not sorted...(it's almost a bug rather than a feature request - but support didn't want to treat it as one).

Dave.

Find more posts tagged with

Accepted answers

All comments

wwiley

I agree with savell's request and I would add to that.... when you are adding infrastructure nodes and you select an interface, the whole page refreshes and you have to scroll back down to your device and select the next interface. Thisis very time consuming and frankly annoying.

FormerMember

Ditto savell & wwiley requests...but the most aggravating to me is the Simulation Node, drop-down list and Name cells are too small. It's trial and error to find the nodes I want to add because the qualifying characters of the node name that signify a VoIP router are truncated from view.. It's a crap shoot picking the right node.

Rather than the Simulation Node be a drop-down list limiting selection to only one node at a time (very time consuming), I would like to see a complete node list and be able to select all devices to add like the node list.

wwiley

Please tell me this will be included in the next version of Voip Monitor. This is horribly aggrevating when you have several hundred nodes and you have weed through them all to check the node off. Then once you check the node off, the page refreshes and you have find the node again in order to check the interfaces off, then the page refreshes again, then you have to find the node again in order to check the next interface off, then the page refreshes again, then you have to find the node again in order to check the next interface off, then the page refreshes again, then you have to find the node again in order to check the next interface off, then the page refreshes again, then you have to find the node again in order to check the next interface off... can u see the aggrevation? The time consumption alone is a killer.

savell

This has been a long time in the fixing.

I regard this as a bug rather than a feature request. It's very close to unusable when you have 4000+ nodes. I don't see that we are being unreasonable in wanting this fixed sooner rather than later!

Dave.