MERLIN LEGEND Communications System Release 6.1 | Issue 1 |
Network Reference | August 1998 |
|
|
4Security
Overview |
| Page |
Overview | 4 | |
|
|
|
Security planning and implementation, like other aspects of networking, require careful coordination among system managers. Local system business needs must be balanced with overall routing and security considerations. Network system managers must combine existing features and new networking features to safeguard against toll fraud. At the same time, security features must be fine- tuned to enable efficient calling across the network.
As discussed in earlier chapters, ARS and Remote Access features are used in combination to allow users to access PSTN trunks connected to other systems in the network. Such ARS calls are made normally, just as they are in non- networked systems. System programming of ARS tables, routes for tandem trunks, and remote access default
NOTE:
The ARS access code of a networked system should never be assigned to the
To enable calling among users on a network, certain calling restrictions are suspended when people on one system call extensions on another system, while others remain in effect. In addition, private network trunks and pools of private network trunks must be safeguarded and treated differently than PSTN trunks in order to avoid toll fraud through access to other networked systems. Table
“Facility Restriction Levels and Remote Access” on page 5 discusses security considerations that require more detailed information.