Call detail record - Revision history

Songtao xie: /* Customer defined CDR records */

2021-02-19T21:55:42Z

Customer defined CDR records

Songtao xie: /* Customer defined CDR records */

2021-02-19T21:54:52Z

Customer defined CDR records

Songtao xie: /* Customer defined CDR records */

2021-02-19T21:50:35Z

Customer defined CDR records

Songtao xie: /* Customer defined CDR records */

2021-02-19T21:48:24Z

Customer defined CDR records

Songtao xie: /* Customer defined CDR records */

2021-02-19T21:47:32Z

Customer defined CDR records

Songtao xie: /* Customer defined CDR records */

2021-02-19T21:05:01Z

Customer defined CDR records

Songtao xie at 21:04, 19 February 2021

2021-02-19T21:04:03Z

Songtao xie: /* Customer defined CDR records */

2020-11-05T11:50:04Z

Customer defined CDR records

Songtao xie: /* Customer defined CDR records */

2020-10-26T14:45:23Z

Customer defined CDR records

Songtao xie: /* Customer defined CDR records */

2020-10-26T14:44:49Z

Customer defined CDR records

← Older revision		Revision as of 21:55, 19 February 2021
Line 91:		Line 91:

	Radius server needs to parse the received value like "TERM-IOI=xxxxxxxxxxxx" for attribute "Telcob-generic-cdr-name1"		Radius server needs to parse the received value like "TERM-IOI=xxxxxxxxxxxx" for attribute "Telcob-generic-cdr-name1"
		+

	If you want to use accounting header with this feature, you need to add the accounting header in script sip_headers_manipulation.rb , for example:		If you want to use accounting header with this feature, you need to add the accounting header in script sip_headers_manipulation.rb , for example:

@@ Line 99: / Line 99: @@
   end
-The header1 and header2 are the accounting headers you defined for your cdr purpose
+The header1 and header2 are the accounting headers name you defined for your cdr purpose. After adding them in sip_headers_manipulation.rb, in text-area box "Customer CDR headers settings", you add :
 Limitation:

← Older revision		Revision as of 21:50, 19 February 2021
Line 99:		Line 99:
	end		end

		+	The header1 and header2 are the accounting headers you defined for your cdr purpose

	Limitation:		Limitation:

@@ Line 93: / Line 93: @@
 If you want to use accounting header with this feature, you need to add the accounting header in script sip_headers_manipulation.rb , for example:
+ def filter_sip_headers_manipulation params
-def filter_sip_headers_manipulation params
+  call[:manipulation][:accounting] = {}
- call[:manipulation][:accounting] = {}
+  call[:manipulation][:accounting]["header1"] = "value1"
- call[:manipulation][:accounting]["header1"] = "value1"
+  call[:manipulation][:accounting]["header2"] = "value2"
- call[:manipulation][:accounting]["header2"] = "value2"
+ end
 end

@@ Line 71: / Line 71: @@
 == Customer defined CDR records   ==
-From release 3.1.101.1, The Customer defined CDR records is supported, you can select the SIP generic headers and their parameters as a CDR records used in TextCdr and Radius CDR, look at the list below to see the headers that are not supported by this new feature.
+From release 3.1.101.1, The Customer defined CDR records is supported, you can select the SIP generic headers and their parameters as a CDR records used in TextCdr and Radius CDR, look at the list below to see the sip call headers that are not supported by this new feature. And from release 3.1.114.1, you can use the accounting header defined in sip_headers_manipulation.rb
 For activating the feature, log on the web portal of SBC and go to Gateway->CDR Options->Use Customer CDR header, enter the CDR records you
@@ Line 81: / Line 82: @@
 This example means that 2 CDR records are needed, one is TERM-IOI and other one is P-CHARGE-INFO. Each line represents a CDR record and lines are separated by a line return. In this example, CDR record TERM-IOI comes from the received SIP header "P-Charging-Vector" and use its param "term-ioi" as the value of CDR record TERM-IOI. For the second line, CDR record is P-CHARGE-INFO and it comes from received SIP header "P-CHARGE-INFO", the parameter "all" means all of the content of sip header "P-CHARGE-INFO" will be used as the value of CDR record P-CHARGE-INFO. If Radius CDR is used, the attribute name will be like Telcob-generic-cdr-nameX (X will be from 1 to 16 , depends on the number of Customer defined CDR records ).
