[cisco-voip] Transfer to mailbox, cross-server

[Ed Leatherman]

Thanks for the reply Pat, I was afraid of that. Unfortunately the
extensions are all over the place sequence-wise.

What we'll probably end up doing then is a separate pattern for a few
targeted assistants so they can correctly forward calls to their bosses'
mailboxes, and do some dial plan tricks so they don't have to learn
anything new.

On Thu, May 17, 2012 at 12:26 PM, Pat Hayes <pat-cv at wcyv.com> wrote:

> The problem is, there is no intelligence in your *XXXX pattern. It just
> creates a new call to the voicemail pilot it is configured to and marks it
> as forwarded from XXXX. When Unity or Unity Connection receives such a
> call, it checks the local db to see if XXXX belongs to a user and if it
> doesn't, you get routed to the default greeting. This is the same reason
> that, once you have more than one voicemail pilot, you have to ensure that
> each DN is configured with the correct voicemail pilot. You can't send a
> call for a mailbox on server A to server B. Unity doesn't have any way to
> recognize the call is intended for another server and immediately transfer
> it.  That would be "cross-server forwarding", which is not a feature that
> exists in either product.
>
> There is a solution to this, but it is usually a bit tough to implement if
> it wasn't taken into consideration earlier on. You need two (or more)
> separate patterns, one that routes to one server and one that routes to the
> other. For this to work, though, you need to have separate extension ranges
> for each server. For example, users on server A have 1XXX extensions and
> server B have 2XXX, so you make a *1XXX pattern that points to server A and
> a *2XXX pattern that points to server B. If you have just moved mostly
> random extensions around and there is no easy set/sets of ranges, then you
> are in a pretty tough spot and I don't think there is any straightforward
> way to get *XXXX dialing back until the migration is finished.
>
> On Wed, May 16, 2012 at 8:36 AM, Ed Leatherman <ealeatherman at gmail.com>wrote:
>
>> Good morning
>>
>> I have a fairly standard (I'm guessing) CTI route point/voice mail
>> profile configured for users to directly transfer callers into an arbitrary
>> voicemail box via a "**XXXXX" type pattern. This works just fine w/ regular
>> Unity v8.
>>
>> We now have a Unity Connection server up (8.6) with networking to regular
>> Unity. End goal is to migrate users to the new system and decommission
>> Unity, due to some upper layer challenges we cannot just fork lift move
>> everyone though.
>>
>> All the networking functions work just fine (cross server login, etc),
>> but I can't get direct transfer to a mailbox working cross-server. I can
>> send to a regular unity mailbox, but if I try to transfer to a CUCxn
>> mailbox it send it to main greeting instead. If I make the voice mail
>> profile point to the connection pilot, I get the problem in reverse - can
>> transfer to connection mailboxes but not unity.
>>
>> Does anyone know of a workaround, or is this just something we'll have to
>> live with until we get everyone moved? Have only found one reference to
>> this particular issue out on the netpro forums but it had no resolution.
>>
>> Thanks!
>>
>>
>>
>> --
>> Ed Leatherman
>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>


-- 
Ed Leatherman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120517/8b0bf2e5/attachment.html>