I have a somewhat strange one, that has me scratching my head at the moment. I have two PBX’s, both are running FreePBX Distro 5.211-65.20, and asterisk 11.13.1. It’s very common for calls to be passed extension to extension between the two PBX’s, and in general is working well. Now I am finding calls from a given extension range are now being rejected.
Here is an example of a call path we are using:
[ext4455]---SIP--- [ALG PBX]---SIP---[DCD-PBX]---SIP---[ext8558]
A call from 4455 to 8558 will fail, with the following error:
Error from ALGPBX:
[2014-11-24 10:00:28] WARNING[C-000019eb] chan_sip.c: Received response: "Forbidden" from '"Name Removed" <sip:[email protected]>;tag=as64c83dfd' [2014-11-24 10:00:28] VERBOSE[C-000019eb] app_dial.c: == Everyone is busy/congested at this time (1:0/0/1)
Error on DCDPBX:
[2014-11-24 11:08:34] NOTICE[C-00006b00] acl.c: SIP Peer ACL: Rejecting ' 10.150.4.36' due to a failure to pass ACL '(BASELINE)' [2014-11-24 11:08:34] NOTICE[C-00006b00] chan_sip.c: Failed to authenticate device "Name Removed" <sip:[email protected]>;tag=as62d2a7f7
There is no ACL on the trunk at all, and what is really strange, is some extensions can dial across, So replace 4455 with say 4801, and then the call will pass across the PBX’s just fine.
The part that perplexes me, is that as this is two internal PBX’s, there is NO ACL on the trunks in either direction, in fact here is a sample of the conf used between the PBX’s:
type=peer host=10.150.4.36 dtmfmode=rfc2833 qualify=yes nat=no canreinvite=no insecure=port,invite callcounter=yes context=from-branches
The from-branches just allows group, meetme, did, and internal. I am sure I am overlooking something, but I don’t see how there is any ACL in play to affect the trunk. Also what is the BASELINE they are referring to in the log entry?