| Oracle® Communications EAGLE Database Administration - SS7 User's Guide Release 46.6 E93318 Revision 1 |
|
 Previous |
 Next |
| Oracle® Communications EAGLE Database Administration - SS7 User's Guide Release 46.6 E93318 Revision 1 |
|
|
Previous |
Next |
The Proxy Point Code feature allows the EAGLE to assume the point codes of other nodes in order to ease the migration of deploying an STP in a network with direct-connect links into other networks. For example, if a foreign network SS7 node is directly connected to an SS7 node in the home network, an EAGLE can be deployed so that the transition is transparent to the foreign node. The foreign node can still behave as if it is connected to the original node in the home network. EAGLE will provide routing connectivity in the home network to the foreign node and will allow the foreign node to connect to the home network.
In the examples in Figure 2-6, foreign network Node A connects to home network Node B. Normally, STP C would connect between them, requiring both Node A and Node B to use STP C as the APC. With this feature, Node A does not require any modifications, as STP C provides a proxy point code B. The configuration in this example assume that the self point code of the STP is C.
Figure 2-6 Context of the Proxy Point Code in the Network
A proxy point code can be any of these types of point codes:
A proxy point code must be a full point code and cannot be a cluster point code or a network routing point code. Private point codes and secondary point codes cannot be used as a proxy point code.
The following types of signaling links can be assigned to a linkset whose adjacent point code is a proxy point code:
Feature Provisioning Requirements
enable-ctrl-feat command and these part numbers shown in Table 2-3. Table 2-3 Proxy Point Code Quantities and Part Numbers
| Part Number | Proxy Point Code Quantity |
|---|---|
| 893-0187-01 | 10 |
| 893-0187-02 | 20 |
| 893-0187-03 | 30 |
| 893-0187-04 | 40 |
| 893-0187-05 | 50 |
| 893-0187-06 | 60 |
| 893-0187-07 | 70 |
| 893-0187-08 | 80 |
| 893-0187-09 | 90 |
| 893-0187-10 | 100 |
Once a proxy point code quantity has been enable, the quantity cannot be decreased.
A temporary feature access key cannot be used to enabled a proxy point code quantity.
Once a proxy point code quantity has been enabled, the proxy point codes are provisioned in the database with the ent-dstn command and the prx parameter. Other point codes can use a proxy point code that is already provisioned in the database. These point codes are provisioned with the ent-dstn command and the ppc parameter.
After the proxy point code has been provisioned in the database, a linkset using the proxy point code can be provisioned in the database. This linkset, referred to as a proxy linkset, is provisioned using the ent-ls command with the adjacent point code of the linkset, the lst=prx parameter, and the ppc parameter. The ppc parameter value is the proxy point code provisioned with the ent-dstn command.
A proxy linkset has the same characteristics as an A linkset.
A proxy point code can be assigned to a maximum of 10 linksets.
Secondary adjacent point codes are not supported on a proxy linkset.
A proxy point code cannot be used as the adjacent point code of an IPGWx linkset.
To provision the Proxy Point Code feature, perform these procedures.
enable-ctrl-feat command. Perform Changing the Proxy Point Code Quantity. Once a proxy point code quantity is enabled, the Proxy Point Code feature is enabled and turned on. The chg-ctrl-feat command cannot be used to turn the Proxy Point Code feature on.ent-dstn command with the prx and ppc parameters. Perform Adding a Destination Point Code. ent-ls command with the lst=prx and ppc parameters. Perform Adding an SS7 Linkset .