MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 351 (stratacom). 110 (basis). 4 (basisLines). 7 (dsx0Vism). 1 (dsx0VismCnfTable). 1 (dsx0VismCnfEntry). 31 (ds0CasIncomingMgcpPackage)
OID : 1.3.6.1.4.1.351.110.4.7.1.1.31
TXT : iso. org. dod. internet. private. enterprises. stratacom. basis. basisLines. dsx0Vism. dsx0VismCnfTable. dsx0VismCnfEntry. ds0CasIncomingMgcpPackage
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.4.1.351.110.4.7.1.1.31
Module CISCO-VISM-DSX0-MIB (CISCO)
Nomds0CasIncomingMgcpPackage
Accesreadwrite
Statuscurrent
DescriptionThis object, in conjunction with the card level persistentXgcpEventsTable, controls how persistent CAS events (like seize, disconnect, etc) related to an incoming call observed on this DS0 are notified to the Media Gateway Controller (MGC). At the card level, the persistentXgcpEventsTable allows MGCP package-event combinations to be configured as persistent. For example, when L/hd is added to the persistentXgcpEventsTable, the hook-down event in line package will be notified to the MGC every time it is observed without the MGC requesting for that event. Since the same CAS event can map to different MGCP events under different packages (eg. the CAS event 'seize' can be 'sup' in 'MS' package and 'hd' in 'BL' package) and different lines could be running different packages at a given time, there needs to be a per-DS0 object indicating what package should be used while notifying CAS events observed on that DS0. This object, ds0CasIncomingMgcpPackage specifies the package that will be used while notifying CAS events observed on an incoming call on this DS0. This object can be set to a package name from xgcpCapabilityPackageTable whose xgcpCapabilityPackageEnable is true or the string 'basic' indicating that one of the basic packages in that table (G, T, L, H, R, D or M) to which the observed event belongs can be used. This object is used only if the protocol is MGCP. If the notification is in response to an RQNT, VISM uses the package (and event name) that the MGC used to request the event regardless what this object is set to. In the absence of an RQNT, the observed CAS event is encoded according to the package that this object specifies. A 'seize' observed on the CAS signaling channel on this DS0, for example is encoded as 'ms/sup' if this object is set to 'ms', 'bl/hd' if this object is set to 'bl' or as 'L/hd' if this object is set to 'basic'. If this package/event is present in persistentXgcpEventsTable, a notification is generated, otherwise this event is discarded. An attempt to set this object to a package name whose xgcpCapabilityPackageEnable is false in xgcpCapabilityPackageTable will fail. This object is used only if the ds0CasDirectionality is set to 'bidirectional' or 'incoming'.
SyntaxeOctetString (0...255)