Manual Dialplan Configuration

From Taridium

Revision as of 22:42, 2 December 2008 (view source) Webmaster (Talk | contribs) ← Older edit		Revision as of 23:13, 2 December 2008 (view source) Webmaster (Talk | contribs) Newer edit →
Line 4:		Line 4:
	The ipbx Dialplan can be access via Configuration → Manual Editor → Dialplan.		The ipbx Dialplan can be access via Configuration → Manual Editor → Dialplan.
		+
		+
		+	== Application Launcher Script ==
		+
		+	The application launcher script allows you to access the main applications directly using common Asterisk AGI compatible syntax.
		+
		+	The applications.ipbx script takes the following two arguments:
		+
		+	1. [application name]
		+
		+	can be any of the following: ivr, conf, queue, channel, group
		+
		+	2. [application ID]
		+
		+	is usually the name of the application element being called.
		+
		+	'''Example calling an IVR named ivrtest'''
		+
		+	exten => 9000,1,agi(ipbx/applications.ipbx,ivr,ivrtest)

---

Revision as of 23:13, 2 December 2008

Most applications and ipbx functions are usually accessed using the pre-built dialplan, but it is also possible to call IVR, Groups, Conference Rooms etc. directly using a variety of AGI (Asterisk Gateway Interface) scripts.

This allows you to write complex diaplans while still retaining the GUI functionality for individual applications.

The ipbx Dialplan can be access via Configuration → Manual Editor → Dialplan.

Application Launcher Script

The application launcher script allows you to access the main applications directly using common Asterisk AGI compatible syntax.

The applications.ipbx script takes the following two arguments:

1. [application name]

can be any of the following: ivr, conf, queue, channel, group

2. [application ID]

is usually the name of the application element being called.

Example calling an IVR named ivrtest

 exten => 9000,1,agi(ipbx/applications.ipbx,ivr,ivrtest)