You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
Each call's description says what became of it, for meetings show, WireCat Desktop and an agent: Incoming call to 600: answered by 101 Анна Смирнова after 0:03, talk 0:24. 102 Борис Кузнецов did not answer.
phone_region takes several countries, es,ru, for an office whose phone lines serve more than one. A number
written without + is read in the country it fits; one that fits two of them is kept as written, linked to no
one, and meetings sync says how many callers that left. See numbers, directions and people.
Changed — may break callers
One call is one meeting. Every CDR row of a call (a ring group's members, a queue, a transfer) is joined by its linkedid, and the meeting's id is that linkedid. Its people are the caller, the employee who placed it and each
one who answered; its metadata says what became of it (outcome: answered, voicemail, busy, no_answer, failed),
who placed it (placedBy), who answered (answeredBy), who rang without answering (rang), what was dialled,
the wait before the first answer (waitMs), the talk time (talkMs) and every leg. The one-row meetings of 0.3.0 and older are marked
deleted once a sync reads their rows again into a call; meetings sync --since-time <first call> reads them all.
A transcript made of a row meeting is made again by meetings transcribe.
An employee's identity is now extension:<profile>/<number> (was extension:<number>), so extension 101 of one
profile and 101 of another are two people, not one. A script that looked people up by extension:101 adds the
profile: extension:office/101.
A ring group's or queue's member who answered is named by the channel that reached them (Local/101@…), not by the
group's number (600), and employees are named from the caller ID of the calls they make.
meetings show --json answers { "item": { … } }; 0.3.0 wrapped the meeting twice, as item.item.
WireCat Desktop and the README link to the guide on wirecat.dev, now that it is
published, instead of the README on GitHub.
A caller is linked to the CRM contact or messenger person with the same mobile number, as Beeline's are: the
caller's participant now carries its phone number.
A recording with nothing but its header, which MixMonitor leaves when nobody talked, is no longer linked or sent to
transcription.
A build starts from an empty dist/, so a renamed file no longer ships: 0.3.0 carried an unused dist/bin/asterisk.js.
Sync runs on a fresh install. A shared WireCat config (~/.config/WireCat/config.json) that could not be
read (a byte-order mark, broken JSON, a folder in its place, an older setup shape) made every WireCat tool
read-only and refused sync. Now only the owner's own "read only" answer limits a tool, and even then a sync runs:
it only reads the service into the local store (cli-core 0.656.0).
The guide starts with what you get from your calls and the work an agent can take over: the overview says what pbx does and does not do yet, install and connect is one page from installation to
the first sync, in WireCat Desktop or a terminal, and use it is built around a team's daily
tasks, with requests to copy and a schedule.