network or, in the case of an incomplete analysis, the MSC in which the call will be further analysed. These can be letters, digits or a combination of both. To make troubleshooting and network maintenance easier it is recommended that a more descriptive name for destinations be used. It is therefore an operator's responsibility to select the most suitable scheme of naming destinations in the network. The network planner should make a study of the existing naming scheme and make recommendations to enhance or initiate one where such a scheme does not exist. Naming of Subdestinations The most informative way of naming subdestinations used for actual routing of calls is by naming them according to the circuit group they are using. Please note that in creating a route in newer MSC SW builds, subdestination and destination names not required, but the system automatically allocates numbers as names of the subdestination and destination and this complicates analysis of routing. This should therefore be avoided to ensure ease of network maintenance. Naming of Signalling Points and Point Codes A signalling point is identified by a signalling point name and a signalling point code. The signalling point name contains one to five ASCII characters that uniquely identify a signalling point. The name should be descriptive of the signalling point, preferably enabling easy identification with the MSC name. The signalling point naming should be consistent within the network. Signalling point codes and a signalling network uniquely identify a signalling point at the MTP level. Some signalling point codes are issued to the operator by the telecommunication authority, while in other cases this may be decided by each operator individually. It is the responsibility of the planning engineer to understand the signalling networks in use and the point codes. The purpose here is to understand the signalling network better and identify how it is intended to work. Introduction to the PS Core Network Border Gateway Other PLMN Firewall External