On Jul 21, 2024, at 6:57 AM, Henning Westerholt via sr-users <sr-users(a)lists.kamailio.org> wrote: For TCP/TLS the server uses a different approach, but this is still something that probably was rarely tested. So, give it a try, but there might be some issues you encounter.

Hello, you can have multiple listen statements of course. Ranges are not supported. If you don’t want to create them by copy/paste, investigate something like ansible or similar tools. For UDP Kamailio would start n children each per listening socket, so 2k sockets would not work without some adaptions in the cfg. For TCP/TLS the server uses a different approach, but this is still something that probably was rarely tested. So, give it a try, but there might be some issues you encounter. Report back on the list if it doesn’t work, and of course also when it works. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com *From:* João Silva via sr-users <sr-users(a)lists.kamailio.org> *Sent:* Sonntag, 21. Juli 2024 11:31 *To:* sr-users(a)lists.kamailio.org *Cc:* João Silva <silvajp9+kamailio(a)gmail.com> *Subject:* [SR-Users] Listening on multiple TLS ports Hello everyone! Is there a way to define a listen port range for TCP/TLS? Or any macro I can use to create the LISTEN commands? And finally is there a performance penalty for having multiple (2k) listening ports at the same time? I am in a strange situation where I need to register multiple credentials on a single SIP trunk, for each registration I need to use a different local port otherwise the trunk will simply overwrite the previous registrations. Furthermore, when I place a call on that trunk I have to be consistent with the port I used for registration for that specific credential. So I am looking into explicitly defining the port to be used per credential, UACREG allows me to use the contact_addr/socket for the registration part and for placing of outbound calls I can use $fsn to force the correct socket. Best regards, Joao