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

Tim Reimers treimers at ashevillenc.gov
Tue Oct 23 14:52:02 EDT 2012


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 3rd, 4th, 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/b98d857a/attachment.html>


More information about the cisco-voip mailing list