This ensures that all xml configuration files are re-generated in the event of system changes. Dial plans and trunk changes are usually not an issue. When you make system changes (domain aliases, nat changes, etc.) or system updates/upgrades, it is desirable to send the profiles, which can prompt a restart/reload of many services, but then start using the newly generated config files.
On Wed, Jul 6, 2011 at 10:14 PM, Roman Gelfand <[email protected]> wrote: > It appears that after sending profiles, it worked. What is the purpose > behind sending profiles? > Thanks, > On Tue, Jul 5, 2011 at 5:47 PM, Roman Gelfand <[email protected]> wrote: >> >> I have set up a dial plan to work with unmanaged gateway. All call are >> to be routed to sbc. I created custom dial plan that uses custom >> permission, enabled by default, and associated it with the unmanaged >> gateway. The dial plan itself expects any number of digits and sends out >> matched suffix. When making a pstn call, it appears that what reaches sbc >> is call attempt to extension 204 and busy signal. >> >> Any help is appreciated. >> >> Thanks in advance > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.326.5325 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
