Enable SIP-based routing across all registered agents. When a SIP call arrives, the server extracts the username from the SIP address and routes the request to the matching agent.
With autoMap enabled, the server automatically creates username-to-route mappings from
each agent’s name and route path. You can add explicit mappings with
registerSipUsername().
Call this method after registering agents. Agents registered after setupSipRouting()
also receive SIP routing automatically.
The URL path where SIP routing requests are handled. Each registered agent receives a routing callback at this path.
Automatically generate SIP username mappings from agent names and route paths. For example,
an agent named "sales-agent" at route "/sales" gets two mappings:
"salesagent" (agent name, lowercase alphanumeric and underscores only)"sales" (route path without leading slash)void
Calling setupSipRouting() more than once logs a warning and returns early.
SIP routing can only be configured once per server.
Create an explicit mapping from a SIP username to an agent route. The username is
stored lowercase for case-insensitive matching. Routes are normalized: leading /
is added if missing and trailing slashes are stripped.
SIP routing must be enabled via setupSipRouting() before calling this method.
If routing is not enabled, a warning is logged and the call is a no-op.
The SIP username to map (e.g., "sales-team"). Matched case-insensitively.
The target agent route (e.g., "/sales"). A warning is logged if the route
does not correspond to a registered agent.
void
With this configuration, SIP calls are routed as follows: