[asterisk-bugs] [Asterisk 0013521]: zap callerid in cdr not coming for incoming calls
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Sep 19 11:33:29 CDT 2008
The following issue has been SUBMITTED.
======================================================================
http://bugs.digium.com/view.php?id=13521
======================================================================
Reported By: sunilgorle
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 13521
Category: Channels/chan_zap
Reproducibility: always
Severity: block
Priority: normal
Status: new
Asterisk Version: 1.4.20
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-09-19 11:33 CDT
Last Modified: 2008-09-19 11:33 CDT
======================================================================
Summary: zap callerid in cdr not coming for incoming calls
Description:
Please provide excat configuration, if mine is wrong.
I have connected FXO 100 device to asterisk device and one PSTN line
[BSNL] to the FXO device.
Now, I can make incoming calls, but missing callerid in cdr.
I'm posting all logs here.
Please provide excat configuration, if mine is wrong.
-- Starting simple switch on 'Zap/1-1'
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6656 ss_thread: Receiving DTMF
cid on channel Zap/1-1
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
2
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 399(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
2
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 398(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
2
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 397(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
5
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 397(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
2
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 396(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
2
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 395(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
2
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 394(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
2
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 393(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
2
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 392(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
2
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 391(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
2
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 390(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
2
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 389(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
2
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 388(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
2
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 387(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
2
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 386(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6671 ss_thread: frame type is
5
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6678 ss_thread: CID state 4,
polarity 0, ringt 400(400)
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6685 ss_thread: CID got string
''
[Sep 19 22:00:16] DEBUG[14980]: callerid.c:183 callerid_get_dtmf: No cid
detected
[Sep 19 22:00:16] DEBUG[14980]: chan_zap.c:6687 ss_thread: CID is '',
flags 8
zapata-channels.conf is
; Autogenerated by ./genzaptelconf -- do not hand edit
; Zaptel Channels Configurations (zapata.conf)
;
; This is not intended to be a complete zapata.conf. Rather, it is
intended
; to be #include-d by /etc/zapata.conf that will include the global
settings
;
; Span 1: WCFXO/0 "Wildcard X100P Board 1"
;;; line="1 WCFXO/0/0 FXSKS (In use)"
usecallerid=yes
cidstart=ring
cidsignalling=dtmf
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 1
context=default
and zapata.conf is
;
; Zapata telephony interface
;
; Configuration file
[trunkgroups]
;
; Trunk groups are used for NFAS or GR-303 connections.
;
; Group: Defines a trunk group.
; group => <trunkgroup>,<dchannel>[,<backup1>...]
;
; trunkgroup is the numerical trunk group to create
; dchannel is the zap channel which will have the
; d-channel for the trunk.
; backup1 is an optional list of backup d-channels.
;
;trunkgroup => 1,24,48
;
; Spanmap: Associates a span with a trunk group
; spanmap => <zapspan>,<trunkgroup>[,<logicalspan>]
;
; zapspan is the zap span number to associate
; trunkgroup is the trunkgroup (specified above) for the mapping
; logicalspan is the logical span number within the trunk group to
use.
; if unspecified, no logical span number is used.
;
;spanmap => 1,1,1
;spanmap => 2,1,2
;spanmap => 3,1,3
;spanmap => 4,1,4
[channels]
;
; Default language
;
;language=en
busydetect=1
busycount=7
relaxdtmf=yes
callwaiting=yes
; don't wait two seconds before answering calls
;usecallerid=no
;
; Support Caller*ID on Call Waiting
;
;callwaitingcallerid=yes
;
; Support three-way calling
;
threewaycalling=yes
;
; Support flash-hook call transfer (requires three way calling)
;
transfer=yes
;
; Support call forward variable
;
cancallforward=yes
;
echocancel=yes
;
; Generally, it is not necessary (and in fact undesirable) to echo cancel
; when the circuit path is entirely TDM. You may, however, reverse this
; behavior by enabling the echo cancel during pure TDM bridging below.
;
echocancelwhenbridged=yes
; In some countries, a polarity reversal is used to signal the disconnect
; of a phone line. If the hanguponpolarityswitch option is selected, the
; call will be considered "hung up" on a polarity reversal
;
hanguponpolarityswitch=yes
callprogress=yes
; Logical groups can be assigned to allow outgoing rollover. Groups
; range from 0 to 31, and multiple groups can be specified.
;
group=1
; Ring groups (a.k.a. call groups) and pickup groups. If a phone is
ringing
; and it is a member of a group which is one of your pickup groups, then
; you can answer it by picking up and dialing *8#. For simple offices,
just
; make these both the same
;
callgroup=1
pickupgroup=1
;
; Specify whether the channel should be answered immediately or
; if the simple switch should provide dialtone, read digits, etc.
;
immediate=no
; For fax detection, uncomment one of the following lines. The default is
*OFF*
;
;faxdetect=both
;faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no
#include "zapata-channels.conf"
hidecallerid=no
usecallerid=yes
cidstart=ring
cidsignalling=dtmf
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2008-09-19 11:33 sunilgorle Asterisk Version => 1.4.20
2008-09-19 11:33 sunilgorle SVN Branch (only for SVN checkouts, not tarball
releases) => N/A
======================================================================
More information about the asterisk-bugs
mailing list