"They" say it can't be done/happen, but I've seen it so it does. Lets see if our pool of knowledge can answer this one...
Legend R3.0 w/ 4 408 ATL, 007 MLM & unused 012.
3 operators defined. Callers in Vmail selecting "0" are sent to "0". Operator 1 does not answer in ~20 seconds, call "rolls" to operator 2 and/then 3. I cannot confirm ring to 3, but I've witnessed the roll to 2. Extensions associated with operator positions have functioning vmail boxes, and operator calls do not forward to those boxes (so operator call retains its identity as an operator call).
Client wants operators 2 & 3 to be 2 different extensions. Move crossconnects to operator ports, renumber, delete old 2 & 3, add new 2 & 3 and poof, no roll from 1 to 2/3. I cannot find any coverage anywhere defining the 1->2->3 roll, but I saw it happen before the change. Put it back as was, and it's still gone.
I saw this operator roll happen on a new/defaulted Magix out of the box, but dismissed it as a goof. That location only had 1 operator, so the "feature" disappeared once the surplus positions were deleted.
Anyone got a solution? This R3 hates SSA buttons (has no MLX cards and won't allow programming SSAs based on unused ATL or 012 ports). Adding the positions to a hunt group is no good because the calls would lose their identity as operator calls and go to personal mailboxes.
ARRRGGGHHH!!!
Legend R3.0 w/ 4 408 ATL, 007 MLM & unused 012.
3 operators defined. Callers in Vmail selecting "0" are sent to "0". Operator 1 does not answer in ~20 seconds, call "rolls" to operator 2 and/then 3. I cannot confirm ring to 3, but I've witnessed the roll to 2. Extensions associated with operator positions have functioning vmail boxes, and operator calls do not forward to those boxes (so operator call retains its identity as an operator call).
Client wants operators 2 & 3 to be 2 different extensions. Move crossconnects to operator ports, renumber, delete old 2 & 3, add new 2 & 3 and poof, no roll from 1 to 2/3. I cannot find any coverage anywhere defining the 1->2->3 roll, but I saw it happen before the change. Put it back as was, and it's still gone.
I saw this operator roll happen on a new/defaulted Magix out of the box, but dismissed it as a goof. That location only had 1 operator, so the "feature" disappeared once the surplus positions were deleted.
Anyone got a solution? This R3 hates SSA buttons (has no MLX cards and won't allow programming SSAs based on unused ATL or 012 ports). Adding the positions to a hunt group is no good because the calls would lose their identity as operator calls and go to personal mailboxes.
ARRRGGGHHH!!!