Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avaya CM 6.1 to Session Manager to ESNA Voicemail. No integration from VDN

Status
Not open for further replies.

Zastruga111

IS-IT--Management
Feb 6, 2013
6
0
0
US
All,

When we call into a VDN and then Route-to an extension WITH Coverage, the system sends the VDN or the Hunt group number as the called party.
The ESNA system answers but not with the expected mailbox.

How do we get the correct called number or history information to pass SIP?

Formerly a modular messaging user.
 
So you can call the extension with coverage directly and it works?


We had an issue and what needed to be changed was.
We use aar routing to route the Hunt Group extension for voicemail with a call type of aar? We recently screwed up ours and would get the default greeting "Enter the mailbox number.." rather than the mailbox.

Our solution involved, changing the messaging trunk group to Numbering Format: unk-pvt and UUI Treatment: service-provider and lastly, Support Request History? y

Support Request History may be what you need more than the other options.
 
Thanks Fataldata,

These are all critical settings, unfortunately I have them set as you describe already.
I am leaning towards the thought that Session Manager may be stripping some of the required information.

 
and Yes, we can directly dial the station and get coverage to the correct VM.
In trace the Called number shows up as the VDN or the Hunt group.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top