Management Information Model. Because a Media Server is unaware of particular applications or services in the network, it is in general a plug and play component, with little initial network configuration or ongoing service provisioning required. Initial network configuration includes IP addresses, netmasks, gateway addresses, host names, etc. Since this information is set once and then left alone, it makes sense to use the Media Server's built-in management interface to do this configuration, and there is little urgency to support configuration of this set of data from an external EMS or OSS. Since Media Servers do not have configuration data for services, customer groups, and subscribers, service provisioning for a Media Server is composed only of media-related data such as audio and video files for playback (also known as announcements). Additionally, storing these media files inside the Media Server is optional as they can be placed on an external file server and retrieved by the Media Server as required. In general, files that change infrequently can be stored internal storage, while those that change frequently should be stored externally. File downloaded to the Media Server are persistent, i.e., remain there through power failures and restarts, until explicitly replaced or deleted by management action. At the simplest level of abstraction a Media Server has an internal directory structure for media files. The Media Server supports an automated management interface for downloading and deleting media files in internal storage. The download command takes as parameters an external, source URL and an internal, destination URL. The delete command takes as parameter an internal URL.
Management Information Model. The Edge node is a device that can be managed via a managment interface. There are a number of attributes that are required to be managed in order to allow the edge node to support an end to end VoIP service. This section defines a management information model which will used as the framework for defining all the objects and attributes that are required to be managed in the edge node. The management information model is described using the Unified Modeling Language (UML) syntax. The management information model is management protocol agnostic, since the exact management protocol to be used for managing the AG is outside the scope of this IA. Edge Node 1 N Interface 1 N Static Gate Each edge node has one or more interfaces which themselves may have one or more static gates. A static gate provides equivalent functionality to a dynamically allocated gate (i.e. one created by H.248) but is defined by management and is always available at the edge node until explicitly deleted by management. A static gate would typically be used to provide classification, packet marking and forwarding rules for signaling (such as SIP) that is received at the edge node. Static gates may provide NAT and PAT functions for signaling, may provide traffic descriptors that limit the maximum amount of signaling traffic that can be sent through a gate and may provide access control type functions to prevent barred customers from gaining access to the network. The following tables provide a textural description of all the classes contained in the management information model and the attributes associated with each of the classes. Edge-Node – This class represents the edge node entity.
Management Information Model. The Management Information Model will be specified in the individual SIP IAs.
Management Information Model. The AG is a device that is managed through the QAG interface and there are a number of attributes that are required to managed in the AG in order to provide a end to end VoIP service. User Port
