For conference-based call recording, this is what I think you need to do (disclaimer: Haven't got around to doing this yet - it's on the things to do list)
1. You'll need an application that can perform media termination: Create a JTAPI provider that controls a CTI port, and register your application with it. when your CTI port becomes involved in a call, events will be delivered to your application via the observers you registered, at which point your application needs to set the RTP parameters to start receiving the stream. See:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_programming_usage_guide_chapter09186a00804050e2.html#wp1016821
2. You need another application that receives connection events for connections on interesting phones. When such an event is received the application conferences in the CTI port in 1). See http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_programming_usage_guide_chapter09186a00804050e2.html#wp1016693
So when a call arrives on an interesting phone, application 2) automatically conferences in the CTI port. When this happens the CTI port alerts application 1), which starts receiving the stream, and then writes it to a file.
Issues with this approach are:
1. Most installations have a finite amount of conferencing resources, so call recording via conferencing is seldom suitable for a record-all solution, but should be fine for ad-hoc recording.
2. Your applications use CTI to control the interesting phones. This can conflict with other CTI applications that want to control the same phones. Multiple applications controlling the same phone is usually discouraged.
