On Wed, 2010-04-21 at 12:07 -0400, Mossman, Paul (Paul) wrote: > Bob wrote: > > Using custom dialplans that require permissions to link sites > > will result in failing calls in many cross-site transfer > > scenarios. To prevent admins from falling into this > > non-obvious trap, a site-to-site dialplan type has been > > created. This type of dialplan ensures that permissions > > cannot be set by mistake. > > So just to confirm... A Permission-less Custom rule, which is > otherwise configured the same as a Site-to-Site rule, is functionally > equivalent to that Site-to-Site rule? > > > How do so Site-to-Site rules work when the calling site is a TLS Peer? > Wasn't TLS Peers added in order to allow remote sites to use dial > rules that require permissions?
All dialing rules control what happens with outbound requests. The TLS Peer functionality (which at this point applies only to ITSP connections through sipXbridge, but is slated to be added to the proxy) adds permissions to an inbound call. Those permissions enable that call to then have permissions needed for dial plans that require them. Once TLS support in the proxy is complete, it may often be appropriate to add an option to site-to-site rules to require that they use TLS. Does that answer your question? _______________________________________________ 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/
