On Thu, 2008-12-18 at 20:09 +0000, Scott Lawrence wrote: > I prefer this second solution: > > > - Have sipXconfig add URI parameters to URIs listed in > > resource-lists.xml so that SUBSCRIBEs to AORs are forked correctly. > > (SUBSCRIBEs to contact URIs are unmodified, but that doesn't matter > > since the proxy won't fork them to VM or call forwarding.) > > This makes the change in the component that's _supposed_ to have a > global view of what services exist, so it's more natural for it to be > dictating the exceptions. > > The best solution is to make the routing decisions method-sensitive, but > that will have to wait for a later round of development.
I favor this approach because it makes the difference in routing between SUBSCRIBE and INVITE manifested and controlled by a configuration file. Ideally, the routing decisions would be method-sensitive, which would be controlled by forwardingrules.xml (or its successor). But specifying the routing decision individually for each watched-URI in resource-list.xml that is similar. The alternative would be hard-coding a change in the RLS, which would be less flexible. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
