Sangoma Netborder SS7, Руководство пользователя

Страница: 151 / 317

v1.14
151
13.5 Dialplan Syntax
There are several elements used to build an XML dialplan. In general, the dialplan groups logically
similar functions and calling activities into a 'context'. Within a context are extensions, each with
'condition' rules and associated 'actions' to perform when the condition rules match.
The following is a sample dialplan to illustrate these concepts. We have left out the XML "wrapper" to
help make the basic concepts more clear:
<context name = "example" >
<extension
name = "500"
>
<condition field = "destination_number" expression = "^500$" >
<action
application = "bridge" data = "user/500"
/>
</condition>
</extension>
<extension name = "501" >
<condition
field = "destination_number" expression = "^501$"
>
<action
application = "bridge" data = "user/501"
/>
<action application = "answer" />
<action
application = "sleep" data = "1000"
/>
<action application = "bridge" data = "loopback/app=voicemail:default ${domain_name} ${dialed_extension}" />
</condition>
</extension>
</context>
Each rule is processed in order until you reach the action tag which tells NSG what action to perform.
You are not limited to only one condition or action tag for a given extension.
In our above example, a call to extension 501 rings the extensions. If the user does not answer, the
second action answers the call, and following actions delay for 1000 milliseconds (which is 1 second)
and connect the call to the voicemail system.