[cisco-voip] selectively pick a BRI or PRI from differentextensions behind call manager

[Erik Erasmus (E)]

Thanks
 
Yes - on the h323 side it is basically the idea I had but a was a bit
curious on how MGCP would do it so now I know 
 
Thanks for the replies
 
yes MGCP versus H.323 -- is it a case of BMW versus Mercedec Benz --
some like the one and others the other one
 
 
erik

________________________________

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Tue 2008-01-29 17:36
To: Matthew Saskin
Cc: Erik Erasmus (E); cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] selectively pick a BRI or PRI from
differentextensions behind call manager



For future reference,

Lelio = MGCP
Scott Voll = H323

:)

----- Original Message -----
From: "Matthew Saskin" <matt at saskin.net>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
Cc: "Erik Erasmus (E)" <ErasmuE4 at telkom.co.za>;
<cisco-voip at puck.nether.net>
Sent: Tuesday, January 29, 2008 9:56 AM
Subject: Re: [cisco-voip] selectively pick a BRI or PRI from
differentextensions behind call manager


> Lelio's suggestion would work perfectly using MGCP gateways.  As an
> alternative (if you want to use H.323) you can use distinct
> CSS/Partition/RP's as with H.323 but instead of differentiating at
the
> route group/route list level, you'd have to add a prefix on outbound
calls
> and use different dial-peers on the gateway to match.
>
> -matt
>
> Lelio Fulgenzi wrote:
>> Calling search space assigned to the different classes would hit
>> different partitions with different route patterns assigned to
different
>> gateways.
>>  So, phone A with CSS A hits 9.@ in Partition A which sends calls
out BRI
>> A.
>> And, phone B with CSS B hits 9.@ in Partition B which sends calls
out BRI
>> B.
>>  I'm not aware of any way (with MGCP anyways) to send calls out
specific
>> channels on a BRI/PRI.
>>
----------------------------------------------------------------------
----------
>> Lelio Fulgenzi, B.A.
>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G
2W1
>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> "Life expectancy would grow by leaps and bounds if green vegetables
>> smelled as good as bacon."
>> Doug Larson
>>  ----- Original Message -----
>>     *From:* Erik Erasmus (E) <mailto:ErasmuE4 at telkom.co.za>
>>     *To:* cisco-voip at puck.nether.net
<mailto:cisco-voip at puck.nether.net>
>>     *Sent:* Monday, January 28, 2008 11:54 PM
>>     *Subject:* [cisco-voip] selectively pick a BRI or PRI from
>>     differentextensions behind call manager
>>
>>     Does anyone have experience in selecting a specific ISDN basic
rate
>>     or primary rate line on a voice gateway from a call manager and
what
>>     would be the best way to do it.
>>
>>      I have a solution where two businesses will share a gateway
and they
>>     will each have a separate BRI to keep pstn billing separate -
they
>>     share a call manager. How would one make a specific range of
>>     extensions always pick one BRI when dialing out to pstn and
another
>>     range select another BRI on the same gateway preferably.
>>
>>      If possible I want to use a single gateway
>>
>>     With two gateways I guess it would be a lot easier - possible
using
>>     different pstn access codes and then selecting different route
>>     patterns / rlists/ routegroups / gateway  I am not too fussy
about
>> h323 versus mgcp - but have more h323
>>     experience so will probably prefer this
>>
>>      Any advice will be appreciated
>>
>>      Erik Erasmus
>>
>>     \
>>
>>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>     This e-mail is subject to the Telkom SA electronic
communication
>>     legal notice, available at :
>>     http://www.telkom.co.za/TelkomEMailLegalNotice.PDF
>>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>>
----------------------------------------------------------------------
--
>>
>>     _______________________________________________
>>     cisco-voip mailing list
>>     cisco-voip at puck.nether.net
>>     https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>>
----------------------------------------------------------------------
--
>>
>> _______________________________________________
>> 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/20080130/08e57393/attachment.html