Cisco Cisco Packet Data Gateway (PDG)
SGSN Changes in Release 17
SGSN Enhancements for 17.1 ▀
Release Change Reference, StarOS Release 17 ▄
485
New Behavior: The 'peer restart counter' is now updated correctly for the EGTPCPathFailClear trap when a new user
session is created after a path failure is detected for that peer. The peer restart counter value is displayed in the output of
the
session is created after a path failure is detected for that peer. The peer restart counter value is displayed in the output of
the
show snmp trap history
command.
CSCup71665 - Routing-context cannot be set to 0
Feature Changes
Routing Context Value for M3UA Messages
Previous Behavior: The SGSN does not support configuration of value “0” for the M3UA routing-context parameter.
New Behavior: The SGSN now supports “0” as a valid configuration value for M3UA routing-context parameter.
Customer Impact: The customer now has an option to configure “0” as a value for the M3UA routing-context
parameter, this is especially required when the HLR is serving SGSNs from other vendors in the network.
parameter, this is especially required when the HLR is serving SGSNs from other vendors in the network.
Command Changes
routing-context
The
routing-context
command in the SS7 Routing Domain Configuration Mode now allows configuration of
routing context ID values starting from “0”.
configure
ss7-routing-domain routing_domain_id variant variant_type
routing-context value
end
routing-context
The
routing-context
command in the Peer-Server Configuration Mode now allows configuration of routing context
ID values starting from “0”.
configure
ss7-routing-domain routing_domain_id variant variant_type
peer-server id server_id
routing-context value
end