Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Xml Lock option?

Hello,

I'm currently looking for a way to "lock" an xml file so that only one person can call into the admin trigger number and make a configuration change.

Any suggestions?

Should I make the trigger number busy on more then 1 call?

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Xml Lock option?

You need two files, one to hold current status, and one to use as a template for the keyword transform step.

The call flow looks like this:

1. call in

2. authenticate

3. read the xml file, and check locked status

4. if not locked goto step 7

5. play back that the file is locked, and optionally by whom

6. disconnect

7. lock the file by writting the same setting value for emergency, but changing the lock values

8. read the xml file, and playback the current emergency setting to the caller

9. ask if they want to change it

10. change the setting if required, then goto step 8

* You must set the ContactInactiveException handler, so you can free the lock when the caller hangs up.

Example XML documents below:

Not locked

    

          unlocked

          null

    

    

          false

    

Locked by aholloway

    

          locked

          aholloway

    

    

          false

    

XML Template file to use with the keyword transform step

    

          %lock_status%

          %locked_by%

    

    

          %emergency_status%

    

Message was edited by: Anthony Holloway - Corrected the XML document nodes

Anthony Holloway

Please use the star ratings to help drive great content to the top of searches.
3 REPLIES

Re: Xml Lock option?

You need two files, one to hold current status, and one to use as a template for the keyword transform step.

The call flow looks like this:

1. call in

2. authenticate

3. read the xml file, and check locked status

4. if not locked goto step 7

5. play back that the file is locked, and optionally by whom

6. disconnect

7. lock the file by writting the same setting value for emergency, but changing the lock values

8. read the xml file, and playback the current emergency setting to the caller

9. ask if they want to change it

10. change the setting if required, then goto step 8

* You must set the ContactInactiveException handler, so you can free the lock when the caller hangs up.

Example XML documents below:

Not locked

    

          unlocked

          null

    

    

          false

    

Locked by aholloway

    

          locked

          aholloway

    

    

          false

    

XML Template file to use with the keyword transform step

    

          %lock_status%

          %locked_by%

    

    

          %emergency_status%

    

Message was edited by: Anthony Holloway - Corrected the XML document nodes

Anthony Holloway

Please use the star ratings to help drive great content to the top of searches.
New Member

Re: Xml Lock option?

Thanks for the information.

Re: Xml Lock option?

Alternatively, you could just set the session limit on the trigger to 1.  that would ensure only one person could access it at a time.

but that's the lazy way.  my way nets you two additional benefits:

1.  You get to tell the caller the file is locked by another user and who

2.  You could implement a super user account that can steal the lock from another user.

Number 2 is also helpful in a pinch if for some reason the unlock failed and the file remains locked.

Anthony Holloway

Please use the star ratings to help drive great content to the top of searches.
308
Views
0
Helpful
3
Replies