Cisco Cisco ASR 5700
Call Control Profile Configuration Mode
▀ attach restrict
▄ Command Line Interface Reference, StarOS Release 17
1910
Usage
Once the IMSI of an incoming call is known and matched with a specific operator policy, according to the
filter definition of the
filter definition of the
mcc
command, then the associated call control profile is selected to determine how the
incoming call is handled.
By default, all attaches are allowed. If no access limitations are needed, then do not use the
By default, all attaches are allowed. If no access limitations are needed, then do not use the
attach
command.
Important:
Before using this command, ensure that the appropriate LAC information has been defined with the
location-area-list
command.
Use this command to restrict attaches for the call control profile.
Use this command to fine-tune the attach configuration specifying which calls/subscribers can attach and
which calls are restricted from attaching and what failure code is included in the Reject message.
Attachment restrictions can be based on any one or combination of the options, such as location area code or
access type. It is even possible to restrict all attaches.
The command can be repeated using different keyword values to further fine-tune the attachment
configuration.
Related Commands
Use this command to fine-tune the attach configuration specifying which calls/subscribers can attach and
which calls are restricted from attaching and what failure code is included in the Reject message.
Attachment restrictions can be based on any one or combination of the options, such as location area code or
access type. It is even possible to restrict all attaches.
The command can be repeated using different keyword values to further fine-tune the attachment
configuration.
Related Commands
Use the
attach access-type
command to define the type of access to restrict or allow. The
command attach restrict
access-type gprs all
has to be enabled , if the command attach
access-type gprs all failure-code < code >
is used to define a failure code. The failure
code is saved after a re-boot only when the command attach restrict access-type gprs all is enabled.
Use the
attach allow
command to re-enable restrictions after an
attach restrict
command has
been used.
Example
For calls under the purview of this call control profile, the following command restricts the attaches of all
subscribers using the GPRS access type.
subscribers using the GPRS access type.
attach restrict access-type gprs all
To change the attach restriction to only restrict attaches of GPRS subscribers from specified LACs included
in location area list #2 and include failure-code 45 as the reject cause. This configuration requires two CLI
commands:
in location area list #2 and include failure-code 45 as the reject cause. This configuration requires two CLI
commands:
attach restrict access-type gprs location-area-list instance 2
attach access-type gprs location-area-list instance 2 failure-code 45
In the case of a dual-access SGSN, it is possible to also add a second definition to restrict attaches of UMTS
subscribers within the LACs included in location area list #3.
subscribers within the LACs included in location area list #3.
attach restrict access-type UMTS location-area-list instance 3
Change the configuration to allow attaches for GPRS access for all previously restricted LACs - note that
GPRS attaches would still be limited:
GPRS attaches would still be limited:
no attach restrict access-type gprs all
Restrict (deny) all GPRS attach requests (coming from any location area) and assign a single failure code for
the reject messages. This is a two command process:
the reject messages. This is a two command process: