Dale Worley wrote: > On Tue, 2009-09-22 at 15:50 -0400, Raymond Dans wrote: >> I have a question regarding Site to Site Dialing rules and their >> interaction with other dialing rules whenever they use the same gateway. >> Site to Site dialing rules have no Permission requirements on them. >> >> The scenario I have is: >> >> Define a Site to Site Dialing rule that uses Gateway 'A'. >> Define another dialing rule (say Long Distance) that uses Gateway 'B'. >> >> If I make a call which uses the Site to Site Dialing rule, the call >> proceeds normally. >> >> Change the Long Distance dialing rule to now use Gateway 'A' (i.e. the >> same gateway as the Site to Site rule). >> >> If I make another call which uses the Site to Site Dialing rule, the >> call fails (No Access). >> >> >> Can anyone tell me if this is design intent and if so what is the >> reasoning behind it. > > I'm not certain, but I believe that the cause of what you are seeing is > that this is the actual logic: Each *gateway* has permissions. If a > dialing rule is directed to a gateway, and the rule has permissions, the > permission is actually applied to the gateway. (It may also be applied > to the translation process. But after that, the permission is applied > to the separate act of routing the call to that gateway.) So one you > direct the Long Distance rule to Gateway A, every call directed to > Gateway A must have Long Distance permission. >
I think Scott already replied but I just wanted to clarify the question of gateways and permissions. Gateways (as seen by sipXecs admin) do not have permissions. Rules have permissions. Each gateway can appear in multiple rules. And different rules may require different permissions for the call through the gateway to succeed. 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 sipXecs IP PBX -- http://www.sipfoundry.org/
