<br><font size=2 face="sans-serif">Do you have to send the leading 9 to
the Telco? I think you can use num-exp 911 9911 or vice versa so
that you don't have to create double dial peers for 911. </font>
<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>
<p><font size=1 face="sans-serif">02/09/2007 11:12 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">"Lelio Fulgenzi" <lelio@uoguelph.ca>,
"Robert Kulagowski" <bob@smalltime.com>, <CarlosOrtiz@bayviewfinancial.com></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif"><cisco-voip@puck.nether.net></font>
<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] Dual PRI Config</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2>Never mind, I put it on the serial interface. Not sure
if that works, but i'll test it later.</font>
<br><font size=3> </font>
<br><font size=2>I was wondering, however, I'd like to be able to route
911 calls over two FXO ports first, and then if required across the digital
trunks.</font>
<br><font size=3> </font>
<br><font size=2>Doesn't look like I can add an interface to multiple trunk
groups.</font>
<br><font size=3> </font>
<br><font size=2>Anyone have an idea how I can accomplish this using trunk
groups?</font>
<br><font size=3> </font>
<br><font size=2>I can always create multiple dial-peers for the 911 dialing,
but that's still 2 dialpeers for each port (911 and 9911) so 8 dial-peers.</font>
<br><font size=3> </font>
<br><font size=3>--------------------------------------------------------------------------------<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:lelio@uoguelph.ca><font size=3 color=blue><u>Lelio
Fulgenzi</u></font></a><font size=3> </font>
<br><font size=3><b>To:</b> </font><a href=mailto:bob@smalltime.com><font size=3 color=blue><u>Robert
Kulagowski</u></font></a><font size=3> ; </font><a href=mailto:CarlosOrtiz@bayviewfinancial.com><font size=3 color=blue><u>CarlosOrtiz@bayviewfinancial.com</u></font></a><font size=3>
</font>
<br><font size=3><b>Cc:</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> Friday, February 09, 2007 10:52 AM</font>
<br><font size=3><b>Subject:</b> Re: [cisco-voip] Dual PRI Config</font>
<br>
<br><font size=2>i get the following error. :(</font>
<br><font size=3> </font>
<br><font size=2>any ideas? </font>
<br><font size=3> </font>
<br><font size=2>3640-vgw(config)#voice-port 3/0:23<br>
3640-vgw(config-voiceport)#trunk-group uogdev_pstn_tg 1<br>
Error: Failed to add port to trunk group<br>
Only analog voice ports can be added to<br>
trunk groups in the voice-port mode.<br>
Configure in cas-custom mode or serial interface<br>
mode as appropriate to add digital ports</font>
<br><font size=3>--------------------------------------------------------------------------------<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:bob@smalltime.com><font size=3 color=blue><u>Robert
Kulagowski</u></font></a><font size=3> </font>
<br><font size=3><b>To:</b> </font><a href=mailto:CarlosOrtiz@bayviewfinancial.com><font size=3 color=blue><u>CarlosOrtiz@bayviewfinancial.com</u></font></a><font size=3>
</font>
<br><font size=3><b>Cc:</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> Friday, February 09, 2007 10:37 AM</font>
<br><font size=3><b>Subject:</b> Re: [cisco-voip] Dual PRI Config</font>
<br>
<br><a href=mailto:CarlosOrtiz@bayviewfinancial.com><font size=3 color=blue><u>CarlosOrtiz@bayviewfinancial.com</u></font></a><font size=3>
wrote:<br>
> <br>
> I usually use MGCP but I am not working at a place that is using H.323
<br>
> on their gateways (been a while for H.323) . They are adding
a second <br>
> PRI to an office and want to set this up to increase <br>
> capacity/redundancy. Is it still typical to use the dial-peer
<br>
> preference command to select the preferred outbound PRI. Is
their <br>
> another way such as trunk group or soemthing like that?<br>
<br>
Here's a snippet from GWGK:<br>
<br>
"<br>
Influencing Path Selection > Using Trunk Groups<br>
Using Trunk Groups<br>
<br>
BRI, PRI, and CAS interfaces and FXO, FXO, and Ear and Mouth (E&M)
voice <br>
ports can be combined into trunk groups. When you create a trunk group,
<br>
you can add configuration to control path selection. Create a trunk <br>
group with the global trunk group name command. This puts you in trunk
<br>
group configuration mode. You can then add commands that will apply to
<br>
all the circuits in the group. The max-call voice number command limits
<br>
the number of incoming and outgoing calls that the trunk group will <br>
accept. By default, the least-used trunk is selected when the gateway <br>
hunts through a trunk group. You can change this with the hunt-scheme <br>
command. This command has the following options:<br>
<br>
*<br>
<br>
least-idle [even | odd | both]— Looks for the most
recently <br>
released channel.<br>
*<br>
<br>
least-used [even | odd | both [up | down]]— Is the
default hunt <br>
method for a trunk group. It looks for the trunk member with the most <br>
unused channels.<br>
*<br>
<br>
longest-idle [even | odd | both]— Looks for the
trunk member that <br>
has been idle the longest amount of time.<br>
*<br>
<br>
Random— Chooses a trunk member at random and a random
channel <br>
within that trunk member.<br>
*<br>
<br>
round-robin [even | odd | both[up | down]]— Looks
at trunk group <br>
members in a round robin fashion, one after the other.<br>
*<br>
<br>
sequential [even | odd | both[up | down]]— Always
starts looking <br>
for a free channel with the highest priority trunk.<br>
<br>
In each command, even selects even-numbered channels within a trunk <br>
member first, odd selects odd-numbered channels within a trunk member <br>
first, and both considers all channels for selection. The option up <br>
hunts through the channels in ascending order, whereas the option down
<br>
hunts through them in descending order.<br>
<br>
Add an interface or voice port to a hunt group with the trunk group name
<br>
[preference] command. The preference value indicates the priority of the
<br>
trunk within the group. A lower preference value equates to a higher <br>
priority trunk. You can then assign multiple trunk groups to dial peers,
<br>
with a priority value to determine their use by the dial peer.<br>
"<br>
<br>
Personally, since I don't don't want to do any fancy load balancing or
<br>
selection, I just use the preference command instead of trunk groups. <br>
Once one PRI is totally full it'll start using the next one, which is <br>
fine by me.<br>
_______________________________________________<br>
cisco-voip mailing list</font><font size=3 color=blue><u><br>
</u></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 color=blue><u><br>
</u></font><a href="https://puck.nether.net/mailman/listinfo/cisco-voip"><font size=3 color=blue><u>https://puck.nether.net/mailman/listinfo/cisco-voip</u></font></a><font size=3><br>
</font>
<br>