Park Call Max Timeout - park_CID.agi (360 seconds)
Posted: Wed Sep 13, 2023 10:55 amHi,
We sometimes have a need to park a client for a long period of time - sometimes in excess of 10 minutes.
When calls are parked through the agent screen by clicking the 'PARK CALL' button, the call is disconnected at 360 seconds of park time exactly (6 minutes), each and every time. I have traced this back to the park_CID.pl agi script. There is a sleep command for exactly 360 seconds. To verify this is the culprit, if you manually edit/change this value in the agi script sleep(360) then perform another test call and park it, the call will disconnect exactly at this modified sleep interval. For the avoidance of doubt, it is nothing to do with any RTP timeouts, SIP session timers, etc.
My question is... Is it safe to just increase this sleep value in park_CID.agi to the maximum time we would need to park a customer? I understand you may end up with orphaned calls where a customer is stuck listening to hold music if the agent has somehow disconnected from the conference (poor network, PC issue, agent error, etc) and thus having a larger sleep period could mean higher call costs incurred in these circumstances. Are there any other considerations? Does anyone know why this value was set at 360? Is it just that it is general consensus not to leave a customer on hold for such a long duration (unavoidable in my case)?
Many thanks.
K.
We sometimes have a need to park a client for a long period of time - sometimes in excess of 10 minutes.
When calls are parked through the agent screen by clicking the 'PARK CALL' button, the call is disconnected at 360 seconds of park time exactly (6 minutes), each and every time. I have traced this back to the park_CID.pl agi script. There is a sleep command for exactly 360 seconds. To verify this is the culprit, if you manually edit/change this value in the agi script sleep(360) then perform another test call and park it, the call will disconnect exactly at this modified sleep interval. For the avoidance of doubt, it is nothing to do with any RTP timeouts, SIP session timers, etc.
My question is... Is it safe to just increase this sleep value in park_CID.agi to the maximum time we would need to park a customer? I understand you may end up with orphaned calls where a customer is stuck listening to hold music if the agent has somehow disconnected from the conference (poor network, PC issue, agent error, etc) and thus having a larger sleep period could mean higher call costs incurred in these circumstances. Are there any other considerations? Does anyone know why this value was set at 360? Is it just that it is general consensus not to leave a customer on hold for such a long duration (unavoidable in my case)?
Many thanks.
K.