Calls to Aura via vector Messaging step not routing 1

[rep860]

We recently moved from Audix to AAM. We have a couple of call vectors that use the 'messaging' step to put calls into specific voicemail boxes for specific clients. This worked without fail on the Audix. However when we made the changes to push those calls to AAM, the calls are not answered by the vm box, instead you get the AAM access message:
"Hello. if you have a mailbox on this system press #... etc"

We encounter this when dialing in via the public TFN and when using the VDN as shortcut.

We have played around with the various COR (VDN, Hunt-grp) without any perceivable difference.

Any input would be appreciated as we work though this.

Rich

Rich Pederzani
Telecom Engineer

 

[montyzummer]

are all the numbers for your messaging extensions in the public unknown ?

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

 

[rep860]

All extension ranges are listed in the table. Do they need to be added to the specific SIP trunk for AAM as well? Making two entries for each extension range, one for the default trunk they come in on and one for the SIP trunks feeding AAM?



Rich Pederzani
Network Engineer
Avaya & Microsoft Lync

 

[rep860]

Solution found. Thanks to Monty for putting me back onto the numbering plans. The problem was not with the public-unknown, but with the private-numbering. Once we added Ext Len 5 and Ext Code 58 (to cover the VDN routing to the vector that sent the calls to messaging), it worked.

Thanks again,

Rich Pederzani
Network Engineer
Avaya & Microsoft Lync

 

[montyzummer]

cool glad you sorted it

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