0

NSS Reject Response code

  • NO NUMBER: No match in NSS STI-AS policy table
  • BAD SBC ID: The SBC may be missing its required keystore/certificates for signing, or the keystore may not be associated correctly with the ingress SBC. this can also happen if the NSS is only considering specific country resources and the dialed numbers fall outside those expectations.
  • NO OPERATOR: The Keystore is not loaded properly. Please contact Sansay Support.
  • NO KEYS: Usually happens when a SBC's signing algorithm on NSS GUI-> STI-AS-> Keystores-> Switches section is set to null
  • HDR GEN FAILED: When the Identity header can be generated by the system. It may be related to an invalid Private Key. Please contact Sansay Support.
  • INVALID REQUEST: The request doesn't have the mandatory headers.
  • UNAUTHORIZED HOST: It can be SBC sending request is not configured on NSS's switch page or invalid service port or protocol mismatch(SIP/REST)
  • FORBIDDEN NUMBER: Any signing request with non-conforming ANI. Conforming is any NANP TN (+1, 1 or 10 digits with NPA format)
  • QPS Exceeded: Query exceeds the license limitation 
  • BAD NUMBER (X): Query matches an entry in extended policy and gets rejected. (X) could be I, M, R, S or U defined by Sansay DNO database
  • ANI TABLE FAILED: Policy table on NSS is not loaded properly. Please contact Sansay Support.
  • FORBIDDEN NUMBER INTERNATIONAL: When the number ANI is detected as international and the attestation of international number is not enabled.
  • BAD NUMBER (X) INTERNATIONAL: The query is for an international number and it match one of the extended policies.
  • UNDEFINED:

Reply

null
Login to reply

Content aside

  • 12 hrs agoLast active
  • 4Views
  • 1 Following