03:52.43 | *** join/#asterisk-scf leedm777 (~Adium@user-69-73-1-116.knology.net) |
12:15.03 | *** join/#asterisk-scf kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
13:42.43 | *** join/#asterisk-scf wesphillips (~wphillips@64-19-240-7.caprock.net) |
14:12.07 | *** join/#asterisk-scf leedm777 (~Adium@nat/digium/x-bqjbmwyhdedspwmu) |
14:59.45 | *** join/#asterisk-scf dms (~Adium@nat/digium/x-zacguuillyyesypa) |
15:24.34 | *** join/#asterisk-scf putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
16:48.10 | *** join/#asterisk-scf leifmadsen (~Leif@asterisk/documenteur-extraordinaire/blitzrage) |
16:58.41 | wesphillips | On the "Sip Session Manager Configuration" there is a reference to a configuration file. Does this mean that there will need to be conf files for the SCF as well as for components built on the framework? |
16:59.08 | wesphillips | s/Configuration" /Configuration" wiki / |
17:01.37 | putnopvut | wesphillips: configuration is something that's in flux at the moment. The end goal is that the only required configuration files would be for Ice-related items. The application-level configuration would be pushed to the component over Ice. Now, this configuration could be supplied via a config file, database, or whatever. |
17:02.10 | putnopvut | at the moment though, there is just a single Ice configuration file that contains both Ice and application-level options in it. |
17:02.20 | wesphillips | ok |
17:02.25 | wesphillips | thank you for explaining it |
20:49.39 | *** join/#asterisk-scf pabelanger (~pabelange@50.22.5.41-static.reverse.softlayer.com) |
20:50.18 | *** join/#asterisk-scf kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
21:41.43 | *** join/#asterisk-scf kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
22:12.08 | *** part/#asterisk-scf wesphillips (~wphillips@64-19-240-7.caprock.net) |
23:20.12 | *** join/#asterisk-scf leedm777 (~Adium@nat/digium/x-chdbcbgphdqkzpcw) |