CTI - Revision history

Webmaster: /* CTI Control */

2011-02-24T14:09:46Z

CTI Control

← Older revision		Revision as of 14:09, 24 February 2011
Line 40:		Line 40:
	== CTI Control ==		== CTI Control ==

-	The CTI control option is available for inbound/outbound call control, in the [[IVR]], [[Groups]] and [[Queues]] applications, for inbound [[~~Routing\|~~Routes]], for timeout functions and for call accounting (see Call Accounting Module). A CTI URL can also be called after every call, but does not provide any control options. The CTI control options can be accessed in each of the application editors by clicking on '''CTI Control''' → '''configure options'''.	+	The CTI control option is available for inbound/outbound call control, in the [[IVR]], [[Groups]] and [[Queues]] applications, for inbound [[Routes\|Routing]], for timeout functions and for call accounting (see Call Accounting Module). A CTI URL can also be called after every call, but does not provide any control options. The CTI control options can be accessed in each of the application editors by clicking on '''CTI Control''' → '''configure options'''.
	In it's simplest form the CTI control allows you to signal that a call was routed to an application, usually passing along some identifying information such as the caller ID.		In it's simplest form the CTI control allows you to signal that a call was routed to an application, usually passing along some identifying information such as the caller ID.

Webmaster: /* CTI Control */

2011-02-24T14:09:26Z

CTI Control

← Older revision		Revision as of 14:09, 24 February 2011
Line 40:		Line 40:
	== CTI Control ==		== CTI Control ==

-	The CTI control option is available for inbound/outbound call control, in the [[IVR]], [[Groups]] and [[Queues]] applications, for inbound [[Routing]], for timeout functions and for call accounting (see Call Accounting Module). A CTI URL can also be called after every call, but does not provide any control options. The CTI control options can be accessed in each of the application editors by clicking on '''CTI Control''' → '''configure options'''.	+	The CTI control option is available for inbound/outbound call control, in the [[IVR]], [[Groups]] and [[Queues]] applications, for inbound [[Routing\|Routes]], for timeout functions and for call accounting (see Call Accounting Module). A CTI URL can also be called after every call, but does not provide any control options. The CTI control options can be accessed in each of the application editors by clicking on '''CTI Control''' → '''configure options'''.
	In it's simplest form the CTI control allows you to signal that a call was routed to an application, usually passing along some identifying information such as the caller ID.		In it's simplest form the CTI control allows you to signal that a call was routed to an application, usually passing along some identifying information such as the caller ID.

Webmaster at 21:31, 4 February 2011

2011-02-04T21:31:29Z

← Older revision		Revision as of 21:31, 4 February 2011
Line 1:		Line 1:
-	This optional ipbx module is installed under '''Advanced Setup''' → '''Modules'''. Registered modules are displayed with '''registered module'''. The CTI module has been made available in ipbx 2.1 and higher versions.	+	This optional ipbx module is installed under '''Advanced Setup''' → '''Modules'''. Registered modules are displayed with '''registered module'''. The CTI module has been made available in ipbx 2.1 and higher versions and is a standard component of ipbx Elite.

	ipbx's CTI module provides a standardized way to interact with incoming calls using external applications. Applications include web driven pop-up windows and call manipulation. CTI interfaces use standard HTTP/S protocol and are completely language agnostic.		ipbx's CTI module provides a standardized way to interact with incoming calls using external applications. Applications include web driven pop-up windows and call manipulation. CTI interfaces use standard HTTP/S protocol and are completely language agnostic.

Webmaster at 21:30, 4 February 2011

2011-02-04T21:30:56Z

← Older revision		Revision as of 21:30, 4 February 2011
Line 1:		Line 1:
	This optional ipbx module is installed under '''Advanced Setup''' → '''Modules'''. Registered modules are displayed with '''registered module'''. The CTI module has been made available in ipbx 2.1 and higher versions.		This optional ipbx module is installed under '''Advanced Setup''' → '''Modules'''. Registered modules are displayed with '''registered module'''. The CTI module has been made available in ipbx 2.1 and higher versions.

-	ipbx's CTI module provides a standardized way to interact with incoming calls using external applications. Applications include web driven pop-up windows and call manipulation.	+	ipbx's CTI module provides a standardized way to interact with incoming calls using external applications. Applications include web driven pop-up windows and call manipulation. CTI interfaces use standard HTTP/S protocol and are completely language agnostic.

	CTI integration is available in two places		CTI integration is available in two places

Webmaster: /* CTI Control */

2011-02-04T20:31:59Z

CTI Control

← Older revision		Revision as of 20:31, 4 February 2011
Line 49:		Line 49:
	http://192.168.77.123/myctitest.html?calleridnumber=%%calleridnumber%%&calleridname=%%calleridname%%		http://192.168.77.123/myctitest.html?calleridnumber=%%calleridnumber%%&calleridname=%%calleridname%%

