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 u
Dmitriy Serov wrote:
The proposed decision confuses me two things:
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 exist
24.03.2015 3:44, Joshua Colp пишет:
Dmitriy Serov wrote:
Hello.
And Sorry for my english :)
https://issues.asterisk.org/jira/browse/ASTERISK-24890
I continue to migrate from asterisk 11 to 13.2 and continues to face
problems of compatibility.
chan_sip has a very good ability to limit registrat
Dmitriy Serov wrote:
Hello.
And Sorry for my english :)
https://issues.asterisk.org/jira/browse/ASTERISK-24890
I continue to migrate from asterisk 11 to 13.2 and continues to face
problems of compatibility.
chan_sip has a very good ability to limit registration for a particular
PEER to the spec
Hello.
And Sorry for my english :)
https://issues.asterisk.org/jira/browse/ASTERISK-24890
I continue to migrate from asterisk 11 to 13.2 and continues to face
problems of compatibility.
chan_sip has a very good ability to limit registration for a particular
PEER to the specified set of IP addr
