<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: verdana,helvetica,sans-serif; font-size: 10pt; color: #000000'><br>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.<br><br>Cheers.<br><br><div><span name="x"></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst, Network Infrastructure<br>Computing and Communications Services (CCS)<br>University of Guelph<br><br>519‐824‐4120 Ext 56354<br>lelio@uoguelph.ca<br>www.uoguelph.ca/ccs<br>Room 037, Animal Science and Nutrition Building<br>Guelph, Ontario, N1G 2W1<span name="x"></span><br></div><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Brian Meade" <bmeade90@vt.edu><br><b>To: </b>"Lelio Fulgenzi" <lelio@uoguelph.ca><br><b>Cc: </b>"Cisco VOIP" <cisco-voip@puck.nether.net><br><b>Sent: </b>Tuesday, April 29, 2014 2:01:25 PM<br><b>Subject: </b>Re: [cisco-voip] loopback SIP trunk for failover calls<br><br>I believe that method should work similarly. You could even try adding<br>CUCM nodes as H.323 gateways even. I've seen some people do it with MGCP<br>PRIs and crossconnect between 2 PRI ports. There's a lot of ways to<br>accomplish it.<br><br>Brian<br><br><br>On Tue, Apr 29, 2014 at 1:56 PM, Lelio Fulgenzi <lelio@uoguelph.ca> wrote:<br><br>> OK ... this just clicked. It doesn't have to be a SIP trunk. Can I create<br>> a non-gatekeeper Intercluster trunk loopback?<br>><br>> ------------------------------<br>> *From: *"Lelio Fulgenzi" <lelio@uoguelph.ca><br>> *To: *"Cisco VOIP" <cisco-voip@puck.nether.net><br>> *Sent: *Tuesday, April 29, 2014 1:53:34 PM<br>> *Subject: *loopback SIP trunk for failover calls<br>><br>><br>><br>> We've built SIP trunks to our Nuance Speech Attendant servers, but have<br>> been told that in order to ensure failover in the event the servers are not<br>> responding, we need to build a loopback SIP trunk back to the CallManager<br>> servers so the call is handled.<br>><br>> I'm not sure of all the SIP parameters we need, I'm gonna start with<br>> defaults, but heeding the old rule of "never allow a trunk to dial a number<br>> that can reach itself" I was going to do the following:<br>><br>> - create a SIP trunk with all cluster members as Destinations<br>> - check "Run On All Active Unified CM Nodes"<br>> - create a "SIP Loopback" partition and put only that partition into a<br>> "SIP Loopback" search space<br>> - in the "SIP Loopback" partition, create a translation for each route<br>> pattern with the failover destination<br>><br>> Any thoughts, will this give me what I need?<br>><br>><br>> Thanks, Lelio<br>><br>><br>><br>> ---<br>> Lelio Fulgenzi, B.A.<br>> Senior Analyst, Network Infrastructure<br>> Computing and Communications Services (CCS)<br>> University of Guelph<br>><br>> 519‐824‐4120 Ext 56354<br>> lelio@uoguelph.ca<br>> www.uoguelph.ca/ccs<br>> Room 037, Animal Science and Nutrition Building<br>> Guelph, Ontario, N1G 2W1<br>><br>><br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> cisco-voip@puck.nether.net<br>> https://puck.nether.net/mailman/listinfo/cisco-voip<br>><br>><br></div><br></div></body></html>