Anyone ever test the ip phone (bi-direction audio) function on View4 with PCoIP for XP vm and XP client ?

[choming_tsai]

Hi,

Can someone tell me if it is OK to use MS Netmeeting audio (two way communication) on View4 PCoIP environment? The VM is XP and the client device is also a XP PC or thin client.

Thanks

Mark

[gunnarb]

I can tell you that Bi-directional audio is not supported using PCoIP. This is a feature that should be coming some time this year.

-Gunnar

[choming_tsai]

Hi Gunnar,

Thanks for your information, but I am confused. Have you test this function yourself with such as ip phone or USB headset on View 4.0.1 ? A local Wyse dealer told me for their Wyse PCoIP thin client, it is OK to support bi-direction audio on our View4. But I have not seen the demo or test. If you have more detail test result, appreciate if you can share with me.

Thanks

[gunnarb]

Most likely he means that the P20 he is selling you supports it, but the feature does not currently exist. It is on the product road map, you won't see any demos of this becuase it is not supported yet with View4.

Understand there are different components to View. The client, the protocol, and the host. View4 is the host, PCoIP is the protocol, and whatever you choose is your client. So the Wyse unit, being the client, probably supports the future enchancement of bi-directional audio, but the host, View4 in this case, does not. I'm not sure if PCoIP, the protocol supports bi-directional audio or not, it might. If PCoIP supports it then you could get bi-directional audio by doing a hardware to hardware solution which requires a Teradici PCoIP hardware card. View4 is a hardware to software solution or a software to software solution, this refers to the manor by which you connect to a PCoIP host, P20 is client hardware device, View4 is the host software (this would becalled hardware to software), you can also do a View Client running on Windows connecting to View4 (this would be called software to software). However there is another solution where you connect a hardward client (such as the P20) to a hardware host:

http://www.brianmadden.com/blogs/videos/archive/2009/04/03/the-teradici-pc-over-ip-demo-kit-a-video-...

In this type of setup you P20 may actually do bi-directional audio, I don't know. So Wyse is not lying to you, they are just misinformed about View4. But again, this feature will be supported later this year.

-Gunnar

[SWCS833]

If you search the forums and the web, you will find conflicting information about bi-directional audio and View 4. If you read the release notes for View 4 with PCoIP, it states that HD Bi-directional audio is supported. Here is what it says in the PCoIP informational guide from VMware "Bi-directional audio of recording quality for dictation or transcription needs."

Now, I am not sure if this supported with PCoIP Clients or if you need to be using the VMware View Client. Also, I beleive only USB headsets or usb devices will work, meaning you cannot use analog MICs or headsets.

I am not sure if you can test this in your environment, but that would be the best solution to see if it truly works.

[gunnarb]

Where did you find your information defiant? What release are they stating that Bi-directional is now supported?

USB audio isn't the same as bi-directional audio, USB as a way of getting around the bi-directional issues within audio and basically uses USB which is bi-directional. This isn't the same as putting in a microphone in the red plug and having it work. From what I've read you can get bi-directional USB audio to work but that the quality isn't good. I just tried standard audio and it doesn't work you don't even get a recording device in the VM so I'm not sure how it could work. Again from what I've read and been told bi-directional audio is not yet supported. It may be supported in a hardware to hardware, I don't see why it wouldn't be supported in that scenario, but would you point me to the VMware documentation that states it is now supported. I'm fine with being wrong, I'm married, it happens all the time. I'd just like to see the documetation on it being supported.

-Gunnar

[SWCS833]

Like I said, there is some conflicting information or not enough detailed information about this issue/feature. I am not saying your right or wrong, just giving my two cents as I believe USB is currently working and or supported, but not the analog MIC port.

I myself haven't tested the USB with bi-directional audio, but I have read from some users that it does work and are able to do transcription, etc.

http://www.vmware.com/files/pdf/VMware-View4-PCoIP-IG-EN.pdf

Now this may just be the PCoIP protocol itself and like I said, I have also heard and as you just confirmed, the MIC port doesn't work for bi-directional.

[sto6ma9ch]

We had a similar issue with using Cisco's SoftPhone and a USB headset. It works with an RDP session but no a PCoIP session.

[choming_tsai]

Hi,

If what you said is true, I am dead meat. Thanks anyway.

[admin]

I just searched the release notes and the Admin Guide and did not find any conflicting information really. I did find an old reference to VoIP and RDP under RDP settings and we will have that removed, it is a doc bug.

Our recomendation has consistent for sometime, here is a recap.

Since VDM 2.x with RDP View has supported bi-direction audio of recording quality using our USB redirection

With View 4.0.1 there is still bi-directional support of recording quality using our USB redirection

Currently, we do not reccomend or support VoIP using any solution. We have done targeted testing of different possibilities and there are several things we feel make this no practical today. You will find with the right combinations of devices and components you can get things to work and demo well but that is about where it ends.

WP

[swisst]

wponder,

it's been nearly a year since your posting above, I realise you were quoting the findings from version 4.01 of VDM.

I am currently putting together a business case to migrate 2/3000 workstations and laptops into a VDI/VDM environment,

I have flicked through a couple of forum postings and the bi directional audio is seems to be a show stopper for anyone using soft phones.

I have read through the "what's new in 4.02" (released  15th September 2010) and there is no mention of this being fixed.

My question is, Is this something you're working on that we can expect in the next few months or will I have to mothball my migration?

failing that what would my alternative be? hardware solution as discussed Re: WYSE ? a dedicated hardware solution?

could something be achieved using the cached/offline model ?

regards