Re: [Serusers] ENUM support

The idea of using ENUM at the server-side has a lot of problems Example: you get this from DNS 1) NAPTR 10 10 "u" "sip+E2U" "!^.*$!sip:blabla@example.com!" . 2) NAPTR 10 20 "u" "sip+E2U" "!^.*$!sip:blabla2@otherexample.com!" . 3) NAPTR 10 10 "u" "tel+E2U" "!^.*$!iax:0900@expensivenumber.sex!" . What to do ?? First try 1) or 3) ??? What happens if this failes ?? (not reachable, busy ??) Is the user willing to pay the costs for 3) ?? Maybe the user wants to dial the REAL number (remember ENUM is a additional information for the real world phone number). How will you find this out ??? My conclusion is that ENUM is ALLWAYS a funktionality of the client and NEVER of the server because of the need for the user to decide what he realy wants to do. Any automatic resolution will fail. Maybe there is a need for a kind of communication between Server and Client (inside SIP ??) to solve these kind of problems. Any ideas how so solve this problem ??? serusers-admin(a)lists.iptel.org wrote on 14.04.2003 21:32:49: based into a (documented