@babelforce/babelconnect-sdk 0.11.0 → 0.13.0

package/dist/gen/babelconnect/v1/babelconnect_connect.js

@@ -3,31 +3,36 @@
 /* eslint-disable */
 // @ts-nocheck
 // Package babelconnect.v1 is the control protocol between a babelconnect client
-// (the SDK, via Go/Dart/gRPC-web) and babelconnect-server. It carries CONTROL
-// ONLY — media is WebRTC on a separate plane; the server terminates the client's
-// WebRTC leg.
+// (the SDK, via Go/Dart/gRPC-web/Connect) and babelconnect-server. It carries
+// CONTROL ONLY — media is WebRTC on a separate plane; the server terminates the
+// client's WebRTC leg.
 //
 // State lives on the SERVER, not the client. babelconnect-server holds the
 // canonical per-agent AgentView and pushes an initial snapshot + entity-level
-// patches over the Session stream; clients are DUMB RENDERERS — they apply
+// patches over the Subscribe stream; clients are DUMB RENDERERS — they apply
 // patches mechanically and send Command intents, with no domain logic.
 //
-// Two entry points:
+// Three entry points:
 //   - Authenticate: unary handshake → the agent's identity.
-//   - Session:      a long-lived bidi stream. Client → server: Command intents
-//                   (register/place/answer/hangup/mute/...). Server → client:
-//                   StateUpdate (snapshot then patches). The WebRTC offer rides
-//                   on CallState (when RINGING); the client answers via the
-//                   AnswerCall intent — signaling fits the state model, no
-//                   separate event channel.
+//   - Subscribe:    the server→client half — StateUpdate (snapshot then
+//                    patches). The WebRTC offer rides on CallState (when
+//                    RINGING); the client answers via the AnswerCall intent —
+//                    signaling fits the state model, no separate event channel.
+//   - Send:         the client→server half — one Command intent per call
+//                    (register/place/answer/hangup/mute/...). Together with
+//                    Subscribe this is the one blessed shape for every client
+//                    (RPC-A4 retired the earlier bidi `Session` RPC once all
+//                    clients had moved onto this split over the Connect
+//                    protocol).
 //
 // The bearer token travels in gRPC metadata ("authorization: Bearer <token>")
 // on every call; Authenticate additionally returns the resolved identity.
 //
-// In addition to gRPC/gRPC-web, the unary RPCs are exposed as a REST+JSON surface
-// via grpc-gateway (the google.api.http annotations below) with an OpenAPI v2 spec
-// — one proto source of truth, two wire surfaces. Streaming stays gRPC/gRPC-web.
-import { Ack, AgentView, AuthenticateRequest, Command, GetStateRequest, HistoryRequest, HistoryResponse, Identity, PhonebookRequest, PhonebookResponse, SendSmsRequest, SmsConversation, SmsThreadRequest, SmsThreadResponse, StateUpdate, SubscribeRequest } from "./babelconnect_pb.js";
+// In addition to gRPC/gRPC-web/Connect, the unary RPCs are exposed as a
+// REST+JSON surface via grpc-gateway (the google.api.http annotations below)
+// with an OpenAPI v2 spec — one proto source of truth, two wire surfaces.
+// Streaming stays gRPC/gRPC-web/Connect.
+import { Ack, AgentView, AuthenticateRequest, Command, GetStateRequest, HistoryRequest, HistoryResponse, Identity, ListCampaignsRequest, ListCampaignsResponse, ListDispositionsRequest, ListDispositionsResponse, PhonebookRequest, PhonebookResponse, SendSmsRequest, SmsConversation, SmsThreadRequest, SmsThreadResponse, StateUpdate, SubscribeRequest, TransferTargetsRequest, TransferTargetsResponse } from "./babelconnect_pb.js";
 import { MethodKind } from "@bufbuild/protobuf";
 /**
  * @generated from service babelconnect.v1.Agent
@@ -48,28 +53,15 @@ export const Agent = {
             kind: MethodKind.Unary,
         },
         /**
-         * Session opens the long-lived control stream. The client sends Command
-         * intents; the server streams StateUpdate (one snapshot on open, then
-         * entity-level patches). UI = f(AgentView).
-         *
-         * Native clients (Go/Dart desktop/mobile over HTTP/2) use this bidi stream.
-         *
-         * @generated from rpc babelconnect.v1.Agent.Session
-         */
-        session: {
-            name: "Session",
-            I: Command,
-            O: StateUpdate,
-            kind: MethodKind.BiDiStreaming,
-        },
-        /**
-         * Subscribe + Send are the browser-friendly split of Session: a browser speaks
-         * gRPC-web, which cannot client-stream, so the bidi Session is impossible there.
-         * Subscribe is the server→client half (the StateUpdate stream); Send is the
-         * client→server half (one Command per unary call). Together they are equivalent
-         * to Session for a single agent — the server keys both to the agent's one state
-         * store. Command rejections still arrive as an Error on the Subscribe stream
-         * (never on Send's reply), exactly as on Session.
+         * Subscribe + Send are the control stream, split into its server→client and
+         * client→server halves — the one shape every client uses (RPC-A4 retired the
+         * earlier bidi `Session` RPC, which needed HTTP/2 end-to-end and couldn't
+         * ride gRPC-web or a plain HTTP/1.1 ingress). Subscribe is the server→client
+         * half (StateUpdate: one snapshot on open, then entity-level patches; UI =
+         * f(AgentView)). Send is the client→server half (one Command per unary
+         * call). Together they key to the agent's one state store. Command
+         * rejections arrive as an Error on the Subscribe stream, never on Send's
+         * reply.
          *
          * @generated from rpc babelconnect.v1.Agent.Subscribe
          */
