Tandberg 3000MXP Protocol
cbrito
Posts: 8
If anyone has it, can you please send me the Protocol for the TANDBERG 300MXP. It would be much appreciated. Thanks.
0
Comments
I don't recall where I got this -- it may have been from the Tandberg site or it may have been included on a Tandberg CD that came with one of their units. Or, it may have been included in one of the AMX module zip files for one of the MXP models.
Every Tandberg, no matter the model number, that we have dealt with has either operated off the MXP protocol (which is the newer) or the standard protocol. All the MXPs, I believe, use the same protocol.
The AMX modules for the Tandberg units work and they will save you a bunch of programming. There are essentially only two modules -- one for MXP models and one for the others. The touch panels included with the modules, in my opinion, are "problematic", but you should be able to find most all the functions you need on them. Other than what is included in the AMX modules, the Tandberg "key" command described in the attached manual will probably cover everything else.
I recently wrote and implemented a module to drive this Tandberg Codec and found it to be a very challenging process. I imagine that most of what follows applies to other Codecs too.
The command protocol is reasonably straightforward, but that is the least of your worries.
The replies that you receive from the box are generally not documented and are not at all straightforward, and you need to dig your way through them to find out what to parse and what to ignore. For instance, when the Codec boots up with various disclosure options switched on, it emits a stream of dozens of different types of message, and each message can be followed by a further stream of who knows what which you need to ignore.
Further, unlike (I imagine) every other box you may have driven, a Codec has a habit of behaving independently of commands sent to it:
1) Calls come in and go "bring bring!" spontaneously.
2) If you have autoanswer switched on, they get connected - spontaneously.
3) If the call is from a telephone, or if bandwidth is restricted, it's audio only.
4) If you send a command to establish a call, nothing happens...
5)... and then a while later, if the call is successful, it connects. Or not.
6) And when it connects, after a few seconds the Tandberg first tells you that it is an audio-only call, and then a few seconds later, video too.
7) But that's not all... this box can and does handle multiple concurrent VC sessions. Woo hoo.
This means that you have to regard the commands that you send to the Codec as mere suggestions, and then pretty much forget about them.
Meanwhile your system's view of what the Codec is doing is all about the replies received, which is why they are so important. I have written hundreds of lines of code, most of it properly placed in the glue code, not the Tandberg module, to present to the user a meaningful view of what their Codec is actually doing.
PM me if you want my module.
Thanks for all your help. I hope I can help you out in the same way.
http://www.tandberg.com/support/documentation.php?p=Application_Programmer_Interfaces
Look for the TANDBERG Reference User Guide for System Integrators. The file is about 12MB
It is probably a good idea to use the newer protocol for the MXP (called XACLI). While the classic protocol is supported, any new commands/configurations will be in the newer format only. It is also possilbe, and I have seend and done this, to use a mixture of both protocols.
Let me know if you have any questions on the protocol.
Regards,
Bryan