There are scenarios of outbound calls in which far-end systems put calls on hold as follows: generate re-Invite, mark the stream with the "a=sendonly" attribute and play the music on hold. The far-end systems wish to only send media on the stream.RC system replies 200 OK and marks the stream with the "a=recvonly". RC system confirms the offer to only receive media from the far-end system.But in some scenarios, RC system does not connect the stream received from the far end to the calling subscriber (RC client making outbound call). Instead, RC system plays client's hold music, specified in settings in Service Web.This creates confusion with users that experience this behavior. In a recent example, a user had a custom prompt recorded specifically for their business which was configured as their extension's hold music within Screening, Greeting and Hold Music. After placing an outbound call, they heard their own custom prompt played back rather than the far-end's hold music while they were waiting to connect with the far-end which created confusion. They would like to listen to music on hold played by the called system rather than their own hold music to eliminate any confusion.Additionally, in some cases, the messages played by the far-end system may contain meaningful information for the calling clients.This was originally raised via JIRA: CNV-23334