About the MIME Value Type
Introduced to modify the MIME attachment, SIP HMR supports a mime value for the type parameter in the element rules configuration. Like the status-code and reason-phrase values, you can only use the mime type value against a specific header—which in this case, is Content-Type.
When you set the element rule type to mime, you must also configure the parameter-name with a value. This step is a requirement because it sets the content-type the Oracle® Enterprise Session Border Controller manipulates in a specific part of the MIME attachment. You cannot leave this parameter blank; the Oracle® Enterprise Session Border Controller does not let you save the configuration if you do. When you use the store action on a multi-part MIME attachment that has different attachment types, the Oracle® Enterprise Session Border Controller stores the final instance of the content-type because it does not support storing multiple instances of element rule stored values.
In the event you do not know the specific content-type where the Oracle® Enterprise Session Border Controller will find the match-value, you can wildcard the parameter-name by setting with the asterisk (*) as a value. You cannot, however, set partial content-types (i.e., application/*). So configured, the Oracle® Enterprise Session Border Controller loops through the MIME attachment’s content types.
You can set the additional action types listed in this table with the described result:
| Action Type | Description |
|---|---|
| delete-element | Removes the matched mime-type from the body. If this is the last mime-type within in message body, the Oracle® Enterprise Session Border Controller removes the Content-Type header. |
| delete-header | Removes all body content and removes the Content-Type header. |
| replace | Performs a complete replacement of the matched mime-type with the new-value you configure. |
| find-replace-all | Searches the specifies mime-type’s contents and replaces all matching regular expressions with the new-value you configure |
| store | Stores the final instance of the content-type (if there are multi-part MIME attachments of various attachment types) |
| add | Not supported |
MIME manipulation does not support manipulating headers in the individual MIME attachments. For example, the Oracle® Enterprise Session Border Controller cannot modify the Content-Type given a portion of a message body like this one:
--boundary-1 Content-Type: application/sdp v=0 o=use1 53655765 2353687637 IN IP4 192.168.1.60 s=- c=IN IP4 192.168.1.60 t=0 0 m=audio 10000 RTP/AVP 8 a=rtpmap:8 PCMA/8000/1 a=sendrecv a=ptime:20 a=maxptime:200
