<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Times New Roman","serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> </span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Bruce B said:<br><br></span><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'>We experience exact same thing on DAHDI with Sangoma USB FXO device on short circuited lines. Phantom calls are actually due to a short in the lines that happen occasionally.<o:p></o:p></p><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'>-Bruce<o:p></o:p></p><div><p class=MsoNormal><span style='color:#1F497D'>Also,</span> Warren Selby <span style='color:#1F497D'>said:</span><o:p></o:p></p><div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'>I've seen this on cases where a "phantom" call comes in on a DAHDI channel - these calls were the results of faulty wiring on the part of the telco. Check your logs for any errors on your DAHDI channels around the time of the "ghost" calls. <br><br>It could also be a case of someone calls in and then hangs up before the call is actually passed to asterisk, and the telco is just slow to hangup the call. <br> <o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Hmmmm. I do see this in the /var/log/asterisk/messages log:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>[Apr 5 00:05:36] NOTICE[9579] chan_dahdi.c: Got event 4 (Alarm)...<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>[Apr 5 00:05:38] NOTICE[9579] chan_dahdi.c: Got event 5 (No more alarm)...<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>[Apr 5 00:05:38] NOTICE[9579] chan_dahdi.c: Got event 17 (Polarity Reversal)...<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>[Apr 5 00:05:41] WARNING[2400] chan_dahdi.c: Detected alarm on channel 3: Red Alarm<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>[Apr 5 00:05:42] NOTICE[2400] chan_dahdi.c: Alarm cleared on channel 3<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>[Apr 5 00:05:51] WARNING[2400] chan_dahdi.c: Detected alarm on channel 2: Red Alarm<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>[Apr 5 00:05:53] NOTICE[2400] chan_dahdi.c: Alarm cleared on channel 2<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>…and it appears to coincide directly with an ‘asterisk’ entry in my SIP phone’s missed call log.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Our wiring is sketchy; this is known at our facility. Some years ago a backhoe severed the entire trunk and the repair work was of questionable quality. Also our service entry point / punch-down area is a rat’s nest (one building and service is shared by three companies). I guess I can chalk this behavior up to the wiring.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Thanks for the input!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Cheers,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>~Brian<o:p></o:p></span></p></div></div></div></div></div></body></html>