We have discovered an issue on our system where an incoming call can be transferred to our Algo Paging Adaptor. The paging adaptor is set up as a SIP extension in our system. All of the phone extensions are between 100 and 200, and the paging extension is 704 under Paging and Intercom module. The issue was accidently discovered in the following way.
An incoming call was answered on a ring-all ring group. The caller was looking for a specific person. This person’s location in the building was not known so it would need to be paged out so they can answer the call.
The call was transferred to the Parking Lot and then the Page button was pressed. (The Page button is a BLF key that calls the Algo Paging adaptor extension.)
Just as they were pushing the Page key another call came in. When the Page button was pressed, the incoming call was transferred to the Algo Paging adaptor extension.
Since auto answer is set, the call was answered but it was a one-way call with the caller saying “Hello?” over the paging system. Other then running and shutting off the adaptor there was no way to hang it up until the caller did on his end.
Is there any way to block transferring active calls to a specific SIP extension?
I also have the same question. Additionally, I have an IVR that is set to allow direct dialing extensions. I don’t want a caller to be able to discover the Paging or Intercom extensions and dial them. Looking forward to hearing everyone’s thoughts!
(On the latter point, some methods are indistinguishable from new calls to the PABX.)
The fact that the destination is SIP is irrelevant, and “SIP extension” is not a term defined in the SIP specifications - it is basically limited to FreePBX. That the original phone is SIP is relevant, as it affects the answers to the questions.
I found a work-around for the Page issue. I switched the Page button from BLF to Speed Dial. I kept extension it dials the same. I tested it and it did not transfer the call to the intercom. Only downside is that it turns the green/red light off.