RFC 4240:Basic Network Media Services with SIP
RFC-Ref

network


Click on the red underlined text to get to the source

... In SIP-based media networks (RFC 3261prop [10]), there is a need to ...
... 3261prop [10]), there is a need to provide basic network media services. Such services include playing ...
... Multifunction media servers provide network media services to clients ...


... A network announcement is the delivery of a multimedia resource, such as a prompt file, to a terminal ...
... SIP dialog. There are two types of network announcements. The differentiating characteristic between the two types is whether the network fully ...
... There are two types of network announcements. The differentiating characteristic between the two types is whether the network fully sets up the SIP dialog before playing the announcement. The analog ...
... sets up the SIP dialog before playing the announcement. The analog in the Public Switched Telephone Network (PSTN) is whether answer supervision is supplied (i.e., does the announcement server answer ...


... with the namespace for an organization. For example, let us take the case where a network offers services for "Ann Charles". She likes to use the name "annc", and thus she would like to use ...
... may "leak out" into the SIP routing network. The most important thing to note about this convention is that the ...
... left-hand side of the request URI is opaque to the network. The only network elements that need to know about the convention are the Media Server ...
... opaque to the network. The only network elements that need to know about the convention are the Media Server and client. Even proxies ...
... service names, rather than fixed names. While this can work in a closed network, where the Application Servers and Media Servers are ...


... Exposing network services with well-known addresses may not be ...
... confidentiality of their user's data, as appropriate. Untrusted network elements could use the convention described here for providing information services. Many extant billing arrangements ...


... We would like to thank Kevin Summers and Ravindra Kabre of Sonus Networks for their constructive comments, as well as Jonathan Rosenberg of Dynamicsoft and Tim Melanchuk of Convedia for their encouragement. In addition, the discussion ...


... Shepler, S., Callaghan, B., Robinson, D., Thurlow, R., Beame, C., Eisler, M., and D. Noveck, "Network File System (NFS) version 4 Protocol", RFC 3530prop ...



Google
Web
RFC-Ref