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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Attd-console transfer 1

Status
Not open for further replies.
Apr 25, 2003
21
US
Attendant would like to transfer callers to external numbers, however, I was unable to setup a xfer button on her console.

Internally, she uses the hundreds board and then hits release button and callers are transferred automatically. Is there anyway to set her up so that when someone calls she can answer, put on hold, and transfer to appropriate off-campus party?

thanks.



 
This would require you to enable trunk-to-trunk transfering. I highly advise against this for security purposes. However, if your operator knows what she's doing then go for it.

change system-parameters features

then set trunk to trunk transfers to restricted.

Usually the console will have COR 0

Do a :
change COS

put a y in the COR 0 trk-to-trk transfer override field
 
Thanks for responding, but what button would she use to transfer the call?

Why is making this change a security issue?

 
She/he would have the caller on the line, then press start, dial 9 and the number she wants to transfer to and simply hit release.

There has been a scheme going referred to as "social engineering" (wherein the caller informs the attendant that he is with a major LD carrier and they are doing testing.)that makes this a security issue, and that is where people call in and ask the operator to transfer them to extension 9000, this puts them to the Outside operator, hence, 9, outside line, then 00 and they are free to place the call that they desire, usually to some strange place like the Ivory Coast, and the cost can get extremely out of hand....(been there with an overtrusting operator...) And once that transfer is made, oftentimes, the party can just stay on the line after they have finished talking and the operator will come back on for further instruction, meaning you have a trunk that has been in someone's hands for hours...
 
This is one of the many schemes that have been around for years, and I bet if you were to call your operator and ask them to transfer you to extension 9000, they just might. We put out memos and it still happened. The security booklet from Avaya I was not able to find online,for obvious reasons I'm sure, but you most likely have one, and it explains all of the common schemes that have taken place. You'll be amazed at the simplicity of most of them, but they can be costly if you do not have stop gap measures in place.

 
Is there a way to set up 00 and 000 in the ars to bounce back or go to a certain extension? Im going to try it...Im eval like that.
 
Oftentimes you will see them as denied, and the transfer would not be completed, but there is a way in ars digit conversion, wherein you can send it to another destination such as a terminating extension group that you could use for Identification of the origination of the call and then ring one of the members of that group which in turn would be your ultimate destination extension, however you would see on the display ATTENDANT to "TERM EXT GROUP NAME HERE"

Typical term-ext-group is almost like a hunt group however it can ring 4 members (or more, been awhile) simultaneously, similiar to a coverage answer group. Oh the workarounds sometimes....
 
If u have Avaya Toll Fraud Indemty Program, then make sure Avaya takes a look at anything u change concerning trunk to trunk transfer, or u might cancel your toll fraud indemety coverage.
The adment manual says in chapter 20

"Transfer — Trunk-to-Trunk
Trunk-to-Trunk Transfer allows the attendant or user to connect an incoming
trunk call to an outgoing trunk.
! SECURITY ALERT:
Trunk-to-trunk transfer poses a significant security risk. Use this feature
only with extreme caution.
The system provides three levels of administration for this feature: system-wide,
COR-to-COR, and COS.
To administer Trunk-to-Trunk Transfer system-wide, complete the
Feature-Related System Parameters screen. To restrict Trunk-to-Trunk Transfer
on a trunk-group basis, assign COR-to-COR calling-party restrictions on the Class
of Restriction (COR) screen. To allow individual users to control Trunk-to-Trunk
Transfers, assign capabilities on the Class of Service (COS) screen.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top