Iñaki Baz Castillo wrote:
2009/2/26 Olle E. Johansson oej@edvina.net:
This is a problem I realize at every SIPit. The implementations are far away from the IETF world. And the gap doesn't seem to close.
Basic stuff like DNS is not understood or used by many SIPit attendees so even trying to mention NAPTR is too complex, and it's necessary for many security scenarious.
RFC 3263 (Locating SIP Servers) is really complex, NAPTR is really complex, and it's not needed in 99% of current SIP deployments, so vendors don't implement it. If a SIP provider whises to use NAPTR records then all its clients should implement it in their SIP phones (obviously this is unfeasible for no
I tend to disagree. I always hate to configure stuff like outbound proxy and protocol in a SIP client. If all client supports NAPTRs then it would be sufficient to configure in your client only the AoR and password.
And people which understand SIP should be able to understand DNS too.
regards klaus