Skip to content

Carrier Identification Code (CIC) Lookup

Teliax exposes CIC lookups via a JSON-based HTTP API.
Server infoserv.net
Port 8080

CIC Lookup

Looks up the CIC for the given call paramters.

Format: GET /cic/(crn)/(ani)/(anilata)

eg curl http://infoserv.net:8080/cic/8009959324/7194931269/658

Parameters

  • crn (string) – The originating number that placed the call
  • ani (string) – The destination number
  • anilata (string) – The LATA that contains the destination number

Response JSON Object

  • carrier – The CIC of the carrier

  • networkmanagementclass – The network management threshhold value (1-15)

  • error – Exists and true when there was an error

  • error_code – The HTTP status code corresponding to the error
  • error_desc – The reason for the error
  • error_type – Indicates the field that caused the error

Status Codes

Example request

GET /cic/8009959324/7194931269/658

Example response

HTTP/1.1 200 OK
Date Tue, 01 Aug 2017 15:27:29 GMT
Server Warp/3.2.13
Content-Type application/json
Content-Length 43

{
  "carrier"333,
  "networkmanagementclass"14
}

Example error responses

HTTP/1.1 404 Unknown CRN
Date Tue, 01 Aug 2017 15:28:59 GMT
Server Warp/3.2.13
Content-Type application/json
Content-Length 96

{
  "error_type""unknowncrn",
  "error_code"404,
  "error"true,
  "error_desc""Unknown CRN: 8509959324"
}

HTTP/1.1 400 Could not parse request
Date Tue, 01 Aug 2017 15:29:28 GMT
Server Warp/3.2.13
Content-Type application/json
Content-Length 155

{
  "error_type""parse",
  "error_code"400,
  "error"true,
  "error_desc""Could not parse request: HTTP > CIC request > LATA > digit: Failed reading: satisfyWith"
}

RespOrg Lookup

Looks up the resporg of record for the provided number.

Format: GET /ror/(crn)

Parameters

  • crn (string) – The number for which to lookup the CIC.

Response JSON Object

  • ror – The resporg for the number

  • error – Exists and true when there was an error

  • error_code – The HTTP status code corresponding to the error

  • error_desc – The reason for the error

  • error_type – Indicates the field that caused the error

Status Codes

Example request

GET /ror/8443119523

Example response

HTTP/1.0 200 OK
Content-Type application/json
Content-Length 15

{"ror""CNM01"}

Example error response

HTTP/1.1 404 Unknown CRN
Date Tue, 01 Aug 2017 13:49:11 GMT
Server Warp/3.2.13
Content-Type application/json
Content-Length 96

{
  "error_type""unknowncrn",
  "error_code"404,
  "error"true,
  "error_desc""Unknown CRN: 8543229543"
}

Combined CIC/RespOrg Lookup

Looks up both the CIC and RespOrg for the given call paramters.

Format: GET /cicror/(crn)/(ani)/(anilata)

Parameters

  • crn (string) – The originating number that placed the call

  • ani (string) – The destination number

  • anilata (string) – The LATA that contains the destination number

Response JSON Object

  • carrier – The CIC of the carrier

  • networkmanagementclass – The network management threshhold value (1-15)

  • ror – The resporg for the number

  • error – Exists and true when there was an error

  • error_code – The HTTP status code corresponding to the error

  • error_desc – The reason for the error

  • error_type – Indicates the field that caused the error

Status Codes

Example request

GET /cicror/8009959324/7194931269/658

Example response

HTTP/1.1 200 OK
Date Tue, 01 Aug 2017 15:27:29 GMT
Server Warp/3.2.13
Content-Type application/json
Content-Length 43

{
  "carrier"333,
  "networkmanagementclass"14,
  "ror""CNM01"
}

Example error responses

HTTP/1.1 404 Unknown CRN
Date Tue, 01 Aug 2017 15:28:59 GMT
Server Warp/3.2.13
Content-Type application/json
Content-Length 96

{
  "error_type""unknowncrn",
  "error_code"404,
  "error"true,
  "error_desc""Unknown CRN: 8509959324"
}

HTTP/1.1 400 Could not parse request
Date Tue, 01 Aug 2017 15:29:28 GMT
Server Warp/3.2.13
Content-Type application/json
Content-Length 155

{
  "error_type""parse",
  "error_code"400,
  "error"true,
  "error_desc""Could not parse request: HTTP > CIC request > LATA > digit: Failed reading: satisfyWith"
}