BTW, digium support confirmed that the hardward hdlc patch wont work in
this case and it is for doing data over the ports.
Thanks for all the inputs.
Dushyanth
Quote:
Hello,
Iam not sure whether this patch will work for TE110P as the module i
load is wcte11xp and the patches specified at
(http://bugs.digium.com/view.php?id=5313) seems to patch the file
wct4xxp.c in zaptel.
Can anyone please confirm ? Or Wat the heck shuld i just go ahead and try ?
Dushyanth
>Look on mantis for some patch to do hdlc in hardware, it might help.
>
>Zoa
>
>Steve Totaro wrote:
>
>
>>Try PRI debug span 1 and see if that sheds any light on the problem.
>>
>>Thanks,
>>Steve
>>
>>
>>
>>
>>
>>>Hello,
>>>
>>>Iam trying to configure asterisk with a PRI E1 line. I got to a point
>>>where incoming calls on PRI is landing on asterisk and asterisk
>>>immediately starts throwing the below errors on the console. The call
>>>
>>
>>is
>>
>>
>>
>>>dropped at this point somehow.
>>>
>>>Dec 12 15:02:57 NOTICE[5783]: chan_zap.c:7437 pri_dchannel: PRI got
>>>event: HDLC Bad FCS (8) on Primary D-channel of span 1
>>>Dec 12 15:02:58 NOTICE[5783]: chan_zap.c:7437 pri_dchannel: PRI got
>>>event: HDLC Bad FCS (8) on Primary D-channel of span 1
>>>Dec 12 15:02:59 NOTICE[5783]: chan_zap.c:7437 pri_dchannel: PRI got
>>>event: HDLC Abort (6) on Primary D-channel of span 1
>>>Dec 12 15:03:00 NOTICE[5783]: chan_zap.c:7437 pri_dchannel: PRI got
>>>event: HDLC Bad FCS (8) on Primary D-channel of span 1
>>>Dec 12 15:03:02 NOTICE[5783]: chan_zap.c:7437 pri_dchannel: PRI got
>>>event: HDLC Bad FCS (8) on Primary D-channel of span 1
>>>Dec 12 15:03:03 NOTICE[5783]: chan_zap.c:7437 pri_dchannel: PRI got
>>>event: HDLC Abort (6) on Primary D-channel of span 1
>>>Dec 12 15:03:04 NOTICE[5783]: chan_zap.c:7437 pri_dchannel: PRI got
>>>event: HDLC Abort (6) on Primary D-channel of span 1
>>>Dec 12 15:03:04 NOTICE[5783]: chan_zap.c:7437 pri_dchannel: PRI got
>>>event: HDLC Abort (6) on Primary D-channel of span 1
>>>
>>>*CLI> show version
>>>Asterisk CVS-v1-0-11/08/05-01:22:43 built by root@ip-pbx on a i686
>>>running Linux
>>>
>>>
>>>
>>>
>>>>>/etc/zaptel.conf
>>>>>
>>>
>>>span=1,1,0,cas,ami
>>>;span=1,0,0,cas,ami ; have tried this too
>>>bchan=1-15
>>>dchan=16
>>>bchan=17-31
>>>
>>>
>>>
>>>
>>>>>/etc/asterisk/zapata.conf
>>>>>
>>>
>>>; T110P - PRI Configuration
>>>signalling=pri_cpe
>>>;switchtype=national
>>>;switchtype=5ess
>>>switchtype=euroisdn
>>>callerid=asreceived
>>>group=1
>>>context=di_mainmenu
>>>channel => 1-15,17-31
>>>
>>>
>>>
>>>
>>>>>cat /proc/zaptel/1
>>>>>
>>>
>>>Span 1: WCT1/0 "Digium Wildcard TE110P T1/E1 Card 0" AMI/
>>>
>>> 1 WCT1/0/1 Clear (In use)
>>> 2 WCT1/0/2 Clear (In use)
>>> 3 WCT1/0/3 Clear (In use)
>>> 4 WCT1/0/4 Clear (In use)
>>> 5 WCT1/0/5 Clear (In use)
>>> 6 WCT1/0/6 Clear (In use)
>>> 7 WCT1/0/7 Clear (In use)
>>> 8 WCT1/0/8 Clear (In use)
>>> 9 WCT1/0/9 Clear (In use)
>>> 10 WCT1/0/10 Clear (In use)
>>> 11 WCT1/0/11 Clear (In use)
>>> 12 WCT1/0/12 Clear (In use)
>>> 13 WCT1/0/13 Clear (In use)
>>> 14 WCT1/0/14 Clear (In use)
>>> 15 WCT1/0/15 Clear (In use)
>>> 16 WCT1/0/16 HDLCFCS (In use)
>>> 17 WCT1/0/17 Clear (In use)
>>> 18 WCT1/0/18 Clear (In use)
>>> 19 WCT1/0/19 Clear (In use)
>>> 20 WCT1/0/20 Clear (In use)
>>> 21 WCT1/0/21 Clear (In use)
>>> 22 WCT1/0/22 Clear (In use)
>>> 23 WCT1/0/23 Clear (In use)
>>> 24 WCT1/0/24 Clear (In use)
>>> 25 WCT1/0/25 Clear (In use)
>>> 26 WCT1/0/26 Clear (In use)
>>> 27 WCT1/0/27 Clear (In use)
>>> 28 WCT1/0/28 Clear (In use)
>>> 29 WCT1/0/29 Clear (In use)
>>> 30 WCT1/0/30 Clear (In use)
>>> 31 WCT1/0/31 Clear (In use)
>>>
>>>
>>>
>>>
>>>>>/etc/asterisk/extensions.conf
>>>>>
>>>
>>>[di_mainmenu]
>>>exten => s,1,Answer ; Answer the line
>>>exten => s,2,SetVar(mloop=0) ; main menu loop count
>>>exten => s,3,SetVar(mloop=$[${mloop} + 1]) ; increment by 1 , first
>>>
>>
>>run
>>
>>
>>
>>>exten => s,4,DigitTimeout,5 ; Set Digit Timeout to 5 seconds
>>>exten => s,5,ResponseTimeout,8 ; Set Response Timeout to 8 seconds
>>>exten => s,6,(di_welcome)
>>>exten => 1,1,Goto(di_sales,s,1)
>>>exten => 2,1,Goto(di_techsupport,s,1)
>>>exten => 3,1,Goto(di_hostingsupport,s,1)
>>>exten => 4,1,Goto(di_billing,s,1)
>>>exten => 5,1,Directory(default)
>>>exten => 9,1,Goto(operator,0,1)
>>>include => internal
>>>
>>>Iam based in India and the PRI line is from TATA indicom. The switch
>>>
>>
>>iam
>>
>>
>>
>>>connected to is a Lucent 5ess. I have tried 5ess as the switchtype too
>>>in zapata.conf and same errors.
>>>
>>>I also get the below warning if i remove and put the PRI line into the
>>>T110p.
>>>
>>>Dec 12 14:26:30 WARNING[5783]: No D-channels available! Using Primary
>>>channel 16 as D-channel anyway!
>>>
>>>zttool shows the PRI status as ok and there are no alarms.
>>>
>>>Interrupts details are below. X server is not installed and i have
>>>disabled dma on my disk.
>>>
>>>[root@ip-pbx ~]# cat /proc/interrupts
>>> CPU0 CPU1
>>> 0: 751204 690283 IO-APIC-edge timer
>>> 1: 9 0 IO-APIC-edge i8042
>>> 8: 1 0 IO-APIC-edge rtc
>>> 9: 0 0 IO-APIC-level acpi
>>>14: 6203 1100 IO-APIC-edge ide0
>>>169: 0 0 IO-APIC-level uhci_hcd
>>>177: 682240 672161 IO-APIC-level uhci_hcd, wctdm
>>>185: 0 0 IO-APIC-level uhci_hcd
>>>193: 102135 1252274 IO-APIC-level wcte11xp
>>>201: 1257747 100020 IO-APIC-level wctdm
>>>217: 94 6793 IO-APIC-level eth0
>>>225: 8722 0 IO-APIC-level eth1
>>>NMI: 0 0
>>>LOC: 1441441 1441440
>>>ERR: 0
>>>MIS: 0
>>>
>>>
>>># hdparm -v /dev/hda
>>>
>>>/dev/hda:
>>>multcount = 16 (on)
>>>IO_support = 0 (default 16-bit)
>>>unmaskirq = 1 (on)
>>>using_dma = 1 (on)
>>>keepsettings = 0 (off)
>>>readonly = 0 (off)
>>>readahead = 256 (on)
>>>geometry = 16383/255/63, sectors = 40020664320, start = 0
>>>
>>>Wat could cause this problem ?
>>>
>>>TIA
>>>dushyanth
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
