| Ahh yes the powerful DMS / SL-100 TRAVER (translation verification) tool would be an awesome addition to the meridian 1 world.
A traver would allow one to "simulate" a call via the tty through Nars/Bars and see the call software wise step by step through the NCOS, FRL, DMI, RLI, ENTR specific items, etc...and "see" the results of the calls with possible trunk routes in order with appropriate digits being output etc. An excellent troubleshooting tool for users of Nars/Bars...
Also, the ability to post and monitor trunks / lines as in the DMS world.
User accessible remote backups ,,,Would be nice !!
How about DES's on DMI's and RLI's ?
How about a backspace ?
How about a trunk restriction command, to put a trunk in a temporary inbound only mode?
The DMS's also have one up on the diagnostics / maint side of things. Those switches will actually print out a list of possible defective cards during a log / error event and the order it thinks they should be changed in. And in many cases it is correct the 1st time.
The DMS's world's design is also such that very few things can affect the cores from continued processing. Where in the M-1, I have seen instances where one line / phone/trunk etc. can cause a system init or even reload. If there is a problem in a DMS peripheral, the issue tends to stay contained within the peripheral not affecting the core or other parts.
The DMS software seems much more robust and stable as well. Being around both systems for many years,,,the M-1 seems much much more suseptible to software corruption, as in 17 years I've seen in the M-1 dozens of times and not once in the DMS. Come on Nortel !
How about a more user friendly / easier upgrade process ?
Guess which switch I like better ? |