Example 9 Status-Line Manipulation
This section shows an HMR configuration set up for status-line manipulation.
Given that the object of this example is to drop the 183 Session Progress response when it does not have SDP, your SIP manipulation configuration needs to:
- Search for the 183 Session Progress response
- Determine if the identified 183 Session Progress responses contain SDP; the Oracle® Enterprise Session Border Controller searches the 183 Session Progress responses where the content length is zero
- If the 183 Session Progress response does not contain SDP, change its status code to 699
- Drop all 699 responses
sip-manipulation name manip description header-rule name IsContentLength0 header-name Content-Length action store comparison-type pattern-rule match-value 0 msg-type reply new-value methods header-rule name is183 header-name @status-line action store comparison-type pattern-rule match-value msg-type reply new-value methods element-rule name is183Code parameter-name type status-code action store match-val-type any comparison-type pattern-rule match-value 183 new-value header-rule name change183 header-name @status-line action manipulate comparison-type case-sensitive match-value msg-type reply new-value methods element-rule name make199 parameter-name type status-code action replace match-val-type any comparison-type pattern-rule match-value $IsContentLength0 & $is183.$is183Code new-value 199 sip-interface options dropResponse=699