The MIB module is defined to configure the Announcements
feature on the Media Gateway Card.
The Media Gateway Card will have the capability to
play pre-recorded local announcements in switched
VoIP solutions only. Under the control of a call agent,
announcements can be played in either direction over
existing connections (calls) or towards the Time
Division Multiplexed (TDM) network on a TDM endpoint
that is terminated on the the Media Gateway Card.
A large number of different announcements may be cached
on the Media Gateway Card for immediate play out.
A persistent announcement store, called the Announcement
file server, will exist in the packet network and hold
all the announcements in the network. Announcements will
be downloaded on demand as announcement files from
the configured announcement store. Downloaded announcement
files will be stored on the Media Gateway Card as either
'permanent' or 'dynamic' announcement files. Permanent
files on the Media Gateway Card are exempt from being
refreshed, replaced, or removed without explicit
provisioning actions. Dynamic announcement files will
not persist across resets. Permanent announcement files
will be reloaded, if possible, following a reset. Dynamic
announcement files are automatically 'aged'. 'Aged'
files are re-fetched from the Announcement file server.
Dynamic Announcement files can be replaced on the
Media Gateway Card if the Announcement memory on the
card is full and additional Announcement files are to
be downloaded. The file(s) to be replaced will be
determined according to some Least Recently Used(LRU)
algorithm.
Announcements can be played over established connections
and unconnected TDM endpoints in any encoding supported
by the Media Gateway Card in its current configuration.
Announcement files must be encoded in G.729a to be
played on G.729ab connections or, if G.729ab has been
chosen as the preferred codec, unconnected endpoints.
The Announcement file server will reside on an IP network
reachable from the Media Gateway Card using TFTP.
The user will configure the Announcement file server
node name on the the Media Gateway Card.
The Announcement file server will have a 'main' file
directory for Announcements. If the Announcement prefix
path is configured to begin with a '/' then the
directory is absolute. If the prefix path is configured
to begin without a '/' then it will be relative to the
default TFTP server directory. If no prefix path is
configured then the Announcement 'main' directory and
the TFTP default directory will be the same. The user
must configure subdirectories within the main
Announcement directory for each encoding that
Announcements may be played in. These subdirectories must
be of the following names: 'g711u', 'g711a', 'g726_40k',
'g726_32k', 'g726_24k', 'g726_16k', 'g729_a',
'g7231_high_rate', 'g7231_a_high_rate', 'g7231_low_rate',
'g7231_a_low_rate'.
The Media Gateway Card maintains an Announcement cache in
resident memory. The cache is populated on demand with
dynamic files or provisioned with permanent files. That
is to say that when an Announcement is requested to be
played it will first be retrieved from the Announcement
file server and placed in the on-board Announcement cache.
Subsequent requests for the same Announcement will not
require retrieval of the Announcement file from the
Announcement file server. Note that an Announcement in
one encoding is a different file than the same
Announcement in a different encoding.
The 'Announcement aging' policy is provisionable for
dynamic files. Once a dynamic Announcement has 'aged'
in the on-board cache it will be 'refreshed' by being
retrieved again from the Announcement file server.
The age time determines the maximum time before an updated
Announcement file is automatically propagated to the card.
Shorter age times will result in more frequent file
server access. Changing the 'age' time does not affect
the age times of dynamic Announcement files currently
loaded. However, once these files are refreshed, they
will then use the new 'age' time.
Announcements may also be provisioned as 'permanent'.
A permanent Announcement will be fetched from the
Announcement file server and 'frozen' in the Media
Gateway Card Announcement cache. Permanent
Announcements will be excluded from aging (and being
automatically refreshed) and excluded from being
replaced if the Announcement cache becomes full.
Permanent Announcements can only be removed from the
cache explicitly by user through command line
interface or through a Network Manager. If the Media
Gateway Card is reset, permanent Announcements will be
re-fetched from the Announcement file server as soon
as the card becomes active. The Announcement encoding
must be specified when provisioning permanent
Announcements.
Parsed from file CISCO-WAN-ANNOUNCEMENT-MIB.mib
Module: CISCO-WAN-ANNOUNCEMENT-MIB
The MIB module is defined to configure the Announcements
feature on the Media Gateway Card.
The Media Gateway Card will have the capability to
play pre-recorded local announcements in switched
VoIP solutions only. Under the control of a call agent,
announcements can be played in either direction over
existing connections (calls) or towards the Time
Division Multiplexed (TDM) network on a TDM endpoint
that is terminated on the the Media Gateway Card.
A large number of different announcements may be cached
on the Media Gateway Card for immediate play out.
A persistent announcement store, called the Announcement
file server, will exist in the packet network and hold
all the announcements in the network. Announcements will
be downloaded on demand as announcement files from
the configured announcement store. Downloaded announcement
files will be stored on the Media Gateway Card as either
'permanent' or 'dynamic' announcement files. Permanent
files on the Media Gateway Card are exempt from being
refreshed, replaced, or removed without explicit
provisioning actions. Dynamic announcement files will
not persist across resets. Permanent announcement files
will be reloaded, if possible, following a reset. Dynamic
announcement files are automatically 'aged'. 'Aged'
files are re-fetched from the Announcement file server.
Dynamic Announcement files can be replaced on the
Media Gateway Card if the Announcement memory on the
card is full and additional Announcement files are to
be downloaded. The file(s) to be replaced will be
determined according to some Least Recently Used(LRU)
algorithm.
Announcements can be played over established connections
and unconnected TDM endpoints in any encoding supported
by the Media Gateway Card in its current configuration.
Announcement files must be encoded in G.729a to be
played on G.729ab connections or, if G.729ab has been
chosen as the preferred codec, unconnected endpoints.
The Announcement file server will reside on an IP network
reachable from the Media Gateway Card using TFTP.
The user will configure the Announcement file server
node name on the the Media Gateway Card.
The Announcement file server will have a 'main' file
directory for Announcements. If the Announcement prefix
path is configured to begin with a '/' then the
directory is absolute. If the prefix path is configured
to begin without a '/' then it will be relative to the
default TFTP server directory. If no prefix path is
configured then the Announcement 'main' directory and
the TFTP default directory will be the same. The user
must configure subdirectories within the main
Announcement directory for each encoding that
Announcements may be played in. These subdirectories must
be of the following names: 'g711u', 'g711a', 'g726_40k',
'g726_32k', 'g726_24k', 'g726_16k', 'g729_a',
'g7231_high_rate', 'g7231_a_high_rate', 'g7231_low_rate',
'g7231_a_low_rate'.
The Media Gateway Card maintains an Announcement cache in
resident memory. The cache is populated on demand with
dynamic files or provisioned with permanent files. That
is to say that when an Announcement is requested to be
played it will first be retrieved from the Announcement
file server and placed in the on-board Announcement cache.
Subsequent requests for the same Announcement will not
require retrieval of the Announcement file from the
Announcement file server. Note that an Announcement in
one encoding is a different file than the same
Announcement in a different encoding.
The 'Announcement aging' policy is provisionable for
dynamic files. Once a dynamic Announcement has 'aged'
in the on-board cache it will be 'refreshed' by being
retrieved again from the Announcement file server.
The age time determines the maximum time before an updated
Announcement file is automatically propagated to the card.
Shorter age times will result in more frequent file
server access. Changing the 'age' time does not affect
the age times of dynamic Announcement files currently
loaded. However, once these files are refreshed, they
will then use the new 'age' time.
Announcements may also be provisioned as 'permanent'.
A permanent Announcement will be fetched from the
Announcement file server and 'frozen' in the Media
Gateway Card Announcement cache. Permanent
Announcements will be excluded from aging (and being
automatically refreshed) and excluded from being
replaced if the Announcement cache becomes full.
Permanent Announcements can only be removed from the
cache explicitly by user through command line
interface or through a Network Manager. If the Media
Gateway Card is reset, permanent Announcements will be
re-fetched from the Announcement file server as soon
as the card becomes active. The Announcement encoding
must be specified when provisioning permanent
Announcements.
Parsed from file CISCO-WAN-ANNOUNCEMENT-MIB.my.txt
Company: None
Module: CISCO-WAN-ANNOUNCEMENT-MIB
The MIB module is defined to configure the Announcements
feature on the Media Gateway Card.
The Media Gateway Card will have the capability to
play pre-recorded local announcements in switched
VoIP solutions only. Under the control of a call agent,
announcements can be played in either direction over
existing connections (calls) or towards the Time
Division Multiplexed (TDM) network on a TDM endpoint
that is terminated on the the Media Gateway Card.
A large number of different announcements may be cached
on the Media Gateway Card for immediate play out.
A persistent announcement store, called the Announcement
file server, will exist in the packet network and hold
all the announcements in the network. Announcements will
be downloaded on demand as announcement files from
the configured announcement store. Downloaded announcement
files will be stored on the Media Gateway Card as either
'permanent' or 'dynamic' announcement files. Permanent
files on the Media Gateway Card are exempt from being
refreshed, replaced, or removed without explicit
provisioning actions. Dynamic announcement files will
not persist across resets. Permanent announcement files
will be reloaded, if possible, following a reset. Dynamic
announcement files are automatically 'aged'. 'Aged'
files are re-fetched from the Announcement file server.
Dynamic Announcement files can be replaced on the
Media Gateway Card if the Announcement memory on the
card is full and additional Announcement files are to
be downloaded. The file(s) to be replaced will be
determined according to some Least Recently Used(LRU)
algorithm.
Announcements can be played over established connections
and unconnected TDM endpoints in any encoding supported
by the Media Gateway Card in its current configuration.
Announcement files must be encoded in G.729a to be
played on G.729ab connections or, if G.729ab has been
chosen as the preferred codec, unconnected endpoints.
The Announcement file server will reside on an IP network
reachable from the Media Gateway Card using TFTP.
The user will configure the Announcement file server
node name on the the Media Gateway Card.
The Announcement file server will have a 'main' file
directory for Announcements. If the Announcement prefix
path is configured to begin with a '/' then the
directory is absolute. If the prefix path is configured
to begin without a '/' then it will be relative to the
default TFTP server directory. If no prefix path is
configured then the Announcement 'main' directory and
the TFTP default directory will be the same. The user
must configure subdirectories within the main
Announcement directory for each encoding that
Announcements may be played in. These subdirectories must
be of the following names: 'g711u', 'g711a', 'g726_40k',
'g726_32k', 'g726_24k', 'g726_16k', 'g729_a',
'g7231_high_rate', 'g7231_a_high_rate', 'g7231_low_rate',
'g7231_a_low_rate'.
The Media Gateway Card maintains an Announcement cache in
resident memory. The cache is populated on demand with
dynamic files or provisioned with permanent files. That
is to say that when an Announcement is requested to be
played it will first be retrieved from the Announcement
file server and placed in the on-board Announcement cache.
Subsequent requests for the same Announcement will not
require retrieval of the Announcement file from the
Announcement file server. Note that an Announcement in
one encoding is a different file than the same
Announcement in a different encoding.
The 'Announcement aging' policy is provisionable for
dynamic files. Once a dynamic Announcement has 'aged'
in the on-board cache it will be 'refreshed' by being
retrieved again from the Announcement file server.
The age time determines the maximum time before an updated
Announcement file is automatically propagated to the card.
Shorter age times will result in more frequent file
server access. Changing the 'age' time does not affect
the age times of dynamic Announcement files currently
loaded. However, once these files are refreshed, they
will then use the new 'age' time.
Announcements may also be provisioned as 'permanent'.
A permanent Announcement will be fetched from the
Announcement file server and 'frozen' in the Media
Gateway Card Announcement cache. Permanent
Announcements will be excluded from aging (and being
automatically refreshed) and excluded from being
replaced if the Announcement cache becomes full.
Permanent Announcements can only be removed from the
cache explicitly by user through command line
interface or through a Network Manager. If the Media
Gateway Card is reset, permanent Announcements will be
re-fetched from the Announcement file server as soon
as the card becomes active. The Announcement encoding
must be specified when provisioning permanent
Announcements.
ciscoWanAnnouncementMIB MODULE-IDENTITY LAST-UPDATED "200312220000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The MIB module is defined to configure the Announcements feature on the Media Gateway Card. The Media Gateway Card will have the capability to play pre-recorded local announcements in switched VoIP solutions only. Under the control of a call agent, announcements can be played in either direction over existing connections (calls) or towards the Time Division Multiplexed (TDM) network on a TDM endpoint that is terminated on the the Media Gateway Card. A large number of different announcements may be cached on the Media Gateway Card for immediate play out. A persistent announcement store, called the Announcement file server, will exist in the packet network and hold all the announcements in the network. Announcements will be downloaded on demand as announcement files from the configured announcement store. Downloaded announcement files will be stored on the Media Gateway Card as either 'permanent' or 'dynamic' announcement files. Permanent files on the Media Gateway Card are exempt from being refreshed, replaced, or removed without explicit provisioning actions. Dynamic announcement files will not persist across resets. Permanent announcement files will be reloaded, if possible, following a reset. Dynamic announcement files are automatically 'aged'. 'Aged' files are re-fetched from the Announcement file server. Dynamic Announcement files can be replaced on the Media Gateway Card if the Announcement memory on the card is full and additional Announcement files are to be downloaded. The file(s) to be replaced will be determined according to some Least Recently Used(LRU) algorithm. Announcements can be played over established connections and unconnected TDM endpoints in any encoding supported by the Media Gateway Card in its current configuration. Announcement files must be encoded in G.729a to be played on G.729ab connections or, if G.729ab has been chosen as the preferred codec, unconnected endpoints. The Announcement file server will reside on an IP network reachable from the Media Gateway Card using TFTP. The user will configure the Announcement file server node name on the the Media Gateway Card. The Announcement file server will have a 'main' file directory for Announcements. If the Announcement prefix path is configured to begin with a '/' then the directory is absolute. If the prefix path is configured to begin without a '/' then it will be relative to the default TFTP server directory. If no prefix path is configured then the Announcement 'main' directory and the TFTP default directory will be the same. The user must configure subdirectories within the main Announcement directory for each encoding that Announcements may be played in. These subdirectories must be of the following names: 'g711u', 'g711a', 'g726_40k', 'g726_32k', 'g726_24k', 'g726_16k', 'g729_a', 'g7231_high_rate', 'g7231_a_high_rate', 'g7231_low_rate', 'g7231_a_low_rate'. The Media Gateway Card maintains an Announcement cache in resident memory. The cache is populated on demand with dynamic files or provisioned with permanent files. That is to say that when an Announcement is requested to be played it will first be retrieved from the Announcement file server and placed in the on-board Announcement cache. Subsequent requests for the same Announcement will not require retrieval of the Announcement file from the Announcement file server. Note that an Announcement in one encoding is a different file than the same Announcement in a different encoding. The 'Announcement aging' policy is provisionable for dynamic files. Once a dynamic Announcement has 'aged' in the on-board cache it will be 'refreshed' by being retrieved again from the Announcement file server. The age time determines the maximum time before an updated Announcement file is automatically propagated to the card. Shorter age times will result in more frequent file server access. Changing the 'age' time does not affect the age times of dynamic Announcement files currently loaded. However, once these files are refreshed, they will then use the new 'age' time. Announcements may also be provisioned as 'permanent'. A permanent Announcement will be fetched from the Announcement file server and 'frozen' in the Media Gateway Card Announcement cache. Permanent Announcements will be excluded from aging (and being automatically refreshed) and excluded from being replaced if the Announcement cache becomes full. Permanent Announcements can only be removed from the cache explicitly by user through command line interface or through a Network Manager. If the Media Gateway Card is reset, permanent Announcements will be re-fetched from the Announcement file server as soon as the card becomes active. The Announcement encoding must be specified when provisioning permanent Announcements. " REVISION "200312220000Z" DESCRIPTION "Update with description changes from review." REVISION "200112260000Z" DESCRIPTION " Initial draft. Created new Media Gateway Card Announcement Group " ::= { ciscoWan 25 }
ciscoWanAnnouncementMIB OBJECT IDENTIFIER ::= { ciscoWan 25 }
Vendor: Stratacom
Module: CISCO-WAN-ANNOUNCEMENT-MIB
[Automatically extracted from oidview.com]
ciscoWanAnnouncementMIB MODULE-IDENTITY LAST-UPDATED "200312220000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The MIB module is defined to configure the Announcements feature on the Media Gateway Card. The Media Gateway Card will have the capability to play pre-recorded local announcements in switched VoIP solutions only. Under the control of a call agent, announcements can be played in either direction over existing connections (calls) or towards the Time Division Multiplexed (TDM) network on a TDM endpoint that is terminated on the the Media Gateway Card. A large number of different announcements may be cached on the Media Gateway Card for immediate play out. A persistent announcement store, called the Announcement file server, will exist in the packet network and hold all the announcements in the network. Announcements will be downloaded on demand as announcement files from the configured announcement store. Downloaded announcement files will be stored on the Media Gateway Card as either 'permanent' or 'dynamic' announcement files. Permanent files on the Media Gateway Card are exempt from being refreshed, replaced, or removed without explicit provisioning actions. Dynamic announcement files will not persist across resets. Permanent announcement files will be reloaded, if possible, following a reset. Dynamic announcement files are automatically 'aged'. 'Aged' files are re-fetched from the Announcement file server. Dynamic Announcement files can be replaced on the Media Gateway Card if the Announcement memory on the card is full and additional Announcement files are to be downloaded. The file(s) to be replaced will be determined according to some Least Recently Used(LRU) algorithm. Announcements can be played over established connections and unconnected TDM endpoints in any encoding supported by the Media Gateway Card in its current configuration. Announcement files must be encoded in G.729a to be played on G.729ab connections or, if G.729ab has been chosen as the preferred codec, unconnected endpoints. The Announcement file server will reside on an IP network reachable from the Media Gateway Card using TFTP. The user will configure the Announcement file server node name on the the Media Gateway Card. The Announcement file server will have a 'main' file directory for Announcements. If the Announcement prefix path is configured to begin with a '/' then the directory is absolute. If the prefix path is configured to begin without a '/' then it will be relative to the default TFTP server directory. If no prefix path is configured then the Announcement 'main' directory and the TFTP default directory will be the same. The user must configure subdirectories within the main Announcement directory for each encoding that Announcements may be played in. These subdirectories must be of the following names: 'g711u', 'g711a', 'g726_40k', 'g726_32k', 'g726_24k', 'g726_16k', 'g729_a', 'g7231_high_rate', 'g7231_a_high_rate', 'g7231_low_rate', 'g7231_a_low_rate'. The Media Gateway Card maintains an Announcement cache in resident memory. The cache is populated on demand with dynamic files or provisioned with permanent files. That is to say that when an Announcement is requested to be played it will first be retrieved from the Announcement file server and placed in the on-board Announcement cache. Subsequent requests for the same Announcement will not require retrieval of the Announcement file from the Announcement file server. Note that an Announcement in one encoding is a different file than the same Announcement in a different encoding. The 'Announcement aging' policy is provisionable for dynamic files. Once a dynamic Announcement has 'aged' in the on-board cache it will be 'refreshed' by being retrieved again from the Announcement file server. The age time determines the maximum time before an updated Announcement file is automatically propagated to the card. Shorter age times will result in more frequent file server access. Changing the 'age' time does not affect the age times of dynamic Announcement files currently loaded. However, once these files are refreshed, they will then use the new 'age' time. Announcements may also be provisioned as 'permanent'. A permanent Announcement will be fetched from the Announcement file server and 'frozen' in the Media Gateway Card Announcement cache. Permanent Announcements will be excluded from aging (and being automatically refreshed) and excluded from being replaced if the Announcement cache becomes full. Permanent Announcements can only be removed from the cache explicitly by user through command line interface or through a Network Manager. If the Media Gateway Card is reset, permanent Announcements will be re-fetched from the Announcement file server as soon as the card becomes active. The Announcement encoding must be specified when provisioning permanent Announcements. " REVISION "200312220000Z" DESCRIPTION "Update with description changes from review." REVISION "200112260000Z" DESCRIPTION " Initial draft. Created new Media Gateway Card Announcement Group " ::= { ciscoWan 25 }
ciscoWanAnnouncementMIB MODULE-IDENTITY LAST-UPDATED "200312220000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The MIB module is defined to configure the Announcements feature on the Media Gateway Card. The Media Gateway Card will have the capability to play pre-recorded local announcements in switched VoIP solutions only. Under the control of a call agent, announcements can be played in either direction over existing connections (calls) or towards the Time Division Multiplexed (TDM) network on a TDM endpoint that is terminated on the the Media Gateway Card. A large number of different announcements may be cached on the Media Gateway Card for immediate play out. A persistent announcement store, called the Announcement file server, will exist in the packet network and hold all the announcements in the network. Announcements will be downloaded on demand as announcement files from the configured announcement store. Downloaded announcement files will be stored on the Media Gateway Card as either 'permanent' or 'dynamic' announcement files. Permanent files on the Media Gateway Card are exempt from being refreshed, replaced, or removed without explicit provisioning actions. Dynamic announcement files will not persist across resets. Permanent announcement files will be reloaded, if possible, following a reset. Dynamic announcement files are automatically 'aged'. 'Aged' files are re-fetched from the Announcement file server. Dynamic Announcement files can be replaced on the Media Gateway Card if the Announcement memory on the card is full and additional Announcement files are to be downloaded. The file(s) to be replaced will be determined according to some Least Recently Used(LRU) algorithm. Announcements can be played over established connections and unconnected TDM endpoints in any encoding supported by the Media Gateway Card in its current configuration. Announcement files must be encoded in G.729a to be played on G.729ab connections or, if G.729ab has been chosen as the preferred codec, unconnected endpoints. The Announcement file server will reside on an IP network reachable from the Media Gateway Card using TFTP. The user will configure the Announcement file server node name on the the Media Gateway Card. The Announcement file server will have a 'main' file directory for Announcements. If the Announcement prefix path is configured to begin with a '/' then the directory is absolute. If the prefix path is configured to begin without a '/' then it will be relative to the default TFTP server directory. If no prefix path is configured then the Announcement 'main' directory and the TFTP default directory will be the same. The user must configure subdirectories within the main Announcement directory for each encoding that Announcements may be played in. These subdirectories must be of the following names: 'g711u', 'g711a', 'g726_40k', 'g726_32k', 'g726_24k', 'g726_16k', 'g729_a', 'g7231_high_rate', 'g7231_a_high_rate', 'g7231_low_rate', 'g7231_a_low_rate'. The Media Gateway Card maintains an Announcement cache in resident memory. The cache is populated on demand with dynamic files or provisioned with permanent files. That is to say that when an Announcement is requested to be played it will first be retrieved from the Announcement file server and placed in the on-board Announcement cache. Subsequent requests for the same Announcement will not require retrieval of the Announcement file from the Announcement file server. Note that an Announcement in one encoding is a different file than the same Announcement in a different encoding. The 'Announcement aging' policy is provisionable for dynamic files. Once a dynamic Announcement has 'aged' in the on-board cache it will be 'refreshed' by being retrieved again from the Announcement file server. The age time determines the maximum time before an updated Announcement file is automatically propagated to the card. Shorter age times will result in more frequent file server access. Changing the 'age' time does not affect the age times of dynamic Announcement files currently loaded. However, once these files are refreshed, they will then use the new 'age' time. Announcements may also be provisioned as 'permanent'. A permanent Announcement will be fetched from the Announcement file server and 'frozen' in the Media Gateway Card Announcement cache. Permanent Announcements will be excluded from aging (and being automatically refreshed) and excluded from being replaced if the Announcement cache becomes full. Permanent Announcements can only be removed from the cache explicitly by user through command line interface or through a Network Manager. If the Media Gateway Card is reset, permanent Announcements will be re-fetched from the Announcement file server as soon as the card becomes active. The Announcement encoding must be specified when provisioning permanent Announcements. " REVISION "200312220000Z" DESCRIPTION "Update with description changes from review." REVISION "200112260000Z" DESCRIPTION " Initial draft. Created new Media Gateway Card Announcement Group " ::= { ciscoWan 25 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.351.150.25.1 | cwAnnounceGrpMIBObjects | 1 | 22 | None |
| 1.3.6.1.4.1.351.150.25.2 | cwAnnounceNotificationPrefix | 1 | 1 | None |
| 1.3.6.1.4.1.351.150.25.3 | cwAnnounceMIBConformance | 2 | 5 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.351.150.1 | ciscoWanAtmConnMIB | 2 | 103 | This MIB is used for configuring/provisioning SPVCs on the ATM interfaces. This is used for ATM switch connection management. Term… |
| 1.3.6.1.4.1.351.150.2 | ciscoWanAtmConnStatMIB | 3 | 155 | This module contains ATM switch connection related real time statistical counter objects. |
| 1.3.6.1.4.1.351.150.3 | ciscoWANSonetMIB | 2 | 106 | The MIB module to describe SONET/SDH interfaces objects. This is an extension to the standard SONET MIB(RFC 2558). |
| 1.3.6.1.4.1.351.150.5 | ciscoWanTrapVarsMIB | 2 | 51 | This MIB module is for Supporting Varbinds used only in trap defintions. The NMS applications should not depend on the implementa… |
| 1.3.6.1.4.1.351.150.7 | ciscoMGX8800IfMappingMIB | 2 | 13 | This MIB module is used for getting the ifIndex values given physical location and/or logical information. The physical informati… |
| 1.3.6.1.4.1.351.150.9 | ciscoWanRpmConnExtMIB | 2 | 19 | This MIB together with the CISCO-WAN-ATM-CONN-MIB support provisioning of PVC endpoints and SPVCs on the MGX's Route Processor Mo… |
| 1.3.6.1.4.1.351.150.10 | ciscoWanMgMIB | 2 | 85 | The MIB module for managing Media Gateways (MGs). Terms used: MG: Media Gateway MGC: Media Gateway Controller MGCP: Media Gatewa… |
| 1.3.6.1.4.1.351.150.11 | ciscoWanSrcpMIB | 2 | 51 | The MIB module for managing SRCP(Simple Resource Coordination Protocol) implementations. SRCP is a resource coordination protocol… |
| 1.3.6.1.4.1.351.150.15 | ciscoWanFeederMIB | 2 | 25 | This MIB is used for configuring a port on an ATM switch module to be aware of feeder connection information. Terminology: AR - Aut… |
| 1.3.6.1.4.1.351.150.16 | ciscoWanAtmCosbMIB | 2 | 29 | The MIB to manage CoS(Class of Service) queue/buffer related parameters. One or more virtual interfaces may exist on a physical in… |
| 1.3.6.1.4.1.351.150.17 | ciscoWanAal2ProfilesMIB | 2 | 17 | The MIB module for configuring AAL2 profile elements. This table will be used in AAL2 switching and trunking applications. |
| 1.3.6.1.4.1.351.150.18 | ciscoWanPersistentXgcpEventsMIB | 2 | 12 | The MIB module for managing CA(Call Agent) events. |
| 1.3.6.1.4.1.351.150.19 | ciscoWanT38FaxRelayMIB | 3 | 28 | The MIB module for configuring T.38 fax relay protocol parameters. This MIB will be used in VoIP(Voice over IP) applications. |
| 1.3.6.1.4.1.351.150.20 | ciscoWanRtpConnMIB | 3 | 46 | The MIB module is defined for establishing connection between an endpoint and another endpoint on a remote VISM in the case of Vo… |
| 1.3.6.1.4.1.351.150.21 | ciscoWanCodecGenParmMIB | 3 | 14 | This MIB provides configuration of Jitter buffer mode on a call and initial jitter delay value per Codec based. Prior to this, th… |
| 1.3.6.1.4.1.351.150.22 | ciscoWanMgcRedunMIB | 3 | 31 | The MIB module for Media Gateways (MGs) to allow multiple Media Gateway Controllers (MGCs) to be configured and managed on the Ga… |
| 1.3.6.1.4.1.351.150.23 | ciscoWanLapdTrunkMIB | 3 | 18 | The MIB module is defined for establishing a Trunk to transport PRI (Primary Rate Interface) signaling information over a RUDP (R… |
| 1.3.6.1.4.1.351.150.24 | vismTonePlanGrpMIB | 3 | 83 | The MIB module is defined to configure the programmable Tone Plan feature on VISM. |
| 1.3.6.1.4.1.351.150.30 | ciscoWanSrmMIB | 1 | 6 | The MIB module for configuration of bulk distribution (de-multiplexing of traffic from higher-bandwidth to lower-bandwidth interf… |
| 1.3.6.1.4.1.351.150.31 | ciscoWanSrmBertMIB | 1 | 7 | The MIB Module for BERT(Bit Error Rate Testing) using Service Resource Module(SRM). This MIB module is used for BERT on FRSM, AUS… |
| 1.3.6.1.4.1.351.150.32 | ciscoWanBbifPortMIB | 1 | 8 | The MIB module for configuration of ATM logical ports in PXM1 Service module in MGX82xx series. This MIB contains information on … |
| 1.3.6.1.4.1.351.150.33 | ciscoWanBbifIlmiMIB | 1 | 6 | The MIB module for ILMI configuration and ILMI statistics for broad band interface ports in PXM1 service module. PXM1 service mod… |
| 1.3.6.1.4.1.351.150.35 | ciscoWanBbifAtmConnMIB | 1 | 7 | The MIB module to configure the ATM Connections on a broad band interface in PXM1 Service module. |
| 1.3.6.1.4.1.351.150.36 | ciscoWanBbifAtmConnStatMIB | 1 | 5 | This MIB module contains ATM Connection related real time statistical counter objects. The ATM connections are applicable to PXM1… |
| 1.3.6.1.4.1.351.150.38 | ciscoMgx82xxVirtualPortMIB | 1 | 8 | The MIB module for configuration ond reporting statistics of virtual ports in PXM1 Service module in MGX82xx series. |
| 1.3.6.1.4.1.351.150.39 | ciscoMgx82xxDsx3BertMIB | 1 | 5 | The MIB Module for BERT (Bit Error Rate Testing) on ds3 interfaces in some of the cards (Service Modules) in MGX products. This M… |
| 1.3.6.1.4.1.351.150.40 | ciscoWanCesPortMIB | 1 | 7 | The MIB module to configure the Circuit Emulation Service(CES) ports. |
| 1.3.6.1.4.1.351.150.41 | ciscoWanCesRsrcPartMIB | 1 | 5 | The mib module to configure the resource partition on Circuit Emulation Service(CES) ports. This is applicable for service module… |
| 1.3.6.1.4.1.351.150.42 | ciscoWanCesConnMIB | 1 | 7 | The MIB module to configure the Circuit Emulation connections in MGX82xx series products. Terminology: CES : Circui… |
| 1.3.6.1.4.1.351.150.43 | ciscoWanCesConnStatMIB | 1 | 6 | The MIB module to provide CES Connections statistics. This MIB is supported in Circuit Emulation Service Modules(CESM) in MGX82xx, … |
| 1.3.6.1.4.1.351.150.44 | ciscoWanFrPortMIB | 1 | 11 | The MIB module to create/configure frame relay ports/interfaces. This module contains tables related to frame relay port states a… |
| 1.3.6.1.4.1.351.150.45 | ciscoWanFrRsrcPartMIB | 1 | 5 | The MIB module to configure the resource partition on Frame Relay Ports. Terminlogies used: LCN : Logical Connection Number. DLCI … |
| 1.3.6.1.4.1.351.150.46 | ciscoWanFrSignalingMIB | 1 | 8 | The MIB module to configure LMI and CLLM on a frame relay ports. This mib module also contains objects to represent LMI and CLLM s… |
| 1.3.6.1.4.1.351.150.47 | ciscoWanFrConnMIB | 1 | 11 | The MIB module to configure the Frame Relay connection configuration. Terminologies Used: SIW - Frame-Relay-to ATM Service Interw… |
| 1.3.6.1.4.1.351.150.48 | ciscoWanFrConnStatMIB | 1 | 7 | The MIB module for frame relay connection statistics. Terminologies Used: SIW - Frame-Relay-to ATM Service Interworking FECN … |
| 1.3.6.1.4.1.351.150.49 | ciscoWanFrX21MIB | 1 | 8 | The MIB module to configure X.21/HSSI physical and logical interfaces. This MIB module also contains alarm configuration of X.21 i… |
| 1.3.6.1.4.1.351.150.58 | ciscoMgx82xxDsx1MIB | 1 | 9 | The MIB module to configure DS1/E1 interface objects. This mib also contains the alarm configuration of DS1/E1 interfaces. This m… |
| 1.3.6.1.4.1.351.150.59 | ciscoMgx82xxDsx3MIB | 1 | 19 | The MIB Module for DS3/E3 interface configuration , statistics and Alarm configuration. This MIB is supported in T3/E3 service mod… |
| 1.3.6.1.4.1.351.150.60 | ciscoMgx82xxRpmSubIfMIB | 1 | 5 | This MIB is used to provision backplane sub-interfaces on the MGX's Route Processor Module (RPM). This MIB is implemented on the… |
| 1.3.6.1.4.1.351.150.61 | ciscoMgx82xxRpmRsrcPartMIB | 1 | 5 | The MIB module to manage resource partition objects. A resource partition is configured on a RPM subinterface. An administrator c… |
| 1.3.6.1.4.1.351.150.62 | ciscoMgx82xxRpmConnMIB | 1 | 5 | The connection MIB module for RPM(Router Blade) service module in MGX8250/MGX8230 products. The 'channel' and 'connection' and 'c… |
| 1.3.6.1.4.1.351.150.63 | ciscoWanParMIB | 1 | 15 | The MIB module for configuring AutoRoute controller. The Portable AutoRoute(PAR) is a Controller providing routing capabilities i… |
| 1.3.6.1.4.1.351.150.67 | basisMIB | 0 | 0 | This MIB Contains OID subtrees used in some of the MIBs under 'stratacom' enterprise. |
| 1.3.6.1.4.1.351.150.69 | basisSerialMIB | 1 | 5 | The MIB module to configure serial ports in Processor Module and different Service Modules(cards) in MGX8850,MGX8250 and MGX8220 A… |
| 1.3.6.1.4.1.351.150.70 | ciscoMgx82xxEnvmonMIB | 1 | 6 | The MIB module to describe the status of the Environmental Monitoring devices in MGX82xx products. |
| 1.3.6.1.4.1.351.150.71 | ciscoMgx82xxAtmUniPortMIB | 1 | 6 | The MIB module containing objects related to user-side of the ATM UNI Port. The mib is applicable for MGX8250 and MGX8220 product… |
| 1.3.6.1.4.1.351.150.72 | ciscoMgx82xxPxmClockMIB | 1 | 8 | The MIB module to describe the clock configuration in Processor Switch Module(PXM) in MGX82xx product. Back cards supported for … |
| 1.3.6.1.4.1.351.150.73 | ciscoMgx82xxModuleRsrcPartMIB | 1 | 5 | The MIB module to configure the resource partition on service modules(cards) supported in MGX82xx and MGX88xx products. This MIB i… |
| 1.3.6.1.4.1.351.150.74 | ciscoMgx82xxCardFeatureMIB | 1 | 7 | The MIB module which describes the features supported in MGX82XX products. This MIB Module provides the features supported in Cont… |
| 1.3.6.1.4.1.351.150.79 | ciscoVismDsx1MIB | 1 | 18 | The MIB module to configure DS1/E1 interface objects in a Voice Interworking Service Module (VISM) module. This MIB is an extensi… |
| 1.3.6.1.4.1.351.150.80 | basisOnlineDiagMIB | 1 | 5 | This MIB contains information on the online diagnostics in MGX82xx(MGX8250, MGX8220, MGX8230 etc) products. |
| 1.3.6.1.4.1.351.150.81 | ciscoVismDsx0MIB | 1 | 12 | This MIB module contains ds0 configuration, Status and DS0 related information on a DS1 interface supported in VISM module. VISM i… |
| 1.3.6.1.4.1.351.150.82 | ciscoVismModuleMIB | 1 | 26 | This MIB module contains VISM Card specific attributes and call statistics information for VISM service module. |
| 1.3.6.1.4.1.351.150.86 | ciscoVismConnMIB | 1 | 8 | The MIB module to contains configuration and connection state information the VISM. For VoIP(Voice over IP) support, VISM needs o… |
| 1.3.6.1.4.1.351.150.87 | ciscoVismAtmTrunkMIB | 1 | 10 | The MIB module contain the Bearer and CID (Channel Identifier) connection information. |
| 1.3.6.1.4.1.351.150.88 | ciscoVismCasMIB | 1 | 7 | The MIB module contain the CAS backhaul feature in VISM |
| 1.3.6.1.4.1.351.150.89 | ciscoVismConnStatMIB | 1 | 11 | The MIB module contain VISM channel counters information. |
| 1.3.6.1.4.1.351.150.90 | ciscoVismSvcMIB | 1 | 8 | The MIB module containing SVC information for VISM service module. |
| 1.3.6.1.4.1.351.150.91 | ciscoVismHdlcMIB | 1 | 6 | The MIB module containing table for configurating and maintaining counters for the HDLC channel on VISM service module. |
| 1.3.6.1.4.1.351.150.92 | ciscoVismPortMIB | 1 | 5 | The MIB module containing Port information for VISM service module. |
| 1.3.6.1.4.1.351.150.93 | ciscoVismRsrcPartMIB | 1 | 5 | The MIB module containing Port Resource Partition information for VISM service module. |
| 1.3.6.1.4.1.351.150.94 | ciscoVismXgcpExtMIB | 1 | 8 | The MIB module contain the XGCP MIB feature in VISM |
| 1.3.6.1.4.1.351.150.95 | ciscoVismSessionMIB | 1 | 8 | The MIB module contain the RUDP session parameter. The relationship between session set, session group and RUDP session is that: … |
| 1.3.6.1.4.1.351.150.96 | ciscoVismCacMIB | 1 | 6 | The MIB module containing the CAC information for VISM service module. |
| 1.3.6.1.4.1.351.150.97 | ciscoVismCodecMIB | 1 | 8 | The MIB module contains tables for configurating and maintaining Codec on VISM service module. |