Cisco Expressway · Arazzo Workflow

Cisco Expressway Zone Health Investigation

Version 1.0.0

Inspect zone connectivity, active calls, and recent call history together.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub CollaborationFirewall TraversalH.323Session Border ControllerSIPUnified CommunicationsVideo ConferencingArazzoWorkflows

Provider

cisco-expressway

Workflows

zone-health-investigation
Read zone status, active calls, and interval call history.
Reads zone connectivity status, lists active calls, and retrieves call history for the supplied interval to correlate zone state with call outcomes.
3 steps inputs: endTime, host, password, startTime, username outputs: activeCalls, callHistory, zoneStatus
1
readZoneStatus
Read zone connectivity status for all configured zones including connection state and active call counts.
2
listActiveCalls
List all currently active calls so calls traversing a degraded zone can be identified.
3
readCallHistory
Retrieve call history for the supplied interval so completed and failed calls can be correlated with the zone status.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Cisco Expressway Zone Health Investigation
  summary: Inspect zone connectivity, active calls, and recent call history together.
  description: >-
    Investigates zone health by reading zone connectivity status, listing active
    calls currently traversing the system, and pulling recent call history for a
    time interval so failed or dropped calls through a degraded zone can be
    correlated. Every step spells out its request inline so the flow can be read
    and executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: callsApi
  url: ../openapi/cisco-expressway-calls-api-openapi.yml
  type: openapi
- name: zonesApi
  url: ../openapi/cisco-expressway-zones-api-openapi.yml
  type: openapi
workflows:
- workflowId: zone-health-investigation
  summary: Read zone status, active calls, and interval call history.
  description: >-
    Reads zone connectivity status, lists active calls, and retrieves call
    history for the supplied interval to correlate zone state with call outcomes.
  inputs:
    type: object
    required:
    - host
    - username
    - password
    - startTime
    - endTime
    properties:
      host:
        type: string
        description: FQDN or IP address of the Expressway node (server variable host).
      username:
        type: string
        description: Expressway administrator username for HTTP Basic auth.
      password:
        type: string
        description: Expressway administrator password for HTTP Basic auth.
      startTime:
        type: string
        description: Interval start time in ISO 8601 format for call history filtering.
      endTime:
        type: string
        description: Interval end time in ISO 8601 format for call history filtering.
  steps:
  - stepId: readZoneStatus
    description: >-
      Read zone connectivity status for all configured zones including connection
      state and active call counts.
    operationId: listZoneStatus
    parameters:
    - name: Authorization
      in: header
      value: Basic $inputs.username:$inputs.password
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      zoneStatus: $response.body
  - stepId: listActiveCalls
    description: >-
      List all currently active calls so calls traversing a degraded zone can be
      identified.
    operationId: listActiveCalls
    parameters:
    - name: Authorization
      in: header
      value: Basic $inputs.username:$inputs.password
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      activeCalls: $response.body
  - stepId: readCallHistory
    description: >-
      Retrieve call history for the supplied interval so completed and failed
      calls can be correlated with the zone status.
    operationId: getCallHistory
    parameters:
    - name: Authorization
      in: header
      value: Basic $inputs.username:$inputs.password
    - name: filter
      in: query
      value: get_records_for_interval
    - name: start_time
      in: query
      value: $inputs.startTime
    - name: end_time
      in: query
      value: $inputs.endTime
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      callHistory: $response.body
  outputs:
    zoneStatus: $steps.readZoneStatus.outputs.zoneStatus
    activeCalls: $steps.listActiveCalls.outputs.activeCalls
    callHistory: $steps.readCallHistory.outputs.callHistory

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/cisco-expressway-zone-health-investigation-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.