You can have a siptrunk setup and receive calls without a dialplan entry. So I don't see why the dialplan entry would be updated unless you deliberately intend to send calls to that gateway, like any other gateway in sipx. I don't think you should have to press APPLY twice to get the <itsp-account> to be included in the sipxbridge config file. Is hitting the APPLY twice new (because I never had to up through 4.2.1)?
On Wed, Oct 27, 2010 at 8:27 AM, Laurentiu Ceausescu <[email protected]>wrote: > Hi, > > In order to add a SIP Trunk ... > - added 'sipTrunk' in 'Name' field; > - checked 'Use built-in SIP Trunk SBC'; > - chose 'VoIP User' from a 'Use provider template' combox; > - pressed 'Apply' button. > After that I noticed that sipxbridge.xml file is unchanged. > > This is because in GatewayContextImpl.storeGateway(Gateway gateway) > method the code looks like ... > boolean isNew = gateway.isNew(); > // Replicate occurs only for update gateway > if (!isNew) { > m_dialPlanActivationManager.replicateDialPlan(true); > SbcDevice sbc = gateway.getSbcDevice(); > if (sbc != null) { > sbc.generateProfiles(sbc.getProfileLocation()); > sbc.restart(); > } > } > > So, only if I press twice the 'Apply' button, the sipxbridge.xml file is > changed (populated with '<itsp-account> tag). > > Does anyone know the reason for replicating sipxbridge.xml and dial plan > files only when gateway is updated (not also on gateway creation)? > Do you think we should change this and to replicate sipxbridge.xml also on > gateway creation? > > Thanks, > Laurentiu > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- ====================== 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
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
