Bug #50
Provide total latency for currently selected data sources in debug window
| Status: | Closed | Start: | 05/09/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | jacobsj | % Done: | 100% |
|
| Category: | - | |||
| Target version: | Caller ID Superfecta v 2.0.0 |
Description
Provide total latency for currently selected data sources in debug window. This will help the user decide if they are delaying their inbound calls to greatly with the combination of providers they have selected.
History
Updated by tshif over 2 years ago
- Target version changed from Caller ID Superfecta v 2.1.0 to Caller ID Superfecta v 2.0.0
Jeremy - if this doesn't cost to much time - it would be a great tool for the users when setting this module up. If you don't think it fits in ver 2.0.0, just assign it back to the "Future Releases" Target Version.
Updated by tshif over 2 years ago
- Subject changed from Provide total latency for currently selected data sourced in debug window to Provide total latency for currently selected data sources in debug window
Updated by jacobsj over 2 years ago
- Status changed from New to Closed
Rather than time the whole thing because the debug isn't stopping after the first result like it would under normal call conditions. I put in the time to the first result, which would be the result that is returned. It should give the user an idea of how long the script will take to get them an answer for Caller ID though.
Updated by tshif over 2 years ago
- % Done changed from 0 to 100
Test / Validate debug timer. Works as expected.
Updated by tshif over 2 years ago
- Status changed from Closed to Assigned
- % Done changed from 100 to 90
Here is the display: (only three sources selected). Timeout set to 3.
Timeout for source ADDRESSES not working. Test performed on current Trixbox CE.
Test a phone number against the selected sources.
Phone Number:
Debugging Enabled, will not stop after first result.
Found valid US npa: 760-494-1154
Searching Yellow Pages ... not found
result took 3.0034 seconds.
Searching Addresses ... not found
result took 40.0108 seconds.
Searching Google ... not found
result took 3.0032 seconds.
Searching Telco Data ... not found
result took 3.0043 seconds.
Returned Result would be:
result took -1,241,912,555.1422 seconds.
Updated by tshif over 2 years ago
Uninstall/reinstall corrects negative total time.
Trixbox is definitely having problems with the search timeout values. Heres another example from trixbox:
Test a phone number against the selected sources.
Phone Number:
Debugging Enabled, will not stop after first result.
Found valid US npa: 760-494-1154
Searching White Pages ... ,
result took 3.0045 seconds.
Searching Yellow Pages ... not found
result took 3.0036 seconds.
Searching PhoneSpamFilter ... not found
result took 40.0117 seconds.
Searching Addresses ... not found
result took 40.0110 seconds.
Returned Result would be: ,
result took 3.0045 seconds.
Updated by tshif over 2 years ago
- Tracker changed from Feature to Bug
Updated by jacobsj over 2 years ago
- Status changed from Assigned to Closed
- % Done changed from 90 to 100
Updated by tshif over 2 years ago
Debug mode results timer no longer shows negative numbers. Function works as expected.
Updated by tshif over 2 years ago
- Status changed from Closed to Assigned
FAILS QA:
Negative latency numbers displayes when no source returns result - current version, under TrixboxCE.
Debugging Enabled, will not stop after first result.
Found valid US npa: 760-494-1154
Searching Addresses ... not found
result took 0.3792 seconds.
Returned Result would be:
result took -1,241,935,252.8841 seconds.
Identical query with identical single source on PABX does NOT produce negative numbers.
Updated by tshif over 2 years ago
- % Done changed from 100 to 90
Updated by tshif over 2 years ago
- Status changed from Assigned to Closed
- % Done changed from 90 to 100
Sorry! Retest on Trixbox yields no errors. Apologies for false alarm.