Asterisk features - Revision history

Pchero: /* Feature Code Call Transfers */

2016-12-21T14:43:20Z

Feature Code Call Transfers

← Older revision		Revision as of 14:43, 21 December 2016
Line 18:		Line 18:

	* Blind transfer		* Blind transfer
			: Blind transfer 는 목표가 되는 party 의 상황을 신경쓰지않고 transfer 를 하는 것을 의미한다.
	: A blind or unsupervised transfer is where the initiating party is blind to what is happening after the transfer. They are removed from the process as soon as they initiate the transfer. It is a sort of "fire and forget" transfer.		: A blind or unsupervised transfer is where the initiating party is blind to what is happening after the transfer. They are removed from the process as soon as they initiate the transfer. It is a sort of "fire and forget" transfer.

	* Attended transfer		* Attended transfer
	: Variations on attended transfer behavior		: Attended transfer 는 목표가 되는 party 의 상황에 따라 transfer 를 결정하는 것을 의미한다. 먼저 목표 party 에 전화를 건 다음, 준비가 되었을 때 transfer 를 시도하는 것이다.
			: Variations on attended transfer behavior.
	: An attended or supervised transfer happens when one party transfer another party to a new location by first dialing the transfer destination and only completing the transfer when ready. The initiating party is attending or supervising the transfer process by contacting the destination before completing the transfer. This is helpful if the transfer initiator wants to make sure someone answers or is ready at the destination.		: An attended or supervised transfer happens when one party transfer another party to a new location by first dialing the transfer destination and only completing the transfer when ready. The initiating party is attending or supervising the transfer process by contacting the destination before completing the transfer. This is helpful if the transfer initiator wants to make sure someone answers or is ready at the destination.

Line 31:		Line 33:

	==== Enabling blind or attended transfers ====		==== Enabling blind or attended transfers ====
	In features.conf ~~you must configure the~~ blindxfer or atxfer ~~options in the featuremap section~~. ~~The options are configureed with the~~ DTMF ~~character string you want to use for accessing the feature~~.		features.conf 파일의 featuremap 섹션에서 blindxfer 혹은 atxfer 옵션을 설정해야 한다. blindxfer 는 blind transfer, atxfer 는 attended transfer 설정이다. 사용하고자하는 DTMF 문자열을 설정해주면 된다.
	<pre>		<pre>
	[featuremap]		[featuremap]

Pchero: /* See also */

2016-12-21T11:39:40Z

Pchero: /* Behavior Options */

2016-12-21T11:39:16Z

Behavior Options

← Older revision		Revision as of 11:39, 21 December 2016
Line 119:		Line 119:

	* TransferContext		* TransferContext
	Blind 혹은 Attended transfer 를 할 경우, transfer 할 때 사용될 context 를 지정해주어야 한다. __TRANSFER_CONTEXT channel variable 에 지정해주면 된다.		Blind 혹은 Attended transfer 를 할 경우, transfer 할 때 사용될 context 를 지정해주어야 한다. __TRANSFER_CONTEXT channel variable 에 지정해주면 된다<ref>http://network.programming4.us/forums/t/10613.aspx</ref>.
	<pre>		<pre>
	exten => s,1,Set(__TRANSFER_CONTEXT=TransferContext)		exten => s,1,Set(__TRANSFER_CONTEXT=TransferContext)

Pchero: /* Feature Code Call Transfers */

2016-12-21T11:38:41Z

Feature Code Call Transfers

← Older revision		Revision as of 11:38, 21 December 2016
Line 116:		Line 116:
	;transferretrysound = "beep" ; Sound to play when a transferer fails to dial a valid extension.		;transferretrysound = "beep" ; Sound to play when a transferer fails to dial a valid extension.
	;transferinvalidsound = "beeperr" ; Sound to play when a transferer fails to dial a valid extension and is out of retries.		;transferinvalidsound = "beeperr" ; Sound to play when a transferer fails to dial a valid extension and is out of retries.
			</pre>

			* TransferContext
			Blind 혹은 Attended transfer 를 할 경우, transfer 할 때 사용될 context 를 지정해주어야 한다. __TRANSFER_CONTEXT channel variable 에 지정해주면 된다.
			<pre>
			exten => s,1,Set(__TRANSFER_CONTEXT=TransferContext)
	</pre>		</pre>

Pchero: /* Call Parking Configuration Files and Module */

2016-12-21T10:10:14Z

Call Parking Configuration Files and Module

Show changes

Pchero: /* Enabling Features */

2016-12-20T15:01:35Z

Enabling Features

@@ Line 405: / Line 405: @@
 </pre>
 : The two leading underscores allow these feature settings to be on the outbound channels, as well. Otherwise, only the original channel will have access to these features.
 == See also ==

Pchero: /* Custom Dynamic Features */

2016-12-20T14:07:10Z

Custom Dynamic Features

@@ Line 366: / Line 366: @@
 </pre>
 * FeatureName : This is the name of the feature used when setting the DYNAMIC_FEATURES variable to enable usage of this feature.
 == See also ==

Pchero: /* Built-in Dynamic Features */

2016-12-20T13:22:27Z

Built-in Dynamic Features

@@ Line 352: / Line 352: @@
 same => n,Hangup()
 </pre>
 == See also ==

Pchero: /* Call Pickup */

2016-12-20T13:09:52Z

Call Pickup

← Older revision		Revision as of 13:09, 20 December 2016
Line 333:		Line 333:

	Named pickup groups are new with Asterisk 11.		Named pickup groups are new with Asterisk 11.

			== Built-in Dynamic Features ==
			The FEATURE and FEATUREMAP dialplan functions allow you to set some features.conf options on a per channel basis.
			: To see what options are currently supported, look at the FEATURE and FEATUREMAP function descriptions. These functions were added in Asterisk 11.
			: At this time the functions do not work with custom features. Those are set with a channel variable as described in the Custom Dynamic Features section.

			Set the parking time of this channel to be 100 seconds if it is parked.
			<pre>
			exten => s,1,Set(FEATURE(parkingtime)=100)
			same => n,Dial(SIP/100)
			same => n,Hangup()
			</pre>

			Set the DTMF sequence for attended transfer on this channel to *9.
			<pre>
			exten => s,1,Set(FEATUREMAP(atxfer)=*9)
			same => n,Dial(SIP/100,,T)
			same => n,Hangup()
			</pre>

	== See also ==		== See also ==

Pchero: /* Numeric call pickup groups */

2016-12-20T13:05:06Z

Numeric call pickup groups

@@ Line 270: / Line 270: @@
 A numeric callgroup and pickupgroup can be set to a comma separated list of ranges(e.g., 1-4) or numbers that can have a value of 0 to 63. There can be a maximum of 64 numeric groups.
 SYNTAX
-<pre>
 callgroup=[number[-number][,number[-number][,...]]]
 pickupgroup=[number[-number][,number[-number][,...]]]
@@ Line 278: / Line 279: @@
 * pickupgroup : specifies which numeric pickup groups this channel can pickup.
 Configuration example
-<pre>
 callgroup=1,5-7
 pickupgroup=1
@@ Line 298: / Line 300: @@
 pickup_group=1
 </pre>
 == See also ==

← Older revision		Revision as of 11:39, 21 December 2016
Line 748:		Line 748:
	same => n,Hangup()		same => n,Hangup()
	</pre>		</pre>

			== References ==
			<references />

	== See also ==		== See also ==