Hello. Sorry for my English.
I stopped working application. The problem arose when xml query:

<?xml version="1.0" encoding="utf-8"?><MonitorStart 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">
<monitorObject>
<deviceObject typeOfNumber="other" mediaClass="notKnown">36607:1:192.168.12.3:0</deviceObject>
</monitorObject>
<requestedMonitorFilter>
<callcontrol><delivered>true</delivered><established>true</established><connectionCleared>true</connectionCleared></callcontrol>
</requestedMonitorFilter>
<extensions>
<privateData>
<private>
<AvayaEvents>
<CallInformationEvents>
<linkDown>true</linkDown>
<linkUp>true</linkUp>
</CallInformationEvents>
<invertFilter>true</invertFilter>
<RegisterTerminalEventsFilter><unregistered>true</unregistered></RegisterTerminalEventsFilter>
</AvayaEvents>
</private>
</privateData>
</extensions>
</MonitorStart>

return response:
<?xml version="1.0" encoding="UTF-8"?>
<CSTAErrorCode xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"><operation>generic</operation></CSTAErrorCode>

I found out that the problems begin when you add the parameters:
"<callcontrol><delivered>true</delivered><established>true</established><connectionCleared>true</connectionCleared></callcontrol>"
before and it worked

in logs:
FINE: invokeID= 1037 Routing request=session[session 0783FE37B29012383295ED6BD5B3259D-0] ch.ecma.csta.binding.MonitorStart@62b39f
2010-12-01 14.14.59,102 com.avaya.cmapi.monitor.MonitoringServicesImpl acquireCrossRefId
FINE: acquired crossRefID=18: 1 are now in use, 79999 still available.
2010-12-01 14.14.59,102 com.avaya.cmapi.monitor.MonitoringServicesImpl startMonitor
FINE: started monitor=18
2010-12-01 14.14.59,102 com.avaya.cmapi.monitor.MonitoringServicesImpl addChangeRegistrationFilter
FINE: added RegistrationListener: 18, id=[78315:1:192.168.12.3:0] , listener=com.avaya.cmapi.monitor.RegistrationListenerImpl@1fe910c
2010-12-01 14.14.59,102 com.avaya.cmapi.monitor.MonitoringServicesImpl addChangePhysicalDeviceFilter
FINE: added PhysicalDeviceListener: crossRef=18, id=[78315:1:192.168.12.3:0] , listener=com.avaya.cmapi.monitor.PhysicalDeviceListenerImpl@1e4d6ef
2010-12-01 14.14.59,102 com.avaya.cmapi.monitor.MonitoringServicesImpl addChangeCallInfoFilter
FINE: added CallInformationListener: 18, id=[78315:1:192.168.12.3:0] , listener=com.avaya.cmapi.monitor.CallInformationListenerImpl@db03a1
2010-12-01 14.14.59,103 com.avaya.cmapi.monitor.MonitoringServicesImpl createCallControlServicesListener
FINE: added CallControlListener: 18, id=[78315:1:192.168.12.3:0] , listener=com.avaya.cmapi.monitor.CallControlServicesListenerImpl@cb5608
2010-12-01 14.14.59,103 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: Received com.avaya.platform.broker.impl.AsyncResponse@167198e in response to session[session 0783FE37B29012383295ED6BD5B3259D-0] ch.ecma.csta.binding.MonitorStart@62b39f
2010-12-01 14.14.59,212 com.avaya.cmapi.monitor.MonitoringServicesImpl stopMonitor
FINE: removed PhysicalDeviceListener: crossRef=18:[Holder]: [78315:1:192.168.12.3:0] ,com.avaya.cmapi.monitor.PhysicalDeviceListenerImpl@1e4d6ef,session 0783FE37B29012383295ED6BD5B3259D-0
2010-12-01 14.14.59,212 com.avaya.cmapi.monitor.MonitoringServicesImpl stopMonitor
FINE: removed RegistrationListener: crossRef=18:[Holder]: [78315:1:192.168.12.3:0] ,com.avaya.cmapi.monitor.RegistrationListenerImpl@1fe910c,session 0783FE37B29012383295ED6BD5B3259D-0
2010-12-01 14.14.59,212 com.avaya.cmapi.monitor.MonitoringServicesImpl stopMonitor
FINE: removed CallInformationListener: crossRef=18:[Holder]: [78315:1:192.168.12.3:0] ,com.avaya.cmapi.monitor.CallInformationListenerImpl@db03a1,session 0783FE37B29012383295ED6BD5B3259D-0
2010-12-01 14.14.59,212 com.avaya.cs.callcontrol.CallControlSnapshotImpl removeCallControlListener
INFO: CCS Remove Listener: listener not found for device: 78315:1:192.168.12.3:0 Possibly received CSTAMonitorEndedEvent or device wasunregistered on the switch. Monitor Stop request will not be sent.
2010-12-01 14.14.59,213 com.avaya.cmapi.monitor.MonitoringServicesImpl stopMonitor
FINE: removing CallControlListener: crossRef=18:[Holder]: [78315:1:192.168.12.3:0] ,com.avaya.cmapi.monitor.CallControlServicesListenerImpl@cb5608,session 0783FE37B29012383295ED6BD5B3259D-0
2010-12-01 14.14.59,213 com.avaya.cmapi.monitor.MonitoringServicesImpl stopMonitor
FINE: removed sessionListener for crossRef=18
2010-12-01 14.14.59,213 com.avaya.cmapi.monitor.MonitoringServicesImpl releaseCrossRefId
FINE: released crossRefID=18: 0 are now in use, 80000 still available.
2010-12-01 14.14.59,213 com.avaya.cmapi.monitor.MonitoringServicesImpl stopMonitor
FINE: removed monitor=18
2010-12-01 14.14.59,213 com.avaya.async.impl.AsyncCallbackImpl handleException
WARNING: A service method threw an Exception when invoked!
ServiceMethod: com.avaya.platform.broker.impl.AsyncServiceMethodImpl@17d26fc[com.avaya.cmapi.monitor.MonitoringServicesImpl@1f8acdc, public synchronized void com.avaya.cmapi.monitor.MonitoringServicesImpl.startMonitor(ch.ecma.csta.binding.MonitorStart,com.avaya.api.async.AsynchronousCallback) throws ch.ecma.csta.errors.InvalidParameterValueException,ch.ecma.csta.errors.InvalidMonitorObjectException,ch.ecma.csta.errors.OverallMonitorLimitExceededException,ch.ecma.csta.errors.OperationException,ch.ecma.csta.errors.InvalidConnectionIDForActiveCallException]
Exception: ch.ecma.csta.errors.OperationException: Internal logic error in the G3PD. A system administrator may find more detailed information about the error in the G3PD error logs. Contact service representative: error code 71
Request: session[session 0783FE37B29012383295ED6BD5B3259D-0] ch.ecma.csta.binding.MonitorStart@62b39f
ch.ecma.csta.errors.OperationException: Internal logic error in the G3PD. A system administrator may find more detailed information about the error in the G3PD error logs. Contact service representative: error code 71
   at com.avaya.cs.callcontrol.handlers.CallControlConfHandler.getCstaException(CallControlConfHandler.java:242)
   at com.avaya.cs.callcontrol.handlers.MonitorDeviceConfHandler.getCstaException(MonitorDeviceConfHandler.java:149)
   at com.avaya.cs.callcontrol.handlers.CallControlConfHandler.handleConf(CallControlConfHandler.java:131)
   at com.avaya.java.tsapiInterface.TSInvokeID.setConf(TSInvokeID.java:49)
   at com.avaya.java.tsapiInterface.TsapiEventDistributor.handleEvent(TsapiEventDistributor.java:119)
   at com.avaya.java.tsapiInterface.TsapiEventQueue.run(TsapiEventQueue.java:96)

tell me what to do when this error?

A call control monitor requires a working TSAPI link between AE Services and Communication Manager. I see a "1" in your deviceID where the switch connection name would be. That just means you have chosen an odd name for your switch connection. However through the AE Services web based OA&M you need to verify that that switch connection is 'connected' and that you have provisioned a TSAPI link for that link.

You also need to verify that you have an available TSAPI Basic User license. This can be done through the AE Services web based OA&M by connecting to the Web License Manager (WebLM) and verifying the availability of the license.

This particular message "Internal logic error in the G3PD. A system administrator may find more detailed information about the error in the G3PD error logs. Contact service representative: error code 71 " make me think something more nefarious may be afoot, but it is prudent to first eliminate the simple possibilities. One easy way to do that would be to use the AE Services web based OA&M TSAPI Test Utility to make a TSAPI test call. If that works then the provisioning and licensing are not the issue here.