This document was generated from CDN thread
Created by: JAMES DEPHILLIP II on 06-06-2011 09:38:59 PM
I am trying to figure out a way to make an RTP stream start in the headset and not on speaker phone. Does anyone have any ideas. I have tried <URL>Key:Headset</URL> along with URLDown for the RTP stream. The problem is that the RTP stream is still played on the speaker phone until released and if the user has the headset button enabled it shuts down the RTP stream. Maybe someone else has a creative way to go about this.
Thanks,
Jim
Subject: RE: Multicast RTP Directly to Headset
Replied by: David Staudt on 08-07-2011 02:30:11 PM
Can you provide a few more details on the scenario you're trying to create and the observations on your attempts so far? A couple of items:
- Audio will be played out of whichever audio output is 'active' - i.e. speaker, handset (if handset is lifted) or headset (if headset button is lit.) There is no programmatic way to select the audio output to use for playback.
- You can use XML commands to simulate button presses for example Key:Headset, but there is no way to read the state of those buttons beforehand, so these keypresses are 'blind.' In your case it sounds like if the headset button is already lit, pressing it again via simulated key turns it off (which is the expected behaviour.)
Subject: RE: Multicast RTP Directly to Headset
Replied by: JAMES DEPHILLIP II on 04-09-2011 12:48:00 AM
That is what I was looking for because I did the URLDOWN to start the stream and URL to push headset but that won't work if the user already has the headset on...I didn't think there was a way but thought I would throw it out there. Thanks for the response
