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

Wed Oct 24 11:30:52 EDT 2012

in our recent upgrade to SIP from the old dialogic fax board we purchased a
30 channel SIP license.  We have 16 channels dedicated to inbound and the
remainder to outbound.  Once they 16 inbound are in use, the next call
will receive a busy.

to be honest, we do have a dedicated PRI for Fax though.  This goes back to
the dialogic fax board we previously had.  the PRI plugged directly into
it.  So at the time of the upgrade we plugged the PRI into an available PRI
port on our VGW and setup our CSS appropriately.  Our Fax DID are
overlapping DN's with our Voice DNs.

Since we have toll bypass for most of the State, we then send outbound
faxes out the closes VGW to the calling area.

YMMV

Scott

On Wed, Oct 24, 2012 at 7:26 AM, Tim Reimers <treimers at ashevillenc.gov>wrote:

> Thanks Scott!****
>
> ** **
>
> Would that ‘dedicating 8 channels inbound’ be done via a trunk group? or
> would RightFax just handle that?****
>
> ** **
>
> What I’m considering is just porting the numbers from the analog DID
> trunks over to an existing PRI, which already is a trunk group with another
> PRI.****
>
> It’d be good if I didn’t need to complicate the PRI configuration with
> AT&T by adding more trunk groups on the same PRI.****
>
> ** **
>
> The same PRI I’m using is currently one of our primary voice trunks for
> callin/callout, so****
>
> I don’t know that I’d want to permanently dedicate channels for exclusive
> fax use.****
>
> ** **
>
> I’m also working out the pros/cons of adding a whole PRI for the purpose**
> **
>
> So I’m working out the details and possibilities for both options.  I’d
> like to have a separate PRI for faxing, which would make a lot of things
> easier,****
>
> including moving faxing to another router if needed in future, etc. ****
>
> ** **
>
> Thanks, Tim****
>
> ** **
>
> ** **
>
> ** **
>
> *From:* Scott Voll [mailto:svoll.voip at gmail.com]
> *Sent:* Wednesday, October 24, 2012 10:08 AM
> *To:* Tim Reimers
> *Cc:* Chris Clouse; 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.****
>
> ** **
>
> Right Fax may be your solution.  you have to license how many concurrent
> calls the Right fax server can have. (I believe both inbound and outbound).
>  so you could just dedicate 8 channels inbound then everything else
> will receive a busy....****
>
> ** **
>
> YMMV****
>
> ** **
>
> Scott****
>
> On Tue, Oct 23, 2012 at 2:51 PM, Tim Reimers <treimers at ashevillenc.gov>
> wrote:****
>
> 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 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****
>
> !****
>
>  ****
>
>  ****
>
>
> _______________________________________________
> 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/20121024/f9c31c1d/attachment.html>