[cisco-voip] Adding DIDs to a PRI - and how to limit total calls to those DID numbers.

[Lelio Fulgenzi]

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. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message -----
From: "Tim Reimers" <treimers at ashevillenc.gov> 
To: "Chris Clouse" <Chris.Clouse at cdw.com>, cisco-voip at puck.nether.net 
Cc: lelio at uoguelph.ca 
Sent: Tuesday, 23 October, 2012 5:51:54 PM 
Subject: RE: [cisco-voip] Adding DIDs to a PRI - and how to limit total calls to those DID numbers. 



That does look very much like what I'm considering - 

Lelio, I am going to investigate options with the telco as well - 
One thing I have to determine is whether we want to do a separate PRI and incur that monthly cost. 
That would give me the option of controlling this from the carrier side as well. 

I'm going to try to get this lit up using Hylafax and t38modem as a test platform. 
Same diagram as below, but I'm going to use Hylafax as a temporary test-FoIP platform to straighten out the Cisco side 
before moving on to the Rightfax phase of the project: migration-from-old-RF version-to-newest-version-of-RF 

Ultimately, this will be a simple 
PSTN >> PRI >> DID number #1515 (for ex,) >> Cisco 2821 >> H.323 to RightFax SR140 module. 

So no real integration with Callmanager or any of that - Just no need to make it that complicated. 
(unless I'm missing something about how awesomely easy and incredibly flexible and low-cost it would be if I involved UCM in this ....;-) 


Thanks, Tim 


From: Chris Clouse [mailto:Chris.Clouse at cdw.com] 
Sent: Tue 10/23/2012 3:11 PM 
To: Tim Reimers; cisco-voip at puck.nether.net 
Subject: RE: [cisco-voip] Adding DIDs to a PRI - and how to limit total calls to those DID numbers. 





I would investigate using ‘max-conn’ on your dialpeers. 



http://www.cisco.com/en/US/docs/ios/solutions_docs/voip_solutions/CAC.html#wp902617 




~Chris 





From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Tim Reimers 
Sent: Tuesday, October 23, 2012 1:52 PM 
To: cisco-voip at puck.nether.net 
Subject: [cisco-voip] Adding DIDs to a PRI - and how to limit total calls to those DID numbers. 



Hi everyone – 



I’ve been asked a question that I don’t know if I’ve heard before – 



I have two existing PRI circuits, built as a single trunk group, with about 1000 DID numbers on them, used for voice calls. 

(for sake of mentioning it, the PRIs arrive on two different routers, and all the DIDs are reachable inbound on either one) 



Someone wants to add more DIDs for the purpose of faxing, with those DIDs being dedicated for fax usage, not for voice calls. 



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. 



How would I limit the allowable calls coming in to the DIDs 1500-1700 and 2100-2300 ? 

(assuming 4-digit delivery from the telco) 



One factor that might do it is that the session-target device mentioned below 

only has two active channels – 

Would that have the effect of stopping the 3 rd , 4 th , etc call and sending them back to the carrier 

with a busy signal? 

I don’t want a re-order tone – just busy. 



Or would I use the ‘max-conn’ option as shown below under the dial-peer to ensure that 

no more calls can come in? 



I think my dial peers would look like this: 



dial-peer voice 1000 voip 

description Inbound faxes 

destination-pattern 1[5-7].. 

max-conn 2 

session target ipv4:192.168.200.17 

session transport udp 

dtmf-relay h245-signal 

codec g711ulaw 

fax rate 14400 

fax protocol t38 ls-redundancy 5 hs-redundancy 2 fallback none 

no vad 

! 



dial-peer voice 1000 voip 

description Inbound faxes 

destination-pattern 2[1-3].. 

max-conn 2 

session target ipv4:192.168.200.17 

session transport udp 

dtmf-relay h245-signal 

codec g711ulaw 

fax rate 14400 

fax protocol t38 ls-redundancy 5 hs-redundancy 2 fallback none 

no vad 

! 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20121023/2551cf3c/attachment.html>