You have two phone numbers
# ❓・ai-evy-supportm
mati_89
07/15/2026, 12:12 PM@AI Evy You have two phone numbers. 503650144 is the one customers call — it only serves to connect to the agent. And you also have:
Number 503650144 — Inbound Call Agent: Maja Riodental/V100, Outbound Call Agent: None (disable outbound).
Number 931c80c9fc1b446aa86fa0cede7db353 — Inbound Call Agent: None (disable inbound), Outbound Call Agent: Maja Riodental/V100. This one is only for outbound calls.
When calling from number 503650144, you present yourself with that number 503650144 — and in Poland this is not allowed, as it falls under the so-called Bezpieczna Zatoka regulation. The end user must present itself with the SIP trunk username, in this case 931c80c9fc1b446aa86fa0cede7db353, and only on that basis does the operator assign the end user the number they are allowed to present.
You should be calling from the second number, and there should be an option at the agent level to choose which trunk to use for outbound calls.
Also, there should generally be an option for authentication via URI — it is not serious for a company of your size not to have this option. If it existed, connections would be free for us, but as it stands they cost as much as butter in the times of law and justice.
a
AI Evy
07/15/2026, 12:12 PMThanks for tagging me @mati_89. I'll look through relevant sources and get back to you shortly.
AI Evy
07/15/2026, 12:13 PM### Answer
Your concern about caller ID presentation and compliance with Polish "Bezpieczna Zatoka" regulations is understood. When you import a phone number into Retell AI via SIP trunking, you specify the termination URI for outbound calls. [(1) ]() The number you import becomes the caller ID that appears for outbound calls made through that number. [(2) ]()
Currently, when you assign an outbound agent to a specific imported number, that number's configuration (including its termination URI and authentication credentials) determines how outbound calls are placed. [(1) ]() The imported number itself serves as the caller ID. [(2) ]()
Regarding your specific requests:
**Per-agent trunk selection**: The current documentation shows that phone numbers are imported with their termination URI and authentication settings, and agents are then bound to those numbers. [(1) ]() There isn't documented functionality to select different SIP trunks at the agent level for the same number.
**URI-based authentication**: When importing numbers, Retell AI supports authentication via username/password credentials or IP whitelisting (for providers that support it) . [(2) ]() [(3) ]() The termination URI is required when importing numbers through elastic SIP trunking. [(2) ]() [(1) ]()
For your Poland compliance scenario, you may need to:
- Ensure your outbound agent is bound only to the number (931c80c9fc1b446aa86f
AI Evy
07/15/2026, 12:13 PMa0cede7db353) that presents the compliant caller ID
- Configure that number's termination URI to use your SIP trunk username as required by your Polish operator
- Keep the inbound-only number (503650144) separate with no outbound agent assigned
If these options don't fully address your regulatory requirements, I'd recommend reaching out through the [Customer Support Portal]() or at support@retellai.com to discuss your specific compliance needs. [(4) ]()
AI Evy
07/15/2026, 12:13 PM
To learn more, see the sources I considered:
[[1] Import Phone Number](https://docs.retellai.com/api-references/import-phone-number)
[[2] Connect Retell voice agents to custom telephony](https://docs.retellai.com/deploy/custom-telephony)
[[3] Twilio](https://docs.retellai.com/deploy/twilio)
[[4] Avaya](https://docs.retellai.com/deploy/avaya)
AI Evy
07/15/2026, 12:13 PMFeel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.