Not Following Voverage Path When arded FROM Another PBX

[keschber]

Hi all,

I have an Avaya 5.2 PBX with an extension that covers to a voicemail hunt group. This user has calls that are forwarded to this Avaya extension from another PBX across an ISDN PRI tie trunk. When he receives calls that are forwarded to the Avaya extension from the other PBX, the calls simply ring continously. I can see the call hit the Avaya extension but it never goes to coverage. When I call the Avaya extension directly it does cover to voicemail as it should. Is there a setting that I can change on the Avaya PBX? It seems to me that it would be treated the same whether the call came from another PBX or from the PSTN.

 

[montyzummer]

Is outside call selected as y on the cover path ?

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[keschber]

For Busy, Don't answer and DND/SAC/Go to Cover, outside call is set to Y on the cover path.

What I see when I do list trace sta is the it does vocer but it covers to cover path 0 point 6. I saw some threads about this refering to it being a known issue about path replacement or some type of restricton such at trunk to trunk transfer being denied vis the COR somewhere. I checked all of that but haven't found anything wrong. t-t transfer is on for all and the COR is OK at every step.

We did get this to work when it is forwarded from a differnt PBX. The difference is that on the one the dosn't work the PRI is Qsig and on the one where it does work it is national.

 

[cgogan13]

is this from one Avaya PBX to another? If so, is coverage after forwarding turned on (station form of the extension you are forwarding)?

 

[keschber]

The solution was that QSIG/SIP Diverted Calls Follow Diverted to Party's Coverage Path? was set to N. We changed it to Y and it worked.