cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
78
Views
0
Helpful
0
Comments
cdnadmin
Community Member
This document was generated from CDN thread

Created by: null on 23-07-2007 10:20:35 AM
This is just a general query regarding the callflow.xml file that is utilised onto the application server after a deployement of an Audium project.

Once the application is developed, it is still possible for a user without the Audium project files to make changes to the xml file and affect the application logic that has been developed. [i:293e5cf6eb]Is it possible to delete the callflow.xml file once it has been deployed onto an application server?[/i:293e5cf6eb]

Essentially, is there some way to persist the application once it has been deployed and loaded into the callservices cache, so that even if call services or the server is restarted, the process does not require the Callflow.xml file anymore?

Subject: RE: Callflow.xml Requirement
Replied by: null on 25-07-2007 08:57:02 PM
Hi Steve,

(1) It is possible to delete the callflow.xml file once the voice application has been deployed onto an application server.

(2) For the case the server is restarted, the Call Services does require the Callflow.xml file to restart the application.

(3) When you run application admin commands (releaseApp and deployApp), the Call Services does require the Callflow.xml file to reload the application.

(4) When you run application admin commands (suspendApp and resumeApp), the Call Services does not require the Callflow.xml file to resume the application.

Regards,

Hong

Subject: RE: Callflow.xml Requirement
Replied by: null on 26-07-2007 10:20:11 AM
Hi,

Thanks your reply - I just want to clarify if there is definately no way to persist an application once it has been deployed to the application server. A concern would be if a developed application is deployed onto the server - a user could modify the callflow and influence the intended application flow.

Is there any way in which this may be prevented? - i.e. by somehow forcing callservices to not load again from the callflow.xml file (on a system or callservices restart) or some setting to prevent the modification of the callflow by anyone (including admin level users) It would be handy if there is a feature which does not require the application to be generated from the callflow.xml each time it is to be loaded.

Essentially, we're asking is it possible to protect the callflow once it has been deployed from Audium / CVP VXML Studio?

Thanks

Subject: RE: Callflow.xml Requirement
Replied by: null on 27-07-2007 09:18:45 PM
Hi Steve,

(1) If you do not want someone else to modify the callflow.xml once the application has been loaded, you can remove it and keep it on a safe place.

(2) There is no way to persist an application once it has been deployed to the application server. Based on our current Call Services, you can change the callflow.xml anytime without using Call Studio before the application is loaded.

Regards,

Hong

Subject: RE: Callflow.xml Requirement
Replied by: null on 27-07-2007 10:23:53 PM
Hi Steve,

(1) Could you please provide us more information about what you are actually trying to accomplish. Maybe we could provide a better recommendation for you later on.

(2) We do not recommend that you remove callflow.xml just because it might be confusing for someone else when the voice application fails to load on next server restart.

Regards,

Hong

Subject: RE: Callflow.xml Requirement
Replied by: null on 30-07-2007 07:33:11 AM
Hi Hong,

We were considering a managed services setup where a developed application is deployed onto an external application server - i.e. a server that is not maintained internally. In this scenario, there is the assumption that there are no more changes required to the application.

Since the application is deployed onto the application server that is not maintained internally - we just want to assure that the application that is deployed onto the server does not change.

Essentially, consider the scenario where a developed application is deployed onto a customer's CVP setup - in this case, we do not have control over how the system is managed but by the same token we do not want the customer making any changes to the callflow that has been developed.

Could you provide any recommendations on any way to acomplsh this - if possible?

Thanks & Regards

Subject: RE: Callflow.xml Requirement
Replied by: Cheng-Dar Yang on 31-07-2007 03:12:45 PM
Hi

Although various methods may exist on the OS level in regards to protecting the callflow.xml, the Audium Call Services itself does support a built-in security mechanism for loading/reloading of the voice application.

One simple way to protect callflow.xml is to mark the application as read-only (with exception to log folders). This won't prevent an determined individual with access to the system to modify the application, but it should prevent accidents. This is really a broader access control issue that goes beyond Audium itself.

However, we acknowledge the importance of application security and have entered an enhancement request in our internal issue-tracking system with an ID of CSCsj88084. Your specific request and use case information have also been added to the description of this issue. This issue will be reviewed by the development team for incorporation into future releases. Please refer to this ID in the future to check the status of this request.

Regards,
Cheng
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links