[cisco-voip] Unity connection - Voicemail playback

[Jose Colon II]

Sorry for the late response to everyone. What I did was go into call
manager and change the order of the voice ports its uses. This successfully
routed the calls to the primary unity app and not across the wan to the DR
site.

Thanks for the reply's everyone. The info helped me figured this out.

On Mon, Feb 16, 2015 at 2:04 PM, Ryan Huff <ryanhuff at outlook.com> wrote:

> Nate,
>
> Admittedly, not very clear.
>
> The design strategy I'm referring to is with the use of Digital Networking
> (
> http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab10/collab10/vmessage.html).
> The intent wasn't to suggest that you could add ad 3rd node to a 2 node CUC
> cluster.
>
> The reason I didn't suggest forcing a failover in CUC serviceability is
> because I have seen it cause issues with the IVR, where the conversation
> service needs restarted on the nodes.
>
> My recommendation for dropping the ports out of the line group was to
> avoid potential issues with CUC.
>
>
> Thanks,
>
> Ryan
>
>
> ------------------------------
> From: nateccie at gmail.com
> To: ryanhuff at outlook.com; chrward at cisco.com; jcolon424 at gmail.com;
> cisco-voip at puck.nether.net
> Subject: RE: [cisco-voip] Unity connection - Voicemail playback
> Date: Mon, 16 Feb 2015 12:27:44 -0700
>
>
> Ryan,
>
>
>
> When did CUC start to allow more than two nodes in a cluster?
>
>
>
> Jose,
>
>
>
> You can go into the unity connection serviceability and click “stop taking
> calls”  Then there are no configuration changes to deal with, just turn it
> back on when the link is stable.
>
>
>
> -Nate
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Ryan Huff
> *Sent:* Monday, February 16, 2015 12:09 PM
> *To:* Chris Ward chrward; jcolon424 at gmail.com; Cisco VOIP
> *Subject:* Re: [cisco-voip] Unity connection - Voicemail playback
>
>
>
> Jose,
>
> If SIP integrated, easy fix, just point the trunk at the pub (and then
> reset the trunk in CUCM).
>
> If SCCP integrated, you have a few different options and the best option
> depends on how you're setup and if this is a perm. change or just temporary?
>
> If this is just temporary and assuming you have the max amount of ports
> per CUC node, In CUCM I would go to the line group of the SCCP ports and
> drop out the ports that are registered to the CUC subscriber node. Once
> your link is no longer saturated, add the ports back to the line group.
>
> There are some other design strategies that you can look at to help
> mitigate this in the future. For example, you could add an additional CUC
> Subscriber node in the same DC as the publisher (so you end up with a
> subscriber in both data centers). This would allow you to have additional
> ports in the same DC as the publisher.
>
>
> Thanks,
>
> Ryan
> ------------------------------
>
> From: chrward at cisco.com
> To: jcolon424 at gmail.com; cisco-voip at puck.nether.net
> Date: Mon, 16 Feb 2015 18:52:43 +0000
> Subject: Re: [cisco-voip] Unity connection - Voicemail playback
>
> You have to route calls to that node. Right now, either you SCCP ports, or
> SIP trunk are pointing to the Sub. You have to change the priority of the
> trunk or the ports so it uses the Sub first.
>
>
>
> +Chris
>
> TME - Unity Connection and MediaSense
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net
> <cisco-voip-bounces at puck.nether.net>] *On Behalf Of *Jose Colon II
> *Sent:* Monday, February 16, 2015 1:44 PM
> *To:* Cisco VOIP
> *Subject:* [cisco-voip] Unity connection - Voicemail playback
>
>
>
> I have a Unity 10.5 HA setup and the subscriber is at our COLO. Currently
> the link between the two is being saturated so voicemail playback is very
> choppy.
>
>
>
> The question is, how do i force the publisher to handle those requests so
> that voicemail playback is handled inside this location and not at the colo?
>
>
>
> Thanks
>
> Jose
>
>
> _______________________________________________ cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150217/083d5bb0/attachment.html>