بنقرة واحدة
extension-list
Retrieve the full list of active extensions and users in a Voicenter organization
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Retrieve the full list of active extensions and users in a Voicenter organization
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Designs the structural skeleton of a Voicenter Bot via interview. Use this skill when the user wants to create, design, scope, or modify a Voicenter voice/chat bot — phrases like "design a bot", "create an agent spec", "build a Voicenter bot", "patch this bot", "add an intent", "change the bot's persona", "modify the flow graph", or any reference to the Agent Spec Designer / Skill 1 in the Voicenter bot generation pipeline. Produces an Agent Spec markdown file (sections 1-4, 4.5, section 5 stubs, section 6 initial, section 7 init). Two named entry modes — greenfield (no spec attached) and patch (spec attached). Does NOT author per-intent language content (validationPrompt, post-execution intentInstructions) — that's Skill 2 (Intent Detail Author). Does NOT emit wire-format JSON — that's Skill 3 (JSON Assembler).
Assembles a fully-detailed Voicenter Agent Spec into Bot JSON wire format — the final mechanical step in the three-skill pipeline. Use this skill when an Agent Spec exists with all section 5 entries marked `[detailed]` and the user wants the deployable JSON. Trigger phrases include "run Skill 3", "assemble the JSON", "emit the bot JSON", "publish the bot", "build the wire-format", "Skill 3 (JSON Assembler)", or any direct continuation from Skill 2's completion handoff. Produces a single `bot-<name>-<date>.json` file plus a banner identifying every fail-loud sentinel and any drift between spec section 6 and what Skill 3 regenerated. Refuses to assemble if any intent is still `[structural]` or `[detailed-revisit]`, or if the spec deviates from the strict template (Doc 2 §3.7). Runs the §15.4 cross-reference pass — 23 checks (8 §15.4 + 3 Compass + 3 botIntents-role + 1 duplicate-global-intent + 8 field-placement doctrine), checks 1–7, 11–13, 15, and 16–21 blocking. Does NOT author any text content (Skills 1 and
Authors the per-intent language content of a Voicenter Agent Spec — slot descriptions, validationPrompt, post-execution intentInstructions, and RT-specific Configuration text. Use this skill when an Agent Spec exists with section 5 entries marked `[structural]` or `[detailed-revisit]`, and the user wants to fill them in. Trigger phrases include "run Skill 2", "detail the intents", "fill in the per-intent fields", "Skill 2 (Intent Detail Author)", or any direct continuation from Skill 1's handoff hint. Walks intents in user-confirmed batches with a checkpoint after each batch. Reactivable — invoke as many times as needed; spec state is the resume point. Does NOT modify the structural skeleton (sections 1, 2, 3, 4, 4.5.1/.2/.4) — that's Skill 1 (Agent Spec Designer). Does NOT emit wire-format JSON — that's Skill 3 (JSON Assembler).
Pull call detail records (CDR) from Voicenter using the Call Log API
Receive and handle CDR push notifications from Voicenter after every call ends
Initiate or terminate outgoing calls using the Voicenter Click2Call API
| name | extension-list |
| description | Retrieve the full list of active extensions and users in a Voicenter organization |
Language. Reply in the user's language: detect what they write — Hebrew→Hebrew, English→English — and mirror it, switching if they switch mid-conversation. This shapes your prose, your questions, and your
AskUserQuestionoption labels only. It does not change the artifacts you produce — identifiers, JSON keys, BCP-47 language codes, API field names, and other data stay exactly as specified.
Help the developer fetch the Organizational Extension List — all SIP extensions, their assigned users, speed dials, and departments.
Use this skill when the user wants to:
VOICENTER_API_CODE=your_api_token_here
https://monitor.voicenter.co.il/Comet/api/GetExtensions
Accepts: GET or POST-JSON
Response: JSON
code field in the request body (your API token from Voicenter back office).
| Field | Required | Description |
|---|---|---|
code | ✅ | API authentication token |
showAll | ❌ | true/1 = all extensions in the entire organization. false/0 = only extensions in the department tied to your code. Default = all. |
https://monitor.voicenter.co.il/Comet/api/GetExtensions?code=XXXXXXXXXXXXXXX&showAll=1
{
"code": "XXXXXXXXXXXXXXX",
"showAll": 1
}
{
"ERR": 0,
"DESC": "OK",
"EXTENSIONS": [
{
"SIP": "SIPSIP1",
"Name": "Extension 1",
"SpeedDial": "11",
"AccountID": 12345678,
"AccountName": "Voicenter Account",
"UserName": "John Doe",
"UserEmail": "[email protected]"
},
{
"SIP": "SIPSIP2",
"Name": "Extension 2",
"SpeedDial": "12",
"AccountID": 12345679,
"AccountName": "Sales Department",
"UserName": "Walter Melon",
"UserEmail": "[email protected]"
}
]
}
| Field | Description |
|---|---|
ERR | 0 = OK, 1 = invalid code format. An invalid code value returns an empty EXTENSIONS array with no error. |
DESC | "OK" or "Unauthorized" |
SIP | Extension's SIP user code — used as phone in Click2Call, extension in Call Log, ExtensionUser in Login/Logout |
Name | Extension display name (as shown in CPanel) |
SpeedDial | Internal speed dial number |
AccountID | Department ID the extension belongs to |
AccountName | Department name |
UserName | Voicenter user assigned to this extension |
UserEmail | Email of the assigned user |
const EXTENSIONS_URL = 'https://monitor.voicenter.co.il/Comet/api/GetExtensions';
const CODE = process.env.VOICENTER_API_CODE!;
interface VoicenterExtension {
SIP: string;
Name: string;
SpeedDial: string;
AccountID: number;
AccountName: string;
UserName: string;
UserEmail: string;
}
interface ExtensionsResponse {
ERR: number;
DESC: string;
EXTENSIONS: VoicenterExtension[];
}
async function getExtensions(showAll = true): Promise<VoicenterExtension[]> {
const res = await fetch(EXTENSIONS_URL, {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ code: CODE, showAll: showAll ? 1 : 0 }),
});
if (!res.ok) throw new Error(`HTTP ${res.status}`);
const data: ExtensionsResponse = await res.json();
if (data.ERR !== 0) throw new Error(`Extensions error: ${data.DESC}`);
return data.EXTENSIONS;
}
// Build a SIP → extension lookup map (useful for enriching CDR records)
async function buildExtensionMap(): Promise<Map<string, VoicenterExtension>> {
const extensions = await getExtensions();
return new Map(extensions.map(e => [e.SIP, e]));
}
// Populate a Click2Call agent dropdown
async function getAgentDropdownOptions() {
const extensions = await getExtensions();
return extensions.map(e => ({
label: `${e.Name} (${e.SpeedDial}) — ${e.UserName}`,
value: e.SIP,
}));
}
// Find extension by user email (e.g. from SSO or CRM login session)
async function findExtensionByEmail(email: string): Promise<VoicenterExtension | undefined> {
const extensions = await getExtensions();
return extensions.find(e => e.UserEmail.toLowerCase() === email.toLowerCase());
}
showAll: false returns only the department tied to your code — useful for multi-tenant setups where each department has its own API key.SIP is the value used as phone in Click2Call, extension in Call Log filters, and ExtensionUser in the Login/Logout API.code value returns ERR: 0 with an empty EXTENSIONS array — always check if the array is empty before assuming success.SIP as the phone parameterSIP as the ExtensionUser parameterSIP as the extension parameter to check a specific agent's call stateSIP as the extensions array parameter