[Home]

Summary:ASTERISK-07089: If CallerID name contains single quote Asterisk answers call but doesn't send it anywhere
Reporter:caribou7 (caribou7)Labels:
Date Opened:2006-06-04 02:23:42Date Closed:2006-06-04 16:32:15
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) callerid_single_quote.txt
Description:When using a SPA-3000 to receive incoming calls, sometimes the CallerID name field contains only one quote.  Asterisk correctly identifies the problem but makes no attempt to work around it, instead simply answering the call, holding the line open a few seconds, and hanging up.  I would think that if Asterisk can identify the problem, it should be able to more gracefully handle it.

****** ADDITIONAL INFORMATION ******

Before I begin please note I am not a programmer but I am going to describe this as best I can.  I am using a Sipura SPA-3000 to receive calls.  It appears that the phone company sometimes sends quoted strings in the Calling Name field.  For whatever reason, perhaps a Sipura bug or perhaps the phone company is sending it this way, the call comes into Asterisk showing this in a SIP debug:

From: "Grand Rapids M <sip:6165555555@192.168.0.200>;tag=19c720c63634095bo1
(Phone number has been munged but otherwise this is exactly as shown.

Further down it shows this:
Jun  4 00:55:17 WARNING[2883] chan_sip.c: No closing quote found in '"Grand Rapids M <sip:6165555555@192.168.0.200>;tag=19c720c63634095bo1'

Which means that Asterisk is identifying the problem, but not working around it.  The next line says this:

Jun  4 00:55:17 NOTICE[2883] chan_sip.c: From address missing 'sip:', using it anyway

And still further down, it shows this:

Jun  4 00:55:17 DEBUG[2883] chan_sip.c: Checking SIP call limits for device
Jun  4 00:55:17 WARNING[2883] chan_sip.c: No closing quote found in '"Grand Rapids M <sip:6165555555@192.168.0.200>;tag=19c720c63634095bo1'
Jun  4 00:55:17 WARNING[2883] chan_sip.c: Huh?  Not a SIP header ("Grand Rapids M <sip:6165555555@192.168.0.200>;tag=19c720c63634095bo1)?
Jun  4 00:55:17 VERBOSE[2883] logger.c: Reliably Transmitting (NAT) to 192.168.0.3:5061:
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.0.3:5061;branch=z9hG4bK-1bc90cb2;received=192.168.0.3
From: "Grand Rapids M <sip:6165555555@192.168.0.200>;tag=19c720c63634095bo1
To: <sip:s@192.168.0.200>;tag=as256207c0

The call is answered, but there is dead silence, and after a few seconds it disconnects.

I am using FreePBX and discussed this with the developer in the IRC channel.  He said to be sure to let you know that I have a s exten in [default] and it's not hitting that. I am attaching a more complete snip from the log so you can hopefully see the problem.
Comments:By: caribou7 (caribou7) 2006-06-04 02:29:28

I only meant for the attached log file to be private, not the entire bug report!
By: Jason Parker (jparker) 2006-06-04 11:59:03

I don't think individual files can be set as private, actually.  Do you want to post a private note with that information, and we can delete the file, and make this bug public?
By: caribou7 (caribou7) 2006-06-04 13:11:18

How do I add a private note?
By: Serge Vecher (serge-v) 2006-06-04 16:32:15

changing, since there is public "duplicate" now on the bt.