<br><font size=2 face="sans-serif">I think you will still have the same
problem. You probably should remove your other dial-peers first run
the CCM-config and then paste back your H.323/SRST dial-peers.</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Lelio Fulgenzi"
<lelio@uoguelph.ca></b> </font>
<br><font size=1 face="sans-serif">Sent by: cisco-voip-bounces@puck.nether.net</font>
<p><font size=1 face="sans-serif">04/16/2007 08:36 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"john Franklin" <john.thevoipguy@gmail.com>,
<cisco-voip@puck.nether.net></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [cisco-voip] Dial Peer Matching</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2>I'd like to configure my two FXO ports as MGCP, but this
note talks about not using CCM config. Can I still use the CCM config statements
to control the PRIs and then manually configure the FXOs?</font>
<br><font size=3> </font>
<br><font size=2>--------------------------------------------------------------------------------<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>
...there's no such thing as a bad timbit...</font>
<br><font size=3>----- Original Message ----- </font>
<br><font size=3><b>From:</b> </font><a href=mailto:john.thevoipguy@gmail.com><font size=3 color=blue><u>john
Franklin</u></font></a><font size=3> </font>
<br><font size=3><b>To:</b> </font><a href="mailto:cisco-voip@puck.nether.net"><font size=3 color=blue><u>cisco-voip@puck.nether.net</u></font></a><font size=3>
</font>
<br><font size=3><b>Sent:</b> Wednesday, April 04, 2007 12:45 AM</font>
<br><font size=3><b>Subject:</b> Re: [cisco-voip] Dial Peer Matching</font>
<br>
<br>
<br><font size=3>Steven, yes you are correct... its a stupid bug/feature
by design (in my opinion) but your H323/SRST dial peers have to be in the
config after the MGCP dial-peers (doesnt matter what numerical order, just
after the mgcp peers in a show run). Be carefull not to use CCM config
as this places the MGCP dial peers in after your existing config. </font>
<br><font size=3> </font>
<br><font size=3>John<br>
<br>
</font>
<br><font size=3>On 4/3/07, <b>STEVEN CASPER</b> <</font><a href=mailto:SCASPER@mtb.com target=_blank><font size=3 color=blue><u>SCASPER@mtb.com</u></font></a><font size=3>>
wrote: </font>
<br><font size=3>Installed a site tonight with analog FXO trunks controlled
via MGCP.<br>
Outbound calls worked fine but inbound did not. Looking at a debug of <br>
the dial peers I could see that the inbound calls were matching the<br>
dial<br>
peers that were built for SRST. These were in front of the MGCP dial<br>
peers in the router config.<br>
<br>
Removed the SRST dial peers and inbound worked fine. Added them back
<br>
in and inbound still works ok Now they are after the MGCP dial peers<br>
in<br>
the config. Are dial peers searched on a hierarchical basis? I would<br>
have thought that because the FXO ports were controlled by MGCP the <br>
dial<br>
peers configured for SRST would not have been used.<br>
<br>
<br>
<br>
Thanks!<br>
<br>
Steve Casper<br>
Voice Technologies<br>
M&T Bank<br>
(410) 347-6026<br>
<br>
************************************<br>
This email may contain privileged and/or confidential information that
is intended solely for the use of the addressee. If you are not the
intended recipient or entity, you are strictly prohibited from disclosing,
copying, distributing or using any of the information contained in the
transmission. If you received this communication in error, please
contact the sender immediately and destroy the material in its entirety,
whether electronic or hard copy. This communication may contain nonpublic
personal information about consumers subject to the restrictions of the
Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly
or indirectly reuse or disclose such information for any purpose other
than to provide the services for which you are receiving the information.
<br>
There are risks associated with the use of electronic transmission. The
sender of this information does not control the method of transmittal or
service providers and assumes no duty or obligation for the security, receipt,
or third party interception of this transmission. <br>
************************************<br>
<br>
_______________________________________________<br>
cisco-voip mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:cisco-voip@puck.nether.net" target=_blank><font size=3 color=blue><u>cisco-voip@puck.nether.net</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank><font size=3 color=blue><u>https://puck.nether.net/mailman/listinfo/cisco-voip</u></font></a><font size=3>
</font>
<br>
<p>
<hr>
<p><font size=3>_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
https://puck.nether.net/mailman/listinfo/cisco-voip</font><font size=2><tt>_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
https://puck.nether.net/mailman/listinfo/cisco-voip<br>
</tt></font>
<p>