belpepsi

We have an Avaya Definity System 75 (G3i v1.1-286), software system level is g3v2g.07.0.0.106.

Our voicemail system is a Digital Speech and uses a voice bridge with 16 analog lines to access it.

Last June we had a full system crash and had to restore from tape to a configuration dated 2001. Up to the time of the crash we were able transfer out of a vector to our voicemail system based on a set of parameters (ie Time-of-Day, Staffing Levels, etc).

While a vector today will still transfer to another extension, it will not go off-net (to the voicemail system). We have changed the COR on the VDN's with no apparent success. We can only guess that there is a system wide parameter affecting the vector transfers or software level has to be higher.

Any help would be appreciated

Thank you
Stephen Fisher
Network Lead

nstephens8

Have you checked the COS settings?

Restrict Call Forwarding Off-Net: n
trk-to-Trk Transfer Override: y

PBXtech.info

 

belpepsi

Yes both are exactly like you typed.

fataldata

So are you able to transfer from your extension off-net? In other words if this is a system wide problem, no ext. should be able to transfer off net. Do you get a wave off tone when it attempts to call the Voice Mail. You could run a list trace on the vdn or vector which may provide more info.
Also there is a parameter on page 4 of display system parameters customer options for off-net forwarding.

__________________
Systems In Use:
S8700 CM3.0 and S8710 CM3.1.1

belpepsi

To answer your question, we can get to voicemail no problem and can even transfer off net to a cell phone, but we cannot transfer off net while in a vector.

As for trying to use a list trace, we are handcuffed as that is not an option on our system and we think that is because we cannot access our system as craft.

PBXBear

Check the COR of the VDN and check COS 1...because...

I remember running into a similiar issue (though not exact) about a year ago, and after troubleshooting with AVAYA we learned that VDN's have a default COS 1 (do a "list extension-type [VDN] to see this). You can't change the COS that VDNs use, thus you may have to change the permissions of COS 1. This can be a big hassle, as if all of your end users are 1 and you don't want them to have the same COS permissions - you're going to have to migrate all the users to a different COS.

We migrated all of the users to COS 2, and use COS 1 for VDN and system stations/extensions/objects specifically for this reason.

Fun, fun, fun.

-Chris

PBXtech.info

 

PBXBear

Also take a look at your trunk-to-trunk transfer option in system features. Not sure how your voice mail is set up in terms of integration and trunking. It's possible that the PBX thinks it's trying to do a trunk-to-trunk transfer.