[cisco-voip] Adding DIDs to a PRI - and how to limit total calls to those DID numbers.
Lelio Fulgenzi
lelio at uoguelph.ca
Tue Oct 23 15:03:12 EDT 2012
I'm sure you have greater control over max calls with H323, but with MGCP I don't think there's any options.
In the PRI world, there's the concepts of route groups as well. You can define a route group to have a max of X calls and then assign those DIDs to that route group that. Changes and route groups are typically chargeable items on your PRI service. There might be a minimum number of DIDs per route group as well. Not sure about that.
That's how I would approach this request.
---
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: cisco-voip at puck.nether.net
Sent: Tuesday, October 23, 2012 2:52:02 PM
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
!
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20121023/11c39dee/attachment.html>
More information about the cisco-voip
mailing list