[Home]

Summary:DAHLIN-00099: CID timed out waiting for ring. Executing simple switch
Reporter:SplatNIX (uxbod)Labels:
Date Opened:2009-05-01 03:52:28Date Closed:2009-05-05 08:22:49
Priority:MajorRegression?No
Status:Closed/CompleteComponents:wctdm
Versions:2.2.0-rc2 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:-- Starting simple switch on 'DAHDI/1-1'
[May  1 09:44:47] NOTICE[18508]: chan_dahdi.c:7253 ss_thread: Got event 17 (Polarity Reversal)...
[May  1 09:44:49] WARNING[18508]: chan_dahdi.c:7311 ss_thread: CID timed out waiting for ring. Exiting simple switch
   -- Hungup 'DAHDI/1-1'

This appears to be very similar too http://bugs.digium.com/view.php?id=12531

I have also tried downgrading to 2.0 with the same result.

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

modules.d/dahdi
---------------
options wctdm opermode=UK fwringdetect=1

dahdi/system.conf
-----------------
# Autogenerated by /usr/sbin/dahdi_genconf on Sun Apr 26 20:09:08 2009 -- do not hand edit
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER)
fxsks=1
echocanceller=mg2,1
# channel 2, WCTDM/4/1, no module.
# channel 3, WCTDM/4/2, no module.
# channel 4, WCTDM/4/3, no module.

# Global data

loadzone        = uk
defaultzone     = uk

asterisk/chan_dahdi.conf
------------------------
[channels]
usecallerid=yes
cidsignalling=v23
cidstart=polarity
hidecallerid=no
callwaiting=no
threewaycalling=yes
transfer=yes
echocancel=yes
immediate=no
faxdetect=no

context=inbound-dahdi
group=0
usecallerid=yes
faxdetect=none
signalling=fxs_ks
rxgain=8
txgain=8
callerid=asreceived
dahdichan => 1
Comments:By: SplatNIX (uxbod) 2009-05-01 09:19:47

Okay, I got a bit further by disabling CID and now it actually runs through the dialplan :-

== Starting post polarity CID detection on channel 1
   -- Starting simple switch on 'DAHDI/1-1'
   -- Executing [s@inbound-dahdi:1] Answer("DAHDI/1-1", "") in new stack
   -- Executing [s@inbound-dahdi:2] Ringing("DAHDI/1-1", "") in new stack
   -- Executing [s@inbound-dahdi:3] Wait("DAHDI/1-1", "1") in new stack
   -- Executing [s@inbound-dahdi:4] Playback("DAHDI/1-1", "home-message") in new stack
   -- <DAHDI/1-1> Playing 'home-message.gsm' (language 'en')
   -- Executing [s@inbound-dahdi:5] Hangup("DAHDI/1-1", "") in new stack
 == Spawn extension (inbound-dahdi, s, 5) exited non-zero on 'DAHDI/1-1'
   -- Hungup 'DAHDI/1-1'

The problem is that DAHDI does not actually pick up the inbound PSTN call and bridge to play the message.  On the dialling phone it just rings and rings and the above loops until the physical call is hungup :(
By: SplatNIX (uxbod) 2009-05-05 05:06:40

Please change status to closed as it was a cable issue. 4pin instead of 2pin on a BT PSTN.
By: Joshua C. Colp (jcolp) 2009-05-05 08:22:49

Closed per reporter.