Guest

Preview Tool

Cisco Bug: CSCup71665 - Routing-context cannot be set to 0

Last Modified

Dec 24, 2016

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases

16.0(1)

Description (partial)

Symptom:
HLR requires to use routing-context = 0 in M3UA messages while SGSN supports only 1 and larger. "0" is not possible to set. This is a live HLR serving other SGSN from different vendors therefore the customer rejected to change this behavior on their side. So I would like to ask you to add 0 into the CLI.

Conditions:
1-) HLR_missing_parameter.txt when there is below config. [Error Code: Missing Parameter (22)]
 
    peer-server id 1
      name TSNTHL1
      mode loadshare
      routing-context 1
      self-point-code 13314
      psp instance 1
        psp-mode server
        exchange-mode single-ended
        routing-context discard-inbound suppress-outbound
        end-point address 10.63.12.11
        associate asp instance 1
      #exit
    #exit
  #exit
 
2-) RC_cannotset0_set1.txt when RC=1 because I cannot set it to 0. [Error Code: Invalid Routing Context]
 
[local]ssi(config-ss7-rd-1-ps-id-1)# routing-context
integer value (1 .. 4294967295)
 
    peer-server id 1
      name TSNTHL1
      mode loadshare
      routing-context 1
      self-point-code 13314
      psp instance 1
        psp-mode server
        exchange-mode single-ended
        routing-context discard-inbound
        end-point address 10.63.12.11
        associate asp instance 1
      #exit
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.