asterisk users - Oct 2004 - Phantom calls on FXO

I'm getting these "calls" at 16 and 46 minutes after every hour. 
The
SIP phone rings, and if we pick up, we get a dial tone.  If we don't
pick up, we get the dial tone in a voicemail message.  An analog phone
connected to the incoming POTS line doesn't ring (whether or not *
remains connected to the line).  It's like the horror movie where the
babysitter is getting threatening calls, and the police tell her the
calls are coming from INSIDE the house...

I thought it might have something to do with Telco voicemail being set
up on the line, but they deny that their messaging software ever calls
the user (they use a stutter dialtone for message notification).  We're
getting rid of the Telco voicemail in any event.  Suggestions
appreciated!

    -- Starting simple switch on 'Zap/2-1'
Oct  5 09:16:30 NOTICE[5898257]: chan_zap.c:5069 ss_thread: Got event 17
(Event 17)...
Oct  5 09:16:37 WARNING[5898257]: chan_zap.c:5140 ss_thread: CallerID
returned with error on channel 'Zap/2-1'
    -- Executing Ringing("Zap/2-1", "") in new stack
    -- Executing Wait("Zap/2-1", "2") in new stack
    -- Executing Answer("Zap/2-1", "") in new stack
    -- Executing Macro("Zap/2-1",
"stdexten|7590|SIP/Cisco403b9e") in
new stack
    -- Executing Dial("Zap/2-1", "SIP/Cisco403b9e|10") in
new stack
    -- Called Cisco403b9e
    -- SIP/Cisco403b9e-d3e0 is ringing
  == Spawn extension (macro-stdexten, s, 1) exited non-zero on 'Zap/2-1'
in macro 'stdexten'
  == Spawn extension (incoming, s, 4) exited non-zero on 'Zap/2-1'
    -- Hungup 'Zap/2-1'


Jim Shilliday
IT Director
Equal Justice Center
1315 Walnut St. Suite 400
Philadelphia PA 19107
215-238-6970

Shilliday, Jim wrote:
> I'm getting these "calls" at 16 and 46 minutes after every
hour.  The
> SIP phone rings, and if we pick up, we get a dial tone.  If we don't
> pick up, we get the dial tone in a voicemail message.  An analog phone
> connected to the incoming POTS line doesn't ring (whether or not *
> remains connected to the line).
Interestingly enough, this just started *again* in the last 3-4 days. 
Nothing has changed in my config, I've not updated to the latest CVS, or 
even a _recent_ CVS.  This simply started happening.  So far I cannot 
explain it.  99% of the time there is no CallerID associated with the 
'dialtone' call, but occasionally there is (seems to be a random recent 
caller id entry).

During my initial * testing and setup I attributed these calls, or 
similar ones, to the fact that one of my lines has a security system 
installed on it and this system will pick up the line from time to time 
to verify it can 'phone home' and 'do its thing'.

I have not verified times for this event as of yet, but I'm sure it is 
somewhat regular like the OP stated.

Also, not to go off topic, _but_ I have recently begun having more echo 
than in my initial testing, and it seems to be getting worse with time. 
  On several occasions I have encountered the 'screeching' recently 
discussed on the list, but this seems very very rare.  My setup is using 
two good ol' TDM400P's with 4 FXO's each.  Every other aspect of my
*
setup is working rather well, all things considered.

Thanks,
Chris


-- 
Christopher L. Wade                     Unistar-Sparco Computers, Inc.
Senior Systems Administrator                            dba Sparco.com
Email: clwade@sparco.com                             7089 Ryburn Drive
Phone: (901) 872 2272 / (800) 840 8400            Millington, TN 38053
Fax:   (901) 872 8482                                              USA