<html><body bgcolor="#FFFFFF"><div>Agreed. It seems like H323 is the best in the long term. I was hoping to avoid a change to H323 under pressure like this though. <br><br>…<div>Don't look at me, my iPod maid that spilling mistake.<span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); "> </span></div></div><div><br>On 2010-10-08, at 7:39 PM, Tim Smith <<a href="mailto:smithsonianwa@gmail.com">smithsonianwa@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><div>This is a nice reason for using h323 or even sip now and avoiding ccm manager config and mgcp.</div><div><br></div><div>It has bugged us here in Australia for years in partial E1 configs. </div>
<div><br></div><div>Also hate the lack of call preservation in a fallback!</div><div><br></div><div>Cheers,</div><div><br></div><div>Tim<br><br>Sent from my iPhone</div><div><br>On 09/10/2010, at 2:12, Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca"><a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a></a>> wrote:<br>
<br></div><div></div><blockquote type="cite"><div><div style="font-family: Verdana; font-size: 10pt; color: #000000">I'm thinking that might be the way to go. remove the ccm-manager config command once i've downloaded the config. If I make any changes on CallManager, then I re-issue the ccm-manager config command and reapply the trunk group settings on each serial interface.<br>
<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 (JNHN)<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 id="zwchr"><b>From: </b>"VoIP Guy" <<a href="mailto:ciscovoiper1@gmail.com"><a href="mailto:ciscovoiper1@gmail.com">ciscovoiper1@gmail.com</a></a>><br>
<b>To: </b>"Matthew Loraditch" <<a href="mailto:MLoraditch@heliontechnologies.com"><a href="mailto:MLoraditch@heliontechnologies.com">MLoraditch@heliontechnologies.com</a></a>><br><b>Cc: </b><a href="mailto:cisco-voip@puck.nether.net"><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></a>, <a href="mailto:lelio@uoguelph.ca"></a><a href="mailto:lelio@uoguelph.ca"><a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a></a><br>
<b>Sent: </b>Friday, October 8, 2010 10:48:23 AM<br><b>Subject: </b>Re: [cisco-voip] SRST and dial peers and trunk groups and CallManager MGCP config downloads<br><br>It might just be worth disabling the command ccm-manager config which means that your config should not be overwritten.<br>
<br><div class="gmail_quote">On Fri, Oct 8, 2010 at 3:32 PM, Matthew Loraditch <span dir="ltr"><<a href="mailto:MLoraditch@heliontechnologies.com" target="_blank"></a><a href="mailto:MLoraditch@heliontechnologies.com"><a href="mailto:MLoraditch@heliontechnologies.com">MLoraditch@heliontechnologies.com</a></a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>
<span style="font-family: Arial,Helvetica,sans-serif; font-size: small; color: black;">I don't think you have a choice. The serial port configs are controlled by ccm in mgcp mode its always going to overwrite anything not from ccm when it resets.<br>
<br>
Sent from my Android phone using TouchDown (<a href="http://www.nitrodesk.com" target="_blank"></a><a href="http://www.nitrodesk.com"><a href="http://www.nitrodesk.com">www.nitrodesk.com</a></a>)</span><div><div></div><div class="h5"><br>
<br>
-----Original Message----- <br>
<b>From:</b> Lelio Fulgenzi [<a href="mailto:lelio@uoguelph.ca" target="_blank"></a><a href="mailto:lelio@uoguelph.ca"><a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a></a>]<br>
<b>Received:</b> 10/8/10 10:10 AM<br>
<b>To:</b> voyp list [<a href="mailto:cisco-voip@puck.nether.net" target="_blank"></a><a href="mailto:cisco-voip@puck.nether.net"><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></a>]<br>
<b>Subject:</b> [cisco-voip] SRST and dial peers and trunk groups and CallManager MGCP config downloads<br>
<br>
<div>
<div style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">So here's my scenario:<br>
<ul>
<li>3845/3945 router with two or more PRIs</li><li>PRIs are in MGCP mode using "ccm-manager config" to download configs</li><li>router acts as SRST so MGCP gateways go into H323 fall back</li></ul>
<span>I had tried configuring trunk groups to use with the dial peers so i wouldn't have to duplicate them for each PRI. This worked until the second SRST trigger. So the behaviour was this:<br>
</span>
<ul>
<li>configure trunk group membership on serial interface as instructed by TAC</li><li>configure dial peers to point to trunk group</li><li>trigger SRST, make calls, calls work</li><li>revert back to normal operation</li>
<li>router downloads MGCP config from CallManager, effectively wiping out the trunk group membership on serial interfaces</li><li>trigger SRST, make calls, calls fail because there are no trunk group members</li></ul>
How are others handling this scenario, i.e. you are using MGCP with "ccm-manager config" command and SRST and trunk groups?<br>
<br>
Why wouldn't CCM allow for a trunk group membership command? I even checked on version 7.1 and there's nothing there. :(<br>
<br>
<span><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 (JNHN)<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>
</div>
</div>
</div></div></div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank"></a><a href="mailto:cisco-voip@puck.nether.net"><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank"></a><a href="https://puck.nether.net/mailman/listinfo/cisco-voip"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></a><br>
<br></blockquote></div><br>
</div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>cisco-voip mailing list</span><br><span><a href="mailto:cisco-voip@puck.nether.net"><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></a></span><br>
<span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></a></span><br></div></blockquote>
</div></blockquote></body></html>