Anyone have a good dialplan recipe for a long distance forced authorization code?
I.e. to require a pin entry prior to bridging an outbound long distance call? I was thinking I could duplicate my outbound gateway bridging rules with an answer, start_dtmf, play_and_get_digits, followed by the actual bridging instruction. Is that the ideal way to do this? Intent is for open access phones that have restricted long distance unless the line-specific authorization code is entered. -- Nathan ------------------------------------------------------------ Nathan Neulinger nneul@mst.edu Missouri S&T Information Technology (573) 612-1412 System Administrator - Architect
Don't use start_dtmf unless you are receiving inband dtmf (audible tones in the audio without rfc2833 or sip info dtmf). Answer and play_and_get_digits probably is the way to do this yes... Whether in dialplan or from lua etc. Rather than duplicate anything, how about having a context that checks the PIN and transfers the call into the existing context for routing? That also means they couldn't get to that context without the correct PIN, so would be an extra layer of security. You can then either send calls for an entire SIP profile into the pin check context (context profile param) or for specific users (user_context user param). Steve On 5 Apr 2013, at 15:37, Nathan Neulinger <nneul@mst.edu> wrote:
I.e. to require a pin entry prior to bridging an outbound long distance call?
I was thinking I could duplicate my outbound gateway bridging rules with an answer, start_dtmf, play_and_get_digits, followed by the actual bridging instruction.
Is that the ideal way to do this? Intent is for open access phones that have restricted long distance unless the line-specific authorization code is entered.
-- Nathan
------------------------------------------------------------ Nathan Neulinger nneul@mst.edu Missouri S&T Information Technology (573) 612-1412 System Administrator - Architect
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Sounds *sorta* like DISA, but for users already authorized just not authorized for long distance. For examples, look up DISA on the wiki or perhaps fusionpbx's lua scripts and take a look... -Avi Marcus BestFone
Ah sorry, this is for specific outbound calls rather than incoming... I might approach this by setting a variable if the call is allowed... For local destinations always set it, and for long distance only if the PIN is correct. Then allow the call to continue processing further into the dialplan, and add an extra condition to the bridging extension that checks the variable is set. Bear in mind that unless you're using TLS+SRTP/ZRTP it may be possible to eavesdrop on the PIN. Steve On 5 Apr 2013, at 15:37, Nathan Neulinger <nneul@mst.edu> wrote:
I.e. to require a pin entry prior to bridging an outbound long distance call?
I was thinking I could duplicate my outbound gateway bridging rules with an answer, start_dtmf, play_and_get_digits, followed by the actual bridging instruction.
Is that the ideal way to do this? Intent is for open access phones that have restricted long distance unless the line-specific authorization code is entered.
-- Nathan
------------------------------------------------------------ Nathan Neulinger nneul@mst.edu Missouri S&T Information Technology (573) 612-1412 System Administrator - Architect
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Ah, so effectively, similar to duplicating the rulesets for outbound long distance, but fall through after setting the variable instead of fully duplicating. That may save some additional trouble later on as well. -- Nathan On 04/05/2013 10:27 AM, Steven Ayre wrote:
Ah sorry, this is for specific outbound calls rather than incoming...
I might approach this by setting a variable if the call is allowed... For local destinations always set it, and for long distance only if the PIN is correct.
Then allow the call to continue processing further into the dialplan, and add an extra condition to the bridging extension that checks the variable is set.
Bear in mind that unless you're using TLS+SRTP/ZRTP it may be possible to eavesdrop on the PIN.
Steve
On 5 Apr 2013, at 15:37, Nathan Neulinger <nneul@mst.edu> wrote:
I.e. to require a pin entry prior to bridging an outbound long distance call?
I was thinking I could duplicate my outbound gateway bridging rules with an answer, start_dtmf, play_and_get_digits, followed by the actual bridging instruction.
Is that the ideal way to do this? Intent is for open access phones that have restricted long distance unless the line-specific authorization code is entered.
-- Nathan
------------------------------------------------------------ Nathan Neulinger nneul@mst.edu Missouri S&T Information Technology (573) 612-1412 System Administrator - Architect
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- ------------------------------------------------------------ Nathan Neulinger nneul@mst.edu Missouri S&T Information Technology (573) 612-1412 System Administrator - Architect
participants (3)
-
Avi Marcus
-
Nathan Neulinger
-
Steven Ayre