On Sat, May 30, 2020 at 3:15 PM roger <ro...@beardandsandals.co.uk> wrote:
> > On 30/05/2020 16:46, Roger James wrote: > > ttp://lists.digium.com/mailman/listinfo/asterisk-dev > <http://lists.digium.com/mailman/listinfo/asterisk-dev> > >> > I am doing that at the moment. I have increased the retry timeouts and > reduced rhe number of retries to zero to damp down. the noise level. > > I have tracked down to sorcery_object_load. My registration object is > constructed from two files, the second of which overrides the transport > type. It looks like asterisk send out the registration request as part of > the file reading (for want of a better term) process. This results in two > registration "attempts" being made. One when the main file is read, the > second when the file that overrides the transport is read. It have not yet > determined whether the second attempt makes it out to the wire. > This isn't how the configuration parser really works. Everything is combined when the .conf file and all included are read in into one category/option/option value assortment. That configuration is then applied. There's no multiple stages where the first .conf is read in, applied, then includes, etc. Are you sure that your "override" is configured properly to be templated into the right thing? What is the complete contents of it? -- Joshua C. Colp Asterisk Technical Lead Sangoma Technologies Check us out at www.sangoma.com and www.asterisk.org
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
