Ah - that doesn't make sense for SIP in general.
You can make it make sense for certain deployments, and what you can do in those cases
is give your client facing interface one name and your server facing interface another.
Something like _sip._tcp.client-interface.example.com _sip._tcp.server-interface.example.com
So, what else are you missing?
Cheers, Aki
_______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors at cs.columbia.edu for questions on current sip Use sipping at ietf.org for new developments on the application of sip