[cisco-voip] UCM - CUBE trusted IP address

[Anthony Holloway]

It depends on whether or not you are using run on all nodes, where your
endpoints are registered, how you plan on taking server4 out of service,
etc.

Your best bet is to put all CPE IP Addresses into the trusted list so you
will not have any toll fraud blocking going on when you change your SIP
trunk CMG.  Assuming you're not using run on all nodes; which you probably
should be, for the route local benefit.

On Mon Jan 26 2015 at 6:29:31 AM Reto Gassmann <voip at mrga.ch> wrote:

> Hello Group
>
> we run a CUCM Cluster 9.1(2) with a SIP Trunk (CUBE) to our telephony
>  provider.
> Our cluster has 8 Servers (1 Pub / 7 Sub).
> On the CUBE we have three dialpeers pointing to three different subs for
> redundancy:
>
> dial-peer voice 1000 voip
> destination-pattern
> session target ipv4: Server5
>
> dial-peer voice 1001 voip
> destination-pattern
> session target ipv4: Server4
>
> dial-peer voice 1002 voip
> destination-pattern
> session target ipv4: Server3
>
> On the UCM we have a SIP Trunk configured with a device that contains
> Server3, Server4 and Server5 in its CUCM Group.
> All IP Phones register to Server4 or Server5.
>
> We now have the problem that Server4 has sometimes a pretty high CPU load
> (Code yellow).
>
> I want to change the dialpeers on the CUBE so that they point to Server7
> and Server8 to reduce the load on Server4.
>
> What do we have to change on the UCM if we change the dial-peer voice 1000
> and 1001 on the CUBE to
> dial-peer voice 1000 voip
> destination-pattern
> session target ipv4: Server7
>
> dial-peer voice 1001 voip
> destination-pattern
> session target ipv4: Server8
>
> Thanks a lot
> Regards Reto
>
>
> _______________________________________________
> 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/20150126/60a99987/attachment.html>