<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Ted,<div><br></div><div>Good Memory! That is indeed another side effect. When an RP is updated then the associated device is reset. When that device is a RL, a virtual device, there is no observed impact. When that device is a gateway then, well, ....</div><div><br></div><div>/wes</div><div><br><div><div>On May 10, 2012, at 3:54 PM, Ted Nugent wrote:</div><br class="Apple-interchange-newline">I vaguely remember a post about this previously where Wes explained another reason why this is a bad idea. If i remember correctly if you make changes on the RP when it is directly pointed to a trunk it can reset the trunk and potentially drop calls... Wes correct me if I'm wrong on this or am remember something incorrectly.<br>
<br><div class="gmail_quote">On Thu, May 10, 2012 at 3:32 PM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div style="font-size:10pt;font-family:Verdana">Yes, that's an option. But I'd rather not have to modify things to test.<br><br>We have 12 trunk groups and we have had occasion to have to test each of them. Moving things in and out of one trunk group is a bit of work.<br>
<br>Plus, the thought was to 'operationalize' the testing so anyone could test from a phone, and not have to go into the callmanager to make changes.<br><br>But your point is valid.<div class="im"><br><span><br><span name="x"></span>---<br>
Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br><hr></div><b>From: </b>"Scott Voll" <<a href="mailto:svoll.voip@gmail.com" target="_blank">svoll.voip@gmail.com</a>><br>
<b>To: </b>"Lelio Fulgenzi" <<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>><br><b>Cc: </b>"Wes Sisk" <<a href="mailto:wsisk@cisco.com" target="_blank">wsisk@cisco.com</a>>, "cisco-voip voyp list" <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br>
<b>Sent: </b>Thursday, May 10, 2012 3:31:02 PM<div><div class="h5"><br><b>Subject: </b>Re: [cisco-voip] can't add gateway to route group when selected in a route pattern<br><br>just create a test RG. use your special code to that RG and then it's just as simple as moving the GW into this special RG or out into production.<div>
<br></div><div>Scott<br><br><div class="gmail_quote">On Thu, May 10, 2012 at 12:28 PM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-size:10pt;font-family:Verdana">ok. thanks for confirming the behaviour.<br><br>too bad, really. makes for additional work. not too much. but a bit.<div>
<br><span><br><span></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span></span><br></span><br><hr></div><b>From: </b>"Wes Sisk" <<a href="mailto:wsisk@cisco.com" target="_blank">wsisk@cisco.com</a>><br>
<b>To: </b>"Lelio Fulgenzi" <<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>><br><b>Cc: </b>"cisco-voip voyp list" <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br>
<b>Sent: </b>Thursday, May 10, 2012 3:27:02 PM<br><b>Subject: </b>Re: [cisco-voip] can't add gateway to route group when selected in a route pattern<div><div><br><br>That is correct in so far as it has been that way since version 2.4.<div>
<br></div><div>A gw can be in multiple RG. However, only one route pattern can point directly to a gateway. When that configuration the gw is not available for addition to a RG.</div><div><br></div><div>/wes</div><div><br>
<div><div>On May 10, 2012, at 3:18 PM, Lelio Fulgenzi wrote:</div><br><span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><div>
<div style="font-size:10pt;font-family:Verdana"><br>Something that I've been wondering for a while is why, if I assign a gateway to a route pattern, can I no longer assign it to a route group? I like to be able to test trunks individually using special codes, i.e. *9-01-01-number for the first trunk group location and the first trunk. But to do this, I have to create route groups for _each_ trunk first.<br>
<br>Anyone come up with a better way to be able to test each trunk? That is, without having to modify things for each test?<br><br>Lelio<br><br><span><br><span></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it.<span> </span><br> - LFJ (with apologies to Mr. Popeil)<br>
<span></span><br></span><br></div>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></span></div><br></div></div></div></div></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>
</div></div></div></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>
_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div><br></div></body></html>