If an application creates a persistent notification information, it can recreate the data associated with the original subscription request by calling this API procedure.

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


public VoipMediaEngine..::.TELEPHONY_RETURN_VALUE RecreateSubscribeRequest(
	VoipMediaEngine MediaEngine,
	VoipMediaEngine..::.SUBSCRIBE_REQUEST DestSubscribeRequest
Visual Basic (Declaration)
Public Function RecreateSubscribeRequest ( _
	MediaEngine As VoipMediaEngine, _
	DestSubscribeRequest As VoipMediaEngine..::.SUBSCRIBE_REQUEST _
Visual C++
VoipMediaEngine..::.TELEPHONY_RETURN_VALUE RecreateSubscribeRequest(
	VoipMediaEngine^ MediaEngine, 
	VoipMediaEngine..::.SUBSCRIBE_REQUEST^ DestSubscribeRequest
public VoipMediaEngine..::.TELEPHONY_RETURN_VALUE RecreateSubscribeRequest(
	VoipMediaEngine MediaEngine,
	VoipMediaEngine..::.SUBSCRIBE_REQUEST DestSubscribeRequest


Type: LanScape..::.VoipMediaEngine
An instance of the media engine.
Type: LanScape..::.VoipMediaEngine..::.SUBSCRIBE_REQUEST
This object will contain the recreated subscription request data.

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)

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.




See Also