HCJes

This is why I keep records of everything. I export everything to word and then label it. I have dones this for my Electronic Switch Network, Speed Call List, Group Call List, ect.

slagburn

Ok here’s my wish list, bear in mind most of these are things I would like to see in future releases some may already be out in 3.0 / 4.0 and I don’t know about it so feel free to enlighten me. I also understand that it simply might not be feasible to implement a lot of the stuff I wish for. And on a final note… we all know we can make the PBX do just about anything with auxiliary processors and applications; this list is about the stuff that should be a part of a basic PBX… I’m not buying 79 symposium servers just to look at one little thing.



[RANT ON] [BITCHING ON] [PERSONAL OPINIONS ON]



Basically I want the Nortel PBX / CS / (whatever it is now) to do anything I want it to when I want it to do it but not do some of the things I don’t want it to do while it’s doing some of the things I wanted it to do. Does that sound like a good customer request?



LD 2… can we make this look and feel more like the admin overlay that it is? Ever tried teaching LD 2 to a newbie? Granted most things are set and forget in there but it’s still an admin overlay, make it look and behave like one.



I want the ability to toggle hard call forward from the CLI via LD 10/11/20 ala what the 100s can do… not DISA+SPRE+whatever.



LD 80… can we get the enhanced trace to keep working after we exit the overlay? When you setup enhanced trace you have to specify a time period but when you leave the overlay it stops… At least mine do.



ACD stuff… lets make another command in LD 22 that lets you stat an ACD queue to see which agents are logged in; I hate having to DNB the queue and then stat every card to figure out who is logged in.



Can we please get FROA (First Ran On Arrival) to do just that? I’m not sure what folks who originally created the command had in mind but it doesn’t do what it says it does although it sort of does… Plenty of use for an absolute RAN on arrival regardless of queue status in situations where callers must be told that they are being recorded without doing a separate NRT / NCFW queue which I’ve found causes problems when you have a lot of queue overflow happening.



How about some more flexibility in reporting options? Yeah I know Nortel (and others) make money on auxiliary processors / applications but customers with small queues and a few agents aren’t gonna pay the price of another PBX to get this ability. In many cases around here they will flat out go with another manufacturer of small systems that gives them more flexibility rather than be financially bent over by the Nortel way.



I want to be able to have options for ACD agent CDR, currently CDR will peg against the ACDID and from what I’m told can’t be changed to peg against lets say the PDN… which is what the CLID goes out as. I’m in a situation where my TMS uses CLID trace through out the network to put CDR records together, it does not do dialed number trace so I’m screwed with a bunch of records at other sites that can’t be traced because I have a CDR record that says one thing and CLID that says something else. I can modify the CLID to match the ACDID but then I have to put a stop to it before it gets off the net.



LAPW… I would like the ability to give print only to some overlays and full access to others under one LAPW, currently print only is a COS that affects the entire LAPW. An example of this is that I don’t want my techs making changes in ESN, CDB, TRK, or RDB overlays but want them to be able to print stuff… in the case of CDB, TRK and RDB this is possible since LD 21 is used to print this stuff, in case of ESN I have to create another LAPW (which they always forget) with a PROA COS to allow them to look at stuff. I don’t think it’s out of the question to break out each LAPW so I can specify which overlays have full access and which ones are print only.



In LD 90 I would like it to print broken out NXXs / NPAs based on the 3 digit code, currently if I print NXX xxx and it happens to be broken out I have to print (or guess) the entire NXX database to actually see the break outs. DNs and TNs will print based upon short inputs so I think NXXx,NPAs and SPNs should too.



I’d like to see something in ESN that lets me work backwards, lets say I have a DMI table and I want to know which RLIs use it… currently I have to print every RLI and look for it, some of my sites have hundreds of RLIs and although I can search for it in Word I would rather have a simple CLI command that would tell me this stuff on the fly. Same goes for RLIs, I would like to be able to enter an RLI and see what and where it’s being used rather than have to print everything and search for it.



Yet another cool thing would be the ability to enter a number in CLI and trace it without making the call… sort of like TRAVER, the output should show everything that happens to that call down to what trunk group it will go out on and what the outpulsed digits will be, great for testing 911 stuff without calling the PSAP all day long.



Hell can we get a linked overlay to 86,87 and 90? Y’all linked 10,11,32 to 20 so I’m sure its possible.



How about linking LD 60 and 96? What a PITA to have to go to one to mess with the DCH, TMDI, MSDL and then back to another one to mess with the carrier portion of a loop and back to the other to undo whatever you did at first.



Lets put a little more information in the DCH MON 0, there is some ok stuff in MON 0 but it doesn’t tell us anything about CPP status or other stuff that most of us have to jump through hoops to figure out while trouble shooting. MON 2 is very useful for additional information but I have yet to find information about what a lot of the IEs mean, those that precede the HEX / ASCII CLNG, CLG etc fields are examples.



This one might be possible I just haven’t found it yet. I want the ability to toggle CPP by route, I know I can do it with a station level COS but there are situations where I want all calls out a certain route to be CPP flagged but not flagged on other routes, in my case public vs private network.



LD 81, I would like to see an enhancement that would break down the Count Sets to show the number of each type of set by loop and shelf along with the grand totals for the entire system.



LD 88 PLEASE FIX THE AUT PRINT TO RETURN TO THE REQ: PROMPT WHEN IT IS DONE PRINTING. Currently it returns to some random area of the memory print and stops.. like so…



CODE CLAS 001



MEM AVAIL: (U/P): 27455923 USED U P: 997217 104168 TOT: 28557308

DISK SPACE NEEDED: 135 KBYTES

2MB BACKUP DISKETTE(S)



This isn’t a big problem for me as I just hit enter but my TMS system expects to see REQ: and hangs because it doesn’t see what it needs to see, also the PBX stops at a random point each time so it’s difficult to get the TMS to figure out when its done. Numerous calls to ETAS have returned the answer that it’s in the software and can’t be patched… IF YOU’RE DOING A NEW RELEASE OF SOFTWARE THEN FIX IT!!!



How about a remote off-site backup command for the large systems? Yeah I know it will probably take awhile over a modem but at least make it an option.


[RANT OFF] [BITCHING OFF] [PERSONAL OPINIONS OFF]

jstyles

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 ?

gwebster

The official "Suggestion Box" for submitting ideas and suggestions for new features and functionality is at http://www38.nortelnetworks.com/nn/ccm/

HCJes

Go SLAG!

I will copy past this post to the link above after it has been around for a few more day.s
Jes

ss

Just had checked this on release 4.0 - all works ok

Rachelle

In additions to all of the great stuff already posted:

I still have interoperability issues with the Day, TOD, and Holiday Automation of Call Redirection and would like Nortel to streamline this feature. You should not have your hands tied like this. You should be able to enter multiple DNs for call termination based on the parameters. This feature needs to be completed. It is incomplete as it stands.


rlc

damo1976

Mine would be a search engine in Symposium's scripting

slagburn

X2 on that!!!