If you are having problems connecting inbound phone calls, you must determine if the far end of the call ever sent the final INVITE ACK SIP message. If it does, you probably have a time-out issue. In that case, you might have to increase the final ACK time-out value using the SetInboundInviteAckTimeout(UInt32) API procedure. If you have determined that the far end SIP device does not transmit final INVITE ACKs properly, you can still get the VOIP Media Engine to connect the incoming call by calling this procedure.
Assembly: LMEVoipManaged (in LMEVoipManaged.dll) Version: 6.0.5226.26700
Syntax
C# |
---|
public VoipMediaEngine..::.TELEPHONY_RETURN_VALUE ConnectIncomingCallWithoutInviteAck( bool EnableState ) |
Visual Basic (Declaration) |
---|
Public Function ConnectIncomingCallWithoutInviteAck ( _ EnableState As Boolean _ ) As VoipMediaEngine..::.TELEPHONY_RETURN_VALUE |
Visual C++ |
---|
public: VoipMediaEngine..::.TELEPHONY_RETURN_VALUE ConnectIncomingCallWithoutInviteAck( bool EnableState ) |
J# |
---|
public VoipMediaEngine..::.TELEPHONY_RETURN_VALUE ConnectIncomingCallWithoutInviteAck( boolean EnableState ) |
Parameters
- EnableState
- Type: System..::.Boolean
If set to a non zero value, the VOIP Media Engine will ignore the reception of the final INVITE ACK and proceed to connect the inbound call immediately.
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 |
---|---|
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) |