Scott wrote: > Here's the real catch that's also actually confused by the > current UI: transformation rules (mappingrules.xml) are > searched first, and only the first match is applied;
Can you confirm what "and only the first match is applied" means? I think you mean that once a transformation is made, the INVITE immediately spirals back into the system (before any lower transformation rules are considered for match.) It could then match an extension (User, Hunt Group, etc.) But if it doesn't match and extension, then transformation rules will be checked again, and there could be another match. It if doesn't mach a transformation rule, then routing rules will be checked. Is that right? > routing rules (fallbackrules.xml) are searched _only_ if no > other mechanism has provided a way to route the call. But, "only the first match is applied" is true for routing rules too right? The difference is that if a routing rule (fallbackrules.xml) matches, the INVITE will not spiral back into the system. (It will either go out on of the Gateways, or be rejected due to permissions.) Is that right? > The current > UI lets you mix them up, so that it looks as though a rule > with a gateway in it takes precedence (is higher in the list) > over a transformation rule, but that's not how it really works. Understood. We need to make the actual behaviour apparent in the UI. -Paul [email protected] _______________________________________________ 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/
