Custom Destinations - Revision history

Admin at 09:58, 22 May 2020

2020-05-22T09:58:23Z

← Older revision		Revision as of 09:58, 22 May 2020
Line 42:		Line 42:

	[[file:runlocalmacro.png\|400px]]		[[file:runlocalmacro.png\|400px]]

			== Search and update/insert in a phone book ==

			You can search one of your phone book/database and insert or update the value inserted in any of the fields.

			For example, you can ask to the caller his account number and save in the database for later retrieval together based on his callerID.

			Mind to have the following Phone Book defined

			[[File:Searchandupdatephonebook1.png\|400px]]

			Mind you have already read the account number from your caller and saved in the variable "USR-accountnumber", you can define the custom destination as following:

			[[File:Searchandupdatephonebook2.png\|400px]]

			In this way you search/update or create the entry with the callerid name, then you can do the same with the account number

			[[File:Searchandupdatephonebook3.png\|400px]]

Admin: /* Route the call by looking up the value from the database */

2019-09-03T09:32:54Z

Route the call by looking up the value from the database

← Older revision		Revision as of 09:32, 3 September 2019
Line 28:		Line 28:

	[[File:Route by looking up value.png\|400px]]		[[File:Route by looking up value.png\|400px]]

			The Custom destination can be configured this way:

			[[File:Route by looking up value from database.png\|400px]]

			The Phone book needs to contain the data to lookup in the "Lookup value" column

			[[File:Lookup value phonebook.png\|400px]]

	== Run Local Macro ==		== Run Local Macro ==

Admin: /* Route the call by looking up the value from the database */

2019-09-03T09:19:48Z

Route the call by looking up the value from the database

← Older revision		Revision as of 09:19, 3 September 2019
Line 27:		Line 27:
	So in the DID destination you may enter something like:		So in the DID destination you may enter something like:

	[[File:Route by looking up value.png\|~~thumb~~]]		[[File:Route by looking up value.png\|400px]]

	== Run Local Macro ==		== Run Local Macro ==

Admin: /* Route the call by looking up the value from the database */

2019-09-03T09:19:06Z

Route the call by looking up the value from the database

← Older revision		Revision as of 09:19, 3 September 2019
Line 22:		Line 22:

	== Route the call by looking up the value from the database ==		== Route the call by looking up the value from the database ==

			Using this feature you can use a Phone Book as a Database to lookup a value contained in a variable and then perform a specific routing for a call. Let's make an example. You have a list of customer ID and you want to route the call in a different way (different Queue, different Escalation, Voicemail...) based on the Customer ID. So you may ask the caller to enter the customer ID and then route the call based on the value entered.

			So in the DID destination you may enter something like:

			[[File:Route by looking up value.png\|thumb]]

	== Run Local Macro ==		== Run Local Macro ==

Admin at 09:14, 3 September 2019

2019-09-03T09:14:51Z

← Older revision		Revision as of 09:14, 3 September 2019
Line 20:		Line 20:

	So for listening to the 6th message from voicemail 104, you can dial 881046		So for listening to the 6th message from voicemail 104, you can dial 881046

			== Route the call by looking up the value from the database ==

	== Run Local Macro ==		== Run Local Macro ==

Admin at 09:05, 3 September 2019

2019-09-03T09:05:29Z

← Older revision		Revision as of 09:05, 3 September 2019
Line 1:		Line 1:
	Custom Destination is one of the most powerful object in MiRTA PBX. It is the magic object ~~capable~~ able to perform all the disparate tasks you may need. The list of capability is increasing at every version.		Custom Destination is one of the most powerful object in MiRTA PBX. It is the magic object able to perform all the disparate tasks you may need. The list of capability is increasing at every version.

	[[file:customdestinations.png\|400px]]		[[file:customdestinations.png\|400px]]

Admin at 07:09, 1 September 2017

2017-09-01T07:09:30Z

← Older revision		Revision as of 07:09, 1 September 2017
Line 15:		Line 15:
	== Play Voicemail Message ==		== Play Voicemail Message ==

	This feature allows ~~to play~~ directly a voicemail message. The voicemail message is not marked as read. This feature is usually used to build "Visual Voicemail" for phones supporting it. It can be used in a feature code like *88[NUM] and then splitting the voicemail box and voicemail message number using CUT function		This feature allows playing directly a voicemail message. The voicemail message is not marked as read. This feature is usually used to build "Visual Voicemail" for phones supporting it. It can be used in a feature code like *88[NUM] and then splitting the voicemail box and voicemail message number using CUT function

	[[file:playvoicemailmessage.png\|400px]]		[[file:playvoicemailmessage.png\|400px]]
Line 21:		Line 21:
	So for listening to the 6th message from voicemail 104, you can dial 881046		So for listening to the 6th message from voicemail 104, you can dial 881046

	==		== Run Local Macro ==

			This feature allows executing a custom macro defined in the system. You can define a local macro by uploading a .conf file in /etc/asterisk/extensions.d

			[[file:runlocalmacro.png\|400px]]

Admin at 07:07, 1 September 2017

2017-09-01T07:07:39Z

← Older revision		Revision as of 07:07, 1 September 2017
Line 20:		Line 20:

	So for listening to the 6th message from voicemail 104, you can dial 881046		So for listening to the 6th message from voicemail 104, you can dial 881046

			==

Admin at 19:19, 12 May 2017

2017-05-12T19:19:37Z

← Older revision		Revision as of 19:19, 12 May 2017
Line 12:		Line 12:

	Almost identical to "Alter CallerID Name", but acting on the number		Almost identical to "Alter CallerID Name", but acting on the number

			== Play Voicemail Message ==

			This feature allows to play directly a voicemail message. The voicemail message is not marked as read. This feature is usually used to build "Visual Voicemail" for phones supporting it. It can be used in a feature code like *88[NUM] and then splitting the voicemail box and voicemail message number using CUT function

			[[file:playvoicemailmessage.png\|400px]]

			So for listening to the 6th message from voicemail 104, you can dial 881046

Admin: Created page with "Custom Destination is one of the most powerful object in MiRTA PBX. It is the magic object capable able to perform all the disparate tasks you may need. The list of capability..."

2016-11-30T21:56:21Z

Created page with "Custom Destination is one of the most powerful object in MiRTA PBX. It is the magic object capable able to perform all the disparate tasks you may need. The list of capability..."

New page

Custom Destination is one of the most powerful object in MiRTA PBX. It is the magic object capable able to perform all the disparate tasks you may need. The list of capability is increasing at every version.

[[file:customdestinations.png|400px]]

== Alter CallerID Name ==

[[file:altercalleridname.png|400px]]

Permit to change the caller ID name of a call. You can use variables like ${CALLERID(name)} or ${CALLERID(num)} so you can just add something to the received caller ID name

== Alter CallerID Num ==

Almost identical to "Alter CallerID Name", but acting on the number