forked from extern/docker
45 lines
1.4 KiB
XML
45 lines
1.4 KiB
XML
|
<!--
|
||
|
NOTICE:
|
||
|
|
||
|
This context is usually accessed via the external sip profile listening on port 5080.
|
||
|
|
||
|
It is recommended to have separate inbound and outbound contexts. Not only for security
|
||
|
but clearing up why you would need to do such a thing. You don't want outside un-authenticated
|
||
|
callers hitting your default context which allows dialing calls thru your providers and results
|
||
|
in Toll Fraud.
|
||
|
-->
|
||
|
|
||
|
<!-- http://wiki.freeswitch.org/wiki/Dialplan_XML -->
|
||
|
<include>
|
||
|
<context name="public">
|
||
|
|
||
|
<extension name="unloop">
|
||
|
<condition field="${unroll_loops}" expression="^true$"/>
|
||
|
<condition field="${sip_looped_call}" expression="^true$">
|
||
|
<action application="deflect" data="${destination_number}"/>
|
||
|
</condition>
|
||
|
</extension>
|
||
|
<!--
|
||
|
Tag anything pass thru here as an outside_call so you can make sure not
|
||
|
to create any routing loops based on the conditions that it came from
|
||
|
the outside of the switch.
|
||
|
-->
|
||
|
<extension name="outside_call" continue="true">
|
||
|
<condition>
|
||
|
<action application="set" data="outside_call=true"/>
|
||
|
<action application="export" data="RFC2822_DATE=${strftime(%a, %d %b %Y %T %z)}"/>
|
||
|
</condition>
|
||
|
</extension>
|
||
|
|
||
|
<!--
|
||
|
You can place files in the public directory to get included.
|
||
|
-->
|
||
|
<X-PRE-PROCESS cmd="include" data="public_docker/*.xml"/>
|
||
|
<X-PRE-PROCESS cmd="include" data="public/*.xml"/>
|
||
|
|
||
|
|
||
|
</context>
|
||
|
|
||
|
</include>
|
||
|
|