Sie sind auf Seite 1von 4

Call latching description cum technical document

Format of API :
http://www.valuecallz.com/utils/sendVoice.php?cid=&tonumber=&bparty=&tts_data=&max_latch_duration= &bufferFlag=&retrytime=&returnurl=

Description for the parameters:


1) Cid: Has to be provided by ValueFirst and binded with the account. It would be string i.e. 123456. 2) Tonumber: Source party number (call center number). It could be of 10 digit with xxxxxxxxxx and 11 digits with 0xxxxxxxxxx and 12 digits with 91xxxxxxxxxx. 3) Bparty: Destination party number (end user number). It could be of 10 to 12 digit Number. It could be of 10 digit with xxxxxxxxxx and 11 digit with 0xxxxxxxxxx and 12 Digit with 91xxxxxxxxxx. 4) Tts_data: Variable data if supported by the template (comma separated -- numeric

alphanumeric and date is currently supported only). It would be string and comma separated i.e. your Account balance is due on, 2011-05-06 12:03:45. 5) Max_latch_duration: Latch duration in seconds (by default 2700 seconds). And we can Specify it to a particular limit in seconds so that call will disconnect after the Specified Time. It would be numeric value i.e. 30. 6) BufferFlag: If user wants to buffer the calls and wants to execute on a specified time. It Must set to true. it would be string. 7) Retrytime: It is time to execute the buffered call (Must be encoded in YYYY-mm-dd H: i: s format) 8) Returnurl: Has to be provided by client where the MIS needs to be updated at their End.(i.e http://someIP.com/somefile)

The format of URL which will be pushing back to client is given below:
http://someIP.com/somefile?srcNo=&destNo=&status=&responseCaptured=&duration=&Credit_used=&deliv

eredon=&latching_status_String=&latching_duration=&latching_credit_used=&actual_duration=&operator= &circle=&lastVoiceClip=&Call_Id=&C_Id=&triedon=&retry_count=&sms_params=&clipplayedcount=

This is the URL which we get from the client. The client can send us the URL up to
http://someIP.com/somefile and client can append one or more parameter to the URL.

Descriptions of the parameters of return URL Cum Action URL


1) srcNo: Source party number(call center number) . It could be of 10 digits with xxxxxxxxxx

and 11 digits with 0xxxxxxxxxx and 12 digits with 91xxxxxxxxxx. 2) destNo: Destination party number(end user number). It could be of 10 digits with xxxxxxxxxx and 11 digits with 0xxxxxxxxxx and 12 digits with 91xxxxxxxxxx. 3) Status: IVR(Interactive Voice Response) call status.

4) responseCaptured: User response captured(default NULL).it would be the value which user enter during call flow in case of IVR. It would be numeric and dash separated i.e. 1-3-4. 5) duration: This parameter specifies the duration of call in Seconds. it would be numeric i.e. 30 6) Credit_used: No. of credits used during a call. In normal case as well as in call latching 1 credit is of 30 seconds will be deducted. 7) Deliveredon: Call end time in encoded date time format. This is the time when first party picks up the call. It would be in date time format i.e. 2011-01-03 02:23:33 8) latching_status_String: Call latching status (source party call status- destination party call status) .It would be in hexadecimal string i.e. 0x11. 9) latching_duration: Call latching duration (default 0). Describe the duration of call in

Seconds. It would be in numeric format i.e 54 10) latching_credit_used: Call latching credit used (30 seconds = 1 credit). It would be numeric i.e. 5. 11) actual_duration: It would be a numeric value. Describes the max duration of an IVR. i.e 30 12) operator: It would be a string. It describes the operator of a number like VODAFONE,IDEA

13) circle: It would be a string. This Parameter describes the circle of a number like Delhi,Mumbai. 14) sms_params: This is for internal use. It contains the dynamic content of sms . 15) clipplayedcount: For internal use only. Describes the count of clips played in IVR before disconnection. It would be numeric. I.e 3. 16) lastVoiceClip: It would be string i.e. vc-1 and it is the last clip which is listened by the enduser during the call flow. And user can perform any kind of action on the basis of the clip. Like to send a message after the particular clip played during the call flow. 17) Call_Id: 13456279. 18) C_Id: Campaign ID same as cid. It would be string like 123456 19) tried_on: This is the time when client initiated the request. It would be in datetime format i.e. 2011-06-07 07:34:45 20) retry_count: .It represents the nth retry and it would be numeric. Its value range depends on the retry configuration during the creation of the campaign. Unique call ID same as Http API returns in response. It would be numeric i.e.

The parameters like status, responseCaptured, duration, credits_used, lastVoiceClip are used in case of IVR (Interactive Voice Response).and the parameters like latching_status_String,

latching_credit_used, latching_duration are set in case of latching.Rest of the parameters are common in both cases.

The table below specifies the sample values for the parameters: Parameter name srcNo destNo Status responseCaptured duration Ivr sample value 91xxxxxxxxxx 91xxxxxxxxxx 0x10 1-2-3 30(in seconds) Latching sample value 91xxxxxxxxxx 91xxxxxxxxxx null null null

Credit_used Deliveredon latching_status_String latching_duration latching_credit_used actual_duration operator circle Call_Id C_Id tried_on retry_count lastVoiceClip tried_on sms_params clipplayedcount

2 Yyyy-mm-dd hh:ii:ss null null null 20 Idea Delhi >= 8 digits 16 digit(Numeric) Yyyy-mm-dd hh:ii:ss 2 vc-1 Yyyy-mm-dd hh:ii:ss null 3

null null 0x10-0x10 30(in seconds) 4 20 Idea Delhi >= 8 digits 16 digit(Numeric) Yyyy-mm-dd hh:ii:ss 2 vc-1 Yyyy-mm-dd hh:ii:ss null 3

Das könnte Ihnen auch gefallen