Outbound to IVR or Message... (restricted calls)

Status
Not open for further replies.

nka

Free User
Advanced Certified
Joined
Oct 10, 2021
Messages
9
Reaction score
5
I'm trying to set up a system where only certain external phone numbers can be dialed from specific extensions.

Here's what I've done so far:
  • Created a "Restricted" department and assigned certain extensions to it.
  • In the Outbound Rules, I've set up three rules:
    • Two rules that allow calls to specific external numbers (e.g., 8885551212 and 8885552424) from the "Restricted" department.
    • The last rule allows any call from that department without specifying a trunk.

This setup is functional, but I want to improve it by adding a message such as "This call cannot be completed since your extension is restricted" for calls that match the last rule.

How can I configure the last rule to route calls to an IVR 8003 to play the message and then end the call? Or is there a better approach to achieve this?

Thanks! :)
 
From an outbound rule you can only select a SIP Trunk. So you could create a "fake" trunk to itself (point the SIP Trunk to 127.0.0.1 without registration), and then the calls you send through this trunk will be received back by the same 3CX instance. Then you configure this fake trunk to send inbound calls to the IVR you want, to play the message "This call cannot be completed since your extension is restricted".
 
  • Like
Reactions: nka and SweetAction
From an outbound rule you can only select a SIP Trunk. So you could create a "fake" trunk to itself (point the SIP Trunk to 127.0.0.1 without registration), and then the calls you send through this trunk will be received back by the same 3CX instance. Then you configure this fake trunk to send inbound calls to the IVR you want, to play the message "This call cannot be completed since your extension is restricted".

This is working, didnt know I could do a "loop" SIP Trunk! thanks! :D
 
Hello @nka,

Something else to note is that with this approach, 3CX will count 2 simultaneous calls for this particular call. This is because the call coming back in through the loopback trunk is considered a separate call. Just mentioning it in case you're close to your license limit.
 
@edossantos_sipcaller Oh, nice to know! I'm not close since it's for home/lab usage and pretty much never call, but I will keep that in note if I have to do this in production where I work!
 
Status
Not open for further replies.

Forum statistics

Threads
111,952
Messages
589,896
Members
164,845
Latest member
tdzski5