[cisco-voip] SIP to SIP (CUBE) and trunk groups

[John Schlimgen]

Ian,

You can use global Call admission control on your CUBE.

call treatment on
call threshold global total-calls low <Low water mark to resume accepting
calls> high <Max number of calls

http://www.cisco.com/en/US/docs/ios/12_2t/12_2t11/feature/guide/ftcac58.html#wp1127100

On Tue, Apr 21, 2009 at 8:37 PM, Nick Matthews <matthnick at gmail.com> wrote:

> You could do this a few ways.  If all incoming calls hit a set of
> outgoing dial peers that you want to limit, you can just put the
> max-conn under the incoming dial peer.
>
> The less elegant way is to create multiple incoming dial peers that
> match on the different incoming called-number ranges, and add some
> type of prefix like **1.  Then you can create a single dial peer with
> a wildcard destination pattern of **1.T and put the max-conn on the
> outgoing dial peer.  This also assumes that all of your dial peers
> have the same outgoing attributes.
>
>
>
> -nick
>
>
>
> On Tue, Apr 21, 2009 at 6:48 AM, Ian MacKinnon
> <Ian.Mackinnon at lumison.net> wrote:
> > Hi All,
> >
> >
> >
> > I am trying to implement some CUBE functionality, and have hit a problem.
> >
> >
> >
> > Say I have a customer who I want to provide a SIP trunk to.
> >
> > Calls will come into CUBE via SIP and be forwarded on the customer using
> SIP
> > and vice-versa
> >
> >
> >
> > If they have a complex numbering scheme, I need to use multiple
> dial-peers
> > to match the numbers.
> >
> >
> >
> > That then means I can’t use max-calls in the dial peer to limit their
> calls
> > effectivley as it only applies per dial-peer.
> >
> >
> >
> > I have found the trunkgroup commands......
> >
> > Can I use a trunk group per customer to do the max-calls stuff, and then
> > link the dial peers to the trunk group?
> >
> >
> >
> > What documentation I can find talks about TDM interfaces and H.323 only.
> >
> >
> >
> > Thanks
> >
> >
> >
> >
> >
> >
> >
> > ________________________________
> > --
> >
> > This email and any files transmitted with it are confidential and
> intended
> > solely for the use of the individual or entity to whom they are
> addressed.
> > If you have received this email in error please notify the sender. Any
> > offers or quotation of service are subject to formal specification.
> > Errors and omissions excepted. Please note that any views or opinions
> > presented in this email are solely those of the author and do not
> > necessarily represent those of Lumison and nPlusOne.
> > Finally, the recipient should check this email and any attachments for
> the
> > presence of viruses. Lumison and nPlusOne accept no liability for any
> > damage caused by any virus transmitted by this email.
> >
> > _______________________________________________
> > 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/20090422/127045c2/attachment.html>