Tandberg 6000 MXP

staticattic

I suppose this should be obvious, but the answer is eluding me. When programming for integrated Tandberg 6000 MXP's, I am trying to correctly find the string or something else that will let the system know the Tandberg is "connected". I had thought of using a Tandberg module, but the only functions our customers are allowed to use are: camera navigation, mic on/off, and source sent to distant end. Given the classifucations of the systems, they can not dial anyone, nor can they do any other functions on the CODEC since all of the menu screens get locked out, even from me. That being the case, by using a module, by the time I take out all of the unused functions, it is almost faster just to code the needed functions in the EVENT section as an array. The problem I am having is with the Duo Video function. Fpr example, when the CODEC is in a call and the user selects to send a PC as the source to be broadcast, the CODEC should automatically go into Duo Video. If the CODEC is not in a call, all it should do when PC is selected is do a simple "vidin 5". What string should I be looking for when the CODEC is in a call in order for this to work? I created a 500 character buffer for testing and looked for "CONNECTED" as the string, but for some reason that did not work. Don't have the code in front of me, but I did something like, "IF FIND STRING cTandBUFF, "CONNECTED,1" do this, then clear the buffer. Right now, I made "cheater buttons", as a "Select Duo Video Source" section. Any help on the "proper" way to do this would be much appreciated. Thanks in advance.

Danny Campbell

Jeff,

I usually just use the module because I'm lazy, but the Tandberg does provide a flood of information while it is running. There is a call status response that is sent by the tandberg that looks something like:
call # (status=xxx, type=yyy and so on.
# is the line number 1-10, xxx will have a variety of values, one of them being connected, and yyy will be the type of call such as Tlph for an audio call or Vtlph for a video call.

The best source for this is the "Tandberg MXP codec reference manual for integrators" available on the tandberg web site.

You could also just go into diagnostics and set up to watch the strings to and from the codec's port to get a better idea of what it returns.

NMarkRoberts

I evolved my code through trial and error and it seems to work fine and use "callstat...connected" to trigger a status change. PM me with your email for my code. You might find 500 bytes is too small as the Tandberg is VERY verbose.

Darkside

I think you have to issue a request for the various feedback areas.

I issue

'xfeedback register status/call/channels/audio'

and it seems to cover most items - specifically call stat etc


HTH

mikec

Jeff,

We also write our own includes/modules, means we can implement a mix of all xml and traditional commands that are still supported.

We're still using the old 'feedback on' command when the codec first comes online and that sees us through ok on the 3000MXP and 6000MXP. Unless there's something strange we need there's no need for dedicated 'status' requuests

Our test for connection? - parse 'h323 connected' for ip & 'h320 connected' for isdn; all in lower case - in our DataEvent for the codec we have:

DataEvent[]
String:
Select
ACTIVE (FIND_STRING(VCBuffer,'h323 connected',1))

You can also test for the incoming calls using 'callstatus n incoming h323' - substituting the call number for n - so in our case when we want to ignore a second endpoint connecting and we test for 'callstatus 2 incoming h323' and just reject it...

As far as the duo goes - on a successful connection we just set an 'am I in a call?' flag and then test for that when content is selected; ie:

ButtonEvent[PC]
If in a call
DuoVideoOpen 5
Else
vidin 5


All works for us so far...

Hope it helps


Mike