Hi,
We are planning to implement service observe method of recording to our Voice recording system. I would like to know the following details regarding the same.

1. From the document "Developing Client side IP recording Applications"It is said that Recording device will be provisioned with service observe button. how this button can be enabled from CM?

2. Should we invoke the Service observe button or Feature access code for Service observe followed by extension number for each call which need to be recorded?

3, I would like to know the best practice of implementation of recording with Service observe. Using Service observe button or using FAC followed by extension numbers.

4. It will be good if you can let me know how to programatically press a Service observe button.

5. PLease give me a clear idea on what all configurations to be done in CM or AES for testing recording with Service observe.

1) Communication Manager can not enable anything on its own. It needs a stimulus... in this case DMCC Can 'push' the button. Alternatively (and the document should have said this), the SO FAC can be dialed using DMCC or TSAPI/JTAPI Make Call methods or DMCC 'manual dialing' methods. Using the SO button's lamp state allows the application to track the state of the SO feature from Communication Manager's perspective.

2) yes, from distinct recording extensions.
3) That is up to you, your app and your desires. I think a button is simpler, and gives you feedback with respect to state via lamp change events.
4) Via what language version of DMCC? For .NET it PressButton(), for Java see the ButtonPress class. For XML

<ButtonPress xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<device typeOfNumber="other" mediaClass="notKnown">32132:cmsim:135.9.65.129:0</device>
<button>268</button>
</ButtonPress>

5) All is a tall order. You will need stations that are the observers, with SO buttons, or the appropriate FACs provisioned. You need dial plans to accommodate those extensions and FACs. You need target devices to SO and you need some devices to originate calls to those target stations. You may need trunking of various protocols depending on your test coverage, you may need to enable dual SO in the 'change sys feat' form. You may need to test with the different types of SO (listen only, talk/listen). you will need to set the Class of Restriction for the SO ers and ed parties. The Communication Manager Administration and Maintenance guide more than likely has a complete procedure for activating SO as it does for most Communication Manager features.