Skip to content

HSS

Configuration questions⚓︎

  • What are your home PLMNs? (please provide list with their realm)

  • Do you want a diameter connection? if yes

  • Do you want SCTP connection or TCP connection for diameter?
  • Do you have specific IP to use (primary and secondary for multi-homing)? (default listen IP is 0.0.0.0)
  • Do you have specific port for diameter connections? (default is 3868)
  • What is the diameter host name of HSS?
  • What is the diameter realm of HSS?
  • What are diameter host routing rules, if any? (list of peer realms and their host list)
  • Are you expecting us to initiate diameter exchange? if yes please provide a list of IP, port, host, realm of external systems that we need to connect to.

  • Do you want a map connection? if yes

  • Please provide list of IP:port for our server that are whitelisted by STP links
  • Please provide sccp protocol version to be used in m3ua (defaults to ANSI if not provided)
  • Please provide below details for this HSS
    • point code
    • HLR global title
    • SCCP header patterns with below details (currently we support only one pattern)
    • address indicator (defaults to 11 = GLOBAL_TITLE_INCLUDES_TRANSLATION_TYPE_ONLY, ssn, dpc present)
    • global title type (defaults to GT0010 = GLOBAL_TITLE_INCLUDES_TRANSLATION_TYPE_ONLY)
    • translation type (defaults to 10 = no translation required)
    • numbering plan (defaults to 1 = ISDN)
    • nature of address (defaults to 4 = INTERNATIONAL)
  • Please provide list of STP network that will be connecting to. For each STP link please provide
    • primary and backup points codes of STP link
    • network indicator (defaults to 2 = NATIONAL if not provided)
    • network appearance (default is not to use this field)
    • traffic mode (defaults to 2 = load share, other value supported is 1 = override)
    • list of SCCP header patterns with below details (usually there will be only one pattern)
    • address indicator (defaults to 11 = GLOBAL_TITLE_INCLUDES_TRANSLATION_TYPE_ONLY, ssn, dpc present)
    • global title type (defaults to GT0010 = GLOBAL_TITLE_INCLUDES_TRANSLATION_TYPE_ONLY)
    • translation type (defaults to 10 = no translation required)
    • numbering plan (defaults to 1 = ISDN)
    • nature of address (defaults to 4 = INTERNATIONAL)
    • list of IP:PORT of the STP link
    • routing contexts, only if the STP requires it. Usually most STPs do not use routing contexts.
  • Please provide list of routing rules based on global title with below details

    • address indicator (defaults to 11 = GLOBAL_TITLE_INCLUDES_TRANSLATION_TYPE_ONLY, ssn, dpc present)
    • global title type (defaults to GT0010 = GLOBAL_TITLE_INCLUDES_TRANSLATION_TYPE_ONLY)
    • translation type (defaults to 10 = no translation required)
    • numbering plan (defaults to 1 = ISDN)
    • nature of address (defaults to 4 = INTERNATIONAL)
    • list of global title prefixes to match
    • routeTo list to decide which PointCode and which SCCP format to use
  • Do you want a SMSc service? if yes

  • Please provide below MAP details for this SMSc

    • point code
    • SMSc global title
    • SCCP header patterns with below details (currently we support only one pattern)
    • address indicator (defaults to 11 = GLOBAL_TITLE_INCLUDES_TRANSLATION_TYPE_ONLY, ssn, dpc present)
    • global title type (defaults to GT0010 = GLOBAL_TITLE_INCLUDES_TRANSLATION_TYPE_ONLY)
    • translation type (defaults to 10 = no translation required)
    • numbering plan (defaults to 1 = ISDN)
    • nature of address (defaults to 4 = INTERNATIONAL)
  • Do you want a SMPP service? If yes

  • Please provide systemId and password
  • Please provide routing rules based on MSISDN

  • Do you want geo-redundant setup? if yes

  • please provide three VMs where one VM will be arbitrator/witness-server for split brain scenario

