Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

AAM not recognizing an extension from Cov Path

AAM not recognizing an extension from Cov Path

AAM not recognizing an extension from Cov Path

Aura 7.0 single server, I followed the document to configure AAM, CM and AAM, however when subscriber is calling from own extension then call is transferred to correct VM subscriber, but when call is transferred from cov path then system ask to enter mailbox number.

1. Ext 3001 has VM box --> Ext 3001 calls HG 2500 (AAM) --> AAM play welcome message
2. Ext 3002 is calling 3001 --> Cov Path 1 --> H99 (AAM) then AAM ask for extension number

HG99 x2500 is already in AAR, UDP and Priv Numbering and also trunk numbering is set to private

RE: AAM not recognizing an extension from Cov Path

What's your traceSM show? I'd figure in case 1 it's "from 3001" and that's the trigger to answer with a password prompt.
Case 2 should have a history info header with stuff in there like reason=avaya-cm-call-coverage-because-no-answer or something to that effect.

There's 'send diversion header' and 'support request history' as options in your trunk group. whatever they are, the defaults have always worked for me. And I think in AAMs advanced options for telephony integration there's maybe a choice to perfer diversion headers to history info.

Oh, and presuming this is an initial configuration, make sure your AAM works in the first place. I know it sounds silly, but triple check. Like, can 3001 call, login to the mailbox, send a new message to 3001, hangup, see 3001's MWI on. Call back in, actually get told you have 1 new message, listen to it, delete it, and turn MWI off.

If you've got a solid history-info header from CM-->SM-->AAM that shows the call was for 3001 and was diverted due to coverage and its a new install, i'd suspect AAM.

RE: AAM not recognizing an extension from Cov Path

Is this the only extension acting this way? if so double check aam mailbox is built correctly as well as his station programming.

RE: AAM not recognizing an extension from Cov Path

I may have overlooked at AAR table, removing the duplicated entry has fixed the issue..


Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close