Ekiga doesn't support RFC 3994 "Indication of Message Composition for Instant Messaging" (sending notification of message writting). Those notifications are sent into a MESSAGE request like:

-------------
MESSAGE sip:carol@domain.net SIP/2.0
Via: SIP/2.0/UDP 192.168.1.58:5062;rport;branch=z9hG4bKmvorvqnm
Max-Forwards: 70
To: "carol" <sip:carol@domain.net>
From: "Alice" <sip:alice@domain.net>;tag=jfrbd
Call-ID: cvptxhvtmllqdvw
CSeq: 706 MESSAGE
Content-Type: application/im-iscomposing+xml
User-Agent: Twinkle/1.3
Content-Length: 155

<?xml version="1.0" encoding="UTF-8"?>
<isComposing xmlns="urn:ietf:params:xml:ns:im-iscomposing"><state>active</state><refresh>90</refresh></isComposing>
---------------

So this is a MESSAGE with "Content-Type: application/im-iscomposing+xml" and Ekiga should render it to the user as a normal MESSAGE. In fact, Ekiga should inspect the "Content-Type" header and just render the body to the user if it is "text/plain" or "text/html" (or other *supported* content type).