[cisco-voip] No MWI - QSIG trunk between CCM and Avaya S8700 with Unity VM

[Brian]

In Unity, 71098 MWI on & 71099 MWI off.

I need to clarify our setup.  We have 2 CallManager clusters and an Avaya
s8700.

It goes Unity>CCM_51>Intercluster Trunk>CCM_41>QSIG>Avaya s8700.

How does this configuration impact the CSS's?

CCM_51 - Has MWI_CSS, with the CCM_51 device partitions and the partition
that the route patterns (using the intercluster trunk) are in.

CCM_41 - Has MWI_CSS, with the CCM_41 device partitions and the partition
that the route patterns (using the QSIG trunks) are in.

Shouldn't we be able to dial the Avaya's MWI on code (*50) followed by an
Avaya phone to light MWI, all from a phone on the CCM_41 cluster?

Thanks.
Brian

On 8/23/07, Wes Sisk <wsisk at cisco.com> wrote:
>
>  In unity what DN is configured for message waiting?
>
> QSIG MWI works like this with Unity/CM:
>
> Unity MWI port (high port usually) goes offhook and specifies calling
> party number = the DN to light MWI for and called party = MWI on number in
> CM.
> When the call reaches the MWI on number CM recognizes this as an MWI
> request and converts the SCCP call to a QSIG call with necessary APDUs.
> Effectively this alters the call so the calling device is the MWI on number
> and the called party number is the DN to light MWI for.
>
> At this point the MWI CSS must contain a route pattern that points to a
> QSIG enabled route list that points the gateway and trunk that provides the
> QSIG link between CM and PBX.
>
>
> Net result - are your DN's, CSS, and route patterns correct?
>
> /Wes
>
> Brian wrote:
>
> We have an environment with CCM 5.1(2)b and an Avaya S8700 connected via
> QSIG PRI's.  We would like to convert some of the Avaya sets to a Unity
> voicemail box.  I have successfully been able to leave and retrieve
> voicemail's on the Avaya phones that have a Unity VM.  However, I am unable
> to get MWI to work.  In the Avaya world, *50XXXX turns on MWI and #50XXXX
> turns it off.  I've created route patterns to point to the Avaya, but can
> not get the MWI to light.
>
> Does anyone have a similar environment where this is working?
>
> Thanks,
> Brian
>
>
> ------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.nethttps://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070823/d11a57f5/attachment.html