Cisco Cisco Packet Data Gateway (PDG) Folheto
HSS Peer Service Configuration Mode Commands
▀ zone-code-format
▄ Cisco ASR 5x00 Command Line Interface Reference
6186
zone-code-format
Configures how the MME must interpret the received zone-code values from the HSS.
Product
MME
Privilege
Administrator
Mode
Exec > Global Configuration > Context Configuration > HSS Peer Service Configuration
configure > context context_name > hss-peer-service service_name
Entering the above command sequence results in the following prompt:
[context_name]host_name(config-hss-peer-service)#
Syntax
zone-code-format { ascii-string }
[ default ] zone-code-format
default
Returns the command to the default setting, where the MME interprets the zone-code as an octet string.
ascii-string
Configures the MME to interpret the zone-code as an ascii string. This option is provided to maintain
backward compatibility.
When configured as ascii-string, the MME interprets the received zone-code as an ASCII string (coded in
hexadecimal representation) and converts it byte by byte to an integer value. For example, if the HSS sends
the zone-code value as 3032, the MME converts this to 02 (ASCII value of 0 in Hex is 0x30, ASCII value of
2 in Hex is 0x32). With this configuration, the MME accepted zone-codes only within the range of 0 to 99.
backward compatibility.
When configured as ascii-string, the MME interprets the received zone-code as an ASCII string (coded in
hexadecimal representation) and converts it byte by byte to an integer value. For example, if the HSS sends
the zone-code value as 3032, the MME converts this to 02 (ASCII value of 0 in Hex is 0x30, ASCII value of
2 in Hex is 0x32). With this configuration, the MME accepted zone-codes only within the range of 0 to 99.
Usage
This new command specifies the format of the zone-code value received from HSS to MME. The MME uses
this configuration to interpret and convert the received zone-code value to an integer value and validate it
against the list of allowed zone-code configured for the zone-code restriction feature.
By default, the MME interprets the received zone-code value from HSS as a octet-string (2 bytes) which is
coded in full hexadecimal representation. The MME converts the entire 2 byte octet string coded in
hexadecimal to integer value and it uses the same for validation for zone-code restriction feature. For
example, if the HSS sends the zone-code value as 3032, MME converts this to 12338 (which is the equivalent
of 0x3032).
this configuration to interpret and convert the received zone-code value to an integer value and validate it
against the list of allowed zone-code configured for the zone-code restriction feature.
By default, the MME interprets the received zone-code value from HSS as a octet-string (2 bytes) which is
coded in full hexadecimal representation. The MME converts the entire 2 byte octet string coded in
hexadecimal to integer value and it uses the same for validation for zone-code restriction feature. For
example, if the HSS sends the zone-code value as 3032, MME converts this to 12338 (which is the equivalent
of 0x3032).
Example
The following command configures the HSS Peer Service to interpret the zone-code received from the HSS
as an ASCII string.
as an ASCII string.
zone-code-format ascii-string