RemoteHangup indicates that call has been terminated by the remote endpoint.

RemoteHangup is fired when a call is terminated by the remote party for any reason. If the call has been successfully answered with AnswerCall, then the associated ConnectionId is automatically destroyed and is defunct. If however the call is in a peer-to-peer relationship, then the other call leg in this peer-to-peer call is automatically hung up as well.

The CallId is defunct if RemoteHangup occurs.

The Call Control API makes every effort to abstract the complexities of the underlying telephony protocol; however, one should consult the Call Control Feature Matrix to understand what Call Control actions and action parameters are valid for each of the four supported protocols. One can set installation and deployment guidelines based on the Call Control actions and action parameters that an application uses; the Call Control Feature Matrix makes developing such guidelines feasible.