[asterisk-users] CallerID on Indian PSTN is not working.

[Arun Sasidhar]

hi,

   I made changes in zapata.conf but no result.
I tried different settings. I am getting differnt logs But no result

when i use "cidstart=ring"
I am getting this in my asterisk log

[Jan 7 09:31:13] VERBOSE[7129] logger.c: -- Starting simple switch on
'DAHDI/1-1'
[Jan 7 09:31:14] ERROR[7129] callerid.c: No start bit found in fsk data.
[Jan 7 09:31:14] WARNING[7129] chan_dahdi.c: CallerID feed failed: Success
[Jan 7 09:31:14] WARNING[7129] chan_dahdi.c: CallerID returned with error on
channel 'DAHDI/1-1'
[Jan 7 09:31:14] VERBOSE[7129] logger.c: -- Executing [s at from-pstn:1]
Wait("DAHDI/1-1", "5") in new stack
[Jan 7 09:31:19] VERBOSE[7129] logger.c: -- Executing [s at from-pstn:2]
Gosub("DAHDI/1-1", "app-blacklist-check|s|1") in new stack
[Jan 7 09:31:19] VERBOSE[7129] logger.c: -- Executing [s at app-blacklist-check:1]
LookupBlacklist("DAHDI/1-1", "") in new stack
[Jan 7 09:31:19] WARNING[7129] app_lookupblacklist.c: LookupBlacklist is
deprecated. Please use ${BLACKLIST()} instead.
[Jan 7 09:31:19] VERBOSE[7129] logger.c: -- Executing [s at app-blacklist-check:2]
GotoIf("DAHDI/1-1", "0?blacklisted") in new stack

And when i use "cidstart=polarity" I am getting this in my log

[Jan 7 09:35:16] VERBOSE[7300] logger.c: -- Starting simple switch on
'DAHDI/1-1'
[Jan 7 09:35:16] VERBOSE[7300] logger.c: -- Executing [s at from-pstn:1]
Wait("DAHDI/1-1", "5") in new stack
[Jan 7 09:35:22] VERBOSE[7300] logger.c: -- Executing [s at from-pstn:2]
Gosub("DAHDI/1-1", "app-blacklist-check|s|1") in new stack
[Jan 7 09:35:22] VERBOSE[7300] logger.c: -- Executing [s at app-blacklist-check:1]
LookupBlacklist("DAHDI/1-1", "") in new stack
[Jan 7 09:35:22] WARNING[7300] app_lookupblacklist.c: LookupBlacklist is
deprecated. Please use ${BLACKLIST()} instead.
[Jan 7 09:35:22] VERBOSE[7300] logger.c: -- Executing [s at app-blacklist-check:2]
GotoIf("DAHDI/1-1", "0?blacklisted") in new stack
[Jan 7 09:35:22] VERBOSE[7300] logger.c: -- Executing [s at app-blacklist-check:3]
Set("DAHDI/1-1", "CALLED_BLACKLIST=1") in new stack
[Jan 7 09:35:22] VERBOSE[7300] logger.c: -- Executing [s at app-blacklist-check:4]
Return("DAHDI/1-1", "") in new stack
[Jan 7 09:35:22] VERBOSE[7300] logger.c: -- Executing [s at from-pstn:3]
ExecIf("DAHDI/1-1", "1 |Set|CALLERID(name)=") in ne

And I tried another option "cidstart=polarity_IN"

Then my log shows this..

Jan 7 09:43:13] VERBOSE[7642] logger.c: -- Starting simple switch on
'DAHDI/1-1'
[Jan 7 09:43:14] NOTICE[7642] chan_dahdi.c: Got event 18 (Ring Begin)...
[Jan 7 09:43:15] NOTICE[7642] chan_dahdi.c: Got event 2 (Ring/Answered)...
[Jan 7 09:43:17] NOTICE[7642] chan_dahdi.c: Got event 18 (Ring Begin)...
[Jan 7 09:43:17] VERBOSE[7642] logger.c: -- Executing [s at from-pstn:1]
Wait("DAHDI/1-1", "5") in new stack
[Jan 7 09:43:22] VERBOSE[7642] logger.c: -- Executing [s at from-pstn:2]
Gosub("DAHDI/1-1", "app-blacklist-check|s|1") in new stack
[Jan 7 09:43:22] VERBOSE[7642] logger.c: -- Executing [s at app-blacklist-check:1]
LookupBlacklist("DAHDI/1-1", "") in new stack
[Jan 7 09:43:22] WARNING[7642] app_lookupblacklist.c: LookupBlacklist is
deprecated. Please use ${BLACKLIST()} instead.
[Jan 7 09:43:22] VERBOSE[7642] logger.c: -- Executing [s at app-blacklist-check:2]
GotoIf("DAHDI/1-1", "0?blacklisted") in new stack

In all these settings I dont have any CID output.

Thanks,
Arun S




On Wed, Jan 6, 2010 at 11:16 PM, Tzafrir Cohen <tzafrir.cohen at xorcom.com>wrote:

> On Wed, Jan 06, 2010 at 08:30:48PM +0530, Arun Sasidhar wrote:
> > Hi,
> >
> >    Its a free service here and My ordinary phone displaying the Caller ID
> > without any problem.
> > I have done some modifications in zapata.conf
> > Now it looks like this
> >
> > *[channels]
> > language=en
> > hanguponpolarityswitch=yes
> > answeronpolarityswitch=yes
> > busydetect=yes
> > busycount=6
> > callprogress=yes
>
> If hanguponpolarityswitch works for you, you don't need the hacks of
> busydetect and callprogress .
>
> > callerid=asreceived
> > hidecallerid=no
> > immediate=no
> > cidsignalling=dtmf
> > cidstart=polarity_IN
>
> This is not supported in Asterisk 1.4 . Only as of 1.6.0, IIRC.
>
> Generally the fixes from that bug report were not applied to Asterisk
> 1.4 .
>
> > cid_rxgain=6
> > useincomingcalleridonzaptransfer=yes
>
> Renamed to "useincomingcalleridondahditransfer" (s/zap/dahdi/).
>
> > rxgain=5.0
> > txgain=2.0
> > ;cidsignalling=bell
> > ;cidsignalling=v23
> > ;cidstart=polarity
> > ;cidstart=ring
> > ; include dahdi extensions defined in FreePBX
> > #include chan_dahdi_additional.conf
> >
> > ; XTDM20B Port #1,2 plugged into PSTN
> > ;AMPLABEL:Channel %c - Button %n
> > context=from-pstn
> > signalling=fxs_ks
> > faxdetect=incoming
> > usecallerid=yes
> > echocancel=yes
> > echocancelwhenbridged=no
> > echotraining=800
> > group=0
> > channel=1-2*
>
> What is this '*'?
>
> --
>                Tzafrir Cohen
> icq#16849755              jabber:tzafrir.cohen at xorcom.com<jabber%3Atzafrir.cohen at xorcom.com>
> +972-50-7952406           mailto:tzafrir.cohen at xorcom.com
> http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>



-- 
Thanks,

Arun S
System Administrator.
Cabot Solutions
www.cabotsolutions.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100107/f0b7be3b/attachment-0001.htm