The SetRfc2833DtmfPayloadType API procedure allows the application to set the RFC2833 DTMF payload type that is used when a call is negotiated using the SIP protocol. Normally the media type for RFC2833 DTMF defaults to payload type 101. This is the recommended payload value that should be used for the highest degree of "telephone-event" RFC2833 DTMF interoperability. However, the application can change this value if required.

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

Syntax

C#
public VoipMediaEngine..::.TELEPHONY_RETURN_VALUE SetRfc2833DtmfPayloadType(
	int PhoneLine,
	int PayloadType
)
Visual Basic (Declaration)
Public Function SetRfc2833DtmfPayloadType ( _
	PhoneLine As Integer, _
	PayloadType As Integer _
) As VoipMediaEngine..::.TELEPHONY_RETURN_VALUE
Visual C++
public:
VoipMediaEngine..::.TELEPHONY_RETURN_VALUE SetRfc2833DtmfPayloadType(
	int PhoneLine, 
	int PayloadType
)
J#
public VoipMediaEngine..::.TELEPHONY_RETURN_VALUE SetRfc2833DtmfPayloadType(
	int PhoneLine,
	int PayloadType
)

Parameters

PhoneLine
Type: System..::.Int32
The zero based phone line to access.
PayloadType
Type: System..::.Int32
Specifies the RFC2833 DTMF payload media type.

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)

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)

SipRfc2833DtmfPayloadTypeNotAllowed
Application software called the SetRfc2833DtmfPayloadType(Int32, Int32) API procedure specifying an RTP payload type that is already being used by the media engine for another purpose. The application should use another payload type value and call the procedure again.

(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)

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.

See Also