@@ Line 91: / Line 91: @@
 Radius server needs to parse the received value like "TERM-IOI=xxxxxxxxxxxx" for attribute "Telcob-generic-cdr-name1"

← Older revision		Revision as of 21:05, 19 February 2021
Line 80:		Line 80:
	P-CHARGE-INFO=P-CHARGE-INFO:all		P-CHARGE-INFO=P-CHARGE-INFO:all

−	This example means that 2 CDR records are needed, one is TERM-IOI and other one is P-CHARGE-INFO. Each line represents a CDR record and lines are separated by a line return. In this example, CDR record TERM-IOI comes from the received SIP header "P-Charging-Vector" and use its param "term-ioi" as the value of CDR record TERM-IOI. For the second line, CDR record is P-CHARGE-INFO and it comes from received SIP header "P-CHARGE-INFO", the parameter "all" means all of the content of sip header "P-CHARGE-INFO" will be used as the value of CDR record P-CHARGE-INFO. If Radius CDR is used, the attribute name will be like Telcob-generic-cdr-nameX (X will be from 1 to 8 , depends on the number of Customer defined CDR records ).	+	This example means that 2 CDR records are needed, one is TERM-IOI and other one is P-CHARGE-INFO. Each line represents a CDR record and lines are separated by a line return. In this example, CDR record TERM-IOI comes from the received SIP header "P-Charging-Vector" and use its param "term-ioi" as the value of CDR record TERM-IOI. For the second line, CDR record is P-CHARGE-INFO and it comes from received SIP header "P-CHARGE-INFO", the parameter "all" means all of the content of sip header "P-CHARGE-INFO" will be used as the value of CDR record P-CHARGE-INFO. If Radius CDR is used, the attribute name will be like Telcob-generic-cdr-nameX (X will be from 1 to 16 , depends on the number of Customer defined CDR records ).

@@ Line 95: / Line 95: @@
 Limitation:
-. The maximal number of Customer defined CDR records is 8.
+. The maximal number of Customer defined CDR records is 16.
 . All of sip header in the the following list are not supported by the feature.

@@ Line 100: / Line 100: @@
 . List of SIP header that are not supported:
-                                                Accept
+ Accept
   Accept-Contact
   Accept-Encoding

← Older revision		Revision as of 14:44, 26 October 2020
Line 100:		Line 100:

	3. List of SIP header that are not supported:		3. List of SIP header that are not supported:
		+	Accept
		+	Accept-Contact
		+	Accept-Encoding
		+	Accept-Language
		+	Alert-Info
		+	Allow
		+	Allow-Events
		+	Also
		+	Anonymity
		+	Authentication-Info
		+	Authorization
		+	Call-ID
		+	Call-Info
		+	Contact
		+	Content-Disposition
		+	Content-Encoding
		+	Content-Language
		+	Content-Length
		+	Content-Type
		+	CSeq
		+	Date
		+	Encryption
		+	Error-Info
		+	Event
		+	Expires
		+	From
		+	In-Reply-To
		+	Max-Forwards
		+	MIME-version
		+	Min-Expires
		+	Min-SE
		+	Organization
		+	P-Asserted-Identity
		+	P-Media-Authorization
		+	P-Preferred-Identity
		+	Priority
		+	Privacy
		+	Proxy-Authenticate
		+	Proxy-Authorization
		+	Proxy-Require
		+	RAck
		+	Reason
		+	Record-Route
		+	Refer-To
		+	Referred-By
		+	Reject-Contact
		+	Remote-Party-ID
		+	Replaces
		+	Reply-To
		+	Request-Disposition
		+	Require
		+	Response-Key
		+	Retry-After
		+	Route
		+	RPID-Privacy
		+	RSeq
		+	Security-Client
		+	Security-Server
		+	Security-Verify
		+	Server
		+	Service-Route
		+	Session-Expires
		+	Subject
		+	Subscription-State
		+	Supported
		+	Timestamp
		+	To
		+	Unsupported
		+	User-Agen
		+	Via
		+	Warning
		+	WWW-Authenticate