Added creator attribute to mute and unmute elements so that these events can be correlated with a particular content type; clarified use of the reason element in cases other than termination.
Note: If the responder supports none of the payload-types offered by the initiator, the responder SHOULD terminate the session and include a Jingle reason of <failed-application/>.
+Note: If the responder supports none of the payload-types offered by the initiator, the responder SHOULD terminate the session and include a Jingle reason of <failed-application/>. This reason can also be included in non-termination events, such as content-reject when the other party has tried to add a content-type for which the recipient supports none of the payload types.
If the responder accepts the session, the initiator acknowledges the session-accept message: