Yes, you’re absolutely right.
It turned out that the Asterisk has this uncommon way of handling ACL.
Asterisk assumes “permit”, then runs down the ACL, and changes the status to
either “deny” or “permit” based on each matching trunk entry, but the last
matching entry of ACL determines the final
Hello,
parameters in the Via header have nothing to do with authentication. It
seems that the key log messages are in Asterisk:
[Jan 21 23:13:20] NOTICE[20785][C-0001] acl.c: SIP Peer ACL:
Rejecting '10.0.1.30' due to a failure to pass ACL '(BASELINE)'
[Jan 21 23:13:20] NOTICE[20785][C-00
Hi, all
We're trying to build a system that consists of pbx, kamailio and asterisk
in the following configuration.
pbx (sip trunk) --- kamailio --- asterisk
The kamailio and asterisk are integrated with same database. The outgoing
calls to pbx works. But there is a problem with incoming calls fr
