You can't officially. You can try creating a DSN that points at 127.0.0.1 but Informix isn't listed as a supported database in the compability matrix. You're better off to write a record to an external database once the agent takes the first call and then query it for each subsiquant call.
One word of caution: If you're using caller ID as your identifier don't forget that many businesses send out a generic/main number and not the individual DIDs.
My preference for this would be SQL since it's faster to get working than all of the xpath and xsl transforms that would be needed.
One other option that is a bit more obscure: You can use a Java hash table stored into a session with a always-known mapping ID. This is probably the most ideal because:
It eliminates any external dependancies.
It will have a smaller footprint in the Java heap than XML documents will.
I suspect it's more efficient than performing all of the xpath logic.
The whole table will self-reset if the session expunges due to inactivity. You'd still need to timestamp specific entries though I suspect. Also don't forget to account for the session not existing and to re-generate it.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...