sipXecs 3.10 introduced a newly merged Proxy (sipXproxy). The design of the merged proxy is such that for INVITEs and INVITE responses, the SIP message/response is required to be looped back to itself.
The Call State Event Observer (separate task in sipXproxy), monitors SIP messages, creates necessary CSEs and writes them to the appropriate DB for later processing into CDR records.
The negative impact of the SIP messages/responses being looped back into the proxy is that duplicate CSE records are being created and stored in the DB. This duplication not only consumes CPU because of record generation but also in DB space. On a heavily loaded system, performance could be impacted severely over time as the database grows.