***

## title: SIP

SIP inbound lets you route calls from PBX, SBC, or carrier SIP infrastructure into the same Voice AI scenarios used for PSTN.

## Setup flow

1. Decide between SIP registration and SIP trunk-style ingress.
2. Configure your SIP side to call your Voximplant destination URI or user.
3. Create a routing rule for the SIP destination pattern.
4. Attach your inbound Voice AI scenario.

## Voice AI notes

* Keep the scenario identical to PSTN inbound: answer, create connector client, bridge audio.
* Use dedicated routing aliases per SIP trunk or tenant to keep prompts/tools isolated.
* Log `CallEvents.Failed` and SIP response details during rollout.

## Common issues

* Destination URI does not match routing regex.
* Firewall or NAT rules block signaling or RTP.
* Codec expectations between SIP side and call path are not aligned.

## Links

* SIP guide: [https://voximplant.com/docs/guides/calls/sip](https://voximplant.com/docs/guides/calls/sip)
* Routing rules basics: [https://voximplant.com/docs/getting-started/basic-concepts/routing-rules](https://voximplant.com/docs/getting-started/basic-concepts/routing-rules)

<Info title="Screenshots needed">
  - SIP destination format examples in the target application.
  - Routing rule that matches SIP usernames or domains.
</Info>