Customer raised concern stating there is double call id for a call on the sip station.
They are using a TSAPI applications using SIP.
After the call is routed we see this Error Value : GENERIC_UNSPECIFIED, followed by a new call id --> Is this working as designed?
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 223 1 com.avaya.aes | csta_trace:Thread 0x8fa50b70 TSERVER Src: CLNT
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 223 1 com.avaya.aes | csta_trace:Thread 0x8fa50b70 Login: "firstel" App Name: "SM Avaya Driver" SessionID: 45 Transport ID: 192.168.63.53
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 223 1 com.avaya.aes | csta_trace:Thread 0x8fa50b70 InvokeID: 26569
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 223 1 com.avaya.aes | csta_trace:Thread 0x8fa50b70 Driver: AVAYA#CM7#CSTA#AESLAB
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 223 1 com.avaya.aes | csta_trace:Thread 0x8fa50b70 Message:
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 223 1 com.avaya.aes | csta_trace:Thread 0x8fa50b70 value CSTARouteSelectInvRequest ::=
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 223 1 com.avaya.aes | csta_trace:Thread 0x8fa50b70 {
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 223 1 com.avaya.aes | csta_trace:Thread 0x8fa50b70 routeRegisterReqID 2,
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 223 1 com.avaya.aes | csta_trace:Thread 0x8fa50b70 routingCrossRefID 1112521,
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 223 1 com.avaya.aes | csta_trace:Thread 0x8fa50b70 routeSelected "61006",
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 223 1 com.avaya.aes | csta_trace:Thread 0x8fa50b70 remainRetry 0,
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 223 1 com.avaya.aes | csta_trace:Thread 0x8fa50b70 setupInformation ''H,
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 223 1 com.avaya.aes | csta_trace:Thread 0x8fa50b70 routeUsedReq FALSE
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 223 1 com.avaya.aes | csta_trace:Thread 0x8fa50b70 }
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 223 1 com.avaya.aes | csta_trace:Thread 0x8fa50b70

<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 246 1 com.avaya.aes | csta_trace:Thread 0x92c55b70 TSERVER Src: DRVR
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 246 1 com.avaya.aes | csta_trace:Thread 0x92c55b70 Login: "firstel" App Name: "SM Avaya Driver" SessionID: 45 Transport ID: 192.168.63.53
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 246 1 com.avaya.aes | csta_trace:Thread 0x92c55b70 Driver: AVAYA#CM7#CSTA#AESLAB
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 246 1 com.avaya.aes | csta_trace:Thread 0x92c55b70 Message:
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 246 1 com.avaya.aes | csta_trace:Thread 0x92c55b70 value CSTARouteEndEvent ::=
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 247 1 com.avaya.aes | csta_trace:Thread 0x92c55b70 {
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 247 1 com.avaya.aes | csta_trace:Thread 0x92c55b70 routeRegisterReqID 2,
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 247 1 com.avaya.aes | csta_trace:Thread 0x92c55b70 routingCrossRefID 1112521,
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 247 1 com.avaya.aes | csta_trace:Thread 0x92c55b70 errorValue genericUnspecified ? Could you please cross check if the call was dropped by the customer before this is routed to an agent?
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 247 1 com.avaya.aes | csta_trace:Thread 0x92c55b70 }
<135>Nov 5 15:18:59 aeslab TSAPI[11754]: +00:00 2018 247 1 com.avaya.aes | csta_trace:Thread 0x92c55b70

From the TSAPI application logs

16:35.34.219 - [CTSAPIBase::RouteTo] cstaRouteSelectInv
Invoke : 26569
RouteRegisterRequestId : 2
RouteCrossRefId : 1112521
Destination : 61006

16:35.34.246 - FROM TSAPI
[CTSAPIAvayaDriver::ManageEvent]
Event Class : CSTAEVENTREPORT
Event Type : CSTA_ROUTE_END
16:35.34.246 - [CTSAPIInterface::ManegeEventClass_CSTAEVENTREPORT] ENTER
16:35.34.246 - FROM TSAPI
[CTSAPIAvayaDriver::ManegeEvent Class CSTAEVENTREPORT]
EventType CSTA_ROUTE_END
CrossRefID : 1112521
Reg Req ID : 2
Error Value : GENERIC_UNSPECIFIED

16:35.35.458 - FROM TSAPI
[CTSAPIAvayaDriver::ManageEvent]
Event Class : CSTAUNSOLICITED
Event Type : CSTA_DELIVERED
16:35.35.458 - [CTSAPIInterface::ManegeEventClass_CSTAUNSOLICITED] ENTER
16:35.35.458 - FROM TSAPI
[CTSAPIAvayaDriver::ManegeEvent Class CSTAUNSOLICITED]
EventType CSTA_DELIVERED
MonitorCrossRefId : 6
CallId : 390
Connection DN : 61006
Alerting DN : 61006 Type : EXPLICIT_PRIVATE_LOCAL_NUMBER
Calling DN : 0645219825 Type : EXPLICIT_PRIVATE_UNKNOWN
Called DN : 61006 Type : EXPLICIT_PRIVATE_UNKNOWN
Last Redir DN : Type : EXPLICIT_PUBLIC_UNKNOWN
Cause : EC_NEW_CALL

According to the TSAPI Programmers Regerence, Error Value : GENERIC_UNSPECIFIED means that the call was routed correctly and this seems to be confirmed by the Delivered event.

If, as you say, the call ID of the delivered event is different to the original call ID, then this may be due to incorrect routing configuration on System Manager. It may be that when the call is sent to Session Manager, it is making a trunk call back to Communication Manager.

As this is happening in a production environment, I suggest your customer request support from his Business Partner or Avaya Client Services.

Martin