Once a port's required link(s) to an Octel / PBX and
CallManager have become active, it then becomes available for
use placing calls between the two realms. This entry shows the
current state of any active call for a port, as described in
the DPA Administration Guide.
Parsed from file CALISTA-DPA-MIB.mib
Module: CALISTA-DPA-MIB
Once a port's required link(s) to an Octel / PBX and
CallManager have become active, it then becomes available for
use placing calls between the two realms. This entry shows the
current state of any active call for a port, as described in
the DPA Administration Guide.
Once a port's required link(s) to an Octel / PBX and
CallManager have become active, it then becomes available for
use placing calls between the two realms. This entry shows the
current state of any active call for a port, as described in
the DPA Administration Guide.
Parsed from file CALISTA-DPA-MIB.my.txt
Company: None
Module: CALISTA-DPA-MIB
Once a port's required link(s) to an Octel / PBX and
CallManager have become active, it then becomes available for
use placing calls between the two realms. This entry shows the
current state of any active call for a port, as described in
the DPA Administration Guide.
portCallState OBJECT-TYPE SYNTAX INTEGER { unknown(1), notApplicable(2), onHook(3), callIn(4), callOut(5), onCall(6), offHook(7), transfer(8), outCall(9), hangingUp(10) } ACCESS read-only STATUS mandatory DESCRIPTION "Once a port's required link(s) to an Octel / PBX and CallManager have become active, it then becomes available for use placing calls between the two realms. This entry shows the current state of any active call for a port, as described in the DPA Administration Guide." ::= { portEntry 5 }
portCallState OBJECT-TYPE SYNTAX INTEGER { unknown(1), notApplicable(2), onHook(3), callIn(4), callOut(5), onCall(6), offHook(7), transfer(8), outCall(9), hangingUp(10) } ACCESS read-only STATUS mandatory DESCRIPTION "Once a port's required link(s) to an Octel / PBX and CallManager have become active, it then becomes available for use placing calls between the two realms. This entry shows the current state of any active call for a port, as described in the DPA Administration Guide." ::= { portEntry 5 }
Vendor: Calista Ltd.
Module: CALISTA-DPA-MIB
[Automatically extracted from oidview.com]
portCallState OBJECT-TYPE SYNTAX INTEGER { unknown(1), notApplicable(2), onHook(3), callIn(4), callOut(5), onCall(6), offHook(7), transfer(8), outCall(9), hangingUp(10) } ACCESS read-only STATUS mandatory DESCRIPTION "Once a port's required link(s) to an Octel / PBX and CallManager have become active, it then becomes available for use placing calls between the two realms. This entry shows the current state of any active call for a port, as described in the DPA Administration Guide." ::= { portEntry 5 }
portCallState OBJECT-TYPE SYNTAX INTEGER { unknown(1), notApplicable(2), onHook(3), callIn(4), callOut(5), onCall(6), offHook(7), transfer(8), outCall(9), hangingUp(10) } ACCESS read-only STATUS mandatory DESCRIPTION "Once a port's required link(s) to an Octel / PBX and CallManager have become active, it then becomes available for use placing calls between the two realms. This entry shows the current state of any active call for a port, as described in the DPA Administration Guide." ::= { portEntry 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.7505.1.1.15.1.1 | portIndex | 0 | 0 | A unique value for each port. Its value ranges from 1 to the total number of ports. |
| 1.3.6.1.4.1.7505.1.1.15.1.2 | portType | 0 | 0 | How this port is currently being used: notInUse not currently in use (may become active later) octel connected to an Oct… |
| 1.3.6.1.4.1.7505.1.1.15.1.3 | portTelephonyLinkState | 0 | 0 | The state of the digital telephony link. This field only has meaning for physical ports connected to Octel voicemail systems or d… |
| 1.3.6.1.4.1.7505.1.1.15.1.4 | portCallManagerLinkState | 0 | 0 | The state of this port's connection to a Cisco CallManager, if such a connection exists. For ports connected to digital PBX syste… |
| 1.3.6.1.4.1.7505.1.1.15.1.6 | portDeviceName | 0 | 0 | The device name under which this port is registered with Cisco CallManager. |
| 1.3.6.1.4.1.7505.1.1.15.1.7 | portCodecInUse | 0 | 0 | If there is a call in progress on this port, this entry gives the codec in use, otherwise it will return none. |
| 1.3.6.1.4.1.7505.1.1.15.1.8 | portErrors | 0 | 0 | The number of centiseconds during which PBX protocol errors were detected for this port. It is normal for there to be some errors… |
| 1.3.6.1.4.1.7505.1.1.15.1.9 | portDacLevel | 0 | 0 | The DAC level for the port; this is related to the voltage level on the digital telephony port, and is only used in diagnosis of … |