The GetOutgoingCallInfo can be called by a user application when the telephony engine indicates that we are in the process of placing an out going call or we are in the process of being transferred to a new location.

Generally you would call this procedure when the event callback sends you the SipOutgoingCallStart or the SipTransferingCall indication. The out going call information that will be made available to you is contained in a structure variable of type VoipMediaEngine..::.SIP_OUTGOING_CALL_INFO.

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

Syntax

C#
public VoipMediaEngine..::.TELEPHONY_RETURN_VALUE GetOutgoingCallInfo(
	int PhoneLine,
	VoipMediaEngine..::.SIP_OUTGOING_CALL_INFO OutgoingCallInfo
)
Visual Basic (Declaration)
Public Function GetOutgoingCallInfo ( _
	PhoneLine As Integer, _
	OutgoingCallInfo As VoipMediaEngine..::.SIP_OUTGOING_CALL_INFO _
) As VoipMediaEngine..::.TELEPHONY_RETURN_VALUE
Visual C++
public:
VoipMediaEngine..::.TELEPHONY_RETURN_VALUE GetOutgoingCallInfo(
	int PhoneLine, 
	VoipMediaEngine..::.SIP_OUTGOING_CALL_INFO^ OutgoingCallInfo
)
J#
public VoipMediaEngine..::.TELEPHONY_RETURN_VALUE GetOutgoingCallInfo(
	int PhoneLine,
	VoipMediaEngine..::.SIP_OUTGOING_CALL_INFO OutgoingCallInfo
)

Parameters

PhoneLine
Type: System..::.Int32
The zero based phone line to access.
OutgoingCallInfo
Type: LanScape..::.VoipMediaEngine..::.SIP_OUTGOING_CALL_INFO
A reference to a class variable of type VoipMediaEngine..::.SIP_OUTGOING_CALL_INFO. Upon successful completion, the address pointed to by this parameter will be filled with out going call information.

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)

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)

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)

Remarks

None.

See Also