Call Detail Record Access Service Part No R01
|
|
|
- Emerald Dixon
- 10 years ago
- Views:
Transcription
1 Call Detail Record Access Service Part No R01 Summary Objective WSDL URL (Testing) WSDL URL (Hosting Production) Endpoint URL (Testing) Endpoint URL (Hosting Production) Namespace URI Service Name Port Provide secure access to Call Detail Records (CDRs) of calls to a particular application. CDRAccessService_v2?WSDL services/cdraccessservice_v2?wsdl CDRAccessService_v2 services/cdraccessservice_v2 CDRAccessService CDRAccessService_v2 Methods Note: For simplicity, this document describes methods as though you used a language such as Java or JavaScript to access the service. In particular, the parameter types are described as Java equivalents. See Using BeVocal Platform Services for the correspondence between Java types and XML Schema built-ins. int int getcalldetailrecordcount( String organizationid, String applicationid, Date starttime, Date endtime ) getcalldetailrecordcountbyfilter( String organizationid, String applicationid, Filter[] filterlist ) CallDetailRecord[] getcalldetailrecords ( String organizationid, String applicationid, Date starttime, Date endtime, boolean requestextendeddata )
2 CALL DETAIL RECORD ACCESS SERVICE CallDetailRecord[] CallDetailRecord[] getcalldetailrecordsbyfilter( String organizationid, String applicationid, Filter[] filterlist, OrderBy[] orderbylist, int startindex, int recordcount, boolean requestextendeddata ) getcalldetailrecordsbyindex( String organizationid, String applicationid, Date starttime, Date endtime, int startindex, int recordcount, boolean requestextendeddata boolean orderbytimeascending ) Data Types CallDetailRecord CallDetailRecord { String sessionid; String parentsessionid; Date startdatetime; Int calldurationseconds; String calledparty; String callingparty; String originalcallingparty; String organizationid; String applicationid; String initialurl; String calltype; // valid values are INBOUND, OUTBOUND, // TROMBONE_TRANSFER, BLIND_TRANSFER String callresult; // valid values are BUSY, RING_NO_ANSWER... String mediagatewayhostname; String mediagatewaychannel; boolean bevocalcalllogavailable; boolean speechvendorcalllogavailable; boolean utterancesavailable; int capturedutterancecount; NameValuePair[] extendeddata; } Filter Filter { EnumFilterField field; //such as EnumFilterField.ERROR_COUNT EnumFilterOperator op; //such as EnumFilterOperator.EQUALS Object operand; //such as 4; type Date, String, or Integer } 2 CALL DETAIL RECORD ACCESS SERVICE
3 Summary EnumFilterField EnumFilterOperat or Enumerated type; one of: EnumFilterField.APPLICATION_ID EnumFilterField.CALLED_PARTY EnumFilterField.CALLING_PARTY EnumFilterField.CALL_TYPE EnumFilterField.DURATION EnumFilterField.END_TIME EnumFilterField.ERROR_COUNT EnumFilterField.MEDIA_GATEWAY_HOST EnumFilterField.MISREC_COUNT EnumFilterField.ORGANIZATION_ID EnumFilterField.START_TIME Enumerated type; one of: EnumFilterOperator.EQUALS EnumFilterOperator.EQUALS_IGNORE_CASE EnumFilterOperator.GREATER_THAN EnumFilterOperator.GREATER_THAN_OR_EQUALS EnumFilterOperator.IS_NOT_NULL EnumFilterOperator.IS_NULL EnumFilterOperator.LESS_THAN EnumFilterOperator.LESS_THAN_OR_EQUALS EnumFilterOperator.NOT_EQUALS EnumFilterOperator.NOT_EQUALS_IGNORE_CASE NameValuePair NameValuePair { String name; String value; } OrderBy OrderBy { EnumOrderByField field; //such as EnumOrderByField.CALL_TYPE boolean ascending; [ascending or descending sort] } EnumOrderByField Enumerated type; one of: EnumOrderByField.APPLICATION_ID EnumOrderByField.CALLED_PARTY EnumOrderByField.CALLING_PARTY EnumOrderByField.CALL_TYPE EnumOrderByField.DURATION EnumOrderByField.END_TIME EnumOrderByField.MEDIA_GATEWAY_HOST EnumOrderByField.ORGANIZATION_ID EnumOrderByField.START_TIME CALL DETAIL RECORD ACCESS SERVICE 3
4 CALL DETAIL RECORD ACCESS SERVICE How to Use This Service The Call Detail Record Access Service provides access to the CDRs of calls made to a particular VoiceXML application. You can use this service, for example, to write a reporting application summarizing the high-level details of usage of your application. You can also use it in conjunction with other BeVocal Platform services to provide more detailed analysis of calls and to write custom tools. For example, the BeVocal Café Vocal Player tool uses this and other services to let you interactively walk through user calls. To use the service, your client application passes parameters describing the set of calls whose records are desired. For a simple request, the parameters specify the application and a start time and an end time for the calls of interest. Other methods allow more complex queries, filtering on various conditions, such as the caller s ANI. The service returns records describing each call to that application matching the criteria that ended during that time period. For example, assume you specify a start time of T08:00:00Z and an end time of T09:00:00Z. A call that started at T07:58:30Z and ended at T08:00:50Z would be included in the records returned, but a call that started at T08:58:30Z and ended at T09:00:50Z would not be included. Using call end times makes it easier for you to be certain that you get access to relevant CDRs in a timely fashion. Because certain information about a call is not available until the call ends, the system must wait until after the call ends to write the CDR for that call. Consequently, an ongoing call does not yet have a CDR you can access. It is fairly common to want your application to access CDRs shortly after they become available. Because there is no way to know when an ongoing call will end, there is no way to know when the CDRs for all calls started during a particular time period will be available and hence how long after that time period you must wait before accessing the CDRs. On the other hand, it is obviously possible to know when the CDRs for all calls that ended during that same time period are available (that is, almost immediately after the time period!). There is a separate CDR for every inbound call, outbound call, and transferred call to and from a VoiceXML application. Once you have an array of CDRs, you work with them directly. You can also use the session ID that identifies a particular call as your handle for other services, such as to use the Media Access Service to get the recordings of what a user said during a call. You use this service to retrieve a limited number of records at a time. The service may limit the maximum number of records returned. Access to this service is restricted by the use of a security key. Before you can use this service, you must first obtain a key from BeVocal. For general information on using BeVocal Platform services, see Using BeVocal Platform Services. For an example of using this service, see the VoiceXML Samples page. 4 CALL DETAIL RECORD ACCESS SERVICE
5 getcalldetailrecordcount getcalldetailrecordcount Syntax Parameters Returns the number of calls that ended during a certain time period. See How to Use This Service on page 4 for a discussion of why the method returns calls that end during the time period and not those that start during the time period. int getcalldetailrecordcount( String organizationid, String applicationid, Date starttime, Date endtime ) Returns Faults Parameter organizationid applicationid starttime endtime Description The number of matching call records. The organization identifier. This ID is assigned when the application is provisioned. For Café developers, the value is always BVCLDEV. The application identifier. This ID is assigned when the application is provisioned. For Café developers, the value is the Café user ID. The start of the time interval for which records are requested. The Date format is described in Data Types on page 3 in Using BeVocal Platform Services. The end of the time interval for which records are requested. The Date format is described in Data Types on page 3 in Using BeVocal Platform Services. For many faults, you can see the fault detail for additional information. Examples Fault Number Description 1002 Access denied. (Client does not have access to the requested data.) 1003 The requested data is not available. SOAP Request POST /CDRAccessService_v2/services/CDRAccessService_v2 HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.0 Host: utopia Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 863 CALL DETAIL RECORD ACCESS SERVICE 5
6 CALL DETAIL RECORD ACCESS SERVICE <?xml version="1.0" encoding="utf-8"?> <soapenv:envelope xmlns:soapenv=" xmlns:xsd=" xmlns:xsi=" <soapenv:header> <ns1:platformservicessessionid xsi:type="xsd:string" xmlns:ns1=" E3EB1B1D378CC147ED935EFF39B8C911 </ns1:platformservicessessionid> </soapenv:header> <soapenv:body> <ns2:getcalldetailrecordcount xmlns:ns2="cdraccessservice_v2"> <arg0 xsi:type="xsd:string">bvcldev</arg0> <arg1 xsi:type="xsd:string"> </arg1> <arg2 xsi:type="xsd:datetime"> t20:00:00.000z</arg2> <arg3 xsi:type="xsd:datetime"> t20:00:00.000z</arg3> </ns2:getcalldetailrecordcount> </soapenv:body> </soapenv:envelope> SOAP Response HTTP/ OK Server: Resin/2.1.4 Content-Type: text/xml; charset=utf-8 Date: Thu, 13 Mar :14:20 GMT <?xml version="1.0" encoding="utf-8"?> <soapenv:envelope xmlns:soapenv=" xmlns:xsd=" xmlns:xsi=" <soapenv:body> <ns1:getcalldetailrecordcountresponse xmlns:ns1="cdraccessservice_v2"> <getcalldetailrecordcountreturn xsi:type="xsd:int"> 11</getCallDetailRecordCountReturn> </ns1:getcalldetailrecordcountresponse> </soapenv:body> </soapenv:envelope> getcalldetailrecordcountbyfilter Syntax Returns the number of calls matching the specified criteria. int getcalldetailrecordcountbyfilter( String organizationid, String applicationid, Filter[] filterlist 6 CALL DETAIL RECORD ACCESS SERVICE
7 getcalldetailrecordcountbyfilter ) Parameters Parameter organizationid applicationid filterlist Description The organization identifier. This ID is assigned when the application is provisioned. For Café developers, the value is always BVCLDEV. The application identifier. This ID is assigned when the application is provisioned. For Café developers, the value is the Café user ID. An array of Filter objects to constrain the query. Each filter specifies: a field on which to filter, such as EnumFilterField.ERROR_COUNT. an operator, such as EnumFilterOperator.GREATER_THAN. if applicable, an operand, such as 4; at present, an operand must be of type Date, String, or Integer. Returns The number of matching call records. Faults For many faults, you can see the fault detail for additional information. Examples Fault Number Description 1002 Access denied. (Client does not have access to the requested data.) 1003 The requested data is not available. SOAP Request POST /CDRAccessService_v2/services/CDRAccessService_v2 HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.0 Host: utopia Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 2882 <?xml version="1.0" encoding="utf-8"?> <soapenv:envelope xmlns:soapenv=" xmlns:xsd=" xmlns:xsi=" <soapenv:header> <ns1:platformservicessessionid xsi:type="xsd:string" xmlns:ns1=" E3EB1B1D378CC147ED935EFF39B8C911 </ns1:platformservicessessionid> </soapenv:header> <soapenv:body> <ns2:getcalldetailrecordcountbyfilter xmlns:ns2="cdraccessservice_v2"> CALL DETAIL RECORD ACCESS SERVICE 7
8 CALL DETAIL RECORD ACCESS SERVICE <arg0 xsi:type="xsd:string">bvcldev</arg0> <arg1 xsi:type="xsd:string"> </arg1> <arg2 xsi:type="soapenc:array" soapenc:arraytype="ns3:filter[2]" xmlns:soapenc=" xmlns:ns3="urn:beanservice"> <item href="#id0"/> <item href="#id1"/> </arg2> </ns2:getcalldetailrecordcountbyfilter> <multiref id="id1" soapenc:root="0" xsi:type="ns4:filter" xmlns:soapenc=" xmlns:ns4="urn:beanservice"> <filterfield href="#id2"/> <filteroperator href="#id3"/> <filteroperand xsi:type="xsd:datetime"> T20:00:00.000Z</filterOperand> <multiref id="id0" soapenc:root="0" xsi:type="ns5:filter" xmlns:ns5="urn:beanservice" <filterfield href="#id4"/> <filteroperator href="#id5"/> <filteroperand xsi:type="xsd:datetime"> T20:00:00.000Z</filterOperand> <multiref id="id3" soapenc:root="0" xsi:type="ns6:enumfilteroperator" xmlns:ns6="urn:beanservice" <value xsi:type="xsd:string">less_than_or_equals</value> <multiref id="id4" soapenc:root="0" xsi:type="ns7:enumfilterfield" xmlns:ns7="urn:beanservice" <value xsi:type="xsd:string">start_time</value> <multiref id="id2" soapenc:root="0" xsi:type="ns8:enumfilterfield" xmlns:ns8="urn:beanservice" <value xsi:type="xsd:string">end_time</value> <multiref id="id5" soapenc:root="0" xsi:type="ns9:enumfilteroperator" xmlns:ns9="urn:beanservice" <value xsi:type="xsd:string">greater_than_or_equals</value> </soapenv:body> </soapenv:envelope> 8 CALL DETAIL RECORD ACCESS SERVICE
9 getcalldetailrecords SOAP Response HTTP/ OK Server: Resin/2.1.4 Content-Type: text/xml; charset=utf-8 Date: Wed, 19 Mar :11:55 GMT <?xml version="1.0" encoding="utf-8"?> <soapenv:envelope xmlns:soapenv=" xmlns:xsd=" xmlns:xsi=" <soapenv:body> <ns1:getcalldetailrecordcountbyfilterresponse xmlns:ns1="cdraccessservice_v2"> <getcalldetailrecordcountbyfilterreturn xsi:type="xsd:int"> 11 </getcalldetailrecordcountbyfilterreturn> </ns1:getcalldetailrecordcountbyfilterresponse> </soapenv:body> </soapenv:envelope> getcalldetailrecords Syntax Parameters Returns a list of call detail records for the set of calls that ended during a certain time period. See How to Use This Service on page 4 for a discussion of why the method returns calls that end during the time period and not those that start during the time period. CallDetailRecord[] getcalldetailrecords ( String organizationid, String applicationid, Date starttime, Date endtime, boolean requestextendeddata ) Parameter organizationid applicationid starttime Description The organization identifier. This ID is assigned when the application is provisioned. For Café developers, the value is always BVCLDEV. The application identifier. This ID is assigned when the application is provisioned. For Café developers, the value is the Café user ID. The start of the time interval for which records are requested. The Date format is described in Data Types on page 3 in Using BeVocal Platform Services. CALL DETAIL RECORD ACCESS SERVICE 9
10 CALL DETAIL RECORD ACCESS SERVICE Returns Faults Parameter endtime requestextendeddata Description The end of the time interval for which records are requested. The Date format is described in Data Types on page 3 in Using BeVocal Platform Services. Determines whether or not to include extended data with the records. In some cases, the platform may associate additional data with a CDR. If this parameter is true, that additional data is included with the returned records as a set of name-value pairs. For Café applications, the platform always associates extended data. Currently, the available extended data are: NUM_ERROR--the number of errors NUM_MISRECS--the number of rejections REQ_ID--outbound request ID associated with the session (for outbound notification calls) CONNECTED--the time the call was actually connected (for outbound notification calls) An array of CallDetailRecord objects describing a particular call. For many faults, you can see the fault detail for additional information. Examples Fault Number Description 1002 Access denied. (Client does not have access to the requested data.) 1003 The requested data is not available. SOAP Request POST /services/cdraccessservice_v2 HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.0 Host: utopia Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 896 <?xml version="1.0" encoding="utf-8"?> <soapenv:envelope xmlns:soapenv=" xmlns:xsd=" xmlns:xsi=" <soapenv:header> <ns1:platformservicessessionid xsi:type="xsd:string" xmlns:ns1=" E3EB1B1D378CC147ED935EFF39B8C911 </ns1:platformservicessessionid> </soapenv:header> <soapenv:body> <ns2:getcalldetailrecords xmlns:ns2="cdraccessservice"> <arg0 xsi:type="xsd:string">bvcldev</arg0> 10 CALL DETAIL RECORD ACCESS SERVICE
11 getcalldetailrecords <arg1 xsi:type="xsd:string"> </arg1> <arg2 xsi:type="xsd:datetime"> t19:36:17.327z</arg2> <arg3 xsi:type="xsd:datetime"> t19:36:17.327z</arg3> <arg4 xsi:type="xsd:boolean">true</arg4> </ns2:getcalldetailrecords> </soapenv:body> </soapenv:envelope> SOAP Response HTTP/ OK Server: Resin/2.1.4 Content-Type: text/xml; charset=utf-8 Date: Tue, 29 Oct :36:07 GMT <?xml version="1.0" encoding="utf-8"?> <soapenv:envelope xmlns:soapenv=" xmlns:xsd=" xmlns:xsi=" <soapenv:body> <ns1:getcalldetailrecordsresponse xmlns:ns1="cdraccessservice"> <getcalldetailrecordsreturn xsi:type="soapenc:array" soapenc:arraytype="ns2:calldetailrecord[4]" xmlns:soapenc=" xmlns:ns2="urn:beanservice"> <item href="#id0"/> <item href="#id1"/> <item href="#id2"/> <item href="#id3"/> </getcalldetailrecordsreturn> </ns1:getcalldetailrecordsresponse> <multiref id="id0" soapenc:root="0" xsi:type="ns3:calldetailrecord" xmlns:soapenc=" xmlns:ns3="urn:beanservice"> <applicationid xsi:type="xsd:string"> </applicationid> <bevocalcalllogavailable xsi:type="xsd:boolean"> true </bevocalcalllogavailable> <calldurationseconds xsi:type="xsd:int">28</calldurationseconds> <callresult xsi:type="xsd:string">completed</callresult> <calltype xsi:type="xsd:string">inbound</calltype> <calledparty xsi:type="xsd:string"> </calledparty> <callingparty xsi:type="xsd:string"> </callingparty> <extendeddata xsi:type="soapenc:array" soapenc:arraytype="ns3:namevaluepair[3]"> <item href="#id4"/> <item href="#id5"/> <item href="#id6"/> </extendeddata> <initialurl xsi:type="xsd:string"> </initialurl> <mediagatewaychannel xsi:type="xsd:string">ch001</mediagatewaychannel> <mediagatewayhostname xsi:type="xsd:string">engcm002 CALL DETAIL RECORD ACCESS SERVICE 11
12 CALL DETAIL RECORD ACCESS SERVICE </mediagatewayhostname> <organizationid xsi:type="xsd:string">bvcldev</organizationid> <originalcallingparty xsi:type="xsd:string" xsi:nil="true"/> <parentsessionid xsi:type="xsd:string">null</parentsessionid> <sessionid xsi:type="xsd:string">2002-engca002-ch001-fhk6w</sessionid> <speechvendorcalllogavailable xsi:type="xsd:boolean">true </speechvendorcalllogavailable> <startdatetime xsi:type="xsd:datetime"> t21:59:20.000z </startdatetime> <utterancesavailable xsi:type="xsd:boolean">false</utterancesavailable> <multiref id="id1" soapenc:root="0" xsi:type="ns4:calldetailrecord" xmlns:ns4="urn:beanservice" <applicationid xsi:type="xsd:string"> </applicationid> <bevocalcalllogavailable xsi:type="xsd:boolean">true </bevocalcalllogavailable> <calldurationseconds xsi:type="xsd:int">27</calldurationseconds> <callresult xsi:type="xsd:string">completed</callresult> <calltype xsi:type="xsd:string">inbound</calltype> <calledparty xsi:type="xsd:string"> </calledparty> <callingparty xsi:type="xsd:string"> </callingparty> <extendeddata xsi:type="soapenc:array" soapenc:arraytype="ns4:namevaluepair[3]"> <item href="#id7"/> <item href="#id8"/> <item href="#id9"/> </extendeddata> <initialurl xsi:type="xsd:string"> </initialurl> <mediagatewaychannel xsi:type="xsd:string">ch001</mediagatewaychannel> <mediagatewayhostname xsi:type="xsd:string">engcm002 </mediagatewayhostname> <organizationid xsi:type="xsd:string">bvcldev</organizationid> <originalcallingparty xsi:type="xsd:string" xsi:nil="true"/> <parentsessionid xsi:type="xsd:string">null</parentsessionid> <sessionid xsi:type="xsd:string">2002-engca002-ch001-fhk7x</sessionid> <speechvendorcalllogavailable xsi:type="xsd:boolean">true </speechvendorcalllogavailable> <startdatetime xsi:type="xsd:datetime"> t21:59:57.000z </startdatetime> <utterancesavailable xsi:type="xsd:boolean">false</utterancesavailable> <multiref id="id2" soapenc:root="0" xsi:type="ns5:calldetailrecord" xmlns:ns5="urn:beanservice" <applicationid xsi:type="xsd:string"> </applicationid> <bevocalcalllogavailable xsi:type="xsd:boolean">true </bevocalcalllogavailable> <calldurationseconds xsi:type="xsd:int">131</calldurationseconds> <callresult xsi:type="xsd:string">completed</callresult> <calltype xsi:type="xsd:string">inbound</calltype> <calledparty xsi:type="xsd:string"> </calledparty> 12 CALL DETAIL RECORD ACCESS SERVICE
13 getcalldetailrecords <callingparty xsi:type="xsd:string"> </callingparty> <extendeddata xsi:type="soapenc:array" soapenc:arraytype="ns5:namevaluepair[3]"> <item href="#id10"/> <item href="#id11"/> <item href="#id12"/> </extendeddata> <initialurl xsi:type="xsd:string"> </initialurl> <mediagatewaychannel xsi:type="xsd:string">ch001</mediagatewaychannel> <mediagatewayhostname xsi:type="xsd:string">engcm002 </mediagatewayhostname> <organizationid xsi:type="xsd:string">bvcldev</organizationid> <originalcallingparty xsi:type="xsd:string" xsi:nil="true"/> <parentsessionid xsi:type="xsd:string">null</parentsessionid> <sessionid xsi:type="xsd:string">2002-engca002-ch001-fgr8n</sessionid> <speechvendorcalllogavailable xsi:type="xsd:boolean">true </speechvendorcalllogavailable> <startdatetime xsi:type="xsd:datetime"> t23:33:59.000z </startdatetime> <utterancesavailable xsi:type="xsd:boolean">false</utterancesavailable> <multiref id="id3" soapenc:root="0" xsi:type="ns6:calldetailrecord" xmlns:ns6="urn:beanservice" <applicationid xsi:type="xsd:string"> </applicationid> <bevocalcalllogavailable xsi:type="xsd:boolean">true </bevocalcalllogavailable> <calldurationseconds xsi:type="xsd:int">57</calldurationseconds> <callresult xsi:type="xsd:string">completed</callresult> <calltype xsi:type="xsd:string">inbound</calltype> <calledparty xsi:type="xsd:string"> </calledparty> <callingparty xsi:type="xsd:string"> </callingparty> <extendeddata xsi:type="soapenc:array" soapenc:arraytype="ns6:namevaluepair[3]"> <item href="#id13"/> <item href="#id14"/> <item href="#id15"/> </extendeddata> <initialurl xsi:type="xsd:string"> </initialurl> <mediagatewaychannel xsi:type="xsd:string">ch001</mediagatewaychannel> <mediagatewayhostname xsi:type="xsd:string">engcm002 </mediagatewayhostname> <organizationid xsi:type="xsd:string">bvcldev</organizationid> <originalcallingparty xsi:type="xsd:string" xsi:nil="true"/> <parentsessionid xsi:type="xsd:string">null</parentsessionid> <sessionid xsi:type="xsd:string">2002-engca002-ch001-fj3a3</sessionid> <speechvendorcalllogavailable xsi:type="xsd:boolean">true </speechvendorcalllogavailable> <startdatetime xsi:type="xsd:datetime"> t17:49:15.000z </startdatetime> <utterancesavailable xsi:type="xsd:boolean">false </utterancesavailable> CALL DETAIL RECORD ACCESS SERVICE 13
14 CALL DETAIL RECORD ACCESS SERVICE <multiref id="id13" soapenc:root="0" xsi:type="ns7:namevaluepair" xmlns:ns7="urn:beanservice" <name xsi:type="xsd:string">num_error</name> <multiref id="id12" soapenc:root="0" xsi:type="ns8:namevaluepair" xmlns:ns8="urn:beanservice" <name xsi:type="xsd:string">log_version</name> <value xsi:type="xsd:string">1.0</value> <multiref id="id7" soapenc:root="0" xsi:type="ns9:namevaluepair" xmlns:ns9="urn:beanservice" <name xsi:type="xsd:string">num_error</name> <multiref id="id6" soapenc:root="0" xsi:type="ns10:namevaluepair" xmlns:ns10="urn:beanservice" <name xsi:type="xsd:string">log_version</name> <value xsi:type="xsd:string">1.0</value> <multiref id="id4" soapenc:root="0" xsi:type="ns11:namevaluepair" xmlns:ns11="urn:beanservice" <name xsi:type="xsd:string">num_error</name> <multiref id="id11" soapenc:root="0" xsi:type="ns12:namevaluepair" xmlns:ns12="urn:beanservice" <name xsi:type="xsd:string">num_mis_rec</name> <multiref id="id5" soapenc:root="0" xsi:type="ns13:namevaluepair" xmlns:ns13="urn:beanservice" <name xsi:type="xsd:string">num_mis_rec</name> <multiref id="id8" soapenc:root="0" xsi:type="ns14:namevaluepair" xmlns:ns14="urn:beanservice" <name xsi:type="xsd:string">num_mis_rec</name> 14 CALL DETAIL RECORD ACCESS SERVICE
15 getcalldetailrecordsbyfilter <multiref id="id15" soapenc:root="0" xsi:type="ns15:namevaluepair" xmlns:ns15="urn:beanservice" <name xsi:type="xsd:string">log_version</name> <value xsi:type="xsd:string">1.0</value> <multiref id="id10" soapenc:root="0" xsi:type="ns16:namevaluepair" xmlns:ns16="urn:beanservice" <name xsi:type="xsd:string">num_error</name> <multiref id="id14" soapenc:root="0" xsi:type="ns17:namevaluepair" xmlns:ns17="urn:beanservice" <name xsi:type="xsd:string">num_mis_rec</name> <multiref id="id9" soapenc:root="0" xsi:type="ns18:namevaluepair" xmlns:ns18="urn:beanservice" <name xsi:type="xsd:string">log_version</name> <value xsi:type="xsd:string">1.0</value> </soapenv:body> </soapenv:envelope> getcalldetailrecordsbyfilter Syntax Returns a list of call detail records for the set of calls that match the specified criteria. CallDetailRecord[] getcalldetailrecordsbyfilter( String organizationid, String applicationid, Filter[] filterlist, OrderBy[] orderbylist, int startindex, int recordcount, boolean requestextendeddata ) CALL DETAIL RECORD ACCESS SERVICE 15
16 CALL DETAIL RECORD ACCESS SERVICE Parameters Returns Faults Parameter organizationid applicationid filterlist orderbylist startindex recordcount requestextendeddata Description A list of CDRs matching the specified criteria. The organization identifier. This ID is assigned when the application is provisioned. For Café developers, the value is always BVCLDEV. The application identifier. This ID is assigned when the application is provisioned. For Café developers, the value is the Café user ID. An array of Filter objects to constrain the query. Each filter specifies: a field on which to filter, such as EnumFilterField.ERROR_COUNT. an operator, such as EnumFilterOperator.GREATER_THAN. if applicable, an operand, such as 4; at present, an operand must be of type Date, String, or Integer. An array of OrderBy objects specifying the columns on which to sort the results. Each object specifies a field to use for ordering (such as EnumOrderByField.CALLING_PARTY) and a boolean indicating whether to sort in ascending or descending order. The starting index of the subset of records matching the criteria that are actually wanted. If you first use getcalldetailrecordcountbyfilter to determine the number of records that match your filter, you can then get those records in batches, by specifying a startindex and recordcount to this method. The number of records to retrieve. Determines whether or not to include extended data with the records. In some cases, the platform may associate additional data with a CDR. If this parameter is true, that additional data is included with the returned records as a set of name-value pairs. For Café applications, the platform always associates extended data. Currently, the available extended data are: NUM_ERROR--the number of errors NUM_MISRECS--the number of rejections REQ_ID--outbound request ID associated with the session (for outbound notification calls) CONNECTED--the time the call was actually connected (for outbound notification calls) For many faults, you can see the fault detail for additional information. Fault Number Description 1002 Access denied. (Client does not have access to the requested data.) 1003 The requested data is not available. 16 CALL DETAIL RECORD ACCESS SERVICE
17 getcalldetailrecordsbyfilter Examples SOAP Request POST /CDRAccessService_v2/services/CDRAccessService_v2 HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.0 Host: utopia Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 4448 <?xml version="1.0" encoding="utf-8"?> <soapenv:envelope xmlns:soapenv=" xmlns:xsd=" xmlns:xsi=" <soapenv:header> <ns1:platformservicessessionid xsi:type="xsd:string" xmlns:ns1=" E3EB1B1D378CC147ED935EFF39B8C911 </ns1:platformservicessessionid> </soapenv:header> <soapenv:body> <ns2:getcalldetailrecordsbyfilter xmlns:ns2="cdraccessservice_v2"> <arg0 xsi:type="xsd:string">bvcldev</arg0> <arg1 xsi:type="xsd:string"> </arg1> <arg2 xsi:type="soapenc:array" soapenc:arraytype="ns3:filter[2]" xmlns:soapenc=" xmlns:ns3="urn:beanservice"> <item href="#id0"/> <item href="#id1"/> </arg2> <arg3 xsi:type="soapenc:array" soapenc:arraytype="ns4:orderby[2]" xmlns:soapenc=" xmlns:ns4="urn:beanservice"> <item href="#id2"/> <item href="#id3"/> </arg3> <arg4 xsi:type="xsd:int">1</arg4> <arg5 xsi:type="xsd:int">33</arg5> <arg6 xsi:type="xsd:boolean">false</arg6> </ns2:getcalldetailrecordsbyfilter> <multiref id="id1" soapenc:root="0" xsi:type="ns5:filter" xmlns:soapenc=" xmlns:ns5="urn:beanservice"> <filterfield href="#id4"/> <filteroperator href="#id5"/> <filteroperand xsi:type="xsd:datetime"> T20:00:00.000Z</filterOperand> CALL DETAIL RECORD ACCESS SERVICE 17
18 CALL DETAIL RECORD ACCESS SERVICE <multiref id="id3" soapenc:root="0" xsi:type="ns6:orderby" xmlns:ns6="urn:beanservice" <orderbyascending xsi:type="xsd:boolean">false</orderbyascending> <orderbyfield href="#id6"/> <multiref id="id0" soapenc:root="0" xsi:type="ns7:filter" xmlns:ns7="urn:beanservice" <filterfield href="#id7"/> <filteroperator href="#id8"/> <filteroperand xsi:type="xsd:datetime"> T20:00:00.000Z</filterOperand> <multiref id="id2" soapenc:root="0" xsi:type="ns8:orderby" xmlns:ns8="urn:beanservice" <orderbyascending xsi:type="xsd:boolean">true</orderbyascending> <orderbyfield href="#id9"/> <multiref id="id5" soapenc:root="0" xsi:type="ns9:enumfilteroperator" xmlns:ns9="urn:beanservice" <value xsi:type="xsd:string">less_than_or_equals</value> <multiref id="id7" soapenc:root="0" xsi:type="ns10:enumfilterfield" xmlns:ns10="urn:beanservice" <value xsi:type="xsd:string">start_time</value> <multiref id="id4" soapenc:root="0" xsi:type="ns11:enumfilterfield" xmlns:ns11="urn:beanservice" <value xsi:type="xsd:string">end_time</value> <multiref id="id9" soapenc:root="0" xsi:type="ns12:enumorderbyfield" xmlns:ns12="urn:beanservice" <value xsi:type="xsd:string">start_time</value> <multiref id="id6" soapenc:root="0" xsi:type="ns13:enumorderbyfield" xmlns:ns13="urn:beanservice" <value xsi:type="xsd:string">end_time</value> <multiref id="id8" soapenc:root="0" 18 CALL DETAIL RECORD ACCESS SERVICE
19 getcalldetailrecordsbyfilter xsi:type="ns14:enumfilteroperator" xmlns:ns14="urn:beanservice" <value xsi:type="xsd:string">greater_than_or_equals</value> </soapenv:body> </soapenv:envelope> SOAP Response HTTP/ OK Server: Resin/2.1.4 Content-Type: text/xml; charset=utf-8 Date: Wed, 19 Mar :16:14 GMT <?xml version="1.0" encoding="utf-8"?> <soapenv:envelope xmlns:soapenv=" xmlns:xsd=" xmlns:xsi=" <soapenv:body> <ns1:getcalldetailrecordsbyfilterresponse xmlns:ns1="cdraccessservice_v2"> <getcalldetailrecordsbyfilterreturn xsi:type="soapenc:array" soapenc:arraytype="ns2:calldetailrecord[33]" xmlns:soapenc=" xmlns:ns2="urn:beanservice"> <item href="#id0"/> <item href="#id1"/> <item href="#id2"/>... <item href="#id32"/> </getcalldetailrecordsbyfilterreturn> </ns1:getcalldetailrecordsbyfilterresponse> <multiref id="id2" soapenc:root="0" xsi:type="ns12:calldetailrecord" xmlns:ns12="urn:beanservice" <calldurationseconds xsi:type="xsd:int">77</calldurationseconds> <capturedutterancecount xsi:type="xsd:int">0</capturedutterancecount> <utterancesavailable xsi:type="xsd:boolean">false</utterancesavailable> <parentsessionid xsi:type="xsd:string" xsi:nil="true"/> <applicationid xsi:type="xsd:string"> </applicationid> <calledparty xsi:type="xsd:string"> </calledparty> <bevocalcalllogavailable xsi:type="xsd:boolean">true</bevocalcalllogavailable> <sessionid xsi:type="xsd:string">2002-engca002-ch001-fw6bz</sessionid> <callresult xsi:type="xsd:string">completed</callresult> <mediagatewayhostname xsi:type="xsd:string">engcm002</mediagatewayhostname> <extendeddata xsi:type="soapenc:array" xsi:nil="true"/> <callingparty xsi:type="xsd:string"> </callingparty> <mediagatewaychannel xsi:type="xsd:string">ch001</mediagatewaychannel> <speechvendorcalllogavailable xsi:type="xsd:boolean">true</speechvendorcalllogavailable> <originalcallingparty xsi:type="xsd:string" xsi:nil="true"/> <startdatetime xsi:type="xsd:datetime"> T11:23:59.000Z</startDateTime> <organizationid xsi:type="xsd:string">bvcldev</organizationid> CALL DETAIL RECORD ACCESS SERVICE 19
20 CALL DETAIL RECORD ACCESS SERVICE <initialurl xsi:type="xsd:string"> <calltype xsi:type="xsd:string">inbound</calltype> <multiref id="id1" soapenc:root="0" xsi:type="ns16:calldetailrecord" xmlns:ns16="urn:beanservice" <calldurationseconds xsi:type="xsd:int">24</calldurationseconds> <capturedutterancecount xsi:type="xsd:int">0</capturedutterancecount> <utterancesavailable xsi:type="xsd:boolean">false</utterancesavailable> <parentsessionid xsi:type="xsd:string" xsi:nil="true"/> <applicationid xsi:type="xsd:string"> </applicationid> <calledparty xsi:type="xsd:string"> </calledparty> <bevocalcalllogavailable xsi:type="xsd:boolean">true</bevocalcalllogavailable> <sessionid xsi:type="xsd:string">2002-engca002-ch001-ftmm3</sessionid> <callresult xsi:type="xsd:string">completed</callresult> <mediagatewayhostname xsi:type="xsd:string">engcm002</mediagatewayhostname> <extendeddata xsi:type="soapenc:array" xsi:nil="true"/> <callingparty xsi:type="xsd:string"> </callingparty> <mediagatewaychannel xsi:type="xsd:string">ch001</mediagatewaychannel> <speechvendorcalllogavailable xsi:type="xsd:boolean"> true</speechvendorcalllogavailable> <originalcallingparty xsi:type="xsd:string" xsi:nil="true"/> <startdatetime xsi:type="xsd:datetime"> T14:22:51.000Z</startDateTime> <organizationid xsi:type="xsd:string">bvcldev</organizationid> <initialurl xsi:type="xsd:string"> <calltype xsi:type="xsd:string">inbound</calltype> <multiref id="id0" soapenc:root="0" xsi:type="ns19:calldetailrecord" xmlns:ns19="urn:beanservice" <calldurationseconds xsi:type="xsd:int">40</calldurationseconds> <capturedutterancecount xsi:type="xsd:int">0</capturedutterancecount> <utterancesavailable xsi:type="xsd:boolean">false</utterancesavailable> <parentsessionid xsi:type="xsd:string" xsi:nil="true"/> <applicationid xsi:type="xsd:string"> </applicationid> <calledparty xsi:type="xsd:string"> </calledparty> <bevocalcalllogavailable xsi:type="xsd:boolean">true</bevocalcalllogavailable> <sessionid xsi:type="xsd:string">2002-engca002-ch001-fo9dr</sessionid> <callresult xsi:type="xsd:string">completed</callresult> <mediagatewayhostname xsi:type="xsd:string">engcm002</mediagatewayhostname> <extendeddata xsi:type="soapenc:array" xsi:nil="true"/> <callingparty xsi:type="xsd:string"> </callingparty> <mediagatewaychannel xsi:type="xsd:string">ch001</mediagatewaychannel> <speechvendorcalllogavailable xsi:type="xsd:boolean"> true</speechvendorcalllogavailable> <originalcallingparty xsi:type="xsd:string" xsi:nil="true"/> <startdatetime xsi:type="xsd:datetime"> T16:49:03.000Z</startDateTime> <organizationid xsi:type="xsd:string">bvcldev</organizationid> <initialurl xsi:type="xsd:string"> 20 CALL DETAIL RECORD ACCESS SERVICE
21 getcalldetailrecordsbyindex <calltype xsi:type="xsd:string">inbound</calltype> <multiref id="id32" soapenc:root="0" xsi:type="ns31:calldetailrecord" xmlns:ns31="urn:beanservice" <calldurationseconds xsi:type="xsd:int">64</calldurationseconds> <capturedutterancecount xsi:type="xsd:int">0</capturedutterancecount> <utterancesavailable xsi:type="xsd:boolean">false</utterancesavailable> <parentsessionid xsi:type="xsd:string" xsi:nil="true"/> <applicationid xsi:type="xsd:string"> </applicationid> <calledparty xsi:type="xsd:string">scripter</calledparty> <bevocalcalllogavailable xsi:type="xsd:boolean">true</bevocalcalllogavailable> <sessionid xsi:type="xsd:string">2003-engcl001-ch000-13v9t0</sessionid> <callresult xsi:type="xsd:string">completed</callresult> <mediagatewayhostname xsi:type="xsd:string">engcl001</mediagatewayhostname> <extendeddata xsi:type="soapenc:array" xsi:nil="true"/> <callingparty xsi:type="xsd:string">scripter</callingparty> <mediagatewaychannel xsi:type="xsd:string">ch000</mediagatewaychannel> <speechvendorcalllogavailable xsi:type="xsd:boolean"> false</speechvendorcalllogavailable> <originalcallingparty xsi:type="xsd:string">scripter</originalcallingparty> <startdatetime xsi:type="xsd:datetime"> T01:07:48.000Z</startDateTime> <organizationid xsi:type="xsd:string">bvcldev</organizationid> <initialurl xsi:type="xsd:string"> <calltype xsi:type="xsd:string">inbound</calltype> </soapenv:body> </soapenv:envelope> getcalldetailrecordsbyindex Syntax Returns a list of call detail records for the set of calls that match the specified criteria. CallDetailRecord[] getcalldetailrecordsbyindex( String organizationid, String applicationid, Date starttime, Date endtime, int startindex, int recordcount, boolean requestextendeddata boolean orderbytimeascending ) CALL DETAIL RECORD ACCESS SERVICE 21
22 CALL DETAIL RECORD ACCESS SERVICE Parameters Parameter organizationid applicationid starttime endtime startindex recordcount requestextendeddata orderbytimeascending Returns Description The organization identifier. This ID is assigned when the application is provisioned. For Café developers, the value is always BVCLDEV. The application identifier. This ID is assigned when the application is provisioned. For Café developers, the value is the Café user ID. The start of the time interval for which records are requested. The Date format is described in Data Types on page 3 in Using BeVocal Platform Services. The end of the time interval for which records are requested. The Date format is described in Data Types on page 3 in Using BeVocal Platform Services. The starting index of the subset of records matching the criteria that are actually wanted. If you first use getcalldetailrecordcount to determine the number of records during the time period, you can then get those records in batches, by specifying a startindex and recordcount to this method. The number of records to retrieve. Determines whether or not to include extended data with the records. In some cases, the platform may associate additional data with a CDR. If this parameter is true, that additional data is included with the returned records as a set of name-value pairs. For Café applications, the platform always associates extended data. Currently, the available extended data are: NUM_ERROR--the number of errors NUM_MISRECS--the number of rejections REQ_ID--outbound request ID associated with the session (for outbound notification calls) CONNECTED--the time the call was actually connected (for outbound notification calls) If true the records are sorted by the ascending order of the starttime. If false the records are sorted by the descending order of the starttime. Faults For many faults, you can see the fault detail for additional information. Fault Number Description 1002 Access denied. (Client does not have access to the requested data.) 1003 The requested data is not available. 22 CALL DETAIL RECORD ACCESS SERVICE
23 getcalldetailrecordsbyindex Examples SOAP Request POST /CDRAccessService_v2/services/CDRAccessService_v2 HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.0 Host: utopia Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 1031 <?xml version="1.0" encoding="utf-8"?> <soapenv:envelope xmlns:soapenv=" xmlns:xsd=" xmlns:xsi=" <soapenv:header> <ns1:platformservicessessionid xsi:type="xsd:string" xmlns:ns1=" E3EB1B1D378CC147ED935EFF39B8C911 </ns1:platformservicessessionid> </soapenv:header> <soapenv:body> <ns2:getcalldetailrecordsbyindex xmlns:ns2="cdraccessservice_v2"> <arg0 xsi:type="xsd:string">bvcldev</arg0> <arg1 xsi:type="xsd:string"> </arg1> <arg2 xsi:type="xsd:datetime"> t20:00:00.000z</arg2> <arg3 xsi:type="xsd:datetime"> t20:00:00.000z</arg3> <arg4 xsi:type="xsd:int">1</arg4> <arg5 xsi:type="xsd:int">7</arg5> <arg6 xsi:type="xsd:boolean">true</arg6> <arg7 xsi:type="xsd:boolean">true</arg7> </ns2:getcalldetailrecordsbyindex> </soapenv:body> </soapenv:envelope> SOAP Response HTTP/ OK Server: Resin/2.1.4 Content-Type: text/xml; charset=utf-8 Date: Thu, 13 Mar :20:23 GMT <?xml version="1.0" encoding="utf-8"?> <soapenv:envelope xmlns:soapenv=" xmlns:xsd=" xmlns:xsi=" <soapenv:body> <ns1:getcalldetailrecordsbyindexresponse xmlns:ns1="cdraccessservice_v2"> <getcalldetailrecordsbyindexreturn xsi:type="soapenc:array" CALL DETAIL RECORD ACCESS SERVICE 23
24 CALL DETAIL RECORD ACCESS SERVICE soapenc:arraytype="ns2:calldetailrecord[7]" xmlns:soapenc=" xmlns:ns2="urn:beanservice"> <item href="#id0"/> <item href="#id1"/> <item href="#id2"/> <item href="#id3"/> <item href="#id4"/> <item href="#id5"/> <item href="#id6"/> </getcalldetailrecordsbyindexreturn> </ns1:getcalldetailrecordsbyindexresponse> <multiref id="id2" soapenc:root="0" xsi:type="ns3:calldetailrecord" xmlns:soapenc=" xmlns:ns3="urn:beanservice"> <calldurationseconds xsi:type="xsd:int">64</calldurationseconds> <capturedutterancecount xsi:type="xsd:int">0</capturedutterancecount> <utterancesavailable xsi:type="xsd:boolean">false</utterancesavailable> <parentsessionid xsi:type="xsd:string" xsi:nil="true"/> <applicationid xsi:type="xsd:string"> </applicationid> <calledparty xsi:type="xsd:string">scripter</calledparty> <bevocalcalllogavailable xsi:type="xsd:boolean">true</bevocalcalllogavailable> <sessionid xsi:type="xsd:string">2003-engcl001-ch000-13ny09</sessionid> <callresult xsi:type="xsd:string">completed</callresult> <mediagatewayhostname xsi:type="xsd:string">engcl001</mediagatewayhostname> <extendeddata xsi:type="soapenc:array" soapenc:arraytype="ns3:namevaluepair[3]"> <item href="#id7"/> <item href="#id8"/> <item href="#id9"/> </extendeddata> <callingparty xsi:type="xsd:string">scripter</callingparty> <mediagatewaychannel xsi:type="xsd:string">ch000</mediagatewaychannel> <speechvendorcalllogavailable xsi:type="xsd:boolean">false</speechvendorcalllogavailable> <originalcallingparty xsi:type="xsd:string">scripter</originalcallingparty> <startdatetime xsi:type="xsd:datetime"> t02:09:45.000z</startdatetime> <organizationid xsi:type="xsd:string">bvcldev</organizationid> <initialurl xsi:type="xsd:string"> L> <calltype xsi:type="xsd:string">inbound</calltype> <multiref id="id0" soapenc:root="0" xsi:type="ns4:calldetailrecord" xmlns:ns4="urn:beanservice" <calldurationseconds xsi:type="xsd:int">32</calldurationseconds> <capturedutterancecount xsi:type="xsd:int">0</capturedutterancecount> <utterancesavailable xsi:type="xsd:boolean">false</utterancesavailable> <parentsessionid xsi:type="xsd:string" xsi:nil="true"/> <applicationid xsi:type="xsd:string"> </applicationid> <calledparty xsi:type="xsd:string">scripter</calledparty> <bevocalcalllogavailable xsi:type="xsd:boolean">true</bevocalcalllogavailable> 24 CALL DETAIL RECORD ACCESS SERVICE
25 getcalldetailrecordsbyindex <sessionid xsi:type="xsd:string">2003-engcl001-ch000-13nazj</sessionid> <callresult xsi:type="xsd:string">completed</callresult> <mediagatewayhostname xsi:type="xsd:string">engcl001</mediagatewayhostname> <extendeddata xsi:type="soapenc:array" soapenc:arraytype="ns4:namevaluepair[3]"> <item href="#id10"/> <item href="#id11"/> <item href="#id12"/> </extendeddata> <callingparty xsi:type="xsd:string">scripter</callingparty> <mediagatewaychannel xsi:type="xsd:string">ch000</mediagatewaychannel> <speechvendorcalllogavailable xsi:type="xsd:boolean">false</speechvendorcalllogavailable> <originalcallingparty xsi:type="xsd:string">scripter</originalcallingparty> <startdatetime xsi:type="xsd:datetime"> t17:52:31.000z</startdatetime> <organizationid xsi:type="xsd:string">bvcldev</organizationid> <initialurl xsi:type="xsd:string"> L> <calltype xsi:type="xsd:string">inbound</calltype> <multiref id="id6" soapenc:root="0" xsi:type="ns5:calldetailrecord" xmlns:ns5="urn:beanservice" <calldurationseconds xsi:type="xsd:int">259</calldurationseconds> <capturedutterancecount xsi:type="xsd:int">0</capturedutterancecount> <utterancesavailable xsi:type="xsd:boolean">false</utterancesavailable> <parentsessionid xsi:type="xsd:string" xsi:nil="true"/> <applicationid xsi:type="xsd:string"> </applicationid> <calledparty xsi:type="xsd:string">scripter</calledparty> <bevocalcalllogavailable xsi:type="xsd:boolean">true</bevocalcalllogavailable> <sessionid xsi:type="xsd:string">2003-engcl001-ch000-13stzf</sessionid> <callresult xsi:type="xsd:string">completed</callresult> <mediagatewayhostname xsi:type="xsd:string">engcl001</mediagatewayhostname> <extendeddata xsi:type="soapenc:array" soapenc:arraytype="ns5:namevaluepair[3]"> <item href="#id13"/> <item href="#id14"/> <item href="#id15"/> </extendeddata> <callingparty xsi:type="xsd:string">scripter</callingparty> <mediagatewaychannel xsi:type="xsd:string">ch000</mediagatewaychannel> <speechvendorcalllogavailable xsi:type="xsd:boolean">false</speechvendorcalllogavailable> <originalcallingparty xsi:type="xsd:string">scripter</originalcallingparty> <startdatetime xsi:type="xsd:datetime"> t17:30:50.000z</startdatetime> <organizationid xsi:type="xsd:string">bvcldev</organizationid> <initialurl xsi:type="xsd:string"> L> <calltype xsi:type="xsd:string">inbound</calltype> <multiref id="id3" soapenc:root="0" xsi:type="ns6:calldetailrecord" xmlns:ns6="urn:beanservice" CALL DETAIL RECORD ACCESS SERVICE 25
26 CALL DETAIL RECORD ACCESS SERVICE <calldurationseconds xsi:type="xsd:int">10</calldurationseconds> <capturedutterancecount xsi:type="xsd:int">0</capturedutterancecount> <utterancesavailable xsi:type="xsd:boolean">false</utterancesavailable> <parentsessionid xsi:type="xsd:string" xsi:nil="true"/> <applicationid xsi:type="xsd:string"> </applicationid> <calledparty xsi:type="xsd:string">scripter</calledparty> <bevocalcalllogavailable xsi:type="xsd:boolean">true</bevocalcalllogavailable> <sessionid xsi:type="xsd:string">2003-engcl001-ch000-13pmqe</sessionid> <callresult xsi:type="xsd:string">completed</callresult> <mediagatewayhostname xsi:type="xsd:string">engcl001</mediagatewayhostname> <extendeddata xsi:type="soapenc:array" soapenc:arraytype="ns6:namevaluepair[3]"> <item href="#id16"/> <item href="#id17"/> <item href="#id18"/> </extendeddata> <callingparty xsi:type="xsd:string">scripter</callingparty> <mediagatewaychannel xsi:type="xsd:string">ch000</mediagatewaychannel> <speechvendorcalllogavailable xsi:type="xsd:boolean">false</speechvendorcalllogavailable> <originalcallingparty xsi:type="xsd:string">scripter</originalcallingparty> <startdatetime xsi:type="xsd:datetime"> t00:01:26.000z</startdatetime> <organizationid xsi:type="xsd:string">bvcldev</organizationid> <initialurl xsi:type="xsd:string"> L> <calltype xsi:type="xsd:string">inbound</calltype> <multiref id="id4" soapenc:root="0" xsi:type="ns7:calldetailrecord" xmlns:ns7="urn:beanservice" <calldurationseconds xsi:type="xsd:int">146</calldurationseconds> <capturedutterancecount xsi:type="xsd:int">0</capturedutterancecount> <utterancesavailable xsi:type="xsd:boolean">false</utterancesavailable> <parentsessionid xsi:type="xsd:string" xsi:nil="true"/> <applicationid xsi:type="xsd:string"> </applicationid> <calledparty xsi:type="xsd:string">scripter</calledparty> <bevocalcalllogavailable xsi:type="xsd:boolean">true</bevocalcalllogavailable> <sessionid xsi:type="xsd:string">2003-engcl001-ch000-13pmrg</sessionid> <callresult xsi:type="xsd:string">completed</callresult> <mediagatewayhostname xsi:type="xsd:string">engcl001</mediagatewayhostname> <extendeddata xsi:type="soapenc:array" soapenc:arraytype="ns7:namevaluepair[3]"> <item href="#id19"/> <item href="#id20"/> <item href="#id21"/> </extendeddata> <callingparty xsi:type="xsd:string">scripter</callingparty> <mediagatewaychannel xsi:type="xsd:string">ch000</mediagatewaychannel> <speechvendorcalllogavailable xsi:type="xsd:boolean">false</speechvendorcalllogavailable> <originalcallingparty xsi:type="xsd:string">scripter</originalcallingparty> <startdatetime xsi:type="xsd:datetime"> t00:02:04.000z</startdatetime> <organizationid xsi:type="xsd:string">bvcldev</organizationid> <initialurl xsi:type="xsd:string"> 26 CALL DETAIL RECORD ACCESS SERVICE
27 getcalldetailrecordsbyindex L> <calltype xsi:type="xsd:string">inbound</calltype> <multiref id="id5" soapenc:root="0" xsi:type="ns8:calldetailrecord" xmlns:ns8="urn:beanservice" <calldurationseconds xsi:type="xsd:int">22</calldurationseconds> <capturedutterancecount xsi:type="xsd:int">0</capturedutterancecount> <utterancesavailable xsi:type="xsd:boolean">true</utterancesavailable> <parentsessionid xsi:type="xsd:string" xsi:nil="true"/> <applicationid xsi:type="xsd:string"> </applicationid> <calledparty xsi:type="xsd:string"> </calledparty> <bevocalcalllogavailable xsi:type="xsd:boolean">true</bevocalcalllogavailable> <sessionid xsi:type="xsd:string">2003-engcm002-ch001-13rni8</sessionid> <callresult xsi:type="xsd:string">completed</callresult> <mediagatewayhostname xsi:type="xsd:string">engcm002</mediagatewayhostname> <extendeddata xsi:type="soapenc:array" soapenc:arraytype="ns8:namevaluepair[3]"> <item href="#id22"/> <item href="#id23"/> <item href="#id24"/> </extendeddata> <callingparty xsi:type="xsd:string"> </callingparty> <mediagatewaychannel xsi:type="xsd:string">ch001</mediagatewaychannel> <speechvendorcalllogavailable xsi:type="xsd:boolean">true</speechvendorcalllogavailable> <originalcallingparty xsi:type="xsd:string"> </originalcallingparty> <startdatetime xsi:type="xsd:datetime"> t02:13:20.000z</startdatetime> <organizationid xsi:type="xsd:string">bvcldev</organizationid> <initialurl xsi:type="xsd:string"> lurl> <calltype xsi:type="xsd:string">inbound</calltype> <multiref id="id1" soapenc:root="0" xsi:type="ns9:calldetailrecord" xmlns:ns9="urn:beanservice" <calldurationseconds xsi:type="xsd:int">28</calldurationseconds> <capturedutterancecount xsi:type="xsd:int">0</capturedutterancecount> <utterancesavailable xsi:type="xsd:boolean">false</utterancesavailable> <parentsessionid xsi:type="xsd:string" xsi:nil="true"/> <applicationid xsi:type="xsd:string"> </applicationid> <calledparty xsi:type="xsd:string">scripter</calledparty> <bevocalcalllogavailable xsi:type="xsd:boolean">true</bevocalcalllogavailable> <sessionid xsi:type="xsd:string">2003-engcl001-ch000-13nfpm</sessionid> <callresult xsi:type="xsd:string">completed</callresult> <mediagatewayhostname xsi:type="xsd:string">engcl001</mediagatewayhostname> <extendeddata xsi:type="soapenc:array" soapenc:arraytype="ns9:namevaluepair[3]"> <item href="#id25"/> <item href="#id26"/> <item href="#id27"/> </extendeddata> <callingparty xsi:type="xsd:string">scripter</callingparty> <mediagatewaychannel xsi:type="xsd:string">ch000</mediagatewaychannel> CALL DETAIL RECORD ACCESS SERVICE 27
28 CALL DETAIL RECORD ACCESS SERVICE <speechvendorcalllogavailable xsi:type="xsd:boolean">false</speechvendorcalllogavailable> <originalcallingparty xsi:type="xsd:string">scripter</originalcallingparty> <startdatetime xsi:type="xsd:datetime"> t19:34:33.000z</startdatetime> <organizationid xsi:type="xsd:string">bvcldev</organizationid> <initialurl xsi:type="xsd:string"> L> <calltype xsi:type="xsd:string">inbound</calltype> <multiref id="id21" soapenc:root="0" xsi:type="ns10:namevaluepair" xmlns:ns10="urn:beanservice" <name xsi:type="xsd:string">log_version</name> <value xsi:type="xsd:string">1.0</value> <multiref id="id22" soapenc:root="0" xsi:type="ns11:namevaluepair" xmlns:ns11="urn:beanservice" <name xsi:type="xsd:string">num_error</name> <multiref id="id13" soapenc:root="0" xsi:type="ns12:namevaluepair" xmlns:ns12="urn:beanservice" <name xsi:type="xsd:string">num_error</name> <multiref id="id24" soapenc:root="0" xsi:type="ns13:namevaluepair" xmlns:ns13="urn:beanservice" <name xsi:type="xsd:string">log_version</name> <value xsi:type="xsd:string">1.0</value> <multiref id="id23" soapenc:root="0" xsi:type="ns14:namevaluepair" xmlns:ns14="urn:beanservice" <name xsi:type="xsd:string">num_mis_rec</name> <multiref id="id16" soapenc:root="0" xsi:type="ns15:namevaluepair" xmlns:ns15="urn:beanservice" <name xsi:type="xsd:string">num_error</name> <multiref id="id18" soapenc:root="0" xsi:type="ns16:namevaluepair" xmlns:ns16="urn:beanservice" 28 CALL DETAIL RECORD ACCESS SERVICE
29 getcalldetailrecordsbyindex <name xsi:type="xsd:string">log_version</name> <value xsi:type="xsd:string">1.0</value> <multiref id="id14" soapenc:root="0" xsi:type="ns17:namevaluepair" xmlns:ns17="urn:beanservice" <name xsi:type="xsd:string">num_mis_rec</name> <multiref id="id10" soapenc:root="0" xsi:type="ns18:namevaluepair" xmlns:ns18="urn:beanservice" <name xsi:type="xsd:string">num_error</name> <multiref id="id25" soapenc:root="0" xsi:type="ns19:namevaluepair" xmlns:ns19="urn:beanservice" <name xsi:type="xsd:string">num_error</name> <multiref id="id26" soapenc:root="0" xsi:type="ns20:namevaluepair" xmlns:ns20="urn:beanservice" <name xsi:type="xsd:string">num_mis_rec</name> <multiref id="id9" soapenc:root="0" xsi:type="ns21:namevaluepair" xmlns:ns21="urn:beanservice" <name xsi:type="xsd:string">log_version</name> <value xsi:type="xsd:string">1.0</value> <multiref id="id12" soapenc:root="0" xsi:type="ns22:namevaluepair" xmlns:ns22="urn:beanservice" <name xsi:type="xsd:string">log_version</name> <value xsi:type="xsd:string">1.0</value> <multiref id="id27" soapenc:root="0" xsi:type="ns23:namevaluepair" xmlns:ns23="urn:beanservice" <name xsi:type="xsd:string">log_version</name> <value xsi:type="xsd:string">1.0</value> <multiref id="id19" soapenc:root="0" CALL DETAIL RECORD ACCESS SERVICE 29
30 CALL DETAIL RECORD ACCESS SERVICE xsi:type="ns24:namevaluepair" xmlns:ns24="urn:beanservice" <name xsi:type="xsd:string">num_error</name> <multiref id="id17" soapenc:root="0" xsi:type="ns25:namevaluepair" xmlns:ns25="urn:beanservice" <name xsi:type="xsd:string">num_mis_rec</name> <multiref id="id8" soapenc:root="0" xsi:type="ns26:namevaluepair" xmlns:ns26="urn:beanservice" <name xsi:type="xsd:string">num_mis_rec</name> <value xsi:type="xsd:string">1</value> <multiref id="id15" soapenc:root="0" xsi:type="ns27:namevaluepair" xmlns:ns27="urn:beanservice" <name xsi:type="xsd:string">log_version</name> <value xsi:type="xsd:string">1.0</value> <multiref id="id7" soapenc:root="0" xsi:type="ns28:namevaluepair" xmlns:ns28="urn:beanservice" <name xsi:type="xsd:string">num_error</name> <multiref id="id11" soapenc:root="0" xsi:type="ns29:namevaluepair" xmlns:ns29="urn:beanservice" <name xsi:type="xsd:string">num_mis_rec</name> <multiref id="id20" soapenc:root="0" xsi:type="ns30:namevaluepair" xmlns:ns30="urn:beanservice" <name xsi:type="xsd:string">num_mis_rec</name> </soapenv:body> </soapenv:envelope> 30 CALL DETAIL RECORD ACCESS SERVICE
Request of end customer against AP AP forwards request to OTACS Aborted with failure code Validate the request Is request syntactically correct? No Send failure code to AP Yes Validate authentication pin
Cisco TelePresence Content Server
Cisco TelePresence Content Server API Guide D1398008 August 2014 TABLE OF CONTENTS 1 INTRODUCTION... 5 1.1 Format of this document... 5 1.2 Variable usage... 6 1.3 Warnings... 6 2 SECURITY... 7 2.1 Security
File Transfer Service (Batch SOAP) User Guide. A Guide to Submitting batches through emedny FTS
File Transfer Service (Batch SOAP) User Guide A Guide to Submitting batches through emedny FTS June 1, 2013 TABLE OF CONTENTS TABLE OF CONTENTS 1 Introduction... 4 2 Requirements... 5 2.1 Exchange mailboxes...
VoIP LAB. 陳 懷 恩 博 士 助 理 教 授 兼 所 長 國 立 宜 蘭 大 學 資 訊 工 程 研 究 所 Email: [email protected] TEL: 03-9357400 # 255
SIP Traversal over NAT 陳 懷 恩 博 士 助 理 教 授 兼 所 長 國 立 宜 蘭 大 學 資 訊 工 程 研 究 所 Email: [email protected] TEL: 03-9357400 # 255 Outline Introduction to SIP and NAT NAT Problem Definition NAT Solutions on NTP VoIP
Web Services in Eclipse. Sistemi Informativi Aziendali A.A. 2012/2013
Web Services in Eclipse A.A. 2012/2013 Outline Apache Axis Web Service Clients Creating Web Services 2 Apache Axis Web Services in Eclipse WS basics (I) Web services are described by their WSDL file Starting
Lecture Notes course 02267 Software Development of Web Services
Lecture Notes course 02267 Software Development of Web Services Hubert Baumeister [email protected] Fall 2014 Contents 1 Web Service Coordination 1 1.1 What is Coordination.........................................
Freight Tracking Web Service Implementation Guide
www.peninsulatruck.com P.O. Box 587 (98071-0587) 1010 S 336 th, Suite 202 Federal Way, Washington 98003 Office (253) 929-2000 Fax (253) 929-2041 Toll Free (800) 942-9909 Freight Tracking Web Service Implementation
Middleware and the Internet
Middleware and the Internet Middleware today Designed for special purposes (e.g. DCOM) or with overloaded specification (e.g. CORBA) Specifying own protocols integration in real world network? Non-performant
Using ilove SharePoint Web Services Workflow Action
Using ilove SharePoint Web Services Workflow Action This guide describes the steps to create a workflow that will add some information to Contacts in CRM. As an example, we will use demonstration site
AXL Troubleshooting. Overview. Architecture
AXL Troubleshooting This chapter contains the following topics: Overview, page 35 Architecture, page 35 Postinstallation Checklist, page 36 Troubleshooting Tools, page 39 Error Codes, page 43 Overview
B2B Appointment Booking Specification
From Issue date 12 nd May 2008 Subject Broadband Connectivity Service and Full Access (T-)TAL Appointment Booking Status released Contract Version - WSG Version 10 Valid until Server location recalled
HTTP - METHODS. Same as GET, but transfers the status line and header section only.
http://www.tutorialspoint.com/http/http_methods.htm HTTP - METHODS Copyright tutorialspoint.com The set of common methods for HTTP/1.1 is defined below and this set can be expanded based on requirements.
What is Distributed Annotation System?
Contents ISiLS Lecture 12 short introduction to data integration F.J. Verbeek Genome browsers Solutions for integration CORBA SOAP DAS Ontology mapping 2 nd lecture BioASP roadshow 1 2 Human Genome Browsers
What is in a Distributed Object System? Distributed Object Systems 5 XML-RPC / SOAP. Examples. Problems. HTTP protocol. Evolution
Distributed Object Systems 5 XML-RPC / SOAP Piet van Oostrum What is in a Distributed Object System? Wire (transport) protocol Marshalling standard Language bindings Middle-ware (ORB) Interface specification
Usage of Evaluate Client Certificate with SSL support in Mediator and CentraSite
Usage of Evaluate Client Certificate with SSL support in Mediator and CentraSite Introduction Pre-requisite Configuration Configure keystore and truststore Asset Creation and Deployment Troubleshooting
DocuSign Connect Guide
Information Guide 1 DocuSign Connect Guide 2 Copyright 2003-2014 DocuSign, Inc. All rights reserved. For information about DocuSign trademarks, copyrights and patents refer to the DocuSign Intellectual
Hacking SAP BusinessObjects
Hacking SAP BusinessObjects 09/22/10 Joshua Jabra Abraham - [email protected] Willis Vandevanter [email protected] Overview Methodology / Threat Model Reconnaissance / Discovery Attacking! Summary Standard
Contents. 2 Alfresco API Version 1.0
The Alfresco API Contents The Alfresco API... 3 How does an application do work on behalf of a user?... 4 Registering your application... 4 Authorization... 4 Refreshing an access token...7 Alfresco CMIS
Table of Contents. Open-Xchange Authentication & Session Handling. 1.Introduction...3
Open-Xchange Authentication & Session Handling Table of Contents 1.Introduction...3 2.System overview/implementation...4 2.1.Overview... 4 2.1.1.Access to IMAP back end services...4 2.1.2.Basic Implementation
Web-Service Example. Service Oriented Architecture
Web-Service Example Service Oriented Architecture 1 Roles Service provider Service Consumer Registry Operations Publish (by provider) Find (by requester) Bind (by requester or invoker) Fundamentals Web
CONTRACT MODEL IPONZ DESIGN SERVICE VERSION 2. Author: Foster Moore Date: 20 September 2011 Document Version: 1.7
CONTRACT MODEL IPONZ DESIGN SERVICE VERSION 2 Author: Foster Moore Date: 20 September 2011 Document Version: 1.7 Level 6, Durham House, 22 Durham Street West PO Box 106857, Auckland City Post Shop, Auckland
Integrating CRM On Demand with the E-Business Suite to Supercharge your Sales Team
Integrating CRM On Demand with the E-Business Suite to Supercharge your Sales Team Presented by: Tom Connolly, Jason Lieberman Company: BizTech Session ID: #10351 Overview Introductions Background Web
ADOBE INDESIGN CS6 ADOBE INDESIGN CS6 SERVER SOLUTIONS
ADOBE INDESIGN CS6 ADOBE INDESIGN CS6 SERVER SOLUTIONS 2012 Adobe Systems Incorporated. All rights reserved. Adobe InDesign CS6 Server Solutions If this guide is distributed with software that includes
Single Sign-On Implementation Guide
Salesforce.com: Salesforce Winter '09 Single Sign-On Implementation Guide Copyright 2000-2008 salesforce.com, inc. All rights reserved. Salesforce.com and the no software logo are registered trademarks,
Secure Password-Based Authenticated Key Exchange. for Web Services
Secure Password-Based Authenticated Key Exchange for Web Services Liang Fang 1,2, Samuel Meder 4, Olivier Chevassut 3, and Frank Siebenlist 1 Abstract. This paper discusses an implementation of an authenticated
ACCREDITATION COUNCIL FOR PHARMACY EDUCATION. CPE Monitor. Technical Specifications
ACCREDITATION COUNCIL FOR PHARMACY EDUCATION CPE Monitor Technical Specifications Prepared by Steven Janis, RWK Design, Inc. Created: 02/10/2012 Revised: 09/28/2012 Revised: 08/28/2013 This document describes
The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into
The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material,
Qualys API Limits. July 10, 2014. Overview. API Control Settings. Implementation
Qualys API Limits July 10, 2014 Overview The Qualys API enforces limits on the API calls a customer can make based on their subscription settings, starting with Qualys version 6.5. The limits apply to
Examining the InDesign Server Solution
Examining the InDesign Server Solution This is an online bonus article for Chapter 13 of Paperless: Real-World Solutions with Adobe Technology. This article details the tools and techniques that were used
"Understanding Devices Profile for Web Services, Web Services Discovery, and SOAPover-UDP"
Understanding Devices Profile for Web Services, Web Services Discovery, and SOAP-over-UDP September 10, 2008 Version 1.0 Authors Ram Jeyaraman, Microsoft Corporation (Editor) Vipul Modi, Microsoft Corporation
JASPERREPORTS SERVER WEB SERVICES GUIDE
JASPERREPORTS SERVER WEB SERVICES GUIDE RELEASE 5.0 http://www.jaspersoft.com JasperReports Server Web Services Guide Copyright 2012 Jaspersoft Corporation. All rights reserved. Printed in the U.S.A. Jaspersoft,
PASS4TEST 専 門 IT 認 証 試 験 問 題 集 提 供 者
PASS4TEST 専 門 IT 認 証 試 験 問 題 集 提 供 者 http://www.pass4test.jp 1 年 で 無 料 進 級 することに 提 供 する Exam : C2090-420 Title : IBM InfoSphere MDM Server v9.0 Vendors : IBM Version : DEMO NO.1 Which two reasons would
HTTP and HTTPS Statistics Services
CHAPTER 9 This chapter describes the HTTP and HTTPS Statistics service, which returns HTTP and HTTPS connection information and statistics for individual WAEs, device groups, and for the WAAS network,
Dynamic Decision-Making Web Services Using SAS Stored Processes and SAS Business Rules Manager
Paper SAS1787-2015 Dynamic Decision-Making Web Services Using SAS Stored Processes and SAS Business Rules Manager Chris Upton and Lori Small, SAS Institute Inc. ABSTRACT With the latest release of SAS
The BritNed Explicit Auction Management System. Kingdom Web Services Interfaces
The BritNed Explicit Auction Management System Kingdom Web Services Interfaces Version 5.1 November 2014 Contents 1. PREFACE... 6 1.1. Purpose of the Document... 6 1.2. Document Organization... 6 2. Web
Single Sign-On Implementation Guide
Version 27.0: Spring 13 Single Sign-On Implementation Guide Last updated: February 1, 2013 Copyright 2000 2013 salesforce.com, inc. All rights reserved. Salesforce.com is a registered trademark of salesforce.com,
CRM On Demand. Oracle CRM On Demand CTI Developer s Guide
CRM On Demand Oracle CRM On Demand CTI Developer s Guide Release 19 September 2011 Copyright 2005, 2011 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided
T320 E-business technologies: foundations and practice
T320 E-business technologies: foundations and practice Block 3 Part 1 Activity 5: Implementing a simple web service Prepared for the course team by Neil Simpkins Introduction 1 Components of a web service
Web Services. Distributed Object Systems 11. Web Services, SOAP and NET. Web Applications. Web Services. Web services vs Distributed Objects
Distributed Object Systems 11 Web Services, SOAP and NET Piet van Oostrum Web Services Some Definitions A Web Service is a software system designed to support interoperable machine-to-machine interaction
9.4 BI Web. SAS Services. Developer's Guide. SAS Documentation
SAS Services Developer's Guide 9.4 BI Web SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2013. SAS 9.4 BI Web Services: Developer's Guide. Cary,
Bindings for the OASIS Security Assertion Markup Language (SAML) V2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 Bindings for the OASIS Security Assertion Markup Language (SAML) V2.0 OASIS Standard,
DEVELOPING CONTRACT - DRIVEN WEB SERVICES USING JDEVELOPER. The purpose of this tutorial is to develop a java web service using a top-down approach.
DEVELOPING CONTRACT - DRIVEN WEB SERVICES USING JDEVELOPER Purpose: The purpose of this tutorial is to develop a java web service using a top-down approach. Topics: This tutorial covers the following topics:
Web Services for deeply embedded extra low-cost devices
Web Services for deeply embedded extra low-cost devices D. Villa, F. J. Villanueva, F.Moya, F. Rincón, J. Barba, and J. C. López Dept. of Technology and Information Systems University of Castilla-La Mancha
Documentation Cendris Web Services Version 20 12 July 2013
Documentation Cendris Web Services Version 20 12 July 2013 Document: Documentation Cendris Webservices.docx blz 1 van 40 Index 1 Introduction... 3 2 Webportal Cendris Web services... 4 3 Implementation
Internet Technologies. World Wide Web (WWW) Proxy Server Network Address Translator (NAT)
Internet Technologies World Wide Web (WWW) Proxy Server Network Address Translator (NAT) What is WWW? System of interlinked Hypertext documents Text, Images, Videos, and other multimedia documents navigate
dctrack Web Services API - Ticketing User Guide 3.0.0
dctrack Web Services API - Ticketing User Guide 3.0.0 Copyright 2013 Raritan, Inc. dctrack-ws-api-0e-3.0.0-e February 2013 255-80-8008-00 This document contains proprietary information that is protected
Single Sign-On Implementation Guide
Single Sign-On Implementation Guide Salesforce, Summer 15 @salesforcedocs Last updated: July 1, 2015 Copyright 2000 2015 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark of
WEB OF KNOWLEDGE WEB SERVICES LITE V. 3.0. July 2, 2013
WEB OF KNOWLEDGE WEB SERVICES LITE V. 3.0 July 2, 2013 Table of Contents Introduction 3 Web Service Clients 3 Service Endpoint Addresses 3 WSDL File Locations 3 Document Namespaces 4 Sequence of Requests
Dev Guide for Encrypted Swipe
Dev Guide for Encrypted Swipe Version 1.5 Last Updated: 20 th August 2014 Table of Contents 1 Introduction... 3 2 Important notes... 4 3 Concept Overview... 5 4 Encrypted Swipe Devices... 6 4.1 Magtek
Sample Usage of TAXII
THE MITRE CORPORATION Sample Usage of TAXII Version 1.0 (draft) Mark Davidson, Charles Schmidt 11/16/2012 The Trusted Automated exchange of Indicator Information (TAXII ) specifies mechanisms for exchanging
Windows Phone 8 Enterprise Device Management Protocol
Windows Phone 8 Enterprise Device Management Protocol January 2014 Version 1.6 Proprietary Notice 2014 Microsoft. All rights reserved. This document is provided as-is. Information and views expressed in
Shibboleth Architecture
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Shibboleth Architecture Technical Overview Working Draft 02, 8 June 2005 Document identifier: draft-mace-shibboleth-tech-overview-02 Location: http://shibboleth.internet2.edu/shibboleth-documents.html
Introduction to Testing Webservices
Introduction to Testing Webservices Author: Vinod R Patil Abstract Internet revolutionized the way information/data is made available to general public or business partners. Web services complement this
Using web service technologies for incremental, real-time data transfers from EDC to SAS
Paper AD08 Using web service technologies for incremental, real-time data transfers from EDC to SAS Andrew Newbigging, Medidata Solutions Worldwide, London, UK ABSTRACT Data collected in EDC systems is
Merchant Web Services API
Merchant Web Services API Automated Recurring Billing (ARB) XML Guide Authorize.Net Developer Support http://developer.authorize.net Authorize.Net LLC 042007 Ver.1.0 Authorize.Net LLC ( Authorize.Net )
Sage CRM. Sage CRM 2016 R1 Web Services Guide
Sage CRM Sage CRM 2016 R1 Web Services Guide Copyright 2015 Sage Technologies Limited, publisher of this work. All rights reserved. No part of this documentation may be copied, photocopied, reproduced,
GetFormatList. Webservice name: GetFormatList. Adress: https://www.elib.se/webservices/getformatlist.asmx
GetFormatList Webservice name: GetFormatList Adress: https://www.elib.se/webservices/getformatlist.asmx WSDL: https://www.elib.se/webservices/getformatlist.asmx?wsdl Webservice Methods: Name: GetFormatList
Types of Cloud Computing
Types of Cloud Computing (SaaS)Software as a Service XaaS (PaaS) Platform as a Service (IaaS) Infrastructure as a Service Access to Cloud computing Service Web URL (standard HTTP methods) web brower HTTP
SOPG (Service Oriented Prepaid Gateway - xml based protocol) Documentation. Version Date Description Author
CLASSIC PAYMENT API SOPG (Service Oriented Prepaid Gateway - xml based protocol) Documentation Version history Version Date Description Author 0.1 2013-10-03 Initial draft Paul Kneidinger 0.2 2013-20-03
UPMC HEALTH PLAN. HIPAA EDI Companion Guide
UPMC HEALTH PLAN HIPAA EDI Companion Guide For 270/271 Eligibility Inquiry & Response Companion Guide Version: 1.2 Refers to the Implementation Guide Based on X12 Version 005010X279A1 ~ 1 ~ Disclosure
Single Sign-On Implementation Guide
Single Sign-On Implementation Guide Salesforce, Winter 16 @salesforcedocs Last updated: November 4, 2015 Copyright 2000 2015 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark
Windows 8.1 Enterprise Device Management Protocol
Windows 8.1 Enterprise Device Management Protocol Published: May 2015 Applies to: Windows 8.1 Windows 8.1 Enterprise Device Management Protocol 2 Copyright This document is provided as-is. Information
Universal Event Monitor for SOA 5.2.0 Reference Guide
Universal Event Monitor for SOA 5.2.0 Reference Guide 2015 by Stonebranch, Inc. All Rights Reserved. 1. Universal Event Monitor for SOA 5.2.0 Reference Guide.............................................................
Responsys Interact January 2011. 900 Cherry Ave. 5 th Floor San Bruno, CA 94066 650.745.1700 www.responsys.com
Interact Campaign Interact Web Services API Developer Guide Responsys Interact January 2011 900 Cherry Ave. 5 th Floor San Bruno, CA 94066 650.745.1700 www.responsys.com Table of Contents Table of Contents
Designing RESTful Web Applications
Ben Ramsey php works About Me: Ben Ramsey Proud father of 7-month-old Sean Organizer of Atlanta PHP user group Founder of PHP Groups Founding principal of PHP Security Consortium Original member of PHPCommunity.org
CONNECTICUT INSURANCE VERIFICATION SYSTEM (CTIVS)
CONNECTICUT INSURANCE VERIFICATION SYSTEM (CTIVS) Implementation Guide for Insurance Companies Version 1.1 August 15, 2015 MV Solutions, Inc. 2014 Table of Contents 1. INTRODUCTION... 3 2. BOOK OF BUSINESS
Web-Programmierung (WPR)
Web-Programmierung (WPR) Vorlesung X. Web Services Teil 2 mailto:[email protected] 1 21 Web Service World Wide Web seit Anfang 1990er Jahren Mensch Web-Browser Applikation HTTP XML over HTTP Web-Server Geschäftslogik
Integration of Hotel Property Management Systems (HPMS) with Global Internet Reservation Systems
Integration of Hotel Property Management Systems (HPMS) with Global Internet Reservation Systems If company want to be competitive on global market nowadays, it have to be persistent on Internet. If we
Vodia PBX RESTful API (v2.0)
Vodia PBX RESTful API (v2.0) 2015 Vodia Networks Inc. All rights reserved. Page 1 of 30 Contents Login... 3 Get license info... 4 Get a complete list of domains... 5 Get the details of a specific domain...
How To Validate A Single Line Address On An Ipod With A Singleline Address Validation (For A Non-Profit) On A Microsoft Powerbook (For An Ipo) On An Uniden Computer (For Free) On Your Computer Or
Informatica AddressDoctor Cloud (Version 2) User Guide Informatica AddressDoctor Cloud User Guide Version 2 December 2014 Copyright (c) 1999-2014 Informatica Corporation. All rights reserved. This software
Nuance Mobile Developer Program. HTTP Services for Nuance Mobile Developer Program Clients
Nuance Mobile Developer Program HTTP Services for Nuance Mobile Developer Program Clients Notice Nuance Mobile Developer Program HTTP Services for Nuance Mobile Developer Program Clients Copyright 2011
2015-11-30. Web Based Single Sign-On and Access Control
0--0 Web Based Single Sign-On and Access Control Different username and password for each website Typically, passwords will be reused will be weak will be written down Many websites to attack when looking
Title page. Alcatel-Lucent 5620 SERVICE AWARE MANAGER 13.0 R7
Title page Alcatel-Lucent 5620 SERVICE AWARE MANAGER 13.0 R7 APPLICATION API DEVELOPER GUIDE 3HE-10590-AAAA-TQZZA Issue 1 December 2015 Legal notice Legal notice Alcatel, Lucent, Alcatel-Lucent and the
Betfair API Quick Start and Best Practice Guide
Betfair API Quick Start and Best Practice Guide Table of Contents TABLE OF CONTENTS... 2 DOCUMENT PURPOSE... 3 WEB SERVICE TESTING TOOLS... 4 HOW DO I?... 5 LOGGING ON TO THE BETFAIR API... 6 REQUESTING
HireDesk API V1.0 Developer s Guide
HireDesk API V1.0 Developer s Guide Revision 1.4 Talent Technology Corporation Page 1 Audience This document is intended for anyone who wants to understand, and use the Hiredesk API. If you just want to
Real-Time Connectivity Specifications For. 270/271 and 276/277 Inquiry Transactions. United Concordia Dental (UCD)
Real-Time Connectivity Specifications For 270/271 and 276/277 Inquiry Transactions United Concordia Dental (UCD) May 15, 2015 1 Contents 1. Overview 2. Trading Partner Requirements 3. Model SOAP Messages
Merchant Service Provider Guide for Mobilpenge Based Acquiring
Merchant Service Provider Guide for Mobilpenge Based Acquiring November 14, 2011 Version 1.07 Nets Technical Guide Copyright Nets Danmark A/S Page 1 Contents 1 Introduction... 4 1.1 Notation convention...
SECURE USE OF CLOUD STORAGE
SECURE USE OF CLOUD STORAGE BLACKHAT BRIEFINGS USA 2010 AUTHOR Grant Bugher Lead Security Program Manager, Online Services Security and Compliance Global Foundation Services, Microsoft Corporation JULY
Web Application Security
Web Application Security The OWASP Foundation Securing the application Input validation Authorization Session mgmt Config mgmt Authenticatio n Error handling Web server App server DB server Secure storage
[MS-SPEMAWS]: SharePoint Email Web Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-SPEMAWS]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
Service Oriented Computing: SOAP, WSDL and UDDI. Dr. Cristian Mateos Diaz (http://users.exa.unicen.edu.ar/~cmateos/cos) ISISTAN - CONICET
Service Oriented Computing: SOAP, WSDL and UDDI Dr. Cristian Mateos Diaz (http://users.exa.unicen.edu.ar/~cmateos/cos) ISISTAN - CONICET XML family of standards Domain-specific XML-based standards e.g.,
gsoap 2.7.0 User Guide
gsoap 2.7.0 User Guide Robert van Engelen Genivia, Inc., [email protected] & [email protected] October 15, 2004 Contents 1 Introduction 6 2 Notational Conventions 7 3 Differences Between gsoap Versions
HP Operations Manager Incident Web Service
HP Operations Manager Incident Web Service for the UNIX and Windows operating systems Software Version: 8.00 Integration Guide Document Release Date: July 2008 Software Release Date: July 2008 Legal Notices
Technical Interface Description
Technical Interface Description Version 2.4.1 28.04.2015 Table of Contents 1 Introduction... 6 1.1 Preamble... 6 1.2 Structure of the Document... 6 1.3 Referenced Documents... 7 1.4 List of Abbreviations...
Penetration Testing Corporate Collaboration Portals. Giorgio Fedon, Co-Founder at Minded Security
Penetration Testing Corporate Collaboration Portals Giorgio Fedon, Co-Founder at Minded Security Something About Me Security Researcher Owasp Italy Member Web Application Security and Malware Research
reference: HTTP: The Definitive Guide by David Gourley and Brian Totty (O Reilly, 2002)
1 cse879-03 2010-03-29 17:23 Kyung-Goo Doh Chapter 3. Web Application Technologies reference: HTTP: The Definitive Guide by David Gourley and Brian Totty (O Reilly, 2002) 1. The HTTP Protocol. HTTP = HyperText
Replacements TECHNICAL REFERENCE. DTCCSOLUTIONS Dec 2009. Copyright 2009 Depository Trust Clearing Corporation. All Rights Reserved.
TECHNICAL REFERENCE Replacements Page 1 Table of Contents Table of Contents 1 Overview... 3 1.1 Replacements Features... 3 2 Roles and Responsibilities... 4 2.1 Sender (Receiving Carrier)... 4 2.2 Recipient
The presentation explains how to create and access the web services using the user interface. WebServices.ppt. Page 1 of 14
The presentation explains how to create and access the web services using the user interface. Page 1 of 14 The aim of this presentation is to familiarize you with the processes of creating and accessing
Address Phone & Fax Internet
Smilehouse Workspace 1.13 Payment Gateway API Document Info Document type: Technical document Creator: Smilehouse Workspace Development Team Date approved: 31.05.2010 Page 2/34 Table of Content 1. Introduction...
EMC Atmos Cloud Optimized Storage for Web Services
EMC Atmos Cloud Optimized Storage for Web Services Best Practices Planning Abstract This white paper provides an in-depth analysis for the management, storage, and retrieval of objects that are accessed
e Merchant Plug-in (MPI) Integration & User Guide
Payment solutions for online commerce e Merchant Plug-in (MPI) Integration & User Guide Enabling merchants to integrate their payment processing with PayPoint.net s 3D Secure Merchant Plug In (MPI) solution.
Specify the location of an HTML control stored in the application repository. See Using the XPath search method, page 2.
Testing Dynamic Web Applications How To You can use XML Path Language (XPath) queries and URL format rules to test web sites or applications that contain dynamic content that changes on a regular basis.
GetLibraryUserOrderList
GetLibraryUserOrderList Webservice name: GetLibraryUserOrderList Adress: https://www.elib.se/webservices/getlibraryuserorderlist.asmx WSDL: https://www.elib.se/webservices/getlibraryuserorderlist.asmx?wsdl
02267: Software Development of Web Services
02267: Software Development of Web Services Week 8 Hubert Baumeister [email protected] Department of Applied Mathematics and Computer Science Technical University of Denmark Fall 2015 1 Recap I BPEL: I Doing
What is a Web service?
What is a Web service? Many people and companies have debated the exact definition of Web services. At a minimum, however, a Web service is any piece of software that makes itself available over the Internet
Web. Services. Web Technologies. Today. Web. Technologies. Internet WWW. Protocols TCP/IP HTTP. Apache. Next Time. Lecture #3 2008 3 Apache.
JSP, and JSP, and JSP, and 1 2 Lecture #3 2008 3 JSP, and JSP, and Markup & presentation (HTML, XHTML, CSS etc) Data storage & access (JDBC, XML etc) Network & application protocols (, etc) Programming
