Joshua Colp wrote:
Nope! Incoming traffic is ALWAYS associated with an endpoint. You can
get the endpoint and see if any ACL names are configured on it. If
there are you can get each individual ACL and apply it. If not the way
it works now can be used.
This statementhas changed a lotin my understanding ofthe checks. After
that, Ishare your viewon implementationnecessary to me.
However, leftunresolveddescribed previouslybad
behaviorandunexpectedresult of the removaloption"acl"inendpoint. ButI
have nothing to offer, unfortunately.
Dmitriy Serov wrote:
1. There is one section of the ACL and one endpoint, which pointed to
ACL section by name. Now I remove the line with the name of ACL in the
endpoint section.
And... ACL becoming global, preventing the registration of all existing
endpoints. Administrator can get very unexpected behavior :(
Unfortunately,I am not goingto implementthis functionality. My
experienceof programming inCis not yet sufficientfor this purpose. I can
only hopethatthis functionalitywill be claimedby someonemore professional.
Dmitriy Serov
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
