Registering with a provider with a register=yes in the [peer] section is convenient for small installations when only one user is registering with that domain since all the info usually is there already (username, secret, host,...), but what if you have 20, 50, 100 users or accounts to register. In that case, the old style register is convenient since it is nice to have things presented in some kind of table (row, column) form, and all the registrations can be maintained in an #include file or a database.
Overloading the register syntax with more params naturally is a drawback, but can actually be simplified by only using the [peer] name instead of the proxyhost/domain and port and eliminate duplication that way.
Lastly, the existing register line syntax (without hostname portion) could be moved into the [peer] section to associate it directly with the peer and still allow multiple account registrations by duplicating the line.
Kevin Walsh wrote:
Karl Brose [EMAIL PROTECTED] wrote:
There is also the option of expanding, or better redesigning, the [peer] sections with proper and logical configuration options and adding a register=yes flag.
I would prefer to see a "register = yes" directive in the "type = peer" sections of both sip.conf and iax.conf, rather than the current method of using a separate "register => whatever" directive. The current method could be maintained for backward compatibility, of course.
Both have been tried, and have their pro's and con's
I see the pros as keeping all of the config in one place, and allowing further options to be added without over-complicating the "register" syntax. What do you see as the cons?
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
