[asterisk-bugs] [JIRA] Closed: (DAHTOOL-41) sethdlc problem setting protocol for nethdlc spans

[Shaun Ruffell (JIRA)]

     [ https://issues.asterisk.org/jira/browse/DAHTOOL-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shaun Ruffell closed DAHTOOL-41.
--------------------------------

    Resolution: Not A Bug

> sethdlc  problem setting protocol for nethdlc spans
> ---------------------------------------------------
>
>                 Key: DAHTOOL-41
>                 URL: https://issues.asterisk.org/jira/browse/DAHTOOL-41
>             Project: DAHDI-Tools
>          Issue Type: Bug
>          Components: Utilities
>    Affects Versions: 2.2.0
>            Reporter: Zsolt Varga
>
> the hdlc0 interface is there, just I cant
> setup the protocol using sethdlc utility like:
> ~# sethdlc hdlc0 cisco
> hdlc0: Unable to set Cisco HDLC protocol information: Invalid argument
> ~# sethdlc hdlc0 hdlc
> hdlc0: Unable to set HDLC protocol information: Invalid argument
> ~# sethdlc hdlc0 ppp
> hdlc0: Unable to set PPP protocol information: Invalid argument
> ****** ADDITIONAL INFORMATION ******
> Linux flexVoip 2.6.23.12-custom #2 SMP Thu Feb 25 16:45:22 CET 2010 i686
> GNU/Linux
> 04:08.0 Communication controller: Digium, Inc. Wildcard TE220 dual-span
> T1/E1/J1 card 3.3V (PCI-Express) (rev 02)
> DAHDI Version: 2.2.1 Echo Canceller: MG2
> Asterisk 1.6.0.25 built by root @ flexVoip on a i686 running Linux on
> 2010-02-25 23:08:49 UTC
> used tarbals to compile:
> libpri-1.4.10.2.tar.gz
> dahdi-linux-complete-2.2.1+2.2.1.tar.gz
> asterisk-1.6.0.25.tar.gz
> asterisk-addons-1.6.0.4.tar.gz
> -----------------------------------
> /etc/dahdi/system.conf looks like:
> span=1,1,0,ccs,hdb3,crc4
> bchan=1-15,17-31
> dchan=16
> echocanceller=mg2,1-15,17-31
> span=2,2,0,ccs,hdb3,crc4
> nethdlc=32-62:hdlc0
> ~# asterisk  -rx 'dahdi show status'
> Description                              Alarms  IRQ    bpviol CRC4   Fra
> Codi Options  LBO
> T2XXP (PCI) Card 0 Span 1                OK      0      0      0      CCS
> HDB3 CRC4     0 db (CSU)/0-133 feet (DSX-1)
> T2XXP (PCI) Card 0 Span 2                OK      0      0      0      CCS
> HDB3 CRC4     0 db (CSU)/0-133 feet (DSX-1)
> # ifconfig hdlc0
> hdlc0     Link encap:UNSPEC  HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>           inet addr:192.168.102.126  P-t-P:192.168.102.125 
> Mask:255.255.255.252
>           POINTOPOINT NOARP  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:50
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Interrupt:16
> the corresponding part of the kernel messages:
> --------------------------------->8-------------
> dahdi: Telephony Interface Registered on major 196
> dahdi: Version: 2.2.1
> Found TE2XXP at base address fe5ffc00, remapped to f88fec00
> TE2XXP version c01a016a, burst ON
> Octasic optimized!
> FALC version: 00000005, Board ID: 00
> Reg 0: 0x3394b400
> Reg 1: 0x3394b000
> Reg 2: 0xffffffff
> Reg 3: 0x00000000
> Reg 4: 0x00000101
> Reg 5: 0x00000000
> Reg 6: 0xc01a016a
> Reg 7: 0x00001300
> Reg 8: 0x010200ff
> Reg 9: 0x00fd0001
> Reg 10: 0x0000004a
> Found a Wildcard: Wildcard TE220 (4th Gen)
> TE2XXP: Launching card: 0
> TE2XXP: Setting up global serial parameters
> About to enter spanconfig!
> Done with spanconfig!
> About to enter spanconfig!
> Done with spanconfig!
> dahdi_echocan_mg2: Registered echo canceler 'MG2'
> dahdi: Registered tone zone 21 (Hungary)
> About to enter startup!
> TE2XXP: Span 1 configured for CCS/HDB3/CRC4
> timing source auto card 0!
> SPAN 1: Primary Sync Source
> VPM400: Not Present
> VPM450: echo cancellation for 64 channels
> VPM450: hardware DTMF disabled.
> VPM450: Present and operational servicing 2 span(s)
> Completed startup!
> About to enter startup!
> TE2XXP: Span 2 configured for CCS/HDB3/CRC4
> SPAN 2: Secondary Sync Source
> Completed startup!
> ---------------------------------->8--------------

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira