Hello,
see:
https://www.kamailio.org/docs/modules/stable/modules/tls.html#tls.p.xavp_cfg
And the OPTIONS keepalive can be handled in event_route[tm:local-request].
Cheers, Daniel
On 18.06.20 02:48, Mack Hendricks wrote:
Yeah...I’m aware. I was just checking if dispatcher could match on the ip:port just in case I wanted to support other use cases with my Kamailio instance. I read thru the source and it looks like the uac module is being used to initiate the OPTIONS message.
Sent from my iPhone
On Jun 17, 2020, at 8:09 PM, Sergiu Pojoga pojogas@gmail.com wrote:
Hi Mack,
You wouldn't have the burden of handling multiple domains whatsoever if you followed Microsoft's recommendations on how to configure SBC Teams for multiple tenants. Dispatcher would be used only for carrier's base domain.
On Wed, Jun 17, 2020, 7:11 PM Mack Hendricks, <mack@dopensource.com mailto:mack@dopensource.com> wrote:
Hey All, I'm attempting to use dispatcher to send probe messages using TLS for two different domains. I'm providing the socket attribute, which maps to a certificate in /etc/kamailio/tls.cfg. But, it seems to always select the default client cert, which is not the certificate I want to use. My attrs column in dispatcher looks like this: socket=tls:142.93.159.231:5061;ping_from=sip:mack.dopensource.com <http://mack.dopensource.com> socket=tls:142.93.159.231:5062;ping_from=sip:levin.dopensource.com <http://levin.dopensource.com> Is there some way to force dispatcher to do TLS cert matching based on the host:ip? Thanks -Mack _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users