Cisco Cisco ASR 5000
SGSN Service Configuration Procedures
▀ Configuring the Peer SGSN Interface Type (S4 Only, Optional)
▄ SGSN Administration Guide, StarOS Release 18
Configuring the Peer SGSN Interface Type (S4 Only, Optional)
Operators can specify the type of interface the S4-SGSN will use to communicate with the peer SGSN in a call control
profile.
profile.
Use the following procedure to configure the peer SGSN interface type:
Step 1
Access the Call Control Profile configuration for the peer SGSN.
Step 2
Configure the interface type to be used for communication between the S4-SGSN and the peer SGSN. s16 must be
specified if the peer SGSN is an S4-SGSN.
specified if the peer SGSN is an S4-SGSN.
Example Configuration
config
call-control-profile <cc_profile_name>
sgsn-address { rac <rac value> lac <lac value> | rnc_id rnc_id } prefer { local |
fallback-for-dns } address ipv4 <ipv4 address> interface { gn | s16 }
fallback-for-dns } address ipv4 <ipv4 address> interface { gn | s16 }
end
Notes:
The
rnc_id
parameter can be used instead of the
rac
and
lac
values if operators wish to configure the target
RNC ID that maps to the address of the peer SGSN via the S16 interface. The RNC ID is used by the S4-SGSN
for inter-SGSN SRNS relocation. Configuration of the
for inter-SGSN SRNS relocation. Configuration of the
rnc_id
is optional, and valid only if SRNS relocation
first has been configured in Call Control Profile Configuration Mode using the
srns-inter
and/or
srns-
intra
commands.
The fallback-for-dns option is under development for future use, and is not currently supported on the S4-
SGSN.
NRI-based validation is not supported on the S4-SGSN.