-	In the above situation an incoming call would cause the URL to be called and the variables '''%%calleridnumber%%''' and '''%%calleridname%%''' to be replaced with the actual information.	+	In the above situation an incoming call would cause the URL to be called and the variables '''%%calleridnumber%%''' and '''%%calleridname%%''' to be replaced with the actual information. The default request timeout is 2 seconds. Both HTTP and HTTPS are supported.

	For a complete list of variables refer to [[CTI#CTI_URL_Variables\|CTI URL variables]].		For a complete list of variables refer to [[CTI#CTI_URL_Variables\|CTI URL variables]].

Webmaster at 21:43, 8 April 2010

2010-04-08T21:43:02Z

← Older revision		Revision as of 21:43, 8 April 2010
Line 5:		Line 5:
	CTI integration is available in two places		CTI integration is available in two places

-	# as CTI control, where calls coming in or out will cause interaction with external web enabled applications.	+	# as CTI control, where calls coming in/out will cause interaction with external web enabled applications.
	# as a means to pop-up an application page in the ipbx [[End User Panel]].		# as a means to pop-up an application page in the ipbx [[End User Panel]].

Line 40:		Line 40:
	== CTI Control ==		== CTI Control ==

-	The CTI control option is available for inbound/outbound call control, in the [[IVR]], [[Groups]] and [[Queues]] applications and for call accounting (see Call Accounting Module). A CTI URL can also be called after every call, but does not provide any control options. The CTI control options can be accessed in each of the application editors by clicking on '''CTI Control''' → '''configure options'''.	+	The CTI control option is available for inbound/outbound call control, in the [[IVR]], [[Groups]] and [[Queues]] applications, for inbound [[Routing]], for timeout functions and for call accounting (see Call Accounting Module). A CTI URL can also be called after every call, but does not provide any control options. The CTI control options can be accessed in each of the application editors by clicking on '''CTI Control''' → '''configure options'''.
	In it's simplest form the CTI control allows you to signal that a call was routed to an application, usually passing along some identifying information such as the caller ID.		In it's simplest form the CTI control allows you to signal that a call was routed to an application, usually passing along some identifying information such as the caller ID.

Webmaster: /* CTI XML Format */

2010-04-08T21:39:34Z

CTI XML Format

← Older revision		Revision as of 21:39, 8 April 2010
Line 74:		Line 74:
	</ipbx>		</ipbx>

-	The '''<set>''' tag can contain any of the following sub-tags:	+	The '''<set/>''' tag can contain any of the following sub-tags:

-	* <calleridname></~~calleridname~~> sets the caller ID name for the call	+	* <calleridname/> sets the caller ID name for the call
-	* <calleridnumber></~~calleridnumber~~> sets the caller ID number for the call	+	* <calleridnumber/> sets the caller ID number for the call
-	* <calleridani></~~calleridani~~> sets the ANI for the call	+	* <calleridani/> sets the ANI for the call
-	* <accountcode></~~accountcode~~> sets the accountcode for the call	+	* <accountcode/> sets the accountcode for the call
-	* <userfield></~~userfield~~> sets the userfield for the call	+	* <userfield/> sets the userfield for the call
-	* <acc_code1></~~acc_code1~~> sets an additional account code in the accounting table	+	* <acc_code1/> sets an additional account code in the accounting table
-	* <acc_code2></~~acc_code2~~> sets an additional account code in the accounting table	+	* <acc_code2/> sets an additional account code in the accounting table
-	* <acc_code3></~~acc_code3~~> sets an additional account code in the accounting table	+	* <acc_code3/> sets an additional account code in the accounting table
-	* <record></~~record~~> 0 or not set, yes(1) whether to record the call, using '''no''' will disable any systemwide recordings	+	* <record/> 0 or not set, yes(1) whether to record the call, using '''no''' will disable any systemwide recordings

	'''Example Code 2'''		'''Example Code 2'''
Line 103:		Line 103:
	</ipbx>		</ipbx>

-	The '''<type>''' tag can contain any of the following keywords:	+	The '''<type/>''' tag can contain any of the following keywords:

	* extension		* extension
Line 115:		Line 115:
	* user		* user

-	The '''<name>''' tag must contain a valid application/function name. Use a function instead of an extension whenever possible.	+	The '''<name/>''' tag must contain a valid application/function name. Use a function instead of an extension whenever possible.

-	The <break></~~break~~> tag is boolean, 0 or 1 and indicated whether to break execution after CTI processing has been completed.	+	The '''<break/>''' tag is boolean, 0 or 1 and indicated whether to break execution after CTI processing has been completed.

	== CTI URL Variables ==		== CTI URL Variables ==

Webmaster: /* CTI XML Format */

2010-04-08T21:38:02Z

CTI XML Format

← Older revision		Revision as of 21:38, 8 April 2010
Line 97:		Line 97:
	<type>extension</type>		<type>extension</type>
	<name>18005554444</name>		<name>18005554444</name>
-	</route>	+	<break>0</break>
		+	</route>
	</call>		</call>
	</cti>		</cti>
Line 115:		Line 116:

	The '''<name>''' tag must contain a valid application/function name. Use a function instead of an extension whenever possible.		The '''<name>''' tag must contain a valid application/function name. Use a function instead of an extension whenever possible.
		+
		+	The <break></break> tag is boolean, 0 or 1 and indicated whether to break execution after CTI processing has been completed.

	== CTI URL Variables ==		== CTI URL Variables ==

Webmaster: /* Post Call CTI */

2010-03-29T19:00:08Z

Post Call CTI

← Older revision		Revision as of 19:00, 29 March 2010
Line 30:		Line 30:
	=== Post Call CTI ===		=== Post Call CTI ===

-	A URL which will be called after each call. This URL's reply will not be processed, but can be used to pass call detail records in the GET argument.	+	A URL which will be called after each call. This URL's reply will not be processed, but can be used to pass call detail records in the GET argument. The valid variables for the URL correspond to the [[CDR]] field names using the common ipbx variable format, e.g. %%accountcode%%.

	== CTI User Panel ==		== CTI User Panel ==

Webmaster: /* CTI URL Variables */

2010-03-29T18:56:56Z

CTI URL Variables

← Older revision		Revision as of 18:56, 29 March 2010
Line 127:		Line 127:
	* '''%%channel%%''' The channel, if available		* '''%%channel%%''' The channel, if available
	* '''%%exten%%''' The called extension		* '''%%exten%%''' The called extension
		+	* '''%%acc_code[1-3]%%''' an additional account code