[Asterisk-Users] SIP extension calls itself intermittently

[David J Carter]

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Lists
Pleasants
Sent: 05 November 2005 01:59
To: asterisk-users at lists.digium.com
Subject: [Asterisk-Users] SIP extension calls itself intermittently

Intermittently I’ll get calls from my only SIP extension to itself via the
Zap/1. I have no clue and have found nothing online. I have listed my
configurations and a sample of the console messages I see why debugging.
Right now it only happens to the 6000 extension.  Any assistance is
appreciated.

Thanks,
Chip



    -- Starting simple switch on 'Zap/1-1'
Nov  4 14:00:54 WARNING[4156]: chan_zap.c:5476 ss_thread: CallerID returned
with error on channel 'Zap/1-1'
    -- Executing Wait("Zap/1-1", "2") in new stack
    -- Executing Answer("Zap/1-1", "") in new stack
    -- Executing Dial("Zap/1-1", "SIP/6000|20") in new stack
    -- Called 6000
    -- SIP/6000-3d34 is ringing
  == Spawn extension (from-pstn, s, 3) exited non-zero on 'Zap/1-1'
    -- Executing Hangup("Zap/1-1", "") in new stack
  == Spawn extension (from-pstn, h, 1) exited non-zero on 'Zap/1-1'
    -- Hungup 'Zap/1-1'
bart*CLI>

============================================================================
=================================================================

Chip,

The output above looks to me as an incoming call.

I think you would have seen the SIP extension calling on ZAP/1-1 if
initiated from your end, and would not call in as the line was busy.

I get this now and again in the UK, usually in an evening time when the
Telco do an auto check of line status.

Regards

Dave