@siphon-project/control 0.4.0 → 0.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.d.cts CHANGED
@@ -938,6 +938,43 @@ interface DialOptions {
938
938
  timeout?: number;
939
939
  /** Headers injected on every branch's INVITE, under each target's own. */
940
940
  headers?: Record<string, string>;
941
+ /**
942
+ * A configured media profile to anchor both legs through, so the caller and
943
+ * the phones never exchange media directly.
944
+ *
945
+ * What a carrier-delivered call to a ring group needs: the carrier hands over
946
+ * plain RTP at a routable address and every phone answers from an address on
947
+ * its own LAN, so without the relay in the middle the two ends cannot reach
948
+ * each other. Left out, the caller's own SDP passes through.
949
+ */
950
+ profile?: string;
951
+ /**
952
+ * The calling identity to present — the From URI (RFC 3261 §8.1.1.3).
953
+ *
954
+ * Without it a B-leg presents the caller's own From, which on a call out to a
955
+ * trunk is the internal extension. A carrier that looks its account up by the
956
+ * From user does not recognise that, so it challenges the INVITE and keeps
957
+ * challenging however correct the digest is. A `headers` entry cannot do
958
+ * this: From is framework-managed on a B-leg and is rewritten after the fact.
959
+ */
960
+ from?: string;
961
+ /**
962
+ * The From display name. Naming a `from` without one drops the caller's
963
+ * rather than presenting it beside a number that replaced it.
964
+ */
965
+ fromDisplay?: string;
966
+ /**
967
+ * `P-Asserted-Identity` for a trusted next hop (RFC 3325 §9.1). Reaches the
968
+ * wire after the header policy, so a preset that strips `P-*` at a trust
969
+ * boundary cannot silently drop it.
970
+ */
971
+ pAssertedIdentity?: string;
972
+ /**
973
+ * Whether the calling identity may be presented (RFC 3323 §4.1 / TS 24.607).
974
+ * `"restricted"` anonymises From and asserts `Privacy: id`, keeping the real
975
+ * identity in `pAssertedIdentity` for the trusted next hop.
976
+ */
977
+ privacy?: "allowed" | "restricted";
941
978
  }
942
979
  /**
943
980
  * What the server answers an accepted `dial` with: the INVITEs are on the wire
package/dist/index.d.ts CHANGED
@@ -938,6 +938,43 @@ interface DialOptions {
938
938
  timeout?: number;
939
939
  /** Headers injected on every branch's INVITE, under each target's own. */
940
940
  headers?: Record<string, string>;
941
+ /**
942
+ * A configured media profile to anchor both legs through, so the caller and
943
+ * the phones never exchange media directly.
944
+ *
945
+ * What a carrier-delivered call to a ring group needs: the carrier hands over
946
+ * plain RTP at a routable address and every phone answers from an address on
947
+ * its own LAN, so without the relay in the middle the two ends cannot reach
948
+ * each other. Left out, the caller's own SDP passes through.
949
+ */
950
+ profile?: string;
951
+ /**
952
+ * The calling identity to present — the From URI (RFC 3261 §8.1.1.3).
953
+ *
954
+ * Without it a B-leg presents the caller's own From, which on a call out to a
955
+ * trunk is the internal extension. A carrier that looks its account up by the
956
+ * From user does not recognise that, so it challenges the INVITE and keeps
957
+ * challenging however correct the digest is. A `headers` entry cannot do
958
+ * this: From is framework-managed on a B-leg and is rewritten after the fact.
959
+ */
960
+ from?: string;
961
+ /**
962
+ * The From display name. Naming a `from` without one drops the caller's
963
+ * rather than presenting it beside a number that replaced it.
964
+ */
965
+ fromDisplay?: string;
966
+ /**
967
+ * `P-Asserted-Identity` for a trusted next hop (RFC 3325 §9.1). Reaches the
968
+ * wire after the header policy, so a preset that strips `P-*` at a trust
969
+ * boundary cannot silently drop it.
970
+ */
971
+ pAssertedIdentity?: string;
972
+ /**
973
+ * Whether the calling identity may be presented (RFC 3323 §4.1 / TS 24.607).
974
+ * `"restricted"` anonymises From and asserts `Privacy: id`, keeping the real
975
+ * identity in `pAssertedIdentity` for the trusted next hop.
976
+ */
977
+ privacy?: "allowed" | "restricted";
941
978
  }
942
979
  /**
943
980
  * What the server answers an accepted `dial` with: the INVITEs are on the wire
package/dist/index.js CHANGED
@@ -718,6 +718,13 @@ function dialArgs(targets, options) {
718
718
  if (options.strategy !== void 0) args.strategy = options.strategy;
719
719
  if (options.timeout !== void 0) args.timeout = options.timeout;
720
720
  if (options.headers !== void 0) args.headers = options.headers;
721
+ if (options.profile !== void 0) args.profile = options.profile;
722
+ if (options.from !== void 0) args.from = options.from;
723
+ if (options.fromDisplay !== void 0) args.from_display = options.fromDisplay;
724
+ if (options.pAssertedIdentity !== void 0) {
725
+ args.p_asserted_identity = options.pAssertedIdentity;
726
+ }
727
+ if (options.privacy !== void 0) args.privacy = options.privacy;
721
728
  return args;
722
729
  }
723
730
  function recordStartArgs(options) {