El Fri, 19 Jan 2024 12:07:39 +0100
Daniel-Constantin Mierla <miconda(a)gmail.com> escribió:
Hello,
the log message in your first email is about not finding the socket. The
record route matches the domain, it is just that the socket to be used
cannot matched by the second Route URI. You can name the sockets and set
them in record-route to handle it.
Thanks Daniel I'll try as soon as I can.
My sockets are all named. It will be enabling sockname_mode modparam enough?
And why the kamctl rpc corex.list_aliases doesn't list what I added to
alias_subdomains corex modparam?
cheers,
Jon
--
PekePBX, the multitenant PBX solution
https://pekepbx.com