I started to test this. I am testing with a T28 and T20. When I put ** in the extension field, the phone doesn’t do anything different when I press the button. For example, if the BLF button has a value of 114 and ** in the extension, pressing the button just calls ext 114, it doesn’t dial **114 which is what I am thinking it is supposed to do??
From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Ash
Sent: Tuesday, February 21, 2012 11:50 PM
To: FreeSWITCH Users Help
Subject: Re: [Freeswitch-users] Shared Line Appearance
I spent a couple of hours trying to get it going today but no luck. I did have it working before but I would say its never been something I have been comfortable with.
My work around would be to use individual extensions and BLF keys. Just make sure you have the following set on advanced under the account on the Yealink:
* Subscribe Period(seconds) - 1800
* Subscribe Register - Enabled
* Dialog-Info Call Pickup - Enabled
Then on the DSS keys page configure the buttons like this:
- Type BLF
- Value - The remote extension e.g. 1002
- Line - The account number registered e.g. Line 1 = Account 1
- Extension - Your intercept dial plan my case **
When you put the call on hold on one of the phones it will flash on the BLF key. Then if you push the button it should dial **MONITORED_EXTENSION e.g. **1001
Here is an example of my Intercept dial plan.
<extension>
<condition field="destination_number" expression="^\*\*([0-9]{4})$">
<action application="answer"/>
<action application="intercept" data="${db(select/${domain}-last_dial_ext/$1}"/>
<action application="log" data="INFO INTERCEPT ${db(select/${domain}-last_dial_ext/$1}"/>
<action application="sleep" data="1000"/>
</condition>
</extension>
In the dial plan that dials your extensions extensions I would insert some db entries like this, replace YOUR-DOMAIN, my installation is a multi-domain scenario:
<extension name="9000 Default">
<condition field="destination_number" expression="^(9000)$">
<action application="set" data="hangup_after_bridge=true"/>
<action application="set" data="ignore_early_media=true"/>
<action application="set" data="continue_on_fail=true"/>
<action application="set" data="call_timeout=20"/>
<action application="db" data="insert/YOUR-DOMAIN-last_dial_ext/1001/${uuid}"/>
<action application="db" data="insert/YOUR-DOMAIN-last_dial_ext/1023/${uuid}"/>
<action application="bridge" data="user/1001@YOUR-DOMAIN/>
</condition>
</extension>
This is how I have got around the issue.
ash.
On 22/02/2012, at 3:02 PM, Yehavi Bourvine wrote:
Last time I tried (about half a year ago) it didn't work.
__Yehavi:
2012/2/21 Ira Tessler <ira@connectmevoice.com>
Does anybody have any documentation on how to get Yealink phones to work with Shared Line Appearance?
Ira Tessler
ConnectMe
(732) 490-9007 x2
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1913 / Virus Database: 2113/4823 - Release Date: 02/21/12