@@ -130,6 +122,24 @@ export const Agent = {
             O: PhonebookResponse,
             kind: MethodKind.Unary,
         },
+        /**
+         * GetTransferTargets autocompletes blind-transfer / add-member targets as the
+         * agent types — agents, raw numbers, and IVR applications (GET
+         * /agent/calls/transfer/targets?query=, bc-standalone-2
+         * src/components/Common/NumberListSelect.vue:59). `query` filters server-side
+         * (substring across name/email/number for agents, name for applications); the
+         * backend has no call-context param, so eligibility by call direction is a
+         * separate, already-server-computed flag the client applies itself
+         * (CallState.can_transfer_to_application hides APPLICATION results — CALL-I3).
+         *
+         * @generated from rpc babelconnect.v1.Agent.GetTransferTargets
+         */
+        getTransferTargets: {
+            name: "GetTransferTargets",
+            I: TransferTargetsRequest,
+            O: TransferTargetsResponse,
+            kind: MethodKind.Unary,
+        },
         /**
          * GetState returns the agent's current AgentView as a single unary call — the
          * REST/web "get current state" (the Subscribe stream is the realtime twin). When
@@ -157,5 +167,35 @@ export const Agent = {
             O: SmsConversation,
             kind: MethodKind.Unary,
         },
+        /**
+         * ListCampaigns lists the outbound-dialer campaigns the agent may join (the
+         * Outbound tab's campaign picker, OBDA1) — on-demand reference data like
+         * GetPhonebook/GetTransferTargets, backed by GET /api/v2/agent/outbound/
+         * campaigns?active=true (sbf/services ObdController#listCampaigns).
+         *
+         * @generated from rpc babelconnect.v1.Agent.ListCampaigns
+         */
+        listCampaigns: {
+            name: "ListCampaigns",
+            I: ListCampaignsRequest,
+            O: ListCampaignsResponse,
+            kind: MethodKind.Unary,
+        },
+        /**
+         * ListDispositions lists the available call-outcome codes for the disposition
+         * picker (OBDC1) — on-demand reference data like ListCampaigns, backed by GET
+         * /api/v2/agent/outbound/campaigns/{id}/dispositions (sbf/services
+         * ObdController#listDispositions). Grounded: the `{id}` path segment is never
+         * read server-side — the list is a static global, not campaign-scoped — so the
+         * request carries no campaign id either.
+         *
+         * @generated from rpc babelconnect.v1.Agent.ListDispositions
+         */
+        listDispositions: {
+            name: "ListDispositions",
+            I: ListDispositionsRequest,
+            O: ListDispositionsResponse,
+            kind: MethodKind.Unary,
+        },
     }
 };