Wrong Call Type when using SIP Dialer

I'm using a SIP Dailer and am experiencing an issue in Preview and Predictive modes where I receive the Reservation call, but when I accept the Customer Preview Call there is an inbound call event (CallType 6) and then an update call event to update the call type to customer_preview event (call type 32) or customer_predictive event (call type 34)

This is only happening when using SIP.

Scenario :

     Receive Reservation call CallType 27

     Accept Customer Preview Call CallType 32

Events are as follows

CallBeginEvent - CallType:27

CallDeliveredEvent - CallType:27

CallDataUpdateEvent - CallType:27

CallEstablishedEvent - CallType:27

CallHeldEvent - CallType:27

CallDataUpdateEvent - CallType:27

CallBeginEvent - CallType:6

CallDeliveredEvent - CallType6

CallDataUpdateEvent - CallType:32

CallDataUpdateEvent - CallType:32

CallEstablishedEvent - CallType:32

When using SCCP I will recieve a CallBeginEvent and CallDeliveredEvent for CallType:32 

Does anyone know of a reason for this behaviour?

Generally the flow is completely different between SIP and SCCP dialer. For the outbound call, SIP dialer uses the voice GW dial peers and CUSP routing policies whereas SCCP dialer talks to CUCM for routing.

The information shared above is not enough to figure out the root cause.

Can you please share the below list of logs and info for both the dialer ( SIP and SCCP ) :

1) Did you noticed any call drop as well ?

2) Complete call Flow

3) Below list of logs:

Dialer:

           Using registry editor set

           - EMSTraceMask= 1F (hex)

           - EMSUserData= FFFF (hex)

Campaign Manager:

           Using registry editor set

           - EMSTraceMask= FFFF (hex)

OPC (Agent PG):

       
C:\>opctest /cust <cust_inst> /node <node>

       
OPCTEST: debug /noall

OPCTEST: debug /on

OPCTEST: quit

EMS Trace 0x40

PIM (Agent PG):

C:\>procmon <cust_inst> <node> pim<pim instance>

  >>>>trace tp* /on

   >>>>trace precall /on

   >>>>trace *event /on

   >>>>trace csta* /on               

JTAPI GW:

  >>>trace JT_TPREQUESTS /on

   >>>trace JT_JTAPI_EVENT_USED* /on

   >>>trace JT_PIM_EVENT /on

    >>>trace JT_ROUTE_MESSAGE /on

    >>>trace *CONF* /on

   >>>trace JT_CONNECTION* /on
 

CTIsrvr:

Using registry editor set

- EMSTraceMask= F8 (hex)

Note: The trace commands are case-sensitive.

Please revert back to default trace once logs were collected.

Did you solve your problem? I have the same issue.