<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'><br>fyi: I'm pretty sure you don't need to separate the PRIs. a group of PRIs can have many route groups associated with it. in my case, the first 5 are free. <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 id="zwchr"><b>From: </b>"Tim Reimers" <treimers@ashevillenc.gov><br><b>To: </b>"Chris Clouse" <Chris.Clouse@cdw.com>, cisco-voip@puck.nether.net<br><b>Cc: </b>lelio@uoguelph.ca<br><b>Sent: </b>Tuesday, 23 October, 2012 5:51:54 PM<br><b>Subject: </b>RE: [cisco-voip] Adding DIDs to a PRI - and how to limit total calls to those DID numbers.<br><br>
<style><!--
font-face
{font-family:"Cambria Math";}
font-face
{font-family:Calibri;}
font-face
{font-family:Tahoma;}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{
font-size:10.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
<div dir="ltr" id="idOWAReplyText69364">
<div dir="ltr"><font color="#000000" face="Arial" size="2">That does look very much like what I'm considering -</font></div>
<div dir="ltr"><font face="Arial" size="2"></font> </div>
<div dir="ltr"><font face="Arial" size="2">Lelio, I am going to investigate options with the telco as well -</font></div>
<div dir="ltr"><font face="Arial" size="2">One thing I have to determine is whether we want to do a separate PRI and incur that monthly cost.</font></div>
<div dir="ltr"><font face="Arial" size="2">That would give me the option of controlling this from the carrier side as well.</font></div>
<div dir="ltr"><font face="Arial" size="2"></font> </div>
<div dir="ltr"><font face="Arial" size="2">I'm going to try to get this lit up using Hylafax and t38modem as a test platform.</font></div>
<div dir="ltr"><font face="Arial" size="2">Same diagram as below, but I'm going to use Hylafax as a temporary test-FoIP platform to straighten out the Cisco side</font></div>
<div dir="ltr"><font face="Arial" size="2">before moving on to the Rightfax phase of the project: migration-from-old-RF version-to-newest-version-of-RF </font></div>
<div dir="ltr"><font face="Arial" size="2"></font> </div>
<div dir="ltr"><font face="Arial" size="2">Ultimately, this will be a simple</font></div>
<div dir="ltr"><font face="Arial" size="2">PSTN >> PRI >> DID number #1515 (for ex,) >> Cisco 2821 >> H.323 to RightFax SR140 module.</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font face="Arial" size="2">So no real integration with Callmanager or any of that - Just no need to make it that complicated.</font></div>
<div dir="ltr"><font face="Arial" size="2">(unless I'm missing something about how awesomely easy and incredibly flexible and low-cost it would be if I involved UCM in this ....;-)</font></div>
<div dir="ltr"><font face="Arial" size="2"></font> </div>
<div dir="ltr"> </div>
<div dir="ltr"><font face="Arial" size="2">Thanks, Tim</font> </div></div>
<div dir="ltr"><br>
<hr>
<font face="Tahoma" size="2"><b>From:</b> Chris Clouse [mailto:Chris.Clouse@cdw.com]<br><b>Sent:</b> Tue 10/23/2012 3:11 PM<br><b>To:</b> Tim Reimers; cisco-voip@puck.nether.net<br><b>Subject:</b> RE: [cisco-voip] Adding DIDs to a PRI - and how to limit total calls to those DID numbers.<br></font><br></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="COLOR: #1f497d">I would investigate using ‘max-conn’ on your dialpeers.</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"></span> </p>
<p class="MsoNormal"><span style="COLOR: #1f497d">http://www.cisco.com/en/US/docs/ios/solutions_docs/voip_solutions/CAC.html#wp902617</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"></span> </p>
<div>
<p style="MARGIN-BOTTOM: 3pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in" class="MsoNormal"><b><span style="COLOR: black">~Chris</span></b><span style="COLOR: #1f497d"></span></p></div>
<p class="MsoNormal"><span style="COLOR: #1f497d"></span> </p>
<div>
<div style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<p class="MsoNormal"><b><span style="FONT-SIZE: 10pt">From:</span></b><span style="FONT-SIZE: 10pt"> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Tim Reimers<br><b>Sent:</b> Tuesday, October 23, 2012 1:52 PM<br><b>To:</b> cisco-voip@puck.nether.net<br><b>Subject:</b> [cisco-voip] Adding DIDs to a PRI - and how to limit total calls to those DID numbers.</span></p></div></div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Hi everyone –</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I’ve been asked a question that I don’t know if I’ve heard before –</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I have two existing PRI circuits, built as a single trunk group, with about 1000 DID numbers on them, used for voice calls.</p>
<p class="MsoNormal">(for sake of mentioning it, the PRIs arrive on two different routers, and all the DIDs are reachable inbound on either one)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Someone wants to add more DIDs for the purpose of faxing, with those DIDs being dedicated for fax usage, not for voice calls.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">But they want to limit the total number of calls that will be allowed to come in, so that we don’t ‘eat’ all 47 channels with attempted inbound faxes.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">How would I limit the allowable calls coming in to the DIDs 1500-1700 and 2100-2300 ?</p>
<p class="MsoNormal">(assuming 4-digit delivery from the telco)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">One factor that might do it is that the session-target device mentioned below</p>
<p class="MsoNormal">only has two active channels – </p>
<p class="MsoNormal">Would that have the effect of stopping the 3<sup>rd</sup>, 4<sup>th</sup>, etc call and sending them back to the carrier</p>
<p class="MsoNormal">with a busy signal? </p>
<p class="MsoNormal">I don’t want a re-order tone – just busy.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Or would I use the ‘max-conn’ option as shown below under the dial-peer to ensure that</p>
<p class="MsoNormal">no more calls can come in?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I think my dial peers would look like this:</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="COLOR: #1f497d">dial-peer voice 1000 voip</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">description Inbound faxes</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">destination-pattern 1[5-7]..</span></p>
<p class="MsoNormal"><b><span style="COLOR: red; FONT-SIZE: 12pt">max-conn 2</span></b></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">session target ipv4:192.168.200.17</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">session transport udp</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">dtmf-relay h245-signal</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">codec g711ulaw</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">fax rate 14400</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">fax protocol t38 ls-redundancy 5 hs-redundancy 2 fallback none</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">no vad</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">!</span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="COLOR: #1f497d">dial-peer voice 1000 voip</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">description Inbound faxes</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">destination-pattern 2[1-3]..</span></p>
<p class="MsoNormal"><b><span style="COLOR: red; FONT-SIZE: 12pt">max-conn 2</span></b></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">session target ipv4:192.168.200.17</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">session transport udp</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">dtmf-relay h245-signal</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">codec g711ulaw</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">fax rate 14400</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">fax protocol t38 ls-redundancy 5 hs-redundancy 2 fallback none</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">no vad</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">!</span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p></div></div></div></body></html>