Call park with Polycom's EFK (enhanced feature key)
I came across this literature on polycoms site and was interested to know if anyone that has the appropriate partner license got this to work succesfully with TB:
http://knowledgebase.polycom.com/kb/search.do?cmd=displayKC&docTy...
For one thing TB uses 70 to park the call, unlike in this article it suggests using *68 to park a call. Not sure how to go about that.....
in my SpeedDial, I have the macro linked to SD 2 with a !callpark name to it, matching the efk settings, but when I hit the SD2 when on an active call, i get a busy tone, changing the 70 to a *68 doesnt help or make any difference.
I have a demo site license for about a month, and I have attempted it with no luck so far.
I have BR 4.1 and SIP ver 3.0.2 running on IP 501
thanks.
My point is you could look at the sip data coming to Freebpx from the Polycom phone. Set's say it is sending *68, or if you have to dial something like 1, maybe Polycom send *681 to Freepbx. Ok, then in Freepbx, all you have to do is translate whatever the Polycom sends, into what Freepbx wants. You can translate number-sequences with "Misc Application"/"Misc Destination" in Trixbox. That way you can leave the Polycom in its current form, no need to figure out how to program its obscure methods, just use what it does, and convert it to what you want.
well heres the problem, the polycom isnt doing what its supposed to be doing, which is running a macro.
I realize what you are saying and I agree with you, but first I cant even get polycom 501 to do what its designed to do as per polycoms article.....
it wont dial the *68 nor would it dial ##70# and I even tried to get it to dial 12346 and still it gives me a busy tone....so there is something else wrong
Here's a shot in the dark as I want to see you prevail.
Here is their example code:
...
efk.efklist.2.mname="callpark"
efk.efklist.2.status="1"
efk.efklist.2.label="Call Park"
efk.efklist.2.use.idle="1"
efk.efklist.2.use.active="1"
efk.efklist.2.use.alerting="1"
efk.efklist.2.use.dialtone="1"
efk.efklist.2.use.proceeding="1"
efk.efklist.2.use.setup="1"
efk.efklist.2.type="invite"
efk.efklist.2.action.string="*68*$P1N10$"
...
/>
What about changing from "invite" to "refer"? I just skimmed their... documentation, and am hoping that "refer" will perfom something akin to a transfer.
try: efk.efklist.2.action.string="70"
and
efk.efklist.2.action.string="##70#"
or
efk.efklist.2.action.string="##70"
and see if that gets you anywhere... at your own risk of course.
George
George,
You earn the unofficial user forum gold star and purple jelly bean award.
Whoever has the trial license try this it should work.
Looking at our the IETF SIP RFC's on refer method vs Invite I found this gem:
REFER is a SIP method as defined by RFC 3261 . The REFER method
indicates that the recipient (identified by the Request-URI) should
contact a third party using the contact information provided in the
request. Unless stated otherwise, the protocol for emitting and responding to
a REFER request are identical to those for a BYE request in . The
behavior of SIP entities not implementing the REFER (or any other
unknown) method is explicitly defined in .
Now we all assume the Asterisk and Polycom follow the letter of the SIP RFC's however that is not guaranteed. This has a very good chance of working.
Is the Polycom EFK documentation available on the public web site?
Thanks George.....
One Button Parking is Working...
Here's the code from my sip.cfg:
<feature feature.18.name="enhanced-feature-keys" feature.18.enabled="1" /> <efk> <version efk.version="1" /> <efklist efk.efklist.1.mname="callpark" efk.efklist.1.status="1" efk.efklist.1.label="Call Park" efk.efklist.1.use.idle="1" efk.efklist.1.use.active="1" efk.efklist.1.use.alerting="1" efk.efklist.1.use.dialtone="1" efk.efklist.1.use.proceeding="1" efk.efklist.1.use.setup="1" efk.efklist.1.type="refer" efk.efklist.1.action.string="100" /> </efk>
*If you use this make sure the forum didn't screw with the formating.
I was emailed a trial key a few hours ago, and have been rebooting-away. The problem was two fold:
a) Polycom's example code didn't include the <version efk.version="1" /> statement which is REQUIRED.
b) the "invite" variable needed to be changed to efk.efklist.1.type="refer"
The License Key simply needs to be placed in the provisioning directory, then you are good to go.
I have more experimenting to do.
George
The feature key license (not trial license) is issued by Polycom only.
I believe you will need to register on polycom's site first and then with the help of a reseller (authorized only) you can acquire a license (per unit or per site) the necessary key etc.
Polycom has come up with this "exciting" new way for resellers to make some extra $$$ sheesh
... 888voipstore.com
Just search for "productivity suite individual license." The licenses are not that expensive, but IMHO it's still wrong that Polycom insists on charging for these types of features when Aastra throws all of the functionality in as soon as they can develop it. Even the old Aastras can accomplish one button call park...and reprogramming of buttons including linking buttons to URLs for retrieval by the XML browser...without an extra license of any kind.
Edit: You might want to make sure (somehow?) that the productivity license includes support for efk. If not, well, this might be even way harder to implement without being a partner.
According to the release notes for SIP 3.0.0 it says that the EFK license is intended to be free.
Check out PDF page 8 (not the document's page 8) there is a chart which outlines the features. One of them is EFK and it says "partner license". If you look at the bottom of the chart. It says "partner license - License by agreement with partner (intended to be free)"
So maybe the partner is supposed to supply that license at no cost?
888voipstore.com is selling the productivity suite license, but that is not the license you need based on the chart. The chart also lists the productivity suite license and for efk it says it needs partner license.
-Rich
I have a few scripts working with EFK 1.0, as soon as I get some time to work with the next version I'll post my code.
Use at your own risk... but for the *current version* here is my trial-and-error-produced transfer-to-VM & call-park script:
<efk> <version efk.version="1" /> <efklist efk.efklist.1.mname="callpark" efk.efklist.1.status="1" efk.efklist.1.label="Park Call" efk.efklist.1.use.idle="1" efk.efklist.1.use.active="1" efk.efklist.1.use.alerting="1" efk.efklist.1.use.dialtone="1" efk.efklist.1.use.proceeding="1" efk.efklist.1.use.setup="1" efk.efklist.1.type="refer" efk.efklist.1.action.string="100" /> <efklist efk.efklist.2.mname="vmtransfer" efk.efklist.2.status="1" efk.efklist.2.label="VM Trans" efk.efklist.2.use.idle="1" efk.efklist.2.use.active="1" efk.efklist.2.use.alerting="1" efk.efklist.2.use.dialtone="1" efk.efklist.2.use.proceeding="1" efk.efklist.2.use.setup="1" efk.efklist.2.type="refer" efk.efklist.2.action.string="*$P1N3$" /> <efkprompt efk.efkprompt.1.status="1" efk.efkprompt.1.label="3 Digit Extension?: " efk.efkprompt.1.userfeedback="visible" efk.efkprompt.1.type="numeric" efk.efkprompt.1.digitmatching="style1" /> </efk>
George
Last Friday Polycom released SIP application ver 3.1.0 Rev. B. However download is available for Polycom Certified VoIP Resellers only. Does anyone here have access to Polycom Resource Center (PRC)? I'm highly interested in testing new EFK version. Two weeks ago we purchased for testing purposes couple of licenses of Polycom Productivity Suite, which enables EFK 1.0 on SIP 3.0. We still need unlock EFK on ~50 phones. We use EFK for one button Call Parking. We'd like to use it to simplify some other multi-button features.
Derek
Derek -
I have a copy of 3.1.0 Rev.B that I am testing now. Send me a private message with your email and I will post a copy for you.
Jonathan Ray
Proactive Networking
www.pbx-supply.com
Here is the code to add for one touch park to work with SIP version 3.1.0:
<efk> <version efk.version="2" /> <efklist efk.efklist.1.mname="callpark" efk.efklist.1.status="1" efk.efklist.1.label="Call Park" efk.efklist.1.use.idle="1" efk.efklist.1.use.active="1" efk.efklist.1.use.alerting="1" efk.efklist.1.use.dialtone="1" efk.efklist.1.use.proceeding="1" efk.efklist.1.use.setup="1" efk.efklist.1.action.string="70$Trefer$" /> </efk> <softkey softkey.1.label="Park" softkey.1.action="70$Trefer$" softkey.1.enable="1" softkey.1.use.active="1" />
Just change "70" to whatever parking extension you use. It will add a new softkey on active calls labeled "Park".
Would I also be able to grab a copy of that from you? I have a customer that needs us to make a custom transfer button that will use Asterisk's built-in transfer mechanism (##) so that I can modify it to return a call to the original transferrer after 4 rings.
Is this going to ever be available to the general public or will you have to always get it through a reseller?
Much appreciated!
-Rich
update sip.cfg
There is an nice example on page 4-48 of how to get it setup in your item_list of the latest firmware guide
http://www.polycom.com/common/documents/support/setup_maintenance...



Member Since:
2007-01-22