Resource - PublicNode

About this Resource

Defines an PublicNode managed object.

REST API Methods for this Resource

Resource Schema

Configuration

Parameter Name Required Create Read-Only Data Type Description
HomePC Yes Yes Yes string This attribute is the point code of network element in the public node with which you will be exchanging ISUP or TCAP traffic.There should be a Routeset at MTP3 to this point code in the public NA. TL1Name: HOME_PC
Name No Yes No string This attribute gives a textual name to the public node. This name will be used as the pointer to this record when you are creating Trunk Records. TL1Name: NAME
StatusSummary No No Yes StatusEnum This attribute is the point code of network element in the public node with which you will be exchanging ISUP or TCAP traffic.There should be a Routeset at MTP3 to this point code in the public NA. TL1Name: STATUS_SUMMARY
PrivNetworkPC No Yes Yes string This attribute is the point code that private nodes will use to access the public node. In almost all cases the same Point Code value as in the public network should be re-used in this attribute. PCE allows you to use a different 'mirror' point code value in the private network, because your network may have a duplicate point code, however this is a rare situation. Using the same point code value in the public and private network spaces for these Public Nodes, makes reading of logs and message traces easier. There must be a corresponding VNode in the MTP3 private NA so that PCE can complete the registration to receive traffic for this destination. TL1Name: PRIV_NETWORK_PC
PrivNetwork2PC No No Yes string This attribute is the point code that private nodes in the second private network will use to access the public node. In almost all cases the same Point Code value as in the public network should be re-used in this attribute. PCE allows you to use a different 'mirror' point code value in the private network, because your network may have a duplicate point code, however this is a rare situation. Using the same point code value in the public and private network spaces for these Public Nodes, makes reading of logs and message traces easier. There must be a corresponding VNode in the MTP3 second private NA so that PCE can complete the registration to receive traffic for this destination. TL1Name: PRIV_NETWORK_PC_2
PrivateMTPStatus No No Yes string This attribute gives a status of the connections of this Public Node to the MTP3 in the first private network. If it is not connected properly the MTP3 running in any of your CPUs, the CPU having connection problems will be noted here. The most common sources of difficulty are IP networking problems, or forgetting to create the VNode at the MTP3 on the CPU(s) in question. The value 'OK' indicates that all connections are working properly. TL1Name: PRIV_MTP_STATUS
PrivateSCCPStatus No No Yes string This attribute gives a status of the connections of this Public Node to the SCCP in the first private network. If it is not connected properly the MTP3 running in any of your CPUs, the CPU having connection problems will be noted here. The most common sources of difficulty are IP networking problems, or forgetting to create the VNode at the MTP3 on the CPU(s) in question. The SCCP connection is required for TCAP level traffic. The value 'OK' indicates that all connections are working properly. TL1Name: PRIV_SCCP_STATUS
Private2MTPStatus No No Yes string This attribute gives a status of the connections of this Public Node to the MTP3 in the second private network. If it is not connected properly the MTP3 running in any of your CPUs, the CPU having connection problems will be noted here. The most common sources of difficulty are IP networking problems, or forgetting to create the VNode at the MTP3 on the CPU(s) in question. The value 'OK' indicates that all connections are working properly. TL1Name: PRIV_MTP_STATUS_2
Private2SCCPStatus No No Yes string This attribute gives a status of the connections of this Public Node to the SCCP in the second private network. If it is not connected properly the MTP3 running in any of your CPUs, the CPU having connection problems will be noted here. The most common sources of difficulty are IP networking problems, or forgetting to create the VNode at the MTP3 on the CPU(s) in question. The SCCP connection is required for TCAP level traffic. The value 'OK' indicates that all connections are working properly. TL1Name: PRIV_SCCP_STATUS_2

  • No labels