From 107c6b2853cec50fc4082844979174e04b808962 Mon Sep 17 00:00:00 2001 From: DanB Date: Wed, 20 Jan 2016 19:01:00 +0100 Subject: [PATCH] Fix docs regarding http_cdr address --- docs/cdrserver.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/cdrserver.rst b/docs/cdrserver.rst index 686ffb510..4d6c9133c 100644 --- a/docs/cdrserver.rst +++ b/docs/cdrserver.rst @@ -11,7 +11,7 @@ CDR-CGR Available as handler within http server. -To feed CDRs in via this interface, one must use url of the form: . +To feed CDRs in via this interface, one must use url of the form: . The CDR fields are received via http form (although for simplicity we support inserting them within query parameters as well) and are expected to be urlencoded in order to transport special characters reliably. All fields are expected by CGRateS as string, particular conversions being done on processing each CDR. The fields received are split into two different categories based on CGRateS interest in them: @@ -38,7 +38,7 @@ Extra fields: any field coming in via the http request and not a member of prima Example of sample CDR generated simply using curl: :: - curl --data "curl --data "tor=*voice&accid=iiaasbfdsaf&cdrhost=192.168.1.1&cdrsource=curl_cdr&reqtype=rated&direction=*out&tenant=192.168.56.66&category=call&account=dan&subject=dan&destination=%2B4986517174963&answer_time=1383813746&usage=1&sip_user=Jitsi&subject2=1003" http://127.0.0.1:2080/cgr + curl --data "curl --data "tor=*voice&accid=iiaasbfdsaf&cdrhost=192.168.1.1&cdrsource=curl_cdr&reqtype=rated&direction=*out&tenant=192.168.56.66&category=call&account=dan&subject=dan&destination=%2B4986517174963&answer_time=1383813746&usage=1&sip_user=Jitsi&subject2=1003" http://127.0.0.1:2080/cdr_http CDR-FS_JSON