Configuration answers to values mapping⚓︎

  • Home PLMNs are configured in agent values, e,g.

    agent:
      hss:
        nodeConfig:
          hssConfig:
            homePlmns:
              - plmn:
                  mcc: '313'
                  mncs:
                    - '260'
                  realm: epc.mnc260.mcc313.3gppnetwork.org
                gts:
                  - 11111111114 # smsc global title
                  - 11111111111 # hlr global title
            # below values are for diameter that has been agreed with DRA links
            hostUri: hss03.node
            originHost: hss03.node.epc.mnc260.mcc313.3gppnetwork.org # diameter host name
            originRealm: epc.mnc260.mcc313.3gppnetwork.org # diameter host realm
            # below values are for map and will match with STP link details
            hlrGt: 11111111111 # hlr global title
            pointCode: 111111 # hlr point code
            hlrTt: 0
            hlrEncoding: BCD_ODD
            hlrGti: GLOBAL_TITLE_INCLUDES_TRANSLATION_TYPE_NUMBERING_PLAN_ENCODING_SCHEME_AND_NATURE_OF_ADDRESS
    

  • Diameter config

    diameter:
      enabled: true
      tcp: true # Do you want SCTP connection or TCP connection for diameter?
      primaryIp: 1.2.3.4 # default is 0.0.0.0
      secondaryIp: 2.3.4.5 # default is not to use secondary IP
      port: 1111 # default is 3868
      host: hss # What is the diameter host name?
      realm: epc.mnc260.mcc313.3gppnetwork.org # What is the diameter realm?
      routingRules:
        - peerRealm: *
          peerHosts:
            - dra1.comfone.com
      peers: # Are you expecting us to initiate diameter exchange? if yes, e.g. below
        - ip: 1.2.3.4 # IP of the DRA
          port: 1234 # port of the DRA
          diameterRealm: bics.3gpp.org
          diameterHost: node01.bics.3gpp.org
          protocol: <SCTP|TCP>
          hssIp: 0.0.0.0 # IP to listen to when initiating connection with the peer
          hssPort: 2345 # port to listen to when initiating connection with the peer
    

  • MAP config yaml map: enabled: true # Do you want a map connection? sccpVersion: ITU # sccp protocol version hlr: pointCode: 3000 globalTitle: '11111111112' sccp: - addressIndicator: '11' globalTitleType: 'GT0010' smsc: pointCode: 2010 globalTitle: '11111111111' sccp: - addressIndicator: '11' globalTitleType: 'GT0010' servers: # Do you want us to be server or client? - ip: 0.0.0.0 port: 2905 name: SCTP1 stps: - routingContexts: [] pointCodes: [ '4444', '4445' ] # point code of the STP and it's backup point code networkIndicator: '0' networkAppearance: 0 trafficMode: 2 sccp: - addressIndicator: '19' globalTitleType: 'GT0100' translationType: '0' encodingScheme: '1' numberingPlan: '0' natureOfAddress: '0' name: stp1_sccp1 ips: - ip: 192.168.2.20 port: 64504 name: unique_name # optional, unique name for this link, helpful in cli link status linkTo: SCTP1 # when we are server - routingContexts: [ '71', '72' ] pointCodes: [ '22222', '22223' ] # point code of the STP and it's backup point code networkIndicator: '0' sccp: - addressIndicator: '19' globalTitleType: 'GT0100' translationType: '0' encodingScheme: '1' numberingPlan: '0' natureOfAddress: '0' name: stp2_sccp1 ips: - ip: 192.168.2.20 port: 64505 hlrIp: 192.168.3.4 # need this when we are client hlrPort: 2906 # need this when we are client routingRules: - addressIndicator: '19' globalTitleType: 'GT0100' translationType: '0' encodingScheme: '1' numberingPlan: '0' natureOfAddress: '0' globalTitlePrefixes: - 3933* routeTo: - pointCode: 4444 sccp: stp1_sccp1 - pointCode: 22222 sccp: stp2_sccp1

  • SMSc config

    smsc:
      enabled: false
      smpp:
      clients:
      - systemId: expeto
        password: 12345678
      routingRules: []
      - destinationAddress: 111111111
        destinationRoute: SMPP
        sourceRoute: ANY
        systemId: expeto