On Thu, 2009-06-18 at 19:37 -0400, M. Ranganathan wrote: > I am not recommending rewriting working code but I don't see how any > system can get away from having to rewrite addresses to those that are > comprehensible by the other system. If the addresses that are in such > events are private, something has to re-write it. I assume that it is > being re-written somehwere by our current federation solution as well. > Yes I agree that there are a large number of cases to cover where > address translation needs to happen.
The crux of the solution is to minimize the number of situations where rewriting has to happen. The minimum set of "local" or context-sensitive addresses are the contact addresses of phones which are on non-public networks -- that is, addresses containing non-global IP addresses. Suitable record-routing by the proxy and the NAT Traversal system handles them for basic call setup. > I am pretty impressed that our > current solution for federating two autonomous sipx installations > actually supports a User Agent on one of those sytems being able to > subscribe to the dialog events of the other system. It turns out that dialog events work across systems acceptably only if phones use their assigned GRUUs as their "target" addresses. But for GRUUs to work, it requires that they are actually Globally Routable, which won't happen if different systems use the same SIP domain. 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 sipXecs IP PBX -- http://www.sipfoundry.org/
