The DtmfDecoderGetMinimumDigitOnTime API procedure allows an application to retrieve the current
minimum digit ON time for the DTMF decoder.
Namespace:
LanScapeAssembly: LMEVoipManaged (in LMEVoipManaged.dll) Version: 6.0.5226.26700
Syntax
C# |
---|
public VoipMediaEngine..::.TELEPHONY_RETURN_VALUE GetInBandMinimumDigitOnTime( int PhoneLine, ref uint MinimumDigitOnTimeMs ) |
Visual Basic (Declaration) |
---|
Public Function GetInBandMinimumDigitOnTime ( _ PhoneLine As Integer, _ ByRef MinimumDigitOnTimeMs As UInteger _ ) As VoipMediaEngine..::.TELEPHONY_RETURN_VALUE |
Visual C++ |
---|
public: VoipMediaEngine..::.TELEPHONY_RETURN_VALUE GetInBandMinimumDigitOnTime( int PhoneLine, unsigned int% MinimumDigitOnTimeMs ) |
J# |
---|
public VoipMediaEngine..::.TELEPHONY_RETURN_VALUE GetInBandMinimumDigitOnTime( int PhoneLine, /** @ref */UInt32 MinimumDigitOnTimeMs ) |
Parameters
- PhoneLine
- Type: System..::.Int32
The zero based phone line to access.
- MinimumDigitOnTimeMs
- Type:
System..::.UInt32
%
The reference location that will receive the minimum digit ON time.
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 Value | Description |
---|---|
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) |
SipBadPhoneLine |
Application software called a telephony API procedure and specified an invalid phone line. Phone lines are numbered starting from zero. This error is most commonly returned when attempting to access phone lines in excess of the max number of lines supported by the telephony engine.
(API return value) |
SipInternalDtmfSupportNotEnabled |
Internal media engine in-band and RFC2833 DTMF support has not been enabled. See the DtmfEnabled startup
parameter in the VoipMediaEngine..::.START_SIP_TELEPHONY_PARAMS structure for additional information.
(API return value) |
SipInBandDtmfDecoderDoesNotExist |
The application tried to destroy an in-band DTMF decoder for a phone line using the
UnInitializeInBandDtmfDecoder(Int32) API procedure and the DTMF decoder did not exists.
(API return value) |
SipMemoryError |
The telephony engine attempted to allocate system memory but the allocation failed. Make sure the
host system has enough virtual memory. Increasing the amount of virtual memory can remove these
errors, however if critical telephony engine code has been swapped out to disk and is not resident
in physical memory, you may experience degraded audio/video performance. If you want to remove
this error and obtain the best possible audio/video performance, make sure the host system has
enough physical memory.
To resolve this error, you may also want to consider disabling certain features of the media engine such
as conference calling. You can also reduce memory requirements if you reduce the maximum signal length of
internal media engine signal paths by specifying a smaller number for the MaxMixerLinebuffers member of
the VoipMediaEngine..::.START_SIP_TELEPHONY_PARAMS class that is passed to the StartSipTelephony(VoipMediaEngine..::.START_SIP_TELEPHONY_PARAMS)
and ReStartSipTelephony(VoipMediaEngine..::.START_SIP_TELEPHONY_PARAMS) API procedures.
(API return value, PHONE_LINE_NOTIFICATION) |
Remarks
None.