mercredi 1 juillet 2009 12:52Hello,
recently I managed the integration of Tandberg MXP 95 videoconferencing device into an OCS 2007 R2 infrastructure.
I am able to see Tandberg device as a contact in MOC with its current presence status. I am able to make an A/V call from Tandberg to MOC client without problems, but the call from MOC to Tandberg leads to only one-way video and audio (from MOC to Tandberg, but not from Tandberg device to MOC client). I cannot see the Tandberg camera picture and cannot hear any sound.
Do you have some ideas?
Thanks a lot,
Toutes les réponses
lundi 20 juillet 2009 09:41Same issue here. Any luck getting this resolved?
lundi 20 juillet 2009 12:22Hi, still no luck... I posted the question and a Communicator log to the TAP Partners forum and now I am waiting for a response.
Please, if you will be more successful in a solution, post an answer.
vendredi 31 juillet 2009 08:42Hello to all
Same issue for we.
The infrastructure is the follwowing: server: OCS2007; client: OC R2 and TANDBERG Edge 95MXP with F8.0 firmware
It was working in the past, but we upgrade / reinstall all components, they is no way to isolate a single point of change.
does somebody received feeb-back to solve this issue?
thanks in advance
dimanche 2 août 2009 21:09Hi
Did you try with the last Communicator 2007 R2 update from 28th of july ? among fixes there is a one way only video flow on XP is QoSEnabled registry is on.
I'am not able to test it, no Tandberg equipment anymore for the moment...
Details of the behaviour:
Please let me know if it solves the issue.
lundi 3 août 2009 10:06Hi,
I tried with all the updates applied... No luck.
I have no QoSEnabled parameter set and my system is Windows 7 RC. I sent the LOG files to TAP Partners forum, but up to now, no answer.
When I asked our local Tandberg partner, I received the following:
Make sure he has turned off encryption in the Moc (registry or group policy on the OCS).
Make sure the 1700 offers h263 in the capset...
Also, check DNS configuration on MOC and MXP. Have seen this behavior before and it was a DNS issue in that the MXP did not have a DNS configuration set.
I have standard encryption settings in registry (see http://edmckinzie.spaces.live.com/blog/cns!687C72A5909E4230!533.entry), DNS is configured on Tandberg device.
I don't know, what does it mean "h263 in the capset"...
Thank to all for help!
jeudi 6 août 2009 12:55Hello
I made another test, I donwgrade the Moc client and it is working!
The issue seem to be at client level (R2)
vendredi 7 août 2009 13:12I will give it a shot. Strange thing is that our outsourcing division is having the exact same issue with LCS 2005 and Tandberg... Also, according to Tandberg, the integration should work.
We are busy logging a Support Call with Tandberg to try and get to the bottom of this....
lundi 10 août 2009 13:11Hi all,
I have to agree with Fernand! I tried to clean install the MS Office Communicator 2007 (R1) client and tested the communication.
Audio/video were working both directions, only the video on the MOC client (from Tandberg camera) was displayed upside down (?).
When I upgraded the MOC client to R2 version, the video from Tandberg stopped to show...
Any further help is appreciated!
mercredi 12 août 2009 20:48
I had worked with MS support on the same issue but we were running ocs 2007 not R2
The fix was to disable encryption of video by changing a registry entry.
[ H K E Y _ L O C A L _ M A C H I N E \ S O F T W A R E \ P o l i c i e s \ M i c r o s o f t \ C o m m u n i c a t o r ]
" P C 2 P C A V E n c r y p t i o n " = d w o r d : 0 0 0 0 0 0 0 2
change the pc2pcavencryption key
that worked for us. hope that helps
mercredi 19 août 2009 08:11Hi all,
the encryption setting in the registry doesn't help...
I am now in a direct contact with Tandberg Represantatives. I will post a message, when I will have some news....
lundi 31 août 2009 17:53Any update on this issue, I am also running into the same issue, our Tandberg MXP has F.8 NTSC and we have OCS R2 with MOC R2. R1 client works fine and R2 client doesn't connect to MXP. A call from MXP to MOC R2 works fine.
mardi 1 septembre 2009 09:43Hi all,
I have an update fromthe TANDBERG technical representative, but there is not final solution yet:
A few of my peer engineers have also encountered the same issue when the MOC (R2) client initiates the call to a TANDBERG MXP (F8.0) resulting in one-way video as you have described. As you have noted, there are currently a couple of workarounds at the moment on this to ensure the video portion works: 1) Utilize an R1 MOC client, or 2) upgrade the MXP to F8.1; F8.1 is currently beta.
I will stay in touch and post any new message...
vendredi 4 septembre 2009 19:48
I too have been plagued with this issue. After many hours of PSS and Tandberg engagement, it has been determined that the only solution is F8.1.
In my testing, the beta 10 code does resolve the issue. So it's either run the beta code or wait for the production release.
vendredi 25 septembre 2009 14:54Hi, the Tandberg FW 8.1 definitely resolved the one-way A/V communication between OCS client and Tandberg device.
- Marqué comme réponse VWojnar vendredi 25 septembre 2009 14:54
lundi 23 novembre 2009 22:14
Hi, the Tandberg FW 8.1 definitely resolved the one-way A/V communication between OCS client and Tandberg device.
This worked for me as well. There is a production ready 8.2 version, recommended by Tandberg support, for the upgrade.
lundi 30 novembre 2009 14:58Hi Jeremy Wood,
You are absolutely right. The FW 8.2 has resolved this issue if the OCS and Tandberg are in same network.
But still i have the same issue ( one-way A/V communication between OCS client and Tandberg device) as we are running the OCS and Tandberg in different network. (Tandberg is placed in perimeter network with a public IP).
Would be grateful if you could help me to resolve this issue.