# Why is there a limitation that only unique Interface is allowed while creating custom trunks

**URL:** <https://wazo-platform.discourse.group/t/why-is-there-a-limitation-that-only-unique-interface-is-allowed-while-creating-custom-trunks/1302>\
**Category:** Installation/Configuration\
**Created:** [July 25, 2023, 6:00pm UTC](https://wazo-platform.discourse.group/t/why-is-there-a-limitation-that-only-unique-interface-is-allowed-while-creating-custom-trunks/1302 "2023-07-25T18:00:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![quintana](https://yyz2.discourse-cdn.com/free1/user_avatar/wazo-platform.discourse.group/quintana/32/916_2.png) [@quintana](https://wazo-platform.discourse.group/u/quintana)\
**Post date:** [August 14, 2023, 2:56pm UTC](https://wazo-platform.discourse.group/t/why-is-there-a-limitation-that-only-unique-interface-is-allowed-while-creating-custom-trunks/1302/2 "2023-08-14T14:56:10Z")

</div>

Hello, the reason is we develop a multi-tenant solution, so by design multi-tenant is not for sharing same configuration/information for a tenant. The best to do what you want is to use a kamailio in front of Wazo and adding header for your different customers to route them on the good internal sip trunk.

---

_[View the full topic](https://wazo-platform.discourse.group/t/why-is-there-a-limitation-that-only-unique-interface-is-allowed-while-creating-custom-trunks/1302)._