CSTA and SOAP/REST translation
Posted: 14 Aug 2016 07:05
Hi,
i have solution that depends on CTI architecture, it includes OTCC SE and Crystal OXE.
however customer requirement for his CTI 3rd party application interface is SOAP/REST as his following message as reply to include TSAPI or TAPI:
"We only need to be notified when the Agent answer a call from PBX interface, along with that notification we need the call information (i.e. calling number, unique call ID, Agent username/IP. Full list of parameters can be found below).
The below API is suitable in case we want to implement the CTI application which runs on the touch screens, but that’s not the case here.
The needed information that should be pushed from PBX solution thru SOAP/REST services once a call is answered are:
1. Calling Number [ANI].
2. A unique Call-ID (very important to handle CFS automatic loading on call routing)
3. Call Classification (Incoming\Transfer).
4. Line owner information (name) via integration with telecom provider for landline and mobiles.
5. Caller information (name and Location [ALI]) via integration with telecom provider for landline and mobiles.
6. Call Accepting Date and Time.
7. Mapping Information (in case of static machine IPs)
8. CTI Application machine IP.
9. Call taker username on CTI.
10. Calling Media (TETRA or Telephone)."
for my design, i opted CSTA licenses and TSAPI, but if there is any solution to get SOAP or REST API directly from OXE, please show me how in ACTIS, if not is there any middleware to translate our CSTA or TSAPI protocol into customer's required SOAP or REST API protocols.
i have solution that depends on CTI architecture, it includes OTCC SE and Crystal OXE.
however customer requirement for his CTI 3rd party application interface is SOAP/REST as his following message as reply to include TSAPI or TAPI:
"We only need to be notified when the Agent answer a call from PBX interface, along with that notification we need the call information (i.e. calling number, unique call ID, Agent username/IP. Full list of parameters can be found below).
The below API is suitable in case we want to implement the CTI application which runs on the touch screens, but that’s not the case here.
The needed information that should be pushed from PBX solution thru SOAP/REST services once a call is answered are:
1. Calling Number [ANI].
2. A unique Call-ID (very important to handle CFS automatic loading on call routing)
3. Call Classification (Incoming\Transfer).
4. Line owner information (name) via integration with telecom provider for landline and mobiles.
5. Caller information (name and Location [ALI]) via integration with telecom provider for landline and mobiles.
6. Call Accepting Date and Time.
7. Mapping Information (in case of static machine IPs)
8. CTI Application machine IP.
9. Call taker username on CTI.
10. Calling Media (TETRA or Telephone)."
for my design, i opted CSTA licenses and TSAPI, but if there is any solution to get SOAP or REST API directly from OXE, please show me how in ACTIS, if not is there any middleware to translate our CSTA or TSAPI protocol into customer's required SOAP or REST API protocols.