Do you guys use the polycom module?
travis
Posts: 180
Or maintain your own? (In larger systems that aren't just a HDX and a video display?)
Follow up question, why is there a password on the .doc that comes in the zip from inconcert?
Follow up question, why is there a password on the .doc that comes in the zip from inconcert?
0
Comments
If I have to supply an address book I use a module because it would be a big task writing that myself.
As the RealPresence Group series codecs don't support keypad emulation I use IR if possible otherwise the module.
I have not come across a zipped doc, now that's taking closed source to a new level!
looking in the integratorsdocument for the software release there is the following;
button <#|*|0|1|2|3|4|5|6|7|8|9|.>
button <down|left|right|select|up>
button <back|call|graphics|hangup>
button <help|mute|volume+|volume->
button <camera|delete|directory|home|keyboard|period|pip|preset> button info
Should make all of our lives slightly easier...
Ed
Just wondering if anyone has used the RPG Module, I've got the majority of it running but the Address Book is only reporting Local and not Global, has anyone got the Global Address Book coming back into the UI?
cheers
when a assign the device to 41001:2:0
and try to search on the address book i receive this message in debugger
Line 1 (11:54:34):: SNAPIRouter ERROR: No components mapped to index [2]DialerComponent: No components mapped to index [2]DialerComponent:
i upload the demo program to confirm it's not my code and change the device pointing for the address book to the global addressbook and same thing.
probably need to call AMX on that to figure out why.
Firstly, Polycom have been known to change the behaviour of the API. I'm not saying that the API has changed.
I've never used the module as I have my own.
The first steps would be to check if the codec is responding to API requests.
- Either telnet (port 24) or RS232 into the codec
- Type "gaddrbook all" without quotes.
This should return with the addresses. If this does, then the module isn't working.
If by chance no addresses are returned, check the codec UI to see if they are there. If they are not, check the global settings.
If they are, make sure they do not show up under the favourite category as anything there will not be returned via the API. There is a setting to show global addresses under favourites (can't remember exact wording). Turn this off.
Hope something may have helped.
Regards
Craig
It remind me when Polycom remove the abk command
I have made some test without the duet module and you have to send a range command to get a response from the unit.
Using an ID different than ID=* give you a response but look like the data parsing doesn't work properly.
That's interesting as my module uses that command and all works well.
I'd say maybe a Polycom bug as the format for the response should not have changed. It's the same as the local address book.
One thing I have noticed is that global address books can be upwards of 1000 entries and I don't know if the AMX module works.
It only supports the local address book, I have been told AMX / Polycom are both working on it so hopefully it should be fixed soon.
There are a few things not apparently supported by the RPG such a button keys & directory buttons so you have to navigate yourself to the address books.
cheers
That sounds about right, hence why I use my own module.
RPG command set is the same as HDX finally in the current version. Those button commands are back
The module seems to only return the H323 or SIP numbers from the phonebook, and not the office/mobile/etc numbers. I can see them coming in from the device, but the module doesn't pass them out. Is there a module setting or something that I'm missing?
Thanks
Can anyone please comment on what I might be doing wrong?
If I change my dvTP to 10002:5:1 and change my button channels to 5, I get feedback, but no control.
Please help!
Thanks!
If the remote moves the gui around, the Api is not advised even with the screen 'registered'. And so if you want to force the gui to the phone book for instance, you are going to have to guess the command as a list of screens is not available.
Created a dial and subsequent hang up and then pressed the home button which flipped the gui to the home screen and instantly invoked a redial!! Wouldn't stop doing it. Reboot fixed that. Nice.
Not amazingly impressive so far...
Not sure I would even attempt the prefab module - looks like a lot of workaround is going to be needed as it is and you will be better off rolling your own IMO.
Firstly, welcome to the world of Polycom API.
Your first observations are correct. The API in the Group series are "buggy" to say the least. There are ways around most of the API limitations.
To find the screen names, request the current screen. Please be aware that Polycom have been known to change these names though.
I use my own module and limit the home screen to display minimal information.
All contacts and call management and codec control is via the AMX UI/code.
There are lots of other annoying things you will notice as in the PIP command has changed to SELFVIEW, or the content commands need to be supplied the content camera.
If you need any help, shoot me a pm/email. Im just around the corner.
Yes, I'm new, but I would still expect better documentation that what we got...
Raphaël Thiffault
I have programmed a simulated polycom codec for both HDX and RPG models.
If you are interested, please have a look at https://dl.dropboxusercontent.com/u/6093446/Polycom%20simulated%20code/polycom_simulated_codec.zip
Please note that some of the code has been written by others.
If you use this code as a test then it doesn't work out on site, then there is most likely an issue with the codec.
straight thru, pin 2 - 2, 3 - 3, and 5 - 5. If that doesn't work just cross it ;-)
working out which pin is which, however, from their diagram, is less easy!
If the wring is like the serial cable for Polycom VSX series the pins are NOT straight thru or crossover of 2,3 and 5.
Like most things Polycom, the serial cabling is proprietary. I am in doubt that Polycom suddenly decided to switch to a standard cable for control. (I could be wrong though)
I made up (and verified) a Polycom serial cable a couple of months ago. If I can find it I will post the pinout here for you.
We have also heard not so good things about the Polycom Groupwise series. I think it's too young, and will need a few revs before it's stable. We decided to switch to Cisco's SX20 to replace our Polycom buys. Surprisingly, we actually got a better quote for the SX20, which (Cisco offering better pricing over Polycom) has never happened in the past. Even the maintenance is cheaper! Brave new world...
Hi Craig - would love to get a copy of this but appears the link is dead - any chance of still getting it?
Here is a picture of the pin for a group series 500 din that worked for me
Cheers Rob
I have moved the files to https://owncloud.atkin.id.au/index.php/s/TwPHAweBhbxEnaL as i am now using my own could service.
With regards to the module, this isn't a full simulated codec. Its only parts of it that can trip up comms modules.
I don't know if any one has access to a RPG with current firmware with RS232 control as I was wondering what the RS232 spits out when you enable usernamepassword in the webUI?
Kind regards
Craig
I am starting now on building my own VC module - its the only one I use from AMX (Polycom and Cisco) and keep getting caught when they change firmware. The Cisco modules I have worked out but the group series is a pain e.g pulsing channel 131 (send content) on the AMX module tries to change to input 6 and on the 500 there is only 3 inputs.
I have got updates for these modules before when something was wrong but time to build my own I think.
Now looking at the picture, that does look like the same pin-out I had to create for the VSX I had.
Polycom kills me with their proprietary cabling... they try to bilk you several hundred dollars for their cables.
Makes me wonder if they share engineers with Apple.
That is precisely why I don't use duet modules for codecs. They like to screw around with the command API between firmware versions, rendering some features broken.
When we got our first C90, the latest module AMX had was for TC4 and the codec came with TC6 on it. I knew right away the duet module was not going to work for me.
As much of a PITA it is to write your own, it will save you headaches down the road.