VISM-SESSION-MIB: View SNMP OID List / Download MIB

This table has entries for a collection of sessGrp(s) each providing connectivity to a different Media gateway Controller (MGC).

An entry for vismSessionSetTable.

This is the logical index of this table. Currently only set 1 is used and all the signaling channels are implicitly mapped to set 1.

This variable is used to allow add or delete a session set. createAndGo: Use this to add an entry in set table. vismSessionSetNum and vismSessionSetFaultTolerant are the mandatory parameters while adding a set. Currently only one set (set #1) can be created. The entry will become 'active' after creation. A set entry may be deleted by setting this object to 'destory'. Deletion of a set is not allowed if there is still group in this set. Enumeration: 'active': 1, 'destroy': 6, 'createAndGo': 4.

When an entry in sessionSet table is created and no group has been added to this set yet or group has been created in this set but no session has been added yet the set state is 'idle'. After a group has been created in this set and one session has been added to the group the set state becomes 'oos',i.e, out of service. After successfully open socket and the session has sent START message to MGC, the state of the set will be changed based on whether this set is fault tolerant(FT) or none fault tolerant(NFT). In NFT case the set state becomes 'activeIs'. In FT case, if one session from a group received an active message from MGC and no standby message received from a session in the other group, the state of the set will change to 'activeIs'. On the other hand, if at least one session from a group received standby message from MGC and no other session from the other group received active message then the set state is transferred to 'standbyIs'. The set becomes 'fullIs' when at least one session from one group receives active message and at least one session from the other group receives standby message. 'unknown' is a state other than the above states. Enumeration: 'fullIs': 5, 'activeIs': 3, 'oos': 2, 'unknown': 6, 'idle': 1, 'standbyIs': 4.

This counter keeps track the number of session groups that has been added to a session set.

This is the current active group number.

This counter keeps track of failed attempts to switch between session groups in this set.

This counter keeps track of successful attempts to switch between session groups in this set.

This object indicates whether the set configuration is fault tolerant or not. If the set is fault tolerant then there can be two groups in this set. If the set is non-fault tolerant then only one group can be added in this set. Once the entry is created this object cannot be modified.

This table has entries for a collection of sessions

An entry for vismSessionGrpTable.

Index for vismSessionGrpEntry table. Currently the range of 1 to 16 is used. One set can have upto two groups.

This is the session set number to which this session Group belongs. Once the entry is created this object cannot be modified.

This variable allows to add or delete an entry in this table. createAndGo: Use this to add an entry in this table. vismSessionGrpNum, vismSessionGrpSetNum and vismSessionGrpMgcName are required to add an entry. Before adding the session group, the session set should already be created. active: This value is returned once the session group is created destroy: Use this to delete a session group. Session group number is the only mandatory parameter to delete an entry. Enumeration: 'active': 1, 'destroy': 6, 'createAndGo': 4.

'idle': This is the initial state. 'oos': Out of service state. when a session group has been created the state of the session group becomes 'oos' or when all sessions belonging to this group are deleted, session group state becomes 'oos' 'is': In service state. After at least one session has been added to the group, socket has been successfully set up and the session has sent a START message to MGC the group state changes to 'is'. 'unknown': This is the state other than the above states. Enumeration: 'unknown': 4, 'idle': 1, 'is': 3, 'oos': 2.

This object indicates the current session that is open to communication with MGC. There is only one active session per session group.

This object keeps track the total number of sessions that have been added to this group.

This counter keeps track of failed attempts to switch between sessions in this group.

This counter keeps track of successful attempts to switch between sessions in this group.

This denotes the name of the media gateway controller. This corresponds to a domain name under which the MGC could also be registered in a DNS. Once this entry becomes active, this value may not be modified.

This table has entries of sessions, which are the connection between MGC and a gateway (VISM). A session is identified by a local IP address, port, remote IP address and remote port. The combination of these four numbers has to be unique to identify one session. This table also maintains the configuration for every session.

An entry for vismSessionCnfEntry.

This is the index of vismRudpSessionCnfEntry table. Currently the range of 1 to 64 is used. One group can have maximum four sessions.

This indicates the session group that this session belongs to. Currently the range of 1 to 16 is used. Once the entry is created, it cannot be modified.

This variable allows the user to add or delete the entry for this table. createAndGo: Use this to add a Rudp session in this table. Rudp session number, session group number, priority, local port and remote port are required while creating an entry for PRI Backhaul. On the other hand Rudp session number, local port, remote port, remote VISM IP and rudp session type are required for Lapd trunking. active: This value is returned, once the row is created. destroy: Use this to delete an RUDP session from this table. Only RUDP session number is needed for deleting. The last session shall not be deleted if there are still active LAPD entries. Enumeration: 'active': 1, 'destroy': 6, 'createAndGo': 4.

This object is used when creating a Rudp session. Once a session has been added it can not be modified. When a session fails it indicates which session the session manager should try to bring active. A lower number means higher priority.

'oos': Out of service state. This is the initial state when create a RUDP session. 'is': In service state. When a channel has been created between gateway (VISM) and MGC and VISM has sent Start message the state of the session changes to 'is'. If the communication is lost between VISM and the MGC, the state of this session becomes 'oos'. 'unknown': This is the state other than the above states. Enumeration: 'unknown': 3, 'is': 2, 'oos': 1.

This object indicates which session has got active message from MGC. The session manager will always try to bring the first added session to active. If the current active session fails the state of this session is changed to 'oos' and the session manager will try to bring the 'primary-is' session with highest priority among the rest of sessions in this group to active.

The IP address of gateway (VISM).

The port number of gateway (VISM) for this session. It can be modified after creation. This port number should be unique across other sessions and XGCP/SRCP.

This is the IP address of the media gateway controller. It is resolved by using vismSessionGrpMgcName in vismSessionGrpTable.

The port number of MGC for this session. It can be modified after creation. This port number should be unique across other sessions and XGCP/SRCP.

This object is the maximum number of segments that should be sent without getting an acknowledgment, i.e. the max size of the receive window in segments. This is used for flow control. This object can be modified after a session is created.

Maximum number of attempts to synchronize with other side (MGC). This object can be modified after a session is created.

The maximum number of octets that can be received by the peer sending the SYN segment. This object can be modified after a session is created.

The maximum number of consecutive auto reset that will be performed before a connection is reset. A value 0 indicates that an auto reset will not be attempted, the connection will be reset immediately if an auto reset condition occurs. This object can be modified after a session is created.

The timeout value for retransmission of unacknowledged packets in milliseconds. This is a negotiable parameter, MGC and VISM must agree on the same value for this parameter. This object can be modified after a session is created.

The maximum number of times consecutive retransmission will be attempted before the connection is considered broken. A value 0 indicates retransmission should be attempted forever. This is a negotiable parameter, both MGC and VISM must agree on the value for this parameter. This object can be modified after a session is created.

This object indicates the maximum number of acknowledgments that will be accumulated before sending an acknowledgment if another segment is not sent. A value of 0 indicates an acknowledgment segment will be sent immediately when a data, null, or reset segment is received. Negotiable parameter. This object can be modified after a session is created.

This object is the timeout value for sending an acknowledgment segment if another segment is not sent. This value is specified in milliseconds. This parameter should be smaller than rudpRetransTmout. Negotiable parameter. This object can be modified after a session is created.

This object is the maximum number of out of sequence packets that will be accumulated before an EACK segment is sent. The EACK segment is used to acknowledge segments received out of sequence. A value of 0 indicates a EACK will be sent immediately if an out of order segment is received. Negotiable parameter. This object can be modified after a session is created.

This object is the number of milliseconds of idle time before sending a null segment. A value of 0 disables null segments. Negotiable parameter. This object can be modified after a session is created.

This object indicates the number of milliseconds to wait for transfer state before an auto reset occurs. 0 indicates the connection will be auto-reset immediately and would not be used with redundant links. This object can be modified after a session is created.

This object indicates if the session is configured for Trunking or PRI Backhaul. By default the object is set to 'backhaul' and it needs to set to lapdTrunking if Lapd trunking needs to be done. Enumeration: 'lapdTrunking': 2, 'backhaul': 1.

This is the IP address of the remote VISM. This will be used only for Lapd Trunking applications and the vismRudpSessionType must be set to Lapd trunking.

This table keeps track of state and connection-specific counts. It is per connection based.

An entry for vismSessionStatEntry.

This is the index of vismRudpSessionStatEntry table. Currently the range of 1 to 64 is used. It is the same as the index of vismRudpSessionCnfEntry table.

Auto reset is also known as soft reset. VISM (gateway) initiates an auto reset when it detects that a connection has failed. This keeps track of the number of auto resets initiated by VISM.

This is the counter for the number of auto resets initiated by MGC and received by VISM.

This object indicates number of packets received in sequence.

Number of packets received out of sequence.

This is the number of packets sent by VISM. Including SYN message.

This is the number of packets received by VISM. Including active message.

This object indicates the number of bytes sent to MGC.

This object keeps track of the number of bytes received from MGC.

This object is the number of data packets sent to MGC.

This object is the number of data packets received from MGC.

This is the number of packets discarded.

This is the number of packets retransmitted.