Accepting a Forked Session Request (Windows Embedded CE 6.0)
1/6/2010
Forking is a routing feature where the server routes a session request to all devices that the user is signed in to. Each device (client application) has the opportunity to accept the request. The first device to accept the request becomes the receiving end point of that session. All other devices that received a session request are sent a message that cancels the original request sent to those devices.
If the SIP server and your client application support forking, the receiving application must do the following things:
- Set the RTCIF_SUPPORT_FORKING flag when calling the IRTCClient2::InitializeEx method.
- Enable the user to accept the session request either implicitly (for example, through a mouse move) or explicitly (for example, the request is displayed and a button is available for the user to accept the request).
- If the answer mode for the application is set to RTCAM_AUTOMATICALLY_ACCEPT for the RTCST_MULTIPARTY_IM session type, handle the situation where the session may time out if multiple clients are first to accept the session request. Note that RTCAM_AUTOMATICALLY_ACCEPT is set by default for the RTCST_MULTIPARTY_IM session type. If the application does not require RTCAM_AUTOMATICALLY_ACCEPT to be set, it should set the answer mode to RTCAM_OFFER_SESSION_EVENT using the IRTCClient2::AnswerMode method.