@dialstack/sdk-dev / native/src / NativeCallBridgeOptions
Interface: NativeCallBridgeOptions
Defined in: sdk/native/src/bridge/NativeCallBridge.ts:62
Properties
answerTtlMs?
answerTtlMs?: number;
Defined in: sdk/native/src/bridge/NativeCallBridge.ts:76
An OS answer held for a call that has not arrived yet is stale past this.
deliveryDeadlineMs?
deliveryDeadlineMs?: number;
Defined in: sdk/native/src/bridge/NativeCallBridge.ts:74
From connect() resolving until incoming. The proxy resumes a parked INVITE
on REGISTER or within its 1s poll, so after this nothing is coming.
hold?
hold?: RuntimeHold;
Defined in: sdk/native/src/bridge/NativeCallBridge.ts:66
lifecycle?
lifecycle?: AppLifecycle;
Defined in: sdk/native/src/bridge/NativeCallBridge.ts:65
log?
log?: (message) => void;
Defined in: sdk/native/src/bridge/NativeCallBridge.ts:67
Parameters
message
string
Returns
void
maxOsCalls?
maxOsCalls?: number;
Defined in: sdk/native/src/bridge/NativeCallBridge.ts:84
How many calls the integration puts on the OS call screen at once (default 1). A second concurrent call past the cap is NOT reported to the OS but still rings and is answerable in-app; it just gets no OS session. Calls pair with sessions by call_id, so any value is safe; raising it is a product choice (OS call-waiting) and needs an adapter whose library holds several sessions.
now?
now?: () => number;
Defined in: sdk/native/src/bridge/NativeCallBridge.ts:87
Returns
number
os
os: OsCallAdapter;
Defined in: sdk/native/src/bridge/NativeCallBridge.ts:64
phone
phone: BridgePhone;
Defined in: sdk/native/src/bridge/NativeCallBridge.ts:63
registrationDeadlineMs?
registrationDeadlineMs?: number;
Defined in: sdk/native/src/bridge/NativeCallBridge.ts:69
From the OS report until connect() resolves: a socket that never comes up.
timers?
timers?: BridgeTimers;
Defined in: sdk/native/src/bridge/NativeCallBridge.ts:86
Defaults to the JS timers; see BridgeTimers for when to pass native ones.