On Sat, 23 Apr 2016 22:45:32 +0100 Julian Beach <jb_s...@trink.co.uk> wrote:
> Hello Phil, > > I have a couple of lines with A&A, and I have not been having any > problems recently. When I have had similar problems in the past, it > has been an issue with the SIP config. I originally had a number of > contexts set up in sip.conf to handle the lines coming in (such as > [aa-line1], [aa-line2]) each with their own username and password > settings. The type=user setting was critical, because all the calls > came from the same IP address, and using type=peer caused matching > problems which resulted in authentication failures. This got too > complex to manage once I added in all the IP addresses A&A calls might > come in from. so I simplified the setup. > > I now have just one context in sip.conf to handle incoming A&A calls, > with the same username for all lines, and type=peer. Calls are then > sent to extensions.conf, where the calls are directed to the correct > call-handler for the line based on the CID. Here is the setup in > sip.conf for A&A calls: Actually, this is now sorted. It turns out the latest recommended configs on the A&A wiki had peer vs. user confusion. On correcting this, all was well. -- Phil Reynolds mail: phil-aster...@tinsleyviaduct.com Web: http://phil.tinsleyviaduct.com/ -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users