Defines an GTTTunnelGateway managed object.
Parameter Name | Required | Create | Read-Only | Data Type | Description |
---|---|---|---|---|---|
PublicPC | Yes | Yes | Yes | string | This attribute describes a point code that will be used for GTT processing of traffic that is NOT to be processed through PCE. ISUP traffic cannot be processed by GTT. The MTP3 on the public NA must have a corresponding VNode. If traffic goes from the public side to the private side via GTT, the Private PC will be used as the Originating Point Code in the private network. TL1Name: PUBLIC_PC |
Name | No | Yes | No | string | TL1Name: NAME |
PrivatePC | No | Yes | Yes | string | This attribute describes a point code that will be used for GTT processing of traffic that is NOT to be processed through PCE. ISUP traffic cannot be processed by GTT. The MTP3 on the private NA must have a corresponding VNode. If traffic goes from the private side to the public side via GTT, the Private PC will be used as the Originating Point Code. TL1Name: PRIVATE_PC |
StatusSummary | No | No | Yes | StatusEnum | This attribute describes a point code that will be used for GTT processing of traffic that is NOT to be processed through PCE. ISUP traffic cannot be processed by GTT. The MTP3 on the private NA must have a corresponding VNode. If traffic goes from the private side to the public side via GTT, the Private PC will be used as the Originating Point Code. TL1Name: STATUS_SUMMARY |
PublicMTPStatus | No | No | Yes | string | This attribute will indicate if any PCE process on any CPU are having difficulties with the connection to the MTP3. The most common cause of problems here is forgetting to create a corresponding VNode in the MTP3 public NA or IP networking errors. Obsolete as of 16.0.0. TL1Name: PUB_MTP_STATUS |
PublicSCCPStatus | No | No | Yes | string | This attribute will indicate if any PCE process on any CPU are having difficulties with the connection to the SCCP. The most common cause of problems here is forgetting to create a corresponding VNode in the MTP3 public NA or IP networking errors. TL1Name: PUB_SCCP_STATUS |
PrivateMTPStatus | No | No | Yes | string | This attribute will indicate if any PCE process on any CPU are having difficulties with the connection to the MTP3. The most common cause of problems here is forgetting to create a corresponding VNode in the MTP3 private NA or IP networking errors. Obsolete as of 16.0.0. TL1Name: PRIV_MTP_STATUS |
PrivateSCCPStatus | No | No | Yes | string | This attribute will indicate if any PCE process on any CPU are having difficulties with the connection to the SCCP. The most common cause of problems here is forgetting to create a corresponding VNode in the MTP3 private NA or IP networking errors. TL1Name: PRIV_SCCP_STATUS |
Private2MTPStatus | No | No | Yes | string | This attribute will indicate if any PCE process on any CPU are having difficulties with the connection to the MTP3. The most common cause of problems here is forgetting to create a corresponding VNode in the MTP3 second private NA or IP networking errors. Obsolete as of 16.0.0. TL1Name: PRIV_MTP_STATUS_2 |
Private2SCCPStatus | No | No | Yes | string | This attribute will indicate if any PCE process on any CPU are having difficulties with the connection to the SCCP. The most common cause of problems here is forgetting to create a corresponding VNode in the MTP3 second private NA or IP networking errors. TL1Name: PRIV_SCCP_STATUS_2 |