Hello,
We developed recording application that is based on SSC (single step conferencing) method.
There is the issue when the H.323 extension calls the SIP extension. SSC fails.
The opposite scenario (SIP calls H.323) is OK.

dmcc-trace.log contains:
<135>Mar 5 13:43:20 AES1678 DmccMain[28583] +00:00 2018 583 1 com.avaya.aes | :ClearableQueuedExecutor-1: com.avaya.mvcs.proxy.CstaMarshallerNode FINE - Returning negative ack to client session (EF385342C402EED94DB6F55D94C40720-17) : ch.ecma.csta.errors.InvalidObjectTypeException: There is incompatible bearer service for the originating or destination address. For example. The originator is administered as a data hotline station or the destination is a data station. Call options are incompatible with this service 18

dmcc-api.log contains:
<135>Mar 5 13:43:20 AES1678 DmccMain[28583] +00:00 2018 583 1 com.avaya.aes | :ClearableQueuedExecutor-1: com.avaya.api.cmapi FINE - invokeID= 4408 Sent response ch.ecma.csta.errors.InvalidObjectTypeException: There is incompatible bearer service for the originating or destination address. For example. The originator is administered as a data hotline station or the destination is a data station. Call options are incompatible with this service 18

The problem appears only when SIP extension is the part of communication. There is no problem when there are only H.323 extensions.
Please help.
Thanks
Vilem Pantucek

I think you may find the FAQ "What is the reason for receiving 'INVALID_OBJECT_TYPE' error during Single Step Conference?" useful. It is in the TSAPI -> General section.

Martin