This occurs with setvar, allow/disallow, and permit/deny. In these cases, you can add multiple values separated by semicolons. Some options in sip.conf are OK to have multiple entries, but in a real-time database, Only one column is available. Options (column names) that not offered in sip.conf are ignored. For instance, a 1.6 version of Asterisk would not use the “cancallforward”, or ‘restrictcid’, or ‘mask’, or ‘qualify’, or “musiconhold” columns, but might require ‘mohinterpret’, ‘mohsuggest’, etc. It is easily possible that different versions of Asterisk will require different tables. The ‘name’ field must also be present to hold equivalent of the in the sip.conf file. Exceptions to this are ‘regserver’ and ‘regseconds’, which the channel driver’s realtime routines use for internal book-keeping. You do not have to have all option names defined in your table you only have to define those columns you actually use in sip.conf. Note: General principles: the column names in your database table correspond to the option names in sip.conf. Note: You can use any table name you wish, just make sure the table name matches what you have the family name bound to. Note: Values in sip.conf or iax.conf like in older versions of * are no longer used.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |