Hello, By disabling MprFromInputDevice resource, it will stop to send RTP too,right? I think doing that way it can lead to other issues, maybe: - close NAT pinholes - close socket listening on remote endpoint (**) The idea would be to keep just sending "mute" RTP packets when mic is muted. Is (1) Zeroing appropriate weights in the Bridge approach more suitable to that aim (**) ? Thanks Paulo On Wed, Jul 15, 2009 at 7:54 PM, Alexander Chemeris < [email protected]> wrote:
> On Thu, Jul 16, 2009 at 02:30, Paulo Vicentini<[email protected]> > wrote: > > I mean that setting volume to 0 (just try setting mic volume to 0 ) does > > not actually mute the mic and remote party is able to hear the quiet (and > > not so quite indeed) sound from the muted mic. > > Ok, then we should find the method to really mute the Mic on Windows. > I know, there must be one :) > > > I was thinking somehow to set audio samples to zero maybe in > > MpidWinMM::waveInCallbackStatic > > There are to proper ways to do this: > 1) Zero appropriate weights in the Bridge > 2) Disable appropriate MprFromInputDevice > > Method (1) is good, but it has a complication, that activity notifications > for the mic will be sent just as if mic in not muted. If you use this > activity notifications for rendering mic activity level in GUI, then it > will > lead to conter-intuitive behaviour. > > Method (2) OTOH completely disables audio from the mic, including > activity notifications. So for sipXtapi I think we should use this method. > It has a downside that you won't be able to monitor mic level when it > is muted, but that's what we want here, right? :) > > > -- > Regards, > Alexander Chemeris. > > SIPez LLC. > SIP VoIP, IM and Presence Consulting > http://www.SIPez.com > tel: +1 (617) 273-4000 >
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
