When will Oracle fix the "local-response-map" configuration issue ?

There is a configuration issue:

There are two session-router configuration elements:

• local-response-map - single general rule that maps local response codes. For example, if you want SBC to generate code 444 instead of 503 in cases when next-hop is out of service, then you can do it here
• sip-response-map - multiple configuration element. A rule that maps one response code to another on egress. For example if you want SBC to send some code 444 instead of generated 503 to some session-agent, then you can configure this conversion here

sbc2(session-router)# local-response-map
sbc2(local-response-map)#
sbc2(local-response-map)# exit
sbc2(session-router)# sip-response-map
sbc2(response-map)#

In session-agent configuration there is parameter "local-response-map" with <pattern> value. You can set here the name of the configured "sip-response-map" element and not real "local-response-map", which is actually nameless. I wonder if Oracle plans to fix this issue.