Hello,

in the past, the only limitation was for sending option keepalives for destinations that had SRV only. That can be controlled now via a flag, see the description for 16 at:

  - https://www.kamailio.org/docs/modules/devel/modules/dispatcher.html#dispatcher.p.ds_probing_mode

Otherwise, for routing, it should just work, but the dispatcher is not fetching the addresses behind the SRV record, that is done by tm+core at the time of sending out, dispatcher will still maintain a single record with the domain name.

Cheers,
Daniel

Is it possible to route to the back-end SIP servers via DNS SRV record rather than specifying multiple IP addresses in the dispatcher list on the Kamailio server?

 

Running in AWS and looking to be able to dynamically update my list of available sip servers if a server goes offline or if a server comes online. Have Cloudwatch/Lambda setup to manipulate the SRV record with the IP address additions or subtractions but when I try to put the SRV record as the destination in dispatcher, it fails.

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com
Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com