Call Rate Limit has nothing to do with CAC...  it's a denial of service
prevention addition to the system.

Mike

2011/6/29 Sven Evensen <[email protected]>

> ** ** ** ** ** **
>
> We are considering writing something ourselves in a plug-in, the problem we
> see is knowing how many****
>
> ongoing calls there are to the specific office/group/location. Obviously if
> something similar is already****
>
> in the sipx roadmap, we will not pursue this.****
>
> ** **
>
> sipx 4.6 has the new somewhat related "Call Rate Limit", so we were hoping
> some CAC would be available too.****
>
> ** **
>
> Sven****
>
> ** **
>  ------------------------------
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Michael Picher
> *Sent:* 29 June 2011 11:49
> *To:* Discussion list for users of sipXecs software
> *Subject:* Re: [sipx-users] Bandwidth control****
>
> ** **
>
> This is something we've asked Audiocodes to build into the SAS feature in
> their gateways.  Technically it's called Call Admission Control.  We feel
> it's best addressed at the network infrastructure level (the routers know
> best their own load and their routes) but realize that most network
> equipment isn't ready to do this.****
>
> ** **
>
> If this can be done as part of SAS, the remote phones are all pointing to
> the remote gateway as an outbound proxy.  The outbound proxy should know all
> the calls going through it.****
>
> ** **
>
> Unless you folks have a better suggestion or would like to write something
> and contribute it back...****
>
> ** **
>
> Thanks,****
>
>   Mike****
>
> 2011/6/29 Sven Evensen <[email protected]>****
>
> We have a centralized sipx and SIP trunk with offices remotely connected
> through a MPLS network.****
>
> Lets say a given link to an office has capacity for 4 simultaneous calls.
> The customer wants the fifth call****
>
> to give re-order tone rather than reduced voice quality.****
>
>  ****
>
> Is there any way that sipx, current or future versions, can handle this?**
> **
>
>  ****
>
> *Sven Evensen, Operations Consultant*****
>
> *OnRelay*****
>
> Elizabeth House │ **39 York Road, **London** **SE1 7NQ**, **UK**** │ +44
> (0) 207 902 8123 │ mailto:[email protected]<[email protected]>│
> www.onrelay.com****
>
>
> This electronic message transmission contains information from OnRelay,
> Ltd., that may be confidential or privileged. The information is intended
> solely for the recipient and use by any other party is not authorised. If
> you are not the intended recipient, be aware that any disclosure, copying,
> distribution or use of the contents of this information or any attachment,
> is prohibited. If you have received this electronic transmission in error,
> please notify us immediately by electronic mail ([email protected]) and
> delete this message, along with any attachments, from your computer.
> Registered in ****England**** No 04006093 | Registered Office 1st Floor,
> 236 Gray's ****Inn Road**, **London** **WC1X 8HB********
>
>  ****
>
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/****
>
>
>
>
> --
> Michael Picher
> eZuce
> Director of Technical Services
> O.978-296-1005 X2015
> M.207-956-0262
> @mpicher <http://twitter.com/mpicher>
> www.ezuce.com****
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



-- 
Michael Picher
eZuce
Director of Technical Services
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
www.ezuce.com
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to