> Dale Worley wrote:
> > So what we need is that these values should be DNS SRV names that
> > preferentially route to the proxy on the same server, but fall back to
> > the proxy on the other server(s). This should be the similar to the old
> > "ap" DNS names. But we don't seem to be generating those names any
> > more.
Damian Krzeminski wrote:
> Just to support Dale's question:
> In 3.10 sipXconfig did not generate a registrar-config.in file.
> The values in registrar-config were inserted from config.defs:
>
> SIP_REDIRECT.999-AUTHROUTER.SIPX_PROXY :
> ${PROXY_SERVER_SIP_HOSTPORT};transport=tcp
>
> Current implementation of sipXconfig mirrors what we had then (unless someone
> manually modified the file but I suspect few users did that).
> If sipXconfig is to generate something else, we'll gladly do that but it's
> need to be fairly clear what this "something else" needs to be.
We don't currently create/require a DNS SRV name that has the desirable
properties (we could use the SIP_DOMAIN_NAME, but that does not have the
property of preferring the local system over any other peers).
Given that the message being processed by the registry/redirect server
came from some proxy, and the response it is creating will go back to
that same proxy (not always the one on the same box, incidentally),
chances are that the current configuration will work.
We already have an issue to track changing all our Record-Routes to use
the SIP Domain name - it would be a good idea to link this new one to
that, Dale.
I don't think we need a change for 4.0
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
