yeah that rdb is using an idc table... i already added the dnis to make sure the cpnd data was working on friday...
ya know what i did though not thinking... when i called the # it was giving a message like we get when a # is denied for outbound calling, i wanted to make sure so i went to ld...
ok i have hopefully a quickie...
we recently added (7) 800 #'s for a company... i now almost know how to build out a new acd/dnis... the company comes back and says they need another one (3) weeks later...i've setup the acd exactly like the previous using an avail dnis...
we already have the...
ok i thought i got it... grr... heres what i did... in route 10 which i thought was just for the 800 's for this particular company... i disabled the DNAM (display idc name) and named the 7110 (route 10) dnis to the company, then all calls that came in showed the right name...
however...
here's the only thing i can possibly think of...
ok we have an 800 # for example... which comes in on 4900... and one that comes in on 4909... then routes to acd # 380 ... which shows up on our phones preceeded by RDB #7110 ... the line # is then shown on the display and the dnis is then shown...
you ain't kidding... and the funny thing is the owner of the company still thinks it's "state of the art" ... it still works and so far has met our needs...isnt that the important thing ? haha ur post made me laugh though i tried to tell ya it was ancient... like if the dinosaurs had pbx's...
well i out'd the cpnd for 4900... outed the acd as well, then redid exactly as 4909... and redid the cpnd... still doesnt show the name... just shows the dnis it's coming in as, and the queue # 380... any suggestions greatly appreciated again, i'd rather try and figure this out myself so if...
well rprt is just something for management reports... im gonna try and out the 4900 and re do it with everything the same as the 4909 ... as far as the release this is 8.71
they're all coming in on the same t1 from sprint (all our 800's new and existing route in on the same t) ... all sprint did on their end is build the #'s out on their end, the company is still the resporg for the new toll free numbers... so they built it in their switches to forward to our...
i probably over killed this thread but i figured i'd post alotta info rather then not enough... the xplns are right i just changed what i posted to company... for 4900 the name is ... xxxxxxx (7) letters... 4909 is the origional that has been in place for years and is showing up properly... that...
this is a ancient meridian max btw...
more fun... ok some quick backround information, we had one toll free # for a company in the past, routing to an an acd (#381)... it's all been working great, calls come in they display the company's name and dnis (#4909)... hasnt been touched in probably 5...
well i think i've gotten further then i've got all day... the first orange terminal on the left (of two) apparently is the maintenance terminal, the one that i powered up that has been off for years and years and got nothing but a blank screen... when i entered something for a username and hit...
oh what fun... ok here's what i see... there's actually 3 terminals over there... one is a green terminal screen, which allows for access to the various loads/modifying phone/acd/dnis data etc... the other 2 are orange terminal screens with vt520 on them...
the first one is connected to port...
hah the switch room is non-existant... my desk is adjacent to the switch, and the switch terminal is about 4 feet away... i have the login/password information for that... i just dont know the load to access the password information from... there's nothing written on or near it, cept the maint...
i'll have to run some packet sniffing util to see what port it uses, and have our sys guy force it to accept traffic on our main router... right now i just use a vnc/type deal to come into my computer at work from home and run it on that, which im sure is a possiblity, i was just looking at...
first question, we have an old meridian max system btw, when i login to the mte software (v.8.11) i enter the supervisor id (no password is set), that lets me view queues, agents logged in etc, im trying to get into the system administration mode option #13...and it asks me for a password... i...
how bad of an error is this ? i've seen it a couple times in the past few weeks, everything is still functioning that I can tell though... any suggested resolutions ? Or can someone explain in more details what it means ? thanks for any ideas !
yea it's damn old that's all i know... 10-15 years minimum... i would consider that legacy :p ... what i meant by when i said the other "module" i meant, there's two boxes containing cards and crap, one's got the cpu, the other's got the miran crap... i powered em both off and back on...that...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.