[asterisk-bugs] [JIRA] (ASTERISK-21155) CallerID on Indian PSTN is not working.

Matt Jordan (JIRA) noreply at issues.asterisk.org
Sat Feb 23 07:11:18 CST 2013


    [ https://issues.asterisk.org/jira/browse/ASTERISK-21155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203375#comment-203375 ] 

Matt Jordan commented on ASTERISK-21155:
----------------------------------------

Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions.  After testing with Asterisk 1.8, if you find this problem has not been resolved, please open a new issue against Asterisk 1.8.


                
> CallerID on Indian PSTN is not working.
> ---------------------------------------
>
>                 Key: ASTERISK-21155
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21155
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>            Reporter: Jee
>
> Hi
> I am using asterisk 1.4.21 and Wilcard TDM400P TDM FXS/FXO..Caller ID of 
> incoming call from PSTN line is not working properly..The phone
> display is showing name as "unknown" and number a 0000000 when there is an incoming cal.As I am India I have used the patch For 
> the start of caller id on ring from the link  https://issues.asterisk.org/view.php?id=6683.
> My log file is showing
> [Jan  1 00:26:50] DEBUG[138] dsp.c: dsp busy pattern set to 0,0
> [Jan  1 00:26:50] VERBOSE[240] logger.c:     -- Starting simple switch on 'Zap/2-1'
> [Jan  1 00:26:51] NOTICE[240] chan_zap.c: Got event 18 (Ring Begin)...
> [Jan  1 00:26:53] NOTICE[240] chan_zap.c: Got event 2 (Ring/Answered)...
> [Jan  1 00:26:54] NOTICE[240] chan_zap.c: Got event 18 (Ring Begin)...
> [Jan  1 00:26:54] VERBOSE[240] logger.c:     -- Executing [s at DID_trunk_1:1] 
> NoOp("Zap/2-1", "") in new stack
> [Jan  1 00:26:54] VERBOSE[240] logger.c:     -- Executing [s at DID_trunk_1:2] 
> ExecIf("Zap/2-1", "1|Set|CALLERID(all)=unknown <0000000>") in new stack
> [Jan  1 00:26:54] VERBOSE[240] logger.c:     -- Executing [s at DID_trunk_1:3] 
> Goto("Zap/2-1", "default|6003|1") in new stack
> [Jan  1 00:26:54] VERBOSE[240] logger.c:     -- Goto (default,6003,1)
> [Jan  1 00:26:54] VERBOSE[240] logger.c:     -- Executing [6003 at default:1] 
> Dial("Zap/2-1", "SIP/6003") in new stack
> [Jan  1 00:26:54] VERBOSE[240] logger.c:     -- Called 6003
> [Jan  1 00:26:55] VERBOSE[240] logger.c:     -- SIP/6003-023cd3d4 is ringing
> [Jan  1 00:26:57] VERBOSE[240] logger.c:     -- SIP/6003-023cd3d4 answered 
> Zap/2-1
> [Jan  1 00:26:57] DEBUG[240] chan_zap.c: Took Zap/2-1 off hook
> [Jan  1 00:26:57] DEBUG[240] chan_zap.c: No echo training requested
> [Jan  1 00:27:06] VERBOSE[240] logger.c:   == Spawn extension (default, 6003, 1) 
> exited non-zero on 'Zap/2-1'
> [Jan  1 00:27:06] VERBOSE[240] logger.c:     -- Hungup 'Zap/2-1'
> Zapata.conf
> [trunkgroups]
> [channels]
> context=default
> switchtype=national
> usecallerid=yes
> hidecallerid=no
> callwaiting=yes
> usecallingpres=yes
> callwaitingcallerid=no
> threewaycalling=yes
> transfer=yes
> canpark=yes
> busydetect=yes
> cancallforward=yes
> callreturn=yes
> echocancel=yes
> echocancelwhenbridged=yes
> rxgain=0.0
> txgain=0.0
> callgroup=1
> pickupgroup=1
> immediate=no
> useincomingcalleridonzaptransfer = yes
> cidsignalling=dtmf
> cidstart=ring
> callerid=asreceived
> sendcalleridafter = 2
> dtmfcidlevel=256
> group=1
> signalling = fxo_ks
> channel => 1
> group=2
> signalling = fxs_ks
> channel => 2
> Anyone please help to solve this issue.
> Thanks 
> Jeetha P J

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list