Response time delay and log research
Posted: Tue Jul 12, 2011 1:58 am
One of our clients submitted a batch of 400 calls today (7/11). Actually each call is submitted individually so that we can have better control over the retry process. A limit of 25 concurrent calls are submitted at a time to prevent too many calls from being concurrently processed and overwhelming either the Plum system or our web service. The client reported that they received over 100 calls from their callees that there was long delays between the time they answered the call and the time they heard anything, or hung up because the system did not say anything. Unfortunately they did not collect the phone numbers or other identifying information so I’m unable to research a specific call. I did a spot check of call logs that we keep and that I could find in Plum’s logs without any success on finding evidence of the issue. The majority of calls were made between 11am and 12 Eastern time, some before and more afterward as well.
So my first question looking for help on researching this kind of issue. The first issue I run into is that the detailed logs only support the last 100 calls on a given account. Of course that limits the number of call records that I can research. This will get even worse as we bring more clients with larger call volumes on line. Any suggestions on research would be helpful.
Second, the detailed call log does not seem to have the level of detail needed to track time delays. In fact the limited time stamps in it seem a little confusing as it indicates 3 voice prompts are prompts are played and then a second later 2 more voice prompts are played. Clearly all three voice prompts could not be played in a single second so I’m not sure what the call log represents. Maybe this is just a lack of understanding how to read the log.
Third, in the log what would really help is knowing what time the fetch of VoiceXML was call and returned. This way if the delay is a result of a slow response by our servers we could tell this clearly in the log.
Fourth, maybe a long shot question but do you know if the Plum Voice systems were experiencing any system issues around this time that could have caused they delays?
Thanks for any feedback and help you can offer,
Rich
So my first question looking for help on researching this kind of issue. The first issue I run into is that the detailed logs only support the last 100 calls on a given account. Of course that limits the number of call records that I can research. This will get even worse as we bring more clients with larger call volumes on line. Any suggestions on research would be helpful.
Second, the detailed call log does not seem to have the level of detail needed to track time delays. In fact the limited time stamps in it seem a little confusing as it indicates 3 voice prompts are prompts are played and then a second later 2 more voice prompts are played. Clearly all three voice prompts could not be played in a single second so I’m not sure what the call log represents. Maybe this is just a lack of understanding how to read the log.
Third, in the log what would really help is knowing what time the fetch of VoiceXML was call and returned. This way if the delay is a result of a slow response by our servers we could tell this clearly in the log.
Fourth, maybe a long shot question but do you know if the Plum Voice systems were experiencing any system issues around this time that could have caused they delays?
Thanks for any feedback and help you can offer,
Rich