Raymond Dans wrote: > Damian wrote: > >> Subject: [sipX-dev] fowardingrules.xml changes >> >> http://track.sipfoundry.org/browse/XCF-3587 >> >> >> I have an issue that contains request to change the way >> sipXconfig generates forwardingrules.xml >> >> -- >> In a HA environment (with a redundant SIP router), the >> forwardingrules for the Sip Registrar should be defined as the >> rr rule in the DNS SRV records. >> In other words, the rule (for the registrar) should look >> something like: >> >> <routeTo><rr.bcmdesk2073.ca.nortel.com;transport=tcp;x-sipx- >> routetoreg></routeTo> >> >> -- >> >> >> sipXconfig used to generate forwardingrules.xml in HA >> environment in couple of releases now. >> >> Why are we changing it now? > > The forwarding rules currently being generated for say the registrar use > the IP address and port number of the registrar. >
Not just any registrar. They contain IP address and port of the registrar running on the server for which forwardingrules.xml is prepared. I think this emulates pretty well what used to happen in 3.10 version and before. This is how forwardingrules.xml template looked like: http://sipxecs.sipfoundry.org/rep/sipXecs/branches/3.10/sipXconfig/neoconf/etc/commserver/forwardingrules.vm Most traffic was routed to: <${REGISTRAR_SERVER_SIP_SRV_OR_HOSTPORT};transport=tcp> Which was handled by config.defs magic REGISTRAR_SERVER_ADDR=${MY_IP_ADDR} REGISTRAR_SERVER_SIP_PORT=5070 REGISTRAR_SERVER_SIP_SRV_OR_HOSTPORT=${REGISTRAR_SERVER_ADDR}:${REGISTRAR_SERVER_SIP_PORT} Hence effectively generated forwarding rules had server IP address and port. It might have been wrong but this is what it was. > In an HA environment, the proxy needs to be able to forward requests to > the registrar on the primary or the registrar on the redundant SIP > router. > > Let's assume the registrar on the primary is down for whatever reason > (PV has been testing this). > > If a request comes to the Proxy on the Primary Server, the forwarding > rules will point it to the Registrar on the Primary (which is down). As > a result, the request will fail and the Proxy will not know to try the > Registrar on the Distributed Server. > > Changing the forwarding rule to use the DNS SRV record definition, the > Proxy will receive (on a DNS lookup) a result containing 2 entries (1 > for the Registrar on the Primary (IP address and port) and 1 for the > Registrar on the Distributed (IP address and port) ). The Proxy will > pick one and try it. If the forwarding fails because it can't connect, > the Proxy will then try the other one. > > BTW. This is how the forwardingrules were generated in previous releases > (i.e. 3.10). As I tried to explain above - it does not look like that from sipXconfig code. > > I hope this accurately described explains it at a higher level a little > better. > So if I understand correctly this change would let sipx handle cases in which proxy is up (it received SIP message after all) but registrar on the same server is down. This is a trivial change in sipXconfig. But it does not look like a trivial change in the system behavior. D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
