The SetDefaultReceiveIlbcFrameMode API procedure is used to set the default iLBC frame mode for received phone calls that do not contain the "mode=" parameter in the calls INVITE sdp information.

Normally you should not call this procedure unless you want to change the default iLBC mode from 30Ms to 20Ms for ill-behaved SIP clients.

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


public VoipMediaEngine..::.TELEPHONY_RETURN_VALUE SetDefaultReceiveIlbcFrameMode(
	int ModeInMs
Visual Basic (Declaration)
Public Function SetDefaultReceiveIlbcFrameMode ( _
	ModeInMs As Integer _
Visual C++
VoipMediaEngine..::.TELEPHONY_RETURN_VALUE SetDefaultReceiveIlbcFrameMode(
	int ModeInMs
public VoipMediaEngine..::.TELEPHONY_RETURN_VALUE SetDefaultReceiveIlbcFrameMode(
	int ModeInMs


Type: System..::.Int32
Specifies the mode of internal iLBC codecs that are used for the phone call. This value must be 20 or 30Ms. The VOIP Media Engine defaults to using lower bandwidth 30Ms iLBC frame sizes.

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

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)

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)



See Also