[asterisk-dev] [Code Review] Remove need for registrationstrings in sip.conf

Nick Lewis Nick.Lewis at atltelecom.com
Mon Jun 21 05:10:03 CDT 2010


>Register=yes does not work with realtime.

Similarly peer callbackextension didn't previously so there's no
regression. I assume the register string works for realtime so as a
minimum I will document this in sip.conf.sample

>The configuration in sip.conf is fast going down 
>to something we can't document, since you're 
>expanding type=peer beyond what we can explain...
>I never liked this hybrid and think this is just 
>going from bad to worse...

How about "If you want an outbound registration for the peer then set
register=yes" as a documented explanation?

Some of us who have been involved with asterisk for a while may forget
just how alien and archane the outbound registration mechanism is to new
users. Even small steps to improve it are long overdue. I agree that
type=service would be better as it represents a new architecture that
also addresses a whole load of other related weaknesses such as peer
matching and DDI but "Le mieux est l'ennemi du bien"

>We need to seriously work with building a product that can be
explained, 
>documented and taught in classes. Not patch, patch, patch

We only have so many hours in the day. I recall you stating on this very
subject "Well, I strongly think we should work on this architecture.
Hopefully I'll get some time for it during christmas." Wisely over
christmas you chose to have a life instead

>and add stuff that doesn't work together. Like the TLS 
>stuff that breaks the domain concept totally. Bad 
>architecture. Desperate need for checkbox items, but 
>not a good product solution. Nothing we can be proud of.  
>Grrr...

Baiting the bear was not the sole purpose of producing this patch

>Yes, it's thunder and rain outside ;-)

It must be the start of Wimbledon

-- N_L

_____________________________________________________________________
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