Bug #350
CNAM shows up as (N/A) when using Trunk provided lookup source
| Status: | Closed | Start: | 09/01/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | 10/11/2010 | |
| Assigned to: | lgaetz | % Done: | 100% |
|
| Category: | - | |||
| Target version: | Caller ID Superfecta v 2.2.4 Maintenance Release |
Description
On first installing CID superfecta and setting up the trunk provided lookup source, I noticed lots of calls showing up with a CNAM of "(N/A)" (without quotes). The trunk provided CNAM is parsed from the output of "core show channel [channel]" which gives an output like this:
-- General --
Name: Zap/4-1
Type: Zap
UniqueID: 1283452929.4253
Caller ID: sanitized
Caller ID Name: (N/A)
DNID Digits: (N/A)
State: Up (6)
Rings: 0
snip
If the CNAM is not available asterisk shows "(N/A)" which is faithfully copied by the trunk provided lookup source and passed as CNAM to superfecta.
Temperary solution:
Add "(N/A)" (without quotes) to the list of ignore keywords for the trunk provided options.
Permanent Solution:
Add "(N/A)" (without quotes) to the code such that the trunk provided source knows to look for them without being specified in the ignore keywords list.
History
Updated by lgaetz over 1 year ago
- Tracker changed from Support to Bug
- Subject changed from CNAM shows up at (N/A) when using Trunk provided lookup source to CNAM shows up as (N/A) when using Trunk provided lookup source
Updated by lgaetz over 1 year ago
I committed a change to the trunk provided code for another issue, and while I was at it I added "(N/A)" to the list of default ignore words. This is not a perfect solution because the end user can always delete it.
Updated by tshif over 1 year ago
- Status changed from New to QA Testing
- Assigned to set to tshif
- % Done changed from 0 to 20
Updated by tshif over 1 year ago
- Target version set to Caller ID Superfecta v 2.2.4 Maintenance Release
Updated by tshif over 1 year ago
- Due date set to 10/11/2010
- Assigned to changed from tshif to lgaetz
- % Done changed from 20 to 40
lgaetz - as you detected, I did get a little confused about the two updates ofr different reasons. I have restored the version with the first update to the live update repo. I have tested this version as well with good results.
DO you feel its ready to release this version into live update?
Updated by lgaetz over 1 year ago
Updated by tshif over 1 year ago
- Status changed from QA Testing to Closed
- % Done changed from 40 to 100
Accepted into live update as of now.