When the initiator sends a session-initiate stanza to the receiver, the &DESCRIPTION; element includes all of the payload types that the initiator can receive for Jingle audio (each one encapsulated in a separate &PAYLOADTYPE; element):
If there is no error, the receiver provisionally accepts the session:
The receiver then should send a list of the payload types that it can receive via a Jingle "content-accept" (or "session-accept") action. The list that the receiver sends MAY include any payload types (not a subset of the payload types sent by the initiator) but SHOULD retain the ID numbers and order specified by the initiator.
The initiator acknowledges the 'content-accept' with an empty IQ result:
After successful transport negotiation (not shown here), the receiver then accepts the session:
And the initiator acknowledges session acceptance: