Configuring BLF on a phone - Revision history

Admin at 17:04, 20 November 2023

2023-11-20T17:04:45Z

← Older revision		Revision as of 17:04, 20 November 2023
Line 22:		Line 22:

	There are some special extension to be monitored. You can monitor a queue for callers, monitoring the number associated to the queue with the tenant code, like 781-DEVEL.		There are some special extension to be monitored. You can monitor a queue for callers, monitoring the number associated to the queue with the tenant code, like 781-DEVEL.

			== Monitoring the voicemail ==

			You can monitor a voicemail with a normal BLF button. You need to define a feature code to retrieve the voicemail, like 97[NUM] and then define 97 in Configuration/Settings, as "Enable Voicemail MWI with prefix:". So if the voicemail you want to monitor is 104 in tenant DEVEL, you can monitor *97104-DEVEL.

			== Using the voicemail button ==

			Some phones have a voicemail button, so if you define the voicemail to monitor in the extension, the voicemail button will light up when there is a voicemail. The phone allows you to configure a special destination to dial when pressing it. If you have defined to retrieve the voicemail with the 97[NUM] prefix and your voicemail is the 104, you can configure 97104

Admin at 12:44, 16 September 2017

2017-09-16T12:44:48Z

← Older revision		Revision as of 12:44, 16 September 2017
Line 5:		Line 5:
	The important thing to remember is the value to monitor will be the "username" of the phone, not just the number. So if you have extension 100 in tenant DEVEL, you need to monitor 100-DEVEL. You can check easily if the monitoring is correct using the command "asterisk -rx 'core show hints'"		The important thing to remember is the value to monitor will be the "username" of the phone, not just the number. So if you have extension 100 in tenant DEVEL, you need to monitor 100-DEVEL. You can check easily if the monitoring is correct using the command "asterisk -rx 'core show hints'"

	<~~code~~>		<pre>
	# asterisk -rx 'core show hints'		# asterisk -rx 'core show hints'

Line 17:		Line 17:
	----------------		----------------
	- 6 hints registered		- 6 hints registered
	</~~code~~>		</pre>

	If you make a mistake and start to monitor something like '100DEVEL', without the dash, that will be a big problem because asterisk will refuse any other change in that extension to monitor. In other words, if you start monitoring 100DEVEL and then reconfigure the phone to monitor 100-DEVEL, asterisk will continue to monitor 100DEVEL... and that will not work. The only solution, in this case, is to restart asterisk.		If you make a mistake and start to monitor something like '100DEVEL', without the dash, that will be a big problem because asterisk will refuse any other change in that extension to monitor. In other words, if you start monitoring 100DEVEL and then reconfigure the phone to monitor 100-DEVEL, asterisk will continue to monitor 100DEVEL... and that will not work. The only solution, in this case, is to restart asterisk.

	There are some special extension to be monitored. You can monitor a queue for callers, monitoring the number associated to the queue with the tenant code, like 781-DEVEL.		There are some special extension to be monitored. You can monitor a queue for callers, monitoring the number associated to the queue with the tenant code, like 781-DEVEL.

Admin: Created page with "If you want to monitor an extension status from another phone, you need to configure the phone for BLF. Based on the brand of phone, it is named in different ways, for example..."

2017-09-16T12:44:34Z

Created page with "If you want to monitor an extension status from another phone, you need to configure the phone for BLF. Based on the brand of phone, it is named in different ways, for example..."

New page

If you want to monitor an extension status from another phone, you need to configure the phone for BLF. Based on the brand of phone, it is named in different ways, for example on Yealink the section is named "DSS Keys".

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

The important thing to remember is the value to monitor will be the "username" of the phone, not just the number. So if you have extension 100 in tenant DEVEL, you need to monitor 100-DEVEL. You can check easily if the monitoring is correct using the command "asterisk -rx 'core show hints'"

<code>
# asterisk -rx 'core show hints'

-= Registered Asterisk Dial Plan Hints =-
103-DEVEL@authentica: Custom:103-DEVEL State:Idle Presence:not_set Watchers 1
104-DEVEL@authentica: Custom:104-DEVEL State:Idle Presence:not_set Watchers 1
105-DEVEL@authentica: Custom:105-DEVEL State:Idle Presence:not_set Watchers 1
50019-DEVEL@authenti: Custom:50019-DEVEL State:Idle Presence:not_set Watchers 1
781-DEVEL@authentica: Custom:781-DEVEL State:Idle Presence:not_set Watchers 1
_X.@authenticated : Custom:${EXTEN} State:Unavailable Presence: Watchers 0
----------------
- 6 hints registered
</code>

If you make a mistake and start to monitor something like '100DEVEL', without the dash, that will be a big problem because asterisk will refuse any other change in that extension to monitor. In other words, if you start monitoring 100DEVEL and then reconfigure the phone to monitor 100-DEVEL, asterisk will continue to monitor 100DEVEL... and that will not work. The only solution, in this case, is to restart asterisk.

There are some special extension to be monitored. You can monitor a queue for callers, monitoring the number associated to the queue with the tenant code, like 781-DEVEL.