Example 4 Storing and Using URI Parameters
For this manipulation rule, the Oracle® Enterprise Session Border Controller stores the value of the URI parameter tag from the From header. It also creates a new header FromTag with the header value from the stored information resulting from the first rule.
This is a sample of the configuration:
sip-manipulation name storeElemParam header-rule name Frohmr header-name From action store comparison-type case-sensitive match-value msg-type request new-value methods INVITE element-rule name elementRule parameter-name tag type uri-param action store match-val-type any comparison-type case-sensitive match-value new-value header-rule name newHeader header-name FromTag action add comparison-type pattern-rule match-value $FromHR.$elementRule msg-type any new-value $FromHR.$elementRule.$0 methods
This is a sample of the result:
Request-Line: INVITE sip:service@192.168.200.60:5060;tgid=123 SIP/2.0 Message Header Via: SIP/2.0/UDP 192.168.200.61:5060;branch=z9hG4bK4oda2e2050ih7acgh6c1.1 From: sipp <sip:sipp@192.168.1.60:5060>;tag=SDf1re601-1 To: sut <sip:service@192.168.1.61:5060> Call-ID: SDf1re601-f85059e74e1b443499587dd2dee504c2-06a3gu0 CSeq: 1 INVITE Contact: <sip:sipp@192.168.200.61:5060;transport=udp> Goodbye: Remove Me Custom: This is my custom header Display: sipp <sip:user@192.168.1.60:5060;up=abc>;hp=123 Params: sipp <sip:sipp1@192.168.1.60:5060> Params: sipp <sip:sipp2@192.168.1.60:5060> Edit: disp <sip:user@192.168.1.60:5060> Max-Forwards: 69 Subject: Performance Test Content-Type: application/sdp Content-Length: 140 FromTag: 1