Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Is there a limit to loop of a component

Discussion in 'CRM / Helpdesk / App Integration' started by kilo13, Sep 8, 2011.

Thread Status:
Not open for further replies.
  1. kilo13

    Joined:
    Dec 22, 2010
    Messages:
    14
    Likes Received:
    0
    I currently have a component with 0-9 wav prompts to match the persons numeric selection to be played back to them by going a count down loop. The first entry allows up to 7 numbers to be entered and replays with no problem however the second entry which consists of a 16 digit (credit card number) freezes on 9th number. I did a break up of the loop to eight numbers and then moved it to additional loop of another 8 numbers only to have it freeze and drop after looping to the second digit. Each time it equals 16 prompts replayed from the same component? This is in the previous version release and will try the newest build but not sure if there is a restriction to component calls.
     
  2. VAD_Support

    VAD_Support Active Member

    Joined:
    Aug 6, 2009
    Messages:
    690
    Likes Received:
    0
    Hi,

    The VAD generates VXML scripts as build output. Those VXML scripts are processed by the 3CX IVR. There is a limitation on the quantity of pages that the 3CX IVR is able to process in a single session (ie per call). That limit is 500 pages. When the VAD generates the output, it creates 1 or 2 pages for each component in release mode, and 2 pages in debug mode. So, using a loop with many components inside may cause that the call executes a lot of pages, and reach that limit.

    There are 2 things that you can do to try to avoid this:
    1) Build the project in release mode. This way it uses less pages. But maybe this is not enough.
    2) Use the recently added feature that allows you to play a wav file creating the name with an expression. For example, if you are using a big conditional component with 10 branches, one for each wav file, it can be simplified by using a single Prompt Playback component with a file name created with an expression. This will pretty sure solve your problem.

    Hope the information helps.

    Regards,
     
  3. kilo13

    Joined:
    Dec 22, 2010
    Messages:
    14
    Likes Received:
    0
    Ok I will see what the dynamic does.
     
Thread Status:
Not open for further replies.