 +	return d->state;
 +}
 +
++void JingleSession::slotReceivingData()
++{
++       // Whatever the sender content is, we send the same received informational message.
++       // That's from the raw-udp specification, later, we will have to do fifferent things
++       // here depending on the transport method used in the sender content.
++
++       JT_JingleAction *rAction = new JT_JingleAction(d->rootTask);
++       d->actions << rAction;
++       connect(rAction, SIGNAL(finished()), this, SLOT(slotAcked()));
++       rAction->setSession(this);
++       rAction->received();
++       rAction->go(true);
++}
 +
 +//--------------------------
 +// JingleReason

+	connect(c, SIGNAL(dataReceived()), this, SLOT(slotReceivingData()));
+}
+
+void JingleSession::terminate(const JingleReason& r)
+{
+//FIXME:should Take an QDomElement as argument, the application should implement this
+//class itself and be able to return the right QDomElement when calling this method

+		JingleContent *c = contentWithName(content.attribute("name"));
+		QList<QDomElement> payloads;
+		QDomElement pType = content.firstChildElement().firstChildElement();
+		//		    content    description	 payload-type
+		while (!pType.isNull())
+		{
+			payloads << pType;
