CUBE Active/Active Config

[KY_]

Hi Everyone,

Is there any way CUBE active/active design model ?Could you please someone explain me sip configuration,

Regards,

Kemal,

[barry]

Hi Kemal

Your question is a bit short on details (call control, ITSP details etc) however in a nutshell, yes this is possible.

I have two 3845 CUBE Gateways that connect to my ITSP and backhaul to CUCM using SIP.

For outbound calls, CUCM has both gateways configured in a Route Group which is configured using the "circular" algorithm.

For inbound calls, the ITSP round robins call into both of my gateways (and will direct all incoming calls to one gateway if one of them fails).

Net result is an active / active configuration for inbound and outbound calls.

HTH. Barry

Barry Hesk

Intrinsic Network Solutions

[KY_]

Hi Barry,

My cube will be works AS5400, I see  only active/standby deployment option,

Call comes from one ITSP when my cube  have a utilization it should do loadbalance to calls,

ITSP have a directly ip reacheble  our cube they will send via cube our side,

[Ayodeji Okanlawon]

+5 to Barry for an excellent idea and explanation. This is how I have my solution working also and its definetly active/active.

Mustafa,

Your issue is not with the CUBE, its what you have told your ITSP or how ITSP is routing calls. You can have active/active as suggested.

1. On CUCM use circular on the Route group for outbound calls

2. Use round robin with your ITSP to send calls to both CUBEs.

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

[KY_]

Thanks aokanlowon ,

I understand fine but i see cisco deployment guide active/active design is not contain, its only active/standbyincluede there,

I want to clarify this, how cube active/active works or configured,

Inbox redundancy

L2 Box-to-Box redundancy

Clustering wişth loadbalancing (I see ıts should be need loadbalancer)

Regards,

[clileikis]

Hi Kemal,

As mentioned above by Barry and Deji, they've listed the most common way to do redundancy with CUBE's.  The benefit of their method is that you can utilize both CUBE's for call processing simulatenously.  If one fails, only 50% of your calls will be affected.  Here is another redundacy option which is available in 15.1(2)T which allows for media preservation if one box fails, however it is an active/standby method of redundancy where one box sits idle (only mirrors traffic/calls on primary CUBE):

http://www.cisco.com/en/US/products/sw/voicesw/ps5640/products_configuration_example09186a0080b40d82.shtml#introhttp://www.cisco.com/en/US/products/sw/voicesw/ps5640/products_configuration_example09186a0080b40d82.shtml#ver8

Signaling preservation is in 15.2.3T. 

HTH,

Chris

[Ayodeji Okanlawon]

clileikis wrote:
Hi Kemal,
  If one fails, only 50% of your calls will be affected.  

Clileikis,

I am sure you dont loose any calls as long as your active/backup CUBE capacity can handle the capacity of the failed cube. From ITSP perspective, all calls will be redirected to the active/fucntioning cube when one of the CUBES fail.

From a CUCM perspective, the same thing happens. CUCM is able to tell if the trunk is down with options ping

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

[clileikis]

Hi Deji,

Sorry should have been more clear, was referring to current active calls when an outage takes place as media is not preserved when a failure occurs.  I agree with your statement that both CUBE's should be sized accordingly to take the full load of the call capacity during an outage.

Chris

[balmain99]

Hello,

how does the ITSP support Active-Active for your incoming? My understanding was that you could not register to the ITSP the same telephone number range from two different cube routers at the same time.

[R0g22]

Hard to tell since ITSP can use a variety of SBC's typically audiocodecs. For your second question, that should be true but it again depends. A single DID can register multiple times. What would differentiate b/w the two will be the "Contact" header and the information contained in it which would be the domain or ip address (location for the endpoint).
But you would see two different DID's linked to two different CUBE's and the ACTIVE/ACTIVE hunting will be done by ITSP preferring one DID first and moving to the second in the event you run out of bandwidth or a complete failure on the first one.