CommuniGate Quick Conference Application
Copyright (c) 2006, Stalker Software, Inc.

This proof of concept conference application is designed to provide a reservation-less type conference service served by CommuniGate Pro. Users with accounts on the CommuniGate Pro server can be assigned a permanent Conference ID by creating a numeric alias for the user's account. An alias is used to provide the assigned conference ID of the account, this is not intended to be the best way to provide this conference ID variable and mostly serves as an example or one way this could be done. I would not recommend this application on a production system that has active accounts and uses the CommuniGate Pro included gateway applications (gatewaycaller and gatewayincoming) only because the numeric aliases could create routing errors. For example, if your conference ID is a 10 digit number this could conflict with ENUM 10 digit phone numbers handled by gateway caller. This conference application can provide a dedicated conference service system on a standalone installation of CommuniGate Pro. Please obtain a valid license for your Communigate Pro server.

The file is distributed as a tar package that can be uploaded directly to a CommuniGate Pro PBX environment

The Application files are:

conf-simple.sppr - The main application
confhost.sppi - The application procedure that handles the leader
confuser.sppi - The application procedure that handles participants

This application can be run under the default pbx account or any special account you create. If you dedicate an account to this application the account should have the following privileges in CommuniGate Pro:

Access Rights
	Can Modify This Domain and its Accounts Settings
		Objects
			Can Access All Files
			Can Impersonate

Known application behavior issues

There is an intentional participant purgatory delay that occurs as participants are joined to the conference after the leader has joined and the purgatory check completes

If an incorrect leader PIN is provided the caller is treated as a participant this is because no error handling has been created for incorrect leader pins in the application at this point