ext Robert Sparks wrote:
Ah - that doesn't make sense for SIP in general.
I rather think it makes perfect sense. With sip-outbound we have what in
practical terms are two different SIP interfaces already; a
client-server interface for UAs that REGISTER to the domain, and a
server-server interface for outside-in traffic like INVITEs from other
UAs (read: servers by whom other UAs send their sip-identity signed
traffic).
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?
A standard mechanism to configure the UAs of your domain to use
_sip._tcp.client-interface.example.com, while the rest of the world uses
_sip._tcp.server-interface.example.com.
Cheers,
Aki
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
