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

application server


Click on the red underlined text to get to the source

... The scenarios below assume there is a SIP Proxy, application server, or media gateway controller between the caller ...


... URI convention tells the media server that the application server is requesting it to act as a Focus. The conf-id value identifies the particular focus instance. ...
... there is no conf-id present. However, such an operation may have other operational issues, such as permissions and billing. Thus an application server or proxy is a better place to do such an operation. Moreover, such action would make the media server ...
... media server SHOULD authenticate the application server or proxy. At a minimum, the media server MUST ...
... conference-framework [22] describes additional parameters and behaviors of the Application Server. For example, the first INVITE from P1 to the Application Server ...
... Application Server. For example, the first INVITE from P1 to the Application Server would include the ";isfocus" parameter; the Application Server ...
... Application Server would include the ";isfocus" parameter; the Application Server would act as a Conference Factory; and so on. However, none of that protocol machinery has an impact on the operation of the Application Server ...
... Application Server would act as a Conference Factory; and so on. However, none of that protocol machinery has an impact on the operation of the Application Server to Media Server interface, ...
... protocol document. P1 P2 P3 Application Server Media Server | | | | | ...
... Using the terminology of conference-framework [22], the Application Server is the Conference Factory, and the Media Server is the Conference Focus. ...
... call flow does not show any 100 TRYING messages that would typically flow from the Application Server to the UACs; nor does it show the ACKs ...
... nor does it show the ACKs from the UACs to the Application Server or from the Application Server to the Media Server ...
... UACs to the Application Server or from the Application Server to the Media Server. ...
... UAC, by the UAC sending a BYE, or under the supervision of the Application Server, by the Application Server issuing a BYE. In either case, the Application Server ...
... UAC sending a BYE, or under the supervision of the Application Server, by the Application Server issuing a BYE. In either case, the Application Server will either issue a BYE on behalf of the UAC ...
... Application Server, by the Application Server issuing a BYE. In either case, the Application Server will either issue a BYE on behalf of the UAC or issue it directly to the Media Server ...
... It is left as a trivial exercise to the reader for how the Application Server can mute legs, create side conferences, and so forth. ...
... forth. Note that the Application Server is a server to the participants (UACs). However, the Application Server ...
... Application Server is a server to the participants (UACs). However, the Application Server is a client for mixing services ...


... service names, rather than fixed names. While this can work in a closed network, where the Application Servers and Media Servers are in the same administrative domain ...



Google
Web
RFC-Ref