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.
Some background... the point of the permissions on rules is to protect you from expensive calls you didn't want to pay for. Anyone who can get onto your LAN (and bad people _can_ get onto your LAN, at least sometimes) could make calls at your expense if you didn't protect them by requiring permissions for them. The site-to-site rule is designed to provide a way for you to configure that certain calls that can be completed purely as SIP calls (and thus have essentially zero incremental cost). Because they are 'free', there's little point in protecting them, so that rule doesn't enforce any permissions. What you've probably hit is a variation on http://track.sipfoundry.org/browse/XX-5882 The details are complicated (they have to do with the separation of decision making about routing and the permissions enforcement), but essentially doing either of two things can, under some conditions, cause problems: * Defining two different names for the same thing (giving the same gateway address two different names in sipXecs). * Leaving a gateway defined that is never used by any dial plan. It sounds like what you did is set up two rules that go to the same place but have different permissions requirements. Without your configuration files, I can't be sure how that caused the symptoms you see, but it's not too surprising. _______________________________________________ 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/
