<div dir="ltr">> What we want to have is a fully automated process. Say someone insert a new skype id remotely, and wish to add this as a new skype channel.<br>> The automated process will grab the authentication information, create a startup script for it, then load the new skype interface. Now, if during the <br>
> skype login for this new user, it got a "P2P connect error" as I mentioned, then all the existing skype interfaces will stop working too. <br>><br>><br>> IF you could possibly offer a configuration parameter for it, that'll be greatly appreciated.<br>
><br><br>at least this is a use case :).<br><br>Please open a Jira request for feature on <a href="http://jira.freeswitch.org">jira.freeswitch.org</a><br> <br>><br>><br>> Yes, that's exactly the problem I got. "reload mod_skyopen" will load the new interface, but "sk_reload" doesn't.<br>
><br><br>sk_reload *must* load the new interface.<br>Please open a Jira bug for this one, with full documentation, as per <a href="http://wiki.freeswitch.org/wiki/Skypopen#How_To_Report_BUGS_and_Feature_Requests">http://wiki.freeswitch.org/wiki/Skypopen#How_To_Report_BUGS_and_Feature_Requests</a> .<br>
<br> <br>><br>><br>><br>>><br>><br>> Yes, what you just wrote is what I was trying to convey, "probably the "good" settings are stored in the skype configuration directory by now"<br>
><br>><br>> Yes. This means that maybe your default skype configuration template may require some minor adjustments?<br>><br><br><br>Why this? What you mean? The configuration directory will be populated with authentication and connection information after the first successful run. No way in my knowledge to prepopulate it. First run may take time to connect and authenticate. Further runs will be quicker. It probably use a peer2peer protocol to discover its path to an authentication server. Anyway, its proprietary skype stuff we're not supposed to mess with.<br>
<br>-giovanni</div>