How to Add Customer VSA Header in CDR

Asset ID:	1-72-2345920.1
Update Date:	2018-04-30
Keywords:

Solution Type Problem Resolution Sure

Solution 2345920.1 : How to Add Customer VSA Header in CDR

Applies to:

Acme Packet 4600 - Version S-Cz7.3.0 to S-Cz8.0.0 [Release S-Cz7.0 to S-Cz8.0]
Information in this document applies to any platform.

Symptoms

User wants to include additional VSA headers into the CDRs.

Call flow is Invite goes to Session Agent XX, XX sends back 300 multiple choice with Contact that points to 0.0.0.0:5060 which resolves as session agent YY,

YY session agent has out-manipulationid CDRInfoToVSA but the process did not pick up and the VSA was not included in the CDRs.

Changes

Cause

User HMR was incorrectly built and manipulation string that back references to the HMR was not present.

Solution

Below sip-manipulation was used where the contents of From header of the INVITE to the P-Acme-VSA header as below –

P-Acme-VSA: 220:sut <sip:service@1.x.x.x:5060>

SD-3820-43-HD(sip-manipulation)# show
sip-manipulation
name generateVSA200
description
split-headers
join-headers
header-rule
name storeFrom
header-name from
action store
comparison-type pattern-rule
msg-type request
methods INVITE
match-value .*
new-value
header-rule
name storeTo
header-name to
action store
comparison-type pattern-rule
msg-type request
methods INVITE
match-value .*
new-value
header-rule
name generateVSA200
header-name P-Acme-VSA
action add
comparison-type case-sensitive
msg-type any
methods INVITE
match-value
new-value 200:+$storeFrom.$0
header-rule
name generateVSA220
header-name P-Acme-VSA
action add
comparison-type case-sensitive
msg-type any
methods INVITE
match-value
new-value 220:+$storeTo.$0
last-modified-by admin@console
last-modified-date 2017-12-09 09:10:40

2. In order to add the header to the CDRs added a manipulation string in the session-agent that sends the INVITE and added a manipulation string that back references to the HMR

manipulation-string $generateVSA200

3. Further in the account-config VSA 200 was put (for testing I put only 200 as this should include all the VSAs that you expect) and this will be populated as a field in the CDR.

Call is made from 1.w.w.w --1.x.x.x (SBC) || (SBC) 1.y.y.y --(1.z.z.z)

cdr-output-redundancy enabled
interim-stats-id-types
prevent-duplicate-attrs disabled
vsa-id-range 200
cdr-output-inclusive disabled

Before adding the VSA in account-config

1,"1.y.y.y",5060,"10-4782@1.w.w.w","sipp <sip:priyesh@1.w.w.w:5060>;tag=4782SIPpTag0010","sut <sip:service@1.x.x.x:5060>","01:46:39.072 EST Dec 11 2017","01:46:39.077 EST Dec 11 2017"
2,"1.y.y.y",5060,"10-4782@1.w.w.w","sipp <sip:priyesh@1.w.w.w:5060>;tag=4782SIPpTag0010","sut <sip:service@1.x.x.x:5060>",1,10,"01:46:39.072 EST Dec 11 2017","01:46:39.077 EST Dec 11 2017","01:46:49.085 EST Dec 11 2017",1

After adding VSA 200 in account-config

1,"1.y.y.y",5060,"10-4818@1.w.w.w","sipp <sip:priyesh@1.w.w.w:5060>;tag=4818SIPpTag0010","sut <sip:service@1.x.x.x:5060>","01:48:08.273 EST Dec 11 2017","01:48:08.277 EST Dec 11 2017","sipp <sip:Sip@1.w.w.w:5060>;tag=4818SIPpTag0010"
2,"1.y.y.y",5060,"10-4818@1.w.w.w","sipp <sip:priyesh@1.w.w.w:5060>;tag=4818SIPpTag0010","sut <sip:service@1.x.x.x:5060>",1,10,"01:48:08.273 EST Dec 11 2017","01:48:08.277 EST Dec 11 2017","01:48:18.285 EST Dec 11 2017",1,"sipp <sip:priyesh@1.w.w.w:5060>;tag=4818SIPpTag0010" <-------------------This is the header that gets added

After making these changes users problem got resolved and the required customer headers were populated in the CDRs.

Attachments

This solution has no attachment