Caller busy, gone to cov pa. I can conference by accident?!

[galwayphoneguy]

The situation is this:
Sta 1111 receives a call, but is busy (appearance on button a). Therefore call goes straight to cov pa and 1111 gets appearance on button b on 6408 handset as green LED. This stays lit for as long as caller is connected to 1111's cov pa. When 1111 user finishes their own original call and hangs up on button a, they can just punch button b and they are automatically into a conference with the outside caller and the cov pa.

Is this normal? I've checked a few stations, and they all seem to work the same way - I presumed that once you went to the cov pa, the path was, er, 'locked'? Or is this a user issue? Should the call stay on the station at button b once the cov pa kicks in? If you were just interrupting a voicemail cov pa I don't think it would be a big deal, but if the cov pa is another person and they're talking to the incoming caller, it's very, er, weird/unprofessional?

 

[ctr999]

There is an PBX-wide option that controls that.

I am not sure what version of Definity you are on, but on my G3rV9, on the system-parameters coverage-forwarding screen, there is an option called "Maintain SBA At Principal?". SBA is Simulated Bridged Appearance. When turned on, and the coverage point answers the call, line b would light up and the original person called could pick up that line. If you set that to no, then line b will not light.

Hope that helps.