Hi,
I’ve been thrown into the world of Asterisk & am currently stumped.
I’m trying to migrate our settings from an old machine running Asterisk 1.4.26 on Centos 5.3 to a newer machine running Asterisk 1.8.11 on Centos 5.5.
The machine was part setup before I got here, and I have got to the point where all of the phones will register, I can make internal calls, and check voicemail, but I just can’t get out through the ISDN.
The first error message I see in the interface is:
######################################################################################################
hastpbxCLI>
e[0K – Executing [07903######@internationalservices:1] Dial(“SIP/gtophonejon-00000004”, “dahdi/g1/07903######”) in new stack
ehastpbxCLI> e[0K[Aug 8 04:31:31] eWARNINGe[971]: app_dial.c:2030 dial_exec_full: Unable to create channel of type ‘dahdi’ (cause 0 - Unknown)
######################################################################################################
Just to check whether the card was talking to anything I ran dahdi_cfg and got:
###################################################################################
[i]DAHDI Version: 2.4.0
Echo Canceller(s): MG2
Configuration
SPAN 1: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
Channel map:
Channel 01: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 01)
Channel 02: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 02)
Channel 03: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 03)
Channel 04: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 04)
Channel 05: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 05)
Channel 06: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 06)
Channel 07: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 07)
Channel 08: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 08)
Channel 16: D-channel (Default) (Echo Canceler: none) (Slaves: 16)
9 channels to configure.
Setting echocan for channel 1 to mg2
Setting echocan for channel 2 to mg2
Setting echocan for channel 3 to mg2
Setting echocan for channel 4 to mg2
Setting echocan for channel 5 to mg2
Setting echocan for channel 6 to mg2
Setting echocan for channel 7 to mg2
Setting echocan for channel 8 to mg2
Setting echocan for channel 16 to none[/i]
#################################################################################
I assume that this means that the card has been interrogated & has responded.
I’ve checked the startup messages & there’s something I don’t understand there:
###############################################################################################
…
dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.4.0
GSI 21 sharing vector 0x32 and IRQ 21
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 20 (level, low) -> IRQ 50
FALC version: 00000000
TE110P: Setting up global serial parameters for E1 FALC V1.2
TE110P: Successfully initialized serial bus for card
Found a Wildcard: Digium Wildcard TE110P T1/E1
dahdi_echocan_mg2: Registered echo canceler 'MG2’
dahdi: Registered tone zone 4 (United Kingdom)
TE110P: Span configured for CCS/HDB3/CRC4
Calling startup (flags is 4099)
wcte1xxp: Setting yellow alarm
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6 over IPv4 tunneling driver
TE110P: Span configured for CCS/HDB3/CRC4
Calling startup (flags is 4099)
TE110P: Span configured for CCS/HDB3/CRC4
Calling startup (flags is 4099)
TE110P: Span configured for CCS/HDB3/CRC4
Calling startup (flags is 4099)
TE110P: Span configured for CCS/HDB3/CRC4
Calling startup (flags is 4099)
tg3: eth0: Link is up at 1000 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
wcte1xxp: Clearing yellow alarm
#################################################################################################
What I don’t understand is that the driver mentioned there is wcte1xxp, but in the /etc/dahdi/modules file I’m loading wcte11xp as the card in this machine is a Digium TE110P.
Also, not knowing quite where Asterisk looks for each item, one thing that’s concerning me a little is that on the old box ‘/etc/asterisk’ is a link to the conf folder in ‘/work/asterisk’, but on the newer box ‘/etc/asterisk’ and (for some reason) ‘/work/work/asterisk’ 's conf folders are separate entities. I don’t think this is a huge problem, but I would like to know for sure which location is used for configuration. I think it’s ‘/etc/asterisk’ - Is that correct?
Another item of concern is the dahdi-channels.conf file - I’m sure that’s wrong:
#################################################################################################
; Span 1: WCT1/0 “Digium Wildcard TE110P T1/E1 Card 0” (MASTER)
group=0,11
context=from-pstn
switchtype = euroisdn
signalling = pri_cpe
channel => 1-15,17-31
context = default
group = 63
#################################################################################################
I’ve tried uncommenting the Span line & changing channel => to 1-8 to no effect, but I have no idea whether the other settings are correct.
The notes on posting said to include files like sip.conf & iax.conf, but attachments don’t seem to be possible & sip.conf is a huge file, so please tell me which bits of which files you would like me to post & I’ll do so asap.
There is another error that pops up in the interface once the call has failed, but that’s an entirely different problem for another post after this has been sorted I think.
Also, does anyone know of a ‘block-diagram / flow-chart’ type documentation site for Asterisk? As in a block diagram of file locations & interaction paths, and flow charts showing module interactions of common call scenarios?
(I’m one of those people that can read stuff 'til they’re blue in the face, but once I can ‘see’ how things interact & then have a play it makes sense immediately)
Many thanks for taking the time to read all this, and if anyone can help out I’d be most grateful.
Paul.
