[cisco-voip] Call reversion on CFNA to first party's Voicemail ->Any way around
Lelio Fulgenzi
lelio at uoguelph.ca
Mon Oct 23 00:15:50 EDT 2006
if what you are trying to do is share voicemailboxes on a non-unity VM, they you can try creating a voicemail profile that sends the call to the appropriate voicemail box.
definately not scalable, but it should work.
in version 3.1 or something like that, on the dn configuration page, there was a voicemail box field that worked perfectly for shared voicemail boxes. they got rid of it. :(
----- Original Message -----
From: Nathan Reeves
To: Lelio Fulgenzi
Cc: cisco-voip at puck.nether.net
Sent: Sunday, October 22, 2006 11:52 PM
Subject: Re: [cisco-voip] Call reversion on CFNA to first party's Voicemail ->Any way around
Good thought. Tried the translation pattern but the call still
reverted to Party A's VM after ringout on Party B so back to the
drawing board.
At least Unity allows for alternate numbers on the one VMB. Our non
unity VM however doesn't have this functionality however which is
where I'm getting stung.
Thanks for the reply
On 10/23/06, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>
> as far as I know, there is no way around this. the story goes, it's working
> by design (as it does in other systems I believe) - if you call person A,
> and they have forwarded to person B, the caller would want to leave a
> message for the person they called originally.
>
> me? i say they did this to get prevent shared mailboxes and get you to pay
> more for each VM licence. ;)
>
> i do know that original called party numbers are not maintained with
> translations, so perhaps you can create a translation *77XXXXX with a
> transformation mask of XXXXX and see if that works.
>
> let us know if it does.
>
>[snip]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061023/8b39fced/attachment.html
More information about the cisco-voip
mailing list