subVoiceConnectionTable

The Voice Subscriber Mapping Table. 
          
This table associates pairs of interface addresses
used by a voice subscriber.
          
The mapping table associates two enpoints (endPoint1 and
endPoint2) pairs.  Each row is indexed by the subscriber id, 
line group Id along with the voice connection index (see 
subNextVoiceConnectionIndex described in
in the subscriber table.
          
Each row contains the definitions of the two endpoints
which at this level, is defined as the protocol type for
the endpoint and an index into the associated protocol
specific table. Each associated protocol table, contained
in the appropriate protocol mib, contains the information
required to define the end point (i.e. vpi/vci/cid in the
case of AAL2). So, a row can be used to map a subscriber 
POTS line to a class 5 switch phone number.
          
For example, an AAL2 endpoint is represented by endpoint1
and has defined a type and the index for the AAL2
connection table defined in the AAL2 mib.
A GR-303 endpoint2 is represented by the endpoint2 type
of GR-303 and an index into the associated GR-303 mib. This
mib contains the GR-303 IG name and CRV value (see GR0303 MIB).
          
The admin status is used to enable/disable the connection. 
This is only used during the creation and deletion process of 
this entry along with the associated type table entries. 
          
The process is a two step approach where the manager creates
a voice connection entry with admin status down which causes
dummy protocol table entries to be added in the EP1 and EP2
(dummy being row entries with 0/NULL values)
protocol tables (since indexes and ep types are specified
on the row create), manager sets the appropriate 
protocol specific entries in the associated mibs, and then 
changes the admin status to active. 
          
All entries (the two protocol specific tables, and the
voice connection entry) are tightly coupled and therefore,
the deletion process is exactly the same. The manager 
deletes the voice connection entry and the handler 
automatically deletes the associated protocol table
entries. AdminStatus must be set to down before the
deletion can occur.
          
Because of this tight coupling, the EndPoint values (both
indexes and types) cannot be modified but must have the
row deleted and readded with the appropriate information.
          
The protocol specific tables are always INDEXED as the
index defined in either the endpoint1 or endpoint2 index fields.
          
This scheme allows flexibility in defining and expanding
the types of connections and allows for use of protocols 
of the same type to be defined at both endpoints.

MIB

ZHONE-GEN-SUBSCRIBER

OID

.1.3.6.1.4.1.5504.3.4.1.5

Type

table

Status

current

Parent

zhoneSubscriberRecords

Siblings

15

Children

1