[asterisk-dev] Peer matching architecture

Nick Lewis Nick.Lewis at atltelecom.com
Mon Dec 21 05:54:53 CST 2009

> For registration matching - it is not that easy. You know 
> many ITSP require the PBX to register, but they will send 
> the DID in the RURI (instead of the registered username) - 
> so this must still be possible to use, also with new peer 
> types. (of course this will not allow anymore to
> differentiate between multiple registrations to the same 
> ITSP).

Rather than using a did=yes parameter for these ITSPs why 
not simply use the existing peer type that provides plain 
IP matching i.e.


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