Skype For Asterisk Frequently Asked Questions (SFAFAQ)
===============================================================================
 1. I'm trying to use the Skype account that I've always used with SFA and
    'skype show users' shows that it is Logged Out!

    SFA cannot be used with an un-managed Skype account. It can only be used
    with accounts created from within the Skype Business Control Panel which
    can be found at http://skype.com/business/

	AS A WORKAROUND one can forward their non-BCP account to a BCP-created
	account with the call forwarding rules found in the normal Skype client.
	See https://support.skype.com/faq/FA507/How-do-I-activate-call-forwarding
	for details on setting up call forwarding.

 2. I just created an account to manage my Business Control Panel and I can't
    get that account to log in via SFA.

    Only Skype accounts that are actually created from inside the Skype
    Business Control Panel can be used. The account that was created to admin
    the BCP was not created from inside the BCP, so it will not work with
    SFA. Inside the BCP, go to Add Members and click "Create a Business
    account" to create an account that can be used with SFA.

 3. I just invited someone to join my BCP using email addresses or existing
    Skype names and they won't log in via SFA.

    The only Skype accounts that can be used with SFA at this time are those
    that are created via the "Create a business account" section in the Skype
    Business Control Panel.

 4. I want to be able to use my existing Skype account with Skype For Asterisk!

    Me too. This limitation is controlled by Skype and isn't something that
    Digium can do anything about. Luckily, Skype also agrees that this policy
    should be changed and they are looking into ways that existing users can
    become managed users under the Business Control Panel.

 5. When chan_skype.so attempts to load, I get an error similar to:
       ERROR[1702]: core.cpp:1553 sfa_startup: Skype engine failed to start.

    The skyhost binary (which shows up in the process list as skypeforasterisk)
    failed to start. This could be because a previous instance of this binary
    is running and was not properly shut down. Since any new instances try to
    bind to the same port, they fail. If 'ps aux|grep skypeforasterisk' returns
    any skypeforasterisk processes when Asterisk is not running, kill them and
    restart asterisk.

    Another reason for failure could be that disable_tcpauto is set to no (the
    default) and can not bind to ports 80 and 443 due to asterisk running as
    a non-root user or other services being bound to those ports.

    Failure can also occur if the engine_directory is set to a directory which
    is mounted with the 'noexec' flag or to a directory where the user does
    not have execute permission.

 6. I am running Asterisk 1.4 < 1.4.25 or Asterisk 1.6.0 < 1.6.0.6 or Asterisk
    1.6.1 < 1.6.1.5 and Asterisk crashes when I make a call or things just
    aren't working right.

    We know. That is why the README files all state the minimum versions of
    Asterisk that are required for Skype For Asterisk. The numbers were not
    chosen arbitrarily. Bad things will happen if Skype For Asterisk is
    used with older releases of Asterisk.