Caller ID problem, not showing full entry from Asteridex.

[timg]

Setting up a new asterisk box with PIAF-Bronze 64 bit install, Sangoma A200 card, POTS lines only and Aastra 6757i phones. Have installed CallerID Superfecta module in FreePBX and it is working kind of.. I have Asteridex 4 installed also and listed as the first lookup source. I have entries in my asteridex database like the following: Smith, John (Cell). I was running PbxInAFlash 1.2 on an older box with the same asteridex database, dumped it to a file and imported back into the new version. When a call comes in and it gets a hit in Asteridex, it will only display the part of the entry before the "," so in this example it only shows Smith and then the number. This same entry worked before on my older set up. The asterisk log files show the complete entry but for some reason it's not making it to the phone. I have tried deleting the entry out of asteridex and re-entering as new but still get the same thing.

 

[timg]

Bump, Bump.

 

[timg]

Lorne, tried the test and it does indeed return the correct information. Here's what the log is showing.

[2011-01-12 11:02:47] VERBOSE[9716] pbx.c: -- Executing [cidlookup_1@cidlookup:1] Set("DAHDI/5-1", "CALLERID(name)=Grooms, Tim (Mobile)") in new stack
[2011-01-12 11:02:47] WARNING[9716] pbx.c: MSet: ignoring entry ' Tim (Mobile)' with no '=' (in cidlookup_1@cidlookup:1
[2011-01-12 11:02:47] VERBOSE[9716] pbx.c: -- Executing [cidlookup_1@cidlookup:2] Return("DAHDI/5-1", "") in new stack

 

[ronw]

I found this information at http://tools.ietf.org/search/draft-ietf-enum-cnam-05

5.
The CNAM data URI

RFC 2397 specifies the structure and parameters for the data URI as
follows

dataurl := "data:" [ mediatype ] [ ";base64" ] "," data
mediatype := [ type "/" subtype ] *( ";" parameter )
data := *urlchar
parameter := attribute "=" value

In order to distinguish the Calling Name data media type used within
this URL this document specifically registers with IANA the media
type "application/cnam".

Base64 does not include commas, so shouldn't they be removed?

Around line 300 in /var/www/html/admin/modules/superfecta/bin/callerid.php, add a comma in the preg_replace pattern match.

$first_caller_id = preg_replace ( "/[\";[B],[/B]']/", "", $first_caller_id);

 

[timg]

Ron,

This worked! The comma in the asterisk database worked just fine before I upgraded. Not sure what happened but it is working now. Many thanks!

 

[ronw]

Looks like this issue was resolved in superfecta version 2.0, but has resurfaced in one of the other updates. I am currently using version 2.2.3. The most current version is 2.2.4. I will upgrade my test box and see if the issue has been fixed.

Here's a brief list of the upgrades and changes that come with version 2.0 of caller ID Superfecta: The Module.

• No longer returns a "," for the white pages data provider. (Ticket #: 3)

 

[ronw]

OK, superfecta version 2.2.4 has again corrected this issue. The only difference is it prints the comma instead of removing it. While the fix may not be RFC 2397 compliant, it works and actually looks better with the comma.

To upgrade, follow the instructions at this link: http://pbxinaflash.com/community/threads/new-callerid-superfecta-2-2-4-the-module.4387/page-33 toward the bottom of the page at post #648.

 

[ronw]

I would have loved to get some answers to my questions above, but now that the problem system is patched ...

Lorne

I can provide some answers based on my tests.

Asterisk versions: 1.8.0, 1.8.1, 1.8.2, 1.6.2.14
FreePBX versions: 2.7.0.6, 2.8.0.4
CNAM source: Asteridex, White Pages

I guess a follow-up question would be:

If there has been no conversation at the Superfecta dev site about returning CNAM with or without commas, what changes made in version 2.2.4 fixed the issue?

 

[ronw]

Additional testing proves that the comma is displayed in the cnam when the call is incoming from google.

The complete cnam is not displayed when the call comes in from a sip trunk. Only data up to the comma is captured in the cdr and displayed on the phone.

So, superfecta 2.2.4 has not fixed the comma issue.