Multi-integration Webex chat/HTTP bot that unifies phone, AV, and network status for retail store support. Consolidates data from Webex Calling, Meraki, Workspace ONE (MDM), Atlas AMP, RED digital signage, and OptiSigns into rich per-store status commands. Key surfaces: - /phonestatus, /avstatus — per-store phone & AV device reports with clickable Meraki deep-links and per-port detail. - /webexhost — check/assign Webex Meetings host licenses via the Service App; adaptive-card confirmation flow, HTTP-API-gated. - /offboarduser — full Webex Admin offboarding (auth revoke, device wipe, license removal); adaptive-card confirmation. - /jirapoll — on-demand trigger for the hourly Jira poller. - /bulkavstatuscsv — bulk store CSV export with concurrency limits. Automation: - Hourly Jira poller (node-cron) with an X.AI (Grok) ticket classifier that categorizes unassigned tickets as phone/av/skip, extracts store numbers from free-text, and enriches Jira with the same detailed markdown the chat commands emit (converted to Jira ADF, preserves bold + Meraki links). Idempotent via a `bot-enriched` Jira label. Architecture: - Node.js 20+, ESM, Express 5, webex-node-bot-framework. - Layered integrations (integrations/*), services (services/*), commands (commands/*), utils (utils/*). - Shared markdown renderers (services/renderers/*) feed both chat handlers and the Jira poller so the two surfaces stay in sync. - Hand-rolled markdown-to-ADF converter (utils/markdownToAdf.js) — no new npm dependency. - Node built-in test runner (`node --test tests/*.test.js`), 30 tests covering the converter, renderers, and poller ADF assembly. Docker + docker-compose deployment. Config via .env (see .env.example for the full option surface).
50 lines
No EOL
2 KiB
JavaScript
50 lines
No EOL
2 KiB
JavaScript
// src/services/phoneDeviceBuilder.js
|
|
//
|
|
// Thin wrapper for phone data rich/build shape for the phone store dashboard.
|
|
// Delegates to collectPhoneStatus (which already does Webex phones/DECT + Meraki attach + relevant ports).
|
|
// Adds optional Meraki topology for viz mirroring the AV dashboard.
|
|
// Keeps backward compat for the /phonestatus command (which uses collect directly).
|
|
|
|
import { collectPhoneStatus } from './phoneService.js';
|
|
import { getMerakiTopology } from '../integrations/meraki/devices.js';
|
|
import { logger } from '../utils/logger.js';
|
|
|
|
export async function buildPhoneDevices(storeNumber) {
|
|
logger('phone:builder', `Building phone devices for store ${storeNumber} (rich shape for dashboard)`, 'debug');
|
|
|
|
try {
|
|
const data = await collectPhoneStatus(storeNumber);
|
|
|
|
// Fetch topology (linkLayer) for rich dashboard viz, similar to AV.
|
|
// Use networkId from the meraki enrichment if present.
|
|
let merakiTopology = null;
|
|
const networkId = data.meraki?.networkId || (data.meraki?.network && data.meraki.network.id);
|
|
if (networkId) {
|
|
try {
|
|
merakiTopology = await getMerakiTopology(networkId);
|
|
logger('phone:builder', `Fetched Meraki topology for network ${networkId}: ${merakiTopology?.nodes?.length || 0} nodes`, 'debug');
|
|
} catch (topoErr) {
|
|
logger('phone:builder', `Failed to fetch Meraki topology: ${topoErr.message}`, 'warn');
|
|
merakiTopology = { nodes: [], links: [], errors: [topoErr.message] };
|
|
}
|
|
}
|
|
|
|
const result = {
|
|
success: true,
|
|
storeNumber: String(storeNumber),
|
|
...data,
|
|
merakiTopology,
|
|
deviceCount: (data.phones?.data?.length || 0) + (data.dectBasestations?.length || 0),
|
|
lastUpdated: new Date().toISOString()
|
|
};
|
|
|
|
logger('phone:builder', `Phone build complete for store ${storeNumber} (${result.deviceCount} devices)`);
|
|
return result;
|
|
|
|
} catch (err) {
|
|
logger('phone:builder', `Phone build failed for store ${storeNumber}: ${err.message}`, 'error');
|
|
throw err;
|
|
}
|
|
}
|
|
|
|
export default buildPhoneDevices; |