[asterisk-dev] Peer matching architecture

Nick Lewis Nick.Lewis at atltelecom.com
Thu Dec 17 03:30:48 CST 2009

>Then remove it a release after that, since it's no longer "new"
with the implied default value changed to "yes" no doubt? Perhaps it
needs three release stages (i) default "no", (ii) default "yes"
(deprecated "no" setting), (iii) implied "yes"

>type=service that implements the callbackexten stuff properly and
deprecates register=
I think that many are going to be confused and specify type=trunk when
they want this functionality. It may not be 'right' but the term "sip
trunking" has come to encompass services such as these.

Apart for these minor issues I am very much in favour of the proposal


This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Control Centre.
Disclaimer of Liability
ATL Telecom Ltd shall not be held liable for any improper or incorrect use of the  information described and/or contained herein and assumes no responsibility for anyones use  of the information. In no event shall ATL Telecom Ltd be liable for any direct, indirect,  incidental, special, exemplary, or consequential damages (including, but not limited to,  procurement or substitute goods or services; loss of use, data, or profits; or business  interruption) however caused and on any theory of liability, whether in contract, strict  liability, or tort (including negligence or otherwise) arising in any way out of the use of  this system, even if advised of the possibility of such damage.

Registered Office: ATL Telecom Ltd, Fountain Lane, St. Mellons Cardiff, CF3 0FB
Registered in Wales Number 4335781

All goods and services supplied by ATL Telecom Ltd are supplied subject to ATL Telecom Ltd standard terms and conditions, available upon request.

More information about the asterisk-dev mailing list