-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/26/2012 09:47 AM, [email protected] wrote: > These are all good points, but it doesn't help when you are not > using a gateway device with limited resources, or an ITSP who > blocks the nth call. What about when you have multi site setup > where you have handsets in the field? What about where you have a > multi-site sipXecs deployment with a sipXecs proxy at each site and > they new to communicate between each other. In both of those > scenarios, you have the potential to flood your link.
Great explanation why CAC is not in sipXecs right now. :) Once you add CAC, you need a host of other tools and options such as alternate routing, overrides for emergency calls, etc etc. While CAC superficially seems "nice", it's incredibly complex beyond just "I have x bandwidth for y calls". This is not to say it shouldn't be discussed or worked on, but by no means is it trivial. > The only way you could get a firewall to create control of this > would be if it was a layer 7 firewall that intercepted the SIP > requests and sent back a 4xx failure to the calling end. I don't > see this happening any time soon and it would lead to a raft of > compatibility issues and finger pointing when there were interop > problems. I wonder about using an sbc and/or gatekeeper to achieve this. I'm not familiar with Karoo, but perhaps something like Kamailio / openSER / openSIPS could be used? - -- ================================================================== Joe Micciche [email protected] Red Hat, Inc. http://www.redhat.com Senior Communications Engineer X (81) 44554 +1.919.754.4554 Key: 65F90FE1 ================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlARnDoACgkQJHjEUGX5D+FULQCgjzicTnM3PVSTmTpMl7b3jYZs cFIAoIGRn/CnoaQWR2PLZ0KkY7f8NxkJ =5dG9 -----END PGP SIGNATURE----- _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
