*53 – Call Forward No Answer/Unavailable Deactivate *52 – Call Forward No Answer/Unavailable Activate *92 – Call Forward Busy Prompting Deactivate *94 - Call Forward Busy Promping Activate Note how I use the BLFGroup= to setup a subscription for 1050, then in the key section, key 27 (third up from bottom) is the BLF key for 1050 The below file is the MN_userID.cfg file in my TFTP server. Then in the section you define a key as Fea='27' Fill the quotes with a comma separated list of extensions to monitor. In the section you need to define the users you want to subscribe to BLF updates for. Just as your phone wont work for you without both the user and the key setup, so the busy lamps wont work without a modification in both of those sections. On these phones you have the tag section to define your user and also the section to define the keys. I scoured the Internet and having patched together a couple of resources managed to get them to work.

Last week I was asked to use these phones and get the BLF working. While my configuration on that particular job used the programable keys on the phone, there was no call for Busy Lamps. It looked like thisĮxten => 2800,n(busy-check),GotoIf($[$)=NOT_INUSE))Ī few years ago I posted a how to guide to getting Mitel dual mode phones into SIP mode and registering them on your SIP server. Then I used WinSCP to open extensions_override_nf and I pasted in the section. I copied the two sections and pasted them into notepad so that I had got an original copy of the config. This took me to a context called and below it. I dod a search for the page group number which was 2800. I used WinSCP to get into the FreePBX file system and opened extensions _nf.

Any config FreePBX writes into here can be overwritten in etc/asterisk/extensions_override_nf. That meant we would need to find a way to modify the config files.Īny config done in the GUI is written into etc/asterisk/extensions_nf. We had a look and the GUI doesn't allow for it.

The customer asked if we could set a maximum page length. This meant that all the other extensions were locked busy for quite some time.

The customer had a user who made a page to a group of handsets but did not hangup his extension properly. We had an issue this week with paging on FreePBX.

Freepbx tftp server