The GetSilenceDecay procedure will return to the caller the current time value associated with "noise" threshold silence decay. The value returned is in milliseconds.

Namespace:  LanScape
Assembly:  LMEVoipManaged (in LMEVoipManaged.dll) Version: 6.0.5226.26700

Syntax

C#
public VoipMediaEngine..::.TELEPHONY_RETURN_VALUE GetSilenceDecay(
	ref uint SilenceDecay
)
Visual Basic (Declaration)
Public Function GetSilenceDecay ( _
	ByRef SilenceDecay As UInteger _
) As VoipMediaEngine..::.TELEPHONY_RETURN_VALUE
Visual C++
public:
VoipMediaEngine..::.TELEPHONY_RETURN_VALUE GetSilenceDecay(
	unsigned int% SilenceDecay
)
J#
public VoipMediaEngine..::.TELEPHONY_RETURN_VALUE GetSilenceDecay(
	/** @ref */UInt32 SilenceDecay
)

Parameters

SilenceDecay
Type: System..::.UInt32 %
A reference to a variable that will receive the current silence decay value.

Return Value

If the function succeeds, the return value will be SipSuccess.

If the function fails, the return value will be one of the following values as specified by the VoipMediaEngine..::.TELEPHONY_RETURN_VALUE data type.

Return ValueDescription
SipCallFailure
This value is returned by telephony API procedures to indicate general API failure. This error value is used as a "catch all error". If you receive this error, check to make sure that all parameters specified in the API procedure call are correct. Particularly, verify that pointers to memory regions are valid. This error return value is only used if a mapping to another specific error value does not exist.

(API return value)

SipInvalidHandle
Application software specified an invalid telephony handle in one of the API procedures. This usually indicates memory corruption on the part of application software.

(API return value)

SipBadParameter
One of the telephony API procedures was called by application software and was passed a pointer to an invalid memory address. Normally this error will occur when application software passes NULL pointer values to the telephony API. For managed code applications, you should never see this error unless your process space has exhausted memory.

(API return value)

Remarks

None.

See Also