[cisco-voip] loopback SIP trunk for failover calls

Lelio Fulgenzi lelio at uoguelph.ca
Tue Apr 29 14:03:55 EDT 2014


Wonderful. Will try with SIP trunk first and see how it goes.... I want to try and keep it generic enough to use for all my loopback requirements. 

Cheers. 


--- 
Lelio Fulgenzi, B.A. 
Senior Analyst, Network Infrastructure 
Computing and Communications Services (CCS) 
University of Guelph 

519‐824‐4120 Ext 56354 
lelio at uoguelph.ca 
www.uoguelph.ca/ccs 
Room 037, Animal Science and Nutrition Building 
Guelph, Ontario, N1G 2W1 

----- Original Message -----

From: "Brian Meade" <bmeade90 at vt.edu> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca> 
Cc: "Cisco VOIP" <cisco-voip at puck.nether.net> 
Sent: Tuesday, April 29, 2014 2:01:25 PM 
Subject: Re: [cisco-voip] loopback SIP trunk for failover calls 

I believe that method should work similarly. You could even try adding 
CUCM nodes as H.323 gateways even. I've seen some people do it with MGCP 
PRIs and crossconnect between 2 PRI ports. There's a lot of ways to 
accomplish it. 

Brian 


On Tue, Apr 29, 2014 at 1:56 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote: 

> OK ... this just clicked. It doesn't have to be a SIP trunk. Can I create 
> a non-gatekeeper Intercluster trunk loopback? 
> 
> ------------------------------ 
> *From: *"Lelio Fulgenzi" <lelio at uoguelph.ca> 
> *To: *"Cisco VOIP" <cisco-voip at puck.nether.net> 
> *Sent: *Tuesday, April 29, 2014 1:53:34 PM 
> *Subject: *loopback SIP trunk for failover calls 
> 
> 
> 
> We've built SIP trunks to our Nuance Speech Attendant servers, but have 
> been told that in order to ensure failover in the event the servers are not 
> responding, we need to build a loopback SIP trunk back to the CallManager 
> servers so the call is handled. 
> 
> I'm not sure of all the SIP parameters we need, I'm gonna start with 
> defaults, but heeding the old rule of "never allow a trunk to dial a number 
> that can reach itself" I was going to do the following: 
> 
> - create a SIP trunk with all cluster members as Destinations 
> - check "Run On All Active Unified CM Nodes" 
> - create a "SIP Loopback" partition and put only that partition into a 
> "SIP Loopback" search space 
> - in the "SIP Loopback" partition, create a translation for each route 
> pattern with the failover destination 
> 
> Any thoughts, will this give me what I need? 
> 
> 
> Thanks, Lelio 
> 
> 
> 
> --- 
> Lelio Fulgenzi, B.A. 
> Senior Analyst, Network Infrastructure 
> Computing and Communications Services (CCS) 
> University of Guelph 
> 
> 519‐824‐4120 Ext 56354 
> lelio at uoguelph.ca 
> www.uoguelph.ca/ccs 
> Room 037, Animal Science and Nutrition Building 
> Guelph, Ontario, N1G 2W1 
> 
> 
> 
> _______________________________________________ 
> 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/20140429/3c4fe061/attachment.html>


More information about the cisco-voip mailing list