@misc{rfc7088,
    series =    {Request for Comments},
    number =    7088,
    howpublished =  {RFC 7088},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC7088},
    url =       {https://www.rfc-editor.org/info/rfc7088},
    author =    {Dale R. Worley},
    title =     {{Session Initiation Protocol Service Example -- Music on Hold}},
    pagetotal = 36,
    year =      2014,
    month =     feb,
    abstract =  {"Music on hold" is one of the features of telephone systems that is most desired by buyers of business telephone systems. Music on hold means that when one party to a call has the call "on hold", that party's telephone provides an audio stream (often music) to be heard by the other party. Architectural features of SIP make it difficult to implement music on hold in a way that is fully standards-compliant. The implementation of music on hold described in this document is fully effective, is standards-compliant, and has a number of advantages over the methods previously documented. In particular, it is less likely to produce peculiar user interface effects and more likely to work in systems that perform authentication than the music-on-hold method described in Section 2.3 of RFC 5359.},
}