Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PRDN and ATDN mutually exclusive?

Status
Not open for further replies.

frazierr

MIS
Jun 23, 2004
46
US
As a holdover from a previous old old Fujitsu series switch, several of our inbound trunk lines showed on different instruments in the office area. As a result, when the Opt11C was installed this was duplicated. Later, these lines were changed to ATDN to 598, an auto attendant number. Nobody noticed that the ability to punch the button for that line didn't work until recently. The maintenance contractor was in the switch and tried for hours to make them both work (being able to have the inbound calls auto-answered with AA, but also be able to directly choose any of the lines for outbound use) but only made things worse. After a restore of a good backup, we are running again, but it seems that you can have either a PRDN and allow use as private lines, or an ATDN and have the lines answered by Auto Attendant. Is this a limitation (or design feature) of the switch, or shortcoming with the contractor tech not knowing? The lines are set up so the user can dial 7 to get a dial tone and use one of these lines outbound, so having them appear directly on the instrument shouldn't be such a big deal...

Thanks
--Rick
 
You can't have an AA and a DN with the same number.

ie:ATDN 598 would term to AA

to have it appear on the phone you would need an SCR/SCN/MCR/MCN key and I don't think you can have both.
 
Initially these lines appeared (and still do) on various phones as PVR. They worked once upon a time, but now, the user gets a fast busy if they try to select one of the lines.

I suspected from all the trouble the tech was having that we can't have both, but was uncertain because that particular company has been wrong on so many instances in the past I typcally take what they say with a grain of salt.

Thanks
--Rick
 
always good to get a second opinion..the post is right.. a pvr needs it's own trunk and atdn.. as well as a pvr key.. if it was a did you can direct the inbound did to a menu (idc)and still have an internal dn with that dn, they would dial the ac1 or 2 and use a line from a line pool.. they can display any of your numbers they want outbound via the clid table.. there's ways to make things closer to a fugi, but it would take someone with a little more experience... i've never had to restore to remove a program error, that must have been a good one..

john poole
bellsouth business
columbia,sc
 
An ATDN is an indication that these are not PVRs, but rahter the route is set to AUTO=YES. That means there is a ACCD (Route Access Code) and the trunk route can be included in any BARS Route List




~
 
Thanks John, I was hoping you'd reply as well. The vendor that contracting hired seems to have less experience than I do, and I don't know enough to get into much trouble, but I am a fairly quick learner despite my over-the-hill age and can typically understand what they are doing if I see them do it...
Every instance that this vendor has logged into the system looks like they are just casting about trying to find out what is wrong, instead of listening to the described problem and using standard debug techniques to attack it (I spent 20 years in high tech hardware and software design and development, so I guess the engineer pops up now and then...). When it gets to the point they are doing the same things over and over without any result except breaking other things during their side trips, I get all testy because once they break enough things the only way I can trust the switch is by doing a restore. (If they aren't competent to fix the problem without breaking other things in the first place, how can I trust that they are competent enough to get the switch back to even the starting point?) Every time someone logs in and pokes long enough, we lose our connection to the Media card and IP phones go down... [sigh]

What gets my goat is when I request a specific process (like determining if a port is bad on a trunk card by swapping two of them) and they poke around everywhere else for hours, and when I take the switch away, I can determine there really is a hardware malfunction in something under 15 minutes with a simple board swap. sorry about the vent..

I'll take the alternatives up the ladder so to speak, but would guess we'll just use these lines as inbound to the AA, and let users access them only by entering 7 to seize one (like most of our office users need to do). It's time to wean them off of the old standard and get them into normal "real switch" use.

Thanks
--Rick

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top