All,
Can anyone tell me if OpenSER's ENUM module takes and NAPTR record order/pref into account when using ENUM? The reason I ask is I'm trying to use ENUM as a simple round robin'ing mechanism. Problem is, even if I alter the preference field on a record OpenSER seems to always dial *both* records (assuming there's 2 records returned naturally.)
For example:
; zone file example 0.4.9.4.2.3.7.4.1.3.1.enum.netlogic. NAPTR 100 9 "u" "E2U+sip" "!^.*$!sip:+13147324940@serverA!" . NAPTR 100 10 "u" "E2U+sip" "!^.*$!sip:+13147324940@serverB!" .
---
(For network's sake, I want to see what's really happening)
# tethereal -i eth0 -n -p -R "sip.To contains 7324940"
5.467316 xxxx -> 206.80.xx.xx SIP/SDP Request: INVITE sip:+13147324940@xxx:5060
5.468512 206.80.xx.xx -> xxxx SIP Status: 100 trying
5.470485 206.80.xx.xx -> serverA SIP/SDP Request: INVITE sip:+13147324940@serverA ..
5.470507 206.80.xx.xx -> serverB SIP/SDP Request: INVITE sip:+13147324940@serverB ..
Naturally, this can cause huge problems.. Thoughts? :-)
Thanks all, Matt