Oh. I didn't understand what the branches were. Excellent!
If you have a moment can you post a link to some good documentation on that? If not...I can find it, I know I saw it earlier....
Juha Heinanen wrote:
Jonathan Creasy writes:
Is there a way to have OpenSER try each NAPTR record when multiple are returned?
4.3.2.1.5.5.5.5.5.5.1.mysite.enum. 0 IN NAPTR 100 15 "u" "E2U+sip" "!^.*$!sip:+15555551234@server2" . 4.3.2.1.5.5.5.5.5.5.1.mysite.enum. 0 IN NAPTR 100 10 "u" "E2U+sip" "!^.*$!sip:+15555551234@server1" . 4.3.2.1.5.5.5.5.5.5.1.mysite.enum. 0 IN NAPTR 100 25 "u" "E2U+sip" "!^.*$!sip:+15555551234@server3" .
That would route the calls to server1 (order 100, preference 10) but if server1 is not responding I would like it to move on and try server2.
enum function appends all matching naptr records as branches to the request. you can then decide in your openser.cfg script what to do with them.
-- juha