| cMgcIndex |
.1.3.6.1.4.1.9.9.321.1.1.1.1.1 |
|
A unique index to identify each MGC which will
communicate with this media gateway.
|
| cMgcDomainName |
.1.3.6.1.4.1.9.9.321.1.1.1.1.2 |
|
This object contains the same name as the one in the
'cMgcDomainName object' of the associated entry in
'cMediaGwDomainNameConfigTable'.
|
| cMgcNumMgcGroups |
.1.3.6.1.4.1.9.9.321.1.1.1.1.3 |
|
This object is used to indicate number of MGC group with
which this MGC associated.
The value zero means this MGC is not associated
with any MGC Group.
If this value greater than zero, then the MGC entry
can not be deleted.
|
| cMgcNumIP |
.1.3.6.1.4.1.9.9.321.1.1.1.1.4 |
|
This object is used to indicate number of IP addresses are
associated with this MGC.
The value zero means there is no IP address associated with
this MGC.
The MGC can not be deleted if the value of this object is
non-zero and cMgcResolution is configured to
'internalOnly'.
|
| cMgcResolution |
.1.3.6.1.4.1.9.9.321.1.1.1.1.5 |
|
This object determines the kind of resolution to
be applied for this MGC.
'internalOnly' means that the gateway will not try to
resolve the IP address for this domain name using
external DNS name server.
'externalOnly' means the IP address for this domain name
will be resolved externally using DNS name server.
The request to change from 'internalOnly' to 'externalOnly'
will be rejected if the DNS name server is not available
for gateway.
The IP addresses related to the same MGC should have the
same cMgcResolution. The value of the MGC associated objects
in the cMgcIpConfigTable can not be modified by NMS if the
value of cMgcResolution for the MGC is 'externalOnly'.
The following are the behavior of changing the value of this
object.
[1] changing the value from 'externalOnly' to 'internalOnly'
1) precondition
MGC is not associated with any MGC group
(value of cMgcNumMgcGroups is zero).
2) behavior
If the value of this object is changed successfully,
all existing IP addresses in cMgcIpConfigTable that are
associated to the MGC will be removed automatically.
Note that MGW can't communicate with MGC if NMS does not
add static IP address into cMgcIpConfigTable for the MGC.
[2] changing the value from 'internalOnly' to 'externalOnly'
1) precondition
All MGC associated statically configured IP addresses
must be removed from cMgcIpConfigTable by NMS before
setting 'externalOnly' value to this object.
An inconsistentValue error is generated for setting
'externalOnly' value if the MGC associated IP addresses
are not removed.
2) behavior
After successfully setting 'externalOnly' value to this
object, the MGC domain name will be resolved by MGW
software using external DNS name server and the resulting
IP addresses will be added to cMgcIpConfigTable
automatically.
|
| cMgcIpIndex |
.1.3.6.1.4.1.9.9.321.1.1.2.1.1 |
|
A unique index to identify the address of a specific
MGC. The MGC is represented by cMgcIndex.
|
| cMgcIpAddressType |
.1.3.6.1.4.1.9.9.321.1.1.2.1.2 |
|
This object is the IP address type for cMgcIpAddress.
|
| cMgcIpAddress |
.1.3.6.1.4.1.9.9.321.1.1.2.1.3 |
|
This object represents the configured IP address.
After adding the entry, this object can not be modified.
|
| cMgcIpPreference |
.1.3.6.1.4.1.9.9.321.1.1.2.1.4 |
|
This object represents preference of the cMgcIpAddress
in the given MGC.
The lower the number the higher the preference. i.e. 1
will have higher preference than 2.
IF more than one IP have the same preference, gateway will
select them one by one.
|
| cMgcIpRowStatus |
.1.3.6.1.4.1.9.9.321.1.1.2.1.5 |
|
This object is used to create/modify/delete entry.
In order to delete an entry, following conditions need to be
met:
1. The MGC to which this IP address is being added,
should be existing.
2. The MGC's resolution (cMgcResolution) should be
'internal only'.
3. the mandatory object is cMgcIpAddress
After the IP address added to the MGC
the related 'cMgcNumIP' in MGC table will be incremented
by 1.
In order to delete an entry, following conditions need to be
met:
1. The MGC's resolution (cMgcResolution) should be
'internal only'.
2. The IP address should not be the only one in the MGC
while the MGC is associated with MGC group.
This means if the value of 'cMgcNumIP' is equal to 1
and the value of 'cMgcNumMgcGroups' is non-zero,
this IP address is the only one associated with the MGC
and it is possible that this IP address is also the
only one associated with MGC group. Therefore this
IP address can not be deleted.
After deleting the IP address from the MGC the related
'cMgcNumIP' in MGC table will be decremented by 1.
|
| cMgcGrpIndex |
.1.3.6.1.4.1.9.9.321.1.2.1.1.1 |
|
A unique index to identify a MGC group.
|
| cMgcGrpNumMgc |
.1.3.6.1.4.1.9.9.321.1.2.1.1.2 |
|
This object is used to indicate number of MGCs
to be associated with this MGC Group.
The value zero means there is no MGC in the MGC Group.
When the entry create, this value is set to 0.
Adding/deleting MGC to/from MGC group is through
cMgcGrpTable.
After a MGC added/deleted to/from this MGC group,
the value of this object will be incremented/decremented
by 1.
If the value of this object is zero, it is not allowed to
associate this MGC group with any profile or gateway.
|
| cMgcGrpAssociationInfo |
.1.3.6.1.4.1.9.9.321.1.2.1.1.3 |
|
This object indicates the association between MGC group
and profile/gateway with bitmap format.
It is 1:N mapping, e.g., each profile or gateway can only
have one MGC group, but one MGC group can be associated
with multi profile and gateway.
The possible bit positions used in the bitmap are listed as
follows:
Bit profile/gateway value
---------------------------------------------------------------
0 profile 1 0: the MGC group is not associated with it
1: the MGC group is associated with it
1 profile 2 0: the MGC group is not associated with it
1: the MGC group is associated with it
2 profile 3 0: the MGC group is not associated with it
1: the MGC group is associated with it
3 profile 4 0: the MGC group is not associated with it
1: the MGC group is associated with it
...
...
30 profile 31 0: the MGC group is not associated with it
1: the MGC group is associated with it
31 gateway 0: the MGC group is not associated with it
1: the MGC group is associated with it
The value zero means the MGC Group is not associated with
any profile or gateway.
|
| cMgcGrpNumProtocol |
.1.3.6.1.4.1.9.9.321.1.2.1.1.4 |
|
This object is used to indicate number of protocols
associated with this MGC group.
The value zero means there is no protocol associated with
this MGC group.
When the entry create, this object is set to 0.
The association between protocol and MGC group is configured
via cMgcGrpProtocolTable.
After a protocol is associated/de-associated with this
MGC group, this object will be incremented/decremented
by 1.
If this object is zero, it is not allowed to associate
the MGC group with any profile or gateway.
|
| cMgcGrpStateChangeNtfy |
.1.3.6.1.4.1.9.9.321.1.2.1.1.5 |
|
This object enables or disables sending gateway state
change notifications to call agent.
|
| cMgcGrpMgcPreference |
.1.3.6.1.4.1.9.9.321.1.2.2.1.1 |
|
The preference of the MGC in the MGC group.
The lower the number the higher the preference. i.e. 1 will
have higher preference than 2.
|
| cMgcGrpMgcUdpPort |
.1.3.6.1.4.1.9.9.321.1.2.2.1.2 |
|
The UDP port of the MGC in the MGC group.
The zero means there is no specific UDP port, the UDP port
in the protocol table will be used.
|
| cMgcGrpRowStatus |
.1.3.6.1.4.1.9.9.321.1.2.2.1.3 |
|
This object is used to create a new row or modify
or delete an existing row in this table.
In order to add an MGC to a MGC group, the following
conditions need to be met:
1. the MGC and the MGC group should be existing
2. at least one IP address is associated with the MGC if
the MGC is configured for internal resolution.
After the MGC added to the MGC group, the related
cMgcGrpNumMgc will be incremented by 1.
cMgcNumMgcGroups will be incremented by 1.
In order to delete an MGC from MGC group, the following
conditions need to be met:
The MGC is not the only MGC associated with the MGC
group if the MGC group is associated with gateway or
one or more profiles.
After the MGC added to the MGC group, the related
cMgcGrpNumMgc will be decremented by 1.
cMgcNumMgcGroups will be decremented by 1.
|
| cMgcGrpProtocolPreference |
.1.3.6.1.4.1.9.9.321.1.2.3.1.1 |
|
The preference of the Protocol in the MGC group.
The lower the number the higher the preference. i.e. 1 will
have higher preference than 2.
When gateway does not know which protocol is used by a call
agent the preference is used to make the decision.
But if gateway knows which protocol used by a call agent,
gateway will use that protocol (as long as the protocol is
added to the MGC group, irrespective of the preference) to
communicate with the call agent.
For example:
when gateway return a call agent message, gateway
will use the protocol which used by the call agent to
send the message.
|
| cMgcGrpProtocolRowStatus |
.1.3.6.1.4.1.9.9.321.1.2.3.1.2 |
|
This object is used to create a new row or modify
or delete an existing row in this table.
In order to add a protocol to MGC group, the following
condition need to be met:
Both the protocol and the MGC group should be existing
After the protocol added to the MGC group, the related
cMgcGrpNumProtocol will be incremented by 1.
In order to delete a protocol from MGC group, the following
condition need to be met:
The protocol to be deleted should not be the only one in the
MGC group when the MGC group is used by a gateway or a
profile.
This means if the value of cMgcGrpNumProtocol is equal to 1
and the value of cMgcGrpAssociationInfo is non-zero, this
protocol is the only one associated with the MGC group which
is still in use by gateways or some profiles. Therefore this
protocol can not be deleted.
After the protocol deleted from the MGC group, the related
cMgcGrpNumProtocol will be decremented by 1.
|
