Newbie question about Polycom presence / BLF with productivity license.
Hi guys, I'm reading the following page: http://wiki.freeswitch.org/wiki/Polycom_Presence_Setup <http://wiki.freeswitch.org/wiki/Polycom_Presence_Setup> and I'm trying to make it work the "attendant" way. The phone is a 601 with 3.1.7.0134. I think the productivity license is installed correctly, both because I see the phone loading the file in the logs and that I enabled corporate directory in sip_317.cfg and I see it in menu - settings - basic - preferences. I made the mac-address-settings.cfg file as outlined, and none of the attendant things even displays on the phone. What am I missing there? Where do I start the troubleshooting? Thanks Michel.
Hello Michel, Version 3.1.7 is very old. Try the 3.3.0 version (3.3.1F loses BLF after a while). __Yehavi: 2011/4/19 Michel Py <michel@arneill-py.sacramento.ca.us>
Hi guys,
I'm reading the following page: http://wiki.freeswitch.org/wiki/Polycom_Presence_Setup and I'm trying to make it work the "attendant" way.
The phone is a 601 with 3.1.7.0134. I think the productivity license is installed correctly, both because I see the phone loading the file in the logs and that I enabled corporate directory in sip_317.cfg and I see it in menu - settings - basic - preferences.
I made the mac-address-settings.cfg file as outlined, and none of the attendant things even displays on the phone.
What am I missing there? Where do I start the troubleshooting?
Thanks Michel.
_______________________________________________ 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
Hello Yehavi,
Yehavi Bourvine wrote: Version 3.1.7 is very old. Try the 3.3.0 version (3.3.1F loses BLF after a while).
I would, if I could get it to load on a 601. I actually tried: I renamed a 3.2 file with the name that the 601 expects, no luck (it says platform does not support the software). I have read contradictory information whether "enhanced BLF" is actually working on pre-3.2. I think I understand the difference between "buddies" and "attendant" but again, if I am posting here is because I don't understand as much as I think I do :P If I am chasing a wild goose, please tell me. Michel. Michel Py <michel@arneill-py.sacramento.ca.us> Hi guys, I'm reading the following page: http://wiki.freeswitch.org/wiki/Polycom_Presence_Setup and I'm trying to make it work the "attendant" way. The phone is a 601 with 3.1.7.0134. I think the productivity license is installed correctly, both because I see the phone loading the file in the logs and that I enabled corporate directory in sip_317.cfg and I see it in menu - settings - basic - preferences. I made the mac-address-settings.cfg file as outlined, and none of the attendant things even displays on the phone. What am I missing there? Where do I start the troubleshooting? Thanks Michel. _______________________________________________ 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
On Tue, Apr 19, 2011 at 8:04 PM, Yehavi Bourvine <yehavi.bourvine@gmail.com>wrote:
Hello Michel,
Version 3.1.7 is very old. Try the 3.3.0 version (3.3.1F loses BLF after a while).
You can't do 3.3.1 on the 501 and 601 phones - they are oldies. Polycom has "legacy" firmware for those old phones and you're stuck w/ what they give you, which is indeed 3.1.7. -MC
Michael Collins You can't do 3.3.1 on the 501 and 601 phones - they are oldies. Polycom has "legacy" firmware for those old phones and you're stuck w/ what they give you, which is indeed 3.1.7.
Indeed :-( Nevertheless, according to the wiki, I should be able to do the attendant thing. http://wiki.freeswitch.org/wiki/Polycom_Presence_Setup and I'm trying to make it work the "attendant" way. What am I missing there? Where do I start the troubleshooting? Thanks Michel.
Hello Michel, The buddies worked for me a long time ago. Some day it stopped working, but since the majority of my phones have productivity license I never bothered to check why it happened. I suggest a TCPDUMP to see whether the Polycom subscribes to the watched extensions. __Yehavi: 2011/4/21 Michel Py <michel@arneill-py.sacramento.ca.us>
Michael Collins You can't do 3.3.1 on the 501 and 601 phones - they are oldies. Polycom has "legacy" firmware for those old phones and you're stuck w/ what they give you, which is indeed 3.1.7.
Indeed :-(
Nevertheless, according to the wiki, I should be able to do the attendant thing. http://wiki.freeswitch.org/wiki/Polycom_Presence_Setup and I'm trying to make it work the "attendant" way.
What am I missing there? Where do I start the troubleshooting?
Thanks Michel.
_______________________________________________ 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
Yehavi,
The buddies worked for me a long time ago.
I can make the buddy part work too, but I don't like that when the other phone is ringing, the light goes red directly. So the operator does not know if the extension was online for a while or if it's ringing. That's why I want to go the attendant way, not the buddy way.
I suggest a TCPDUMP to see whether the Polycom subscribes to the watched extensions.
I'm not there yet. I can't even get the attendant/BLF extensions to show up on the phone screen, so I suppose it does not even try to subscribe. I suspect I'm missing a step in the configuration. Michel.
Hello Michel, If I understand you correctly, then for attendant type you need the productivity license. Do you have it? If so, I'll send you sample of my config. __Yehavi: 2011/4/21 Michel Py <michel@arneill-py.sacramento.ca.us>
Yehavi,
The buddies worked for me a long time ago.
I can make the buddy part work too, but I don't like that when the other phone is ringing, the light goes red directly. So the operator does not know if the extension was online for a while or if it's ringing. That's why I want to go the attendant way, not the buddy way.
I suggest a TCPDUMP to see whether the Polycom subscribes to the watched extensions.
I'm not there yet. I can't even get the attendant/BLF extensions to show up on the phone screen, so I suppose it does not even try to subscribe. I suspect I'm missing a step in the configuration.
Michel.
_______________________________________________ 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
Yehavi Bourvine wrote: If I understand you correctly, then for attendant type you need the productivity license. Do you have it?
Yes, and I see in the logs that the phone is loading it: from tcpdump port 69 -v 17:34:57.813155 IP (tos 0x0, ttl 64, id 1322, offset 0, flags [none], proto: UDP (17), length: 61) 192.168.17.233.ams > 192.168.17.1.tftp: 33 RRQ "0004f203590e-license.cfg" octet from 0004f203590e-app.log 0413174046|copy |3|01|'tftp://192.168.17.1/0004f203590e-license.cfg' from '192.168.17.1' 0413174046|copy |3|01|Download of '0004f203590e-license.cfg' succeeded on attempt 1 (addr 1 of 1)
If so, I'll send you sample of my config.
That would be very useful, thanks. Michel.
Hello Michel, In local-phone1.cfg add: <attendant> <attendant.behaviors> <attendant.behaviors.display> <attendant.behaviors.display.spontaneousCallAppearances attendant.behaviors.display.spontaneousCallAppearances.automata="1" attendant.behaviors.display.remoteCallerID.normal="1" /> </attendant.behaviors.display> </attendant.behaviors> <attendant.resourceList attendant.resourceList.1.type="automata" (repeat it for 2, 3, etc,), </attendant> in the phone's specific configuration file add: <attendant attendant.reg="1" attendant.ringType="1" attendant.behaviors.display.spontaneousCallAppearances.normal="1" attendant.behaviors.display.spontaneousCallAppearances.automata="1" attendant.behaviors.display.remoteCallerID.normal="1" attendant.behaviors.display.remoteCallerID.automata="1" attendant.resourceList.1.address="8000" attendant.resourceList.1.label="Namei" (repeat this for the others) </attendant> I hipe this helps... __Yehavi: 2011/4/21 Michel Py <michel@arneill-py.sacramento.ca.us>
Yehavi Bourvine wrote: If I understand you correctly, then for attendant type you need the productivity license. Do you have it?
Yes, and I see in the logs that the phone is loading it:
from tcpdump port 69 -v 17:34:57.813155 IP (tos 0x0, ttl 64, id 1322, offset 0, flags [none], proto: UDP (17), length: 61) 192.168.17.233.ams > 192.168.17.1.tftp: 33 RRQ "0004f203590e-license.cfg" octet
from 0004f203590e-app.log 0413174046|copy |3|01|'tftp://192.168.17.1/0004f203590e-license.cfg' from '192.168.17.1' 0413174046|copy |3|01|Download of '0004f203590e-license.cfg' succeeded on attempt 1 (addr 1 of 1)
If so, I'll send you sample of my config.
That would be very useful, thanks.
Michel.
_______________________________________________ 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
I'm not there yet. I can't even get the attendant/BLF extensions to show up on the phone screen, so I suppose it does not even try to subscribe. I suspect I'm missing a step in the configuration.
Hi Michel! Just a wild guess - are you actually loading the file with the attendant-settings? Usually phone1.cfg or $MAC-phone1.cfg - there should be an entry in the basic $MAC.cfg for this file. Best regards Christian
Hi Christian and Yehavi, Thanks for the time looking into this!
Christian Benke wrote: Just a wild guess - are you actually loading the file with the attendant-settings? Usually phone1.cfg or $MAC-phone1.cfg - there should be an entry in the basic $MAC.cfg for this file.
Thanks for suggesting this; it did not solve my problem, but it made me change / clean my test setting for the better. Here is my new test procedure: - On the phone, I regularly do erase local config, factory settings, and format file system. Just to be sure. - I completely cleaned the /tftpboot directory, except for 2 files: 0004f2xxxxxx-phone.cfg 0004f2xxxxxx-license.cfg - Extracted the files from the Polycom zip into /tftpboot, tried that both with 3.1.7 and 3.1.0 rev C. I can positively confirm that even after a format file system, the phone will successfully load both the 3.x SIP version of the moment AND the 0004f2xxxxxx-phone.cfg. - I don't bother to have a 0004f2xxxxxx.cfg file anymore. I don't need it as long as I keep the 0000000000000.cfg file into /tftproot. It finds the phone1_31x.cfg and the sip_31x.cfg files just fine. - About the reading of the 0004f2xxxxxx-phone.cfg: I am absolutely positive that it reads it for 2 reasons: 1. I can see it in tcpdump port 69 -v 2. Changes made to 0004f2xxxxxx-phone.cfg will show up on the phone after reboot. I pasted the current version of the file below. It reads the file, parses it, and some parts work and some don't. What does work: - The reg.1.stuff. The line shows up, registers, can make calls, etc. - The SNTP timezone stuff. Changes to the gmtOffset value will show up at next phone reboot. - The presence feature. Changing it to "1" will indeed enable the feature, and if I add buddy entries in the directory (from the phone itself) they actually work, with their known limitations. If enabled, the "MyStat" and "Buddies" softkey do appear on the main screen, and do go out if deactivated. - The corporate directory feature. I have not actually tested it, but the feature does show in the menus when activated and not when deactivated. What does not work: - The attendant thing (duh). - Trying to disable the "MyStat" and "Buddies" softkeys when presence is enabled. In short: - The phone DOES read the 0004f2xxxxxx-phone.cfg file. - When it parses it, some functions work and some don't. - In my tests, it does not matter in which file you put things. Let's say the TZ commands or the feature commands: they work regardless if I put them in 0004f2xxxxxx-phone.cfg or in {phone1_31x.cfg|sip_31x.cfg}. I know, I'm not supposed to modify these but I did try, and it does work as expected. Same applies to the attendant commands: regardless of which file you put them in, they don't work. - In case it was not clear: I can make the "buddies" thing work any way I want, and I can't make the "attendant" way work at all, regardless of what I do. I have tried about 25 different variants, no go. What bugs the ##^%@# out of me is this: Whether it actually works or does anything at all, just the following 2 lines should display something on the phone's screen: attendant.resourceList.1.address="8000" attendant.resourceList.1.label="Name1" So the LED may not change, the button may not work, but it should show. It does not. So my problem is not that the phone does or does not register with the server, which may or may not work... It's that the phone fails to parse the config file for these items. Feedback more than welcome! Thanks, Michel. <?xml version="1.0" encoding="utf-8" standalone="yes"?> <userinfo> <reg reg.1.displayName="Test 2499" reg.1.address="2499" reg.1.type="private" reg.1.auth.userId="2499" reg.1.auth.password="xxxxxxx" reg.1.server.1.register="1" reg.1.server.1.address="192.168.17.1" reg.1.server.1.port="5060" /> </userinfo> <attendant attendant.reg="1" attendant.ringType="1" attendant.behaviors.display.spontaneousCallAppearances.normal="1" attendant.behaviors.display.spontaneousCallAppearances.automata="1" attendant.behaviors.display.remoteCallerID.normal="1" attendant.behaviors.display.remoteCallerID.automata="1" attendant.resourceList.1.address="8000" attendant.resourceList.1.label="Name1" attendant.resourceList.2.address="8001" attendant.resourceList.2.label="Name2" /> <softkey softkey.feature.mystatus="0" softkey.feature.buddies="0" /> <SNTP tcpIpApp.sntp.gmtOffset="-25200" /> <feature feature.1.name="presence" feature.1.enabled="0" feature feature.19.name="corporate-directory" feature.19.enabled="0" />
Hello Michel, Please start TCPDUMP of your phone for port 5060 only, and reboot it. After it is up do a few operations on the watched phones (i.e. extensions 8000, 8001) like oroginating and receiving calls, and send me the resultant dump. Regards, __Yehavi: 2011/4/23 Michel Py <michel@arneill-py.sacramento.ca.us>
Hi Christian and Yehavi,
Thanks for the time looking into this!
Christian Benke wrote: Just a wild guess - are you actually loading the file with the attendant-settings? Usually phone1.cfg or $MAC-phone1.cfg - there should be an entry in the basic $MAC.cfg for this file.
Thanks for suggesting this; it did not solve my problem, but it made me change / clean my test setting for the better. Here is my new test procedure:
- On the phone, I regularly do erase local config, factory settings, and format file system. Just to be sure.
- I completely cleaned the /tftpboot directory, except for 2 files: 0004f2xxxxxx-phone.cfg 0004f2xxxxxx-license.cfg
- Extracted the files from the Polycom zip into /tftpboot, tried that both with 3.1.7 and 3.1.0 rev C. I can positively confirm that even after a format file system, the phone will successfully load both the 3.x SIP version of the moment AND the 0004f2xxxxxx-phone.cfg.
- I don't bother to have a 0004f2xxxxxx.cfg file anymore. I don't need it as long as I keep the 0000000000000.cfg file into /tftproot. It finds the phone1_31x.cfg and the sip_31x.cfg files just fine.
- About the reading of the 0004f2xxxxxx-phone.cfg: I am absolutely positive that it reads it for 2 reasons:
1. I can see it in tcpdump port 69 -v 2. Changes made to 0004f2xxxxxx-phone.cfg will show up on the phone after reboot.
I pasted the current version of the file below. It reads the file, parses it, and some parts work and some don't.
What does work: - The reg.1.stuff. The line shows up, registers, can make calls, etc. - The SNTP timezone stuff. Changes to the gmtOffset value will show up at next phone reboot. - The presence feature. Changing it to "1" will indeed enable the feature, and if I add buddy entries in the directory (from the phone itself) they actually work, with their known limitations. If enabled, the "MyStat" and "Buddies" softkey do appear on the main screen, and do go out if deactivated. - The corporate directory feature. I have not actually tested it, but the feature does show in the menus when activated and not when deactivated.
What does not work: - The attendant thing (duh). - Trying to disable the "MyStat" and "Buddies" softkeys when presence is enabled.
In short: - The phone DOES read the 0004f2xxxxxx-phone.cfg file. - When it parses it, some functions work and some don't.
- In my tests, it does not matter in which file you put things. Let's say the TZ commands or the feature commands: they work regardless if I put them in 0004f2xxxxxx-phone.cfg or in {phone1_31x.cfg|sip_31x.cfg}. I know, I'm not supposed to modify these but I did try, and it does work as expected. Same applies to the attendant commands: regardless of which file you put them in, they don't work.
- In case it was not clear: I can make the "buddies" thing work any way I want, and I can't make the "attendant" way work at all, regardless of what I do. I have tried about 25 different variants, no go.
What bugs the ##^%@# out of me is this: Whether it actually works or does anything at all, just the following 2 lines should display something on the phone's screen: attendant.resourceList.1.address="8000" attendant.resourceList.1.label="Name1"
So the LED may not change, the button may not work, but it should show. It does not. So my problem is not that the phone does or does not register with the server, which may or may not work... It's that the phone fails to parse the config file for these items.
Feedback more than welcome!
Thanks, Michel.
<?xml version="1.0" encoding="utf-8" standalone="yes"?> <userinfo> <reg reg.1.displayName="Test 2499" reg.1.address="2499" reg.1.type="private" reg.1.auth.userId="2499" reg.1.auth.password="xxxxxxx" reg.1.server.1.register="1" reg.1.server.1.address="192.168.17.1" reg.1.server.1.port="5060" /> </userinfo>
<attendant attendant.reg="1" attendant.ringType="1" attendant.behaviors.display.spontaneousCallAppearances.normal="1" attendant.behaviors.display.spontaneousCallAppearances.automata="1" attendant.behaviors.display.remoteCallerID.normal="1" attendant.behaviors.display.remoteCallerID.automata="1" attendant.resourceList.1.address="8000" attendant.resourceList.1.label="Name1" attendant.resourceList.2.address="8001" attendant.resourceList.2.label="Name2" />
<softkey softkey.feature.mystatus="0" softkey.feature.buddies="0" /> <SNTP tcpIpApp.sntp.gmtOffset="-25200" /> <feature feature.1.name="presence" feature.1.enabled="0" feature feature.19.name="corporate-directory" feature.19.enabled="0" />
_______________________________________________ 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
<attendant attendant.reg="1" attendant.ringType="1" attendant.behaviors.display.spontaneousCallAppearances.normal="1" attendant.behaviors.display.spontaneousCallAppearances.automata="1" attendant.behaviors.display.remoteCallerID.normal="1" attendant.behaviors.display.remoteCallerID.automata="1" attendant.resourceList.1.address="8000" attendant.resourceList.1.label="Name1" attendant.resourceList.2.address="8001" attendant.resourceList.2.label="Name2" />
I don't think this is the cause of the problem - but what about attendant.resourceList.1.type? attendant.resourceList.1.type="automata" None of these attendant-parameters are listed in the 3.1.7 sip admin guide though(In the 3.3.0-guide they are). I didn't look deeply into the docs - is this actually supposed to work in 3.1.7? Regards Christian
Christian,
Christian Benke wrote: I don't think this is the cause of the problem - but what about attendant.resourceList.1.type? attendant.resourceList.1.type="automata"
Nice catch (I posted my latest try) but no cigar, sorry. And yes I did try again. You have sharp eyes.
None of these attendant-parameters are listed in the 3.1.7 sip admin guide though(In the 3.3.0-guide they are). I didn't look deeply into the docs - is this actually supposed to work in 3.1.7?
That is THE question, indeed. Well, supposedly, according to the wiki that started this, regular 3.1.0 won't work but 3.10 with the productivity license would. I did not challenge the wiki earlier because I am both a freeswitch and a polycom idiot, but I am starting to doubt it. Oh, unrelated and FWIW, I have conducted another quick round of stupid experiments this morning. Note the "blah" line. I literally tried this. <?xml version="1.0" encoding="utf-8" standalone="yes"?> <userinfo> <reg reg.1.displayName="Test 2499" reg.1.blah="Blah" reg.1.address="2499" {<other commands snipped} /> </userinfo> Well the "blah" line acts as expected: it does not do anything, but it does not break anything either. That part of the config file was working fine before, and it still is after the introduction of the "blah" thing, so we can safely assume, as expected, that the inclusion of a not-yet-implemented command (that would be the case with a 3.2 command in a 3.1 config file) does not do anything (heck that would be nice, btw: do what I expect future software to do) but does not break anything either. In a lousy effort to compensate for your time reading this, I offer you the syntax of the new polycom software: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <userinfo> <reg reg.1.MagicMindRead="read_the_user's_mind" reg.1.MagicAction="implement_thought" /> </userinfo> :D Michel.
Well the "blah" line acts as expected: it does not do anything, but it does not break anything either.
Haha, so you are not too frustrated, that's good :-) I've taken a look at http://downloads.polycom.com/voice/voip/uc/UC_Software_Release_Notes_3_3_1F.... and on page 44 you will find that the BLF-features including the enhanced attendant-features where introduced with firmware version 3.2 - sorry to say, but you're most probably out of luck. I've updated the wiki accordingly. Best regards Christian
Christian Benke wrote: you will find that the BLF-features including the enhanced attendant features where introduced with firmware version 3.2
I found some other references that mentioned something with 3.1, though. http://support.polycom.com/global/documents/support/technical/products/v oice/SoundPoint_IP_Enhanced_BLF_QT37381.pdf http://www.polycomnz.co.nz/software/spip_ssip_3_1_0RevB_relnotes.pdf http://blog.voipsupply.com/polycom-sip-firmware-31-released-whats-in-it- for-me Are you the author of the original wiki page?
Are you the author of the original wiki page?
nope. Interesting links - have you tried to remove the attendant-settings from the FS-wiki and to only apply the settings listed in spip_ssip_3_1_0RevB_relnotes.pdf resp. http://supportdocs.polycom.com/PolycomService/support/global/documents/suppo... So the BLF-configuration is probably working, but not as straightforward as documented in the wiki(attendant.uri and stuff). I've updated the wiki again to reflect your findings. Regards Christian
Christian,
So the BLF-configuration is probably working, but not as straightforward as documented in the wiki(attendant.uri and stuff).
That would not solve my problem; I have read in multiple places that there could be only one attendant.uri, and I need more. I guess I will fall back to buddies; if only I could make the light blink when ringing instead of going directly solid red. I have the feeling I'm missing something stupid, since it's my first encounter with Polycom (I'm not thrilled, BTW). Oh well, thanks for the time. Michel.
On 27 April 2011 21:24, Michel Py <michel@arneill-py.sacramento.ca.us> wrote:
Christian,
So the BLF-configuration is probably working, but not as straightforward as documented in the wiki(attendant.uri and stuff).
That would not solve my problem; I have read in multiple places that there could be only one attendant.uri, and I need more.
Yeah, sorry, i'm out of ideas. Think about upgrading the phones if you have a chance, the feature works just fine on the new generation of phones(Had it setup in 10min last week).
I have the feeling I'm missing something stupid, since it's my first encounter with Polycom (I'm not thrilled, BTW).
Well, it seems you did not yet see what nightmares other vendors sell ;-) Polycom are phantastic phones(imho the best on the market), the documentation is extensive and detailed and the provisioning options are marvellous. The interface is intuitive and the hardware is well laid-out, both mechanical and performance-wise. These phones are clearly built by engineers and i'm not surprised they are so popular. Best regards Christian
participants (5)
-
Brian West
-
Christian Benke
-
Michael Collins
-
Michel Py
-
Yehavi Bourvine