Avaya Support Forums  

Go Back   Avaya Support Forums > Contact Center Applications

Thread Tools Search this Thread Display Modes
Old 10-18-2012, 02:03 PM
bear67 bear67 is offline
Aspiring Member
Join Date: Oct 2012
Posts: 1
bear67 has 10 reputation points
Default Coverage Paths Not working for UM

I recently worked with an Avaya Business partner to install SBC to allow us to migrate the office 365 and Unified Messaging. We are migrating away from Modular Messaging. However I cannot get an existing auto attednandt which cover to a vector with an option to ring a station cover back to Vmail. If I imbed the VDN number in the name field I can get the "messaging split" vector command to cover to an extension.

Currently a call comes into the PBX cover to UM attendant with an option to transfer to our box office vector where they can transfer to an individual station. The call routes and rings as it should but never goes to cover. If I trace the call you see it leave the vec but you never see it on a trace to the individual station (even though the call rings and can be picked up). The integration of the SBC is SIP and shows the correct header for the call destination. This is SO Frustrating as our business partner cant figure out why this works in MM but wont work in UM. So far I have been this is dual coevrage path but has worked from day 1 of the MM installation. If this does not get solved find me follow me wont work as it should either. I am open to suggestions!
Reply With Quote

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -7. The time now is 08:57 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.