Miniport drivers use the NDIS_STATUS_WWAN_CONTEXT_STATE notification to send an event notification when the activation state of a particular context changes.
Miniport drivers can also send unsolicited events with this notification.
This notification uses the NDIS_WWAN_CONTEXT_STATE structure.
Miniport drivers must also notify the MB Service when context state changes are not caused as a result of a set request from the MB Service. For example, miniport drivers must notify the MB Service if the network deactivates a context. Miniport drivers should not implement network initiated context activations.
Miniport drivers must notify Windows directly about all applicable context state changes, such as when processing NDIS_STATUS_WWAN_PACKET_SERVICE or NDIS_STATUS_WWAN_REGISTER_STATE status notifications.
Miniport drivers of MB devices that support separate voice and data connections must follow these guidelines:
At the time of initialization, the VoiceCallState must be set to WwanVoiceCallStateNone.
On the start of the voice call, send an event notification with VoiceCallState set to WwanVoiceCallStateInProgress. All the other members must reflect their current state. In case of no active connection during the voice call, the ConnectionId should be set to "0" .
Once the voice call is completed, send an event notification with VoiceCallState set to WwanVoiceCallStateHangUp. All the other members must reflect their current state. In case of no active connection during the voice call hang up, the ConnectionId should be set to "0". After this event, the VoiceCallState must be set to WwanVoiceCallStateNone in the miniport driver.
|Available in Windows 7 and later versions of Windows.|
Build date: 11/16/2013