[cisco-voip] unity 5 and MIW issue
Erick Wellnitz
ewellnitzvoip at gmail.com
Wed Aug 1 16:32:26 EDT 2012
What I have is:
7151/7152 on/off and for the standby Unity server I see VM ports with the
same DNs. I have changed the Port DNs.
What we're seeing is collisions on the MWI dialout ports so I have
increased the number of those.
I just need enough band-aids and duct tape for 2-3 more months. :)
On Wed, Aug 1, 2012 at 3:19 PM, Jason Aarons (AM) <
jason.aarons at dimensiondata.com> wrote:
> I’ve seen where the MWI On/Off numbers were overlapping
>
>
>
> Eg 1998 on and 1999 off and someone added a phone with extension 19981 by
> accident causing problems. Also check the SCCP ports CSS for problems.
> Used Dialed Number Analyzer as well.
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Erick Wellnitz
> *Sent:* Wednesday, August 01, 2012 4:13 PM
> *To:* Chris Ward (chrward)
> *Cc:* cisco-voip
> *Subject:* Re: [cisco-voip] unity 5 and MIW issue
>
>
>
>
>
> I think we may have found at least part of the problem but I don't know
> for sure because I usually don't work with SCCP ports.
>
>
>
> There shouldn't be a corresponding VM port for the MWI on/off numbers,
> correct?
>
>
>
> On Wed, Aug 1, 2012 at 12:58 PM, Chris Ward (chrward) <chrward at cisco.com>
> wrote:
>
> Doing a quick topic search, I see some similar issues but no resolutions
> (mostly cause there were no traces) or bugs that seem to fit. I suspect
> that it is some type of port issue. You may want to verify that all your VM
> ports are configured exactly the same. Perhaps one has a different CSS or
> something like that.
>
>
>
> Otherwise, trace reading is going to be required to figure out what is
> going on.
>
>
>
> +Chris
>
> Unity Connection TME
>
>
>
> *From:* Erick Wellnitz [mailto:ewellnitzvoip at gmail.com]
> *Sent:* Wednesday, August 01, 2012 1:26 PM
> *To:* Chris Ward (chrward)
> *Cc:* cisco-voip
> *Subject:* Re: [cisco-voip] unity 5 and MIW issue
>
>
>
> 6.1.3
>
> On Wed, Aug 1, 2012 at 12:21 PM, Chris Ward (chrward) <chrward at cisco.com>
> wrote:
>
> What’s your CUCM version?
>
>
>
> +Chris
>
> Unity Connection TME
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Erick Wellnitz
> *Sent:* Wednesday, August 01, 2012 1:12 PM
> *To:* cisco-voip
> *Subject:* [cisco-voip] unity 5 and MIW issue
>
>
>
> I have a bit of a strange issue with Unity 5 UM / Exchange 2010 / SCCP
> ports. The real answer is in the works - move to UCONN 8.6.
>
>
>
> On occasion random MWIs do not turn off when messages are marked as read.
> I have the MWI resynch set to 3 AM every day and I turned off the IPv4
> checksum offload because I read it can cause 'randomness' in MWI turning
> on. Refreshing the MWI on the particular mailbox corrects it for a a
> couple days. Dialing the MWI numbers turns MWI on and off as expected.
>
>
>
> Has anyone else experienced this kind of behavior before?
>
>
>
>
>
>
>
>
>
>
> itevomcid
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120801/3d85b869/attachment.html>
More information about the cisco-voip
mailing list