VoIP Community of Thailand - เว็บบอร์ด VoIP Issabel, Elastix Asterisk FreePBX IPPhone VoIP Gateway Call Center IPPBX ของไทย โดยคนไทย เพื่อคนไทย

มือใหม่หัดศึกษาตามหนังสือของ อ.กิตติพงษ์ ครับ เบื้องต้นติดตั้ง Card X100P เรียบร้อยแล้ว และสามารถโทรหากันภายในได้แล้วโดยใช้ X-lite ครับ
แต่ติดปัญหาคือใช้สายโทรศัพท์ RJ-11 ต่อเข้ากับ Card X100P แล้วเพื่อทดสอบ โทรเข้ามาแล้วเสียงในโทรศัพท์ดังเหมือนไม่มีคนรับสายครับ และไม่ได้ยินข้อความเสียงที่อัดไว้ใน asterisk (welcome.gsm) ครับ
รบกวนขอคำแนะนำด้วยครับ ว่าต้อง Config ตรงไหนเพิ่มเติมครับ

OS:Ubuntu 11.10
Software
asterisk - 1.8.4.4
dahdi tools - 2.4.1
dahdi - 2.4.1

----------------
sip.conf

โค้ด: เลือกทั้งหมด

[general]
context=default
allowoverlap=no
udpbindaddr=0.0.0.0
tcpenable=no
tcpbindaddr=0.0.0.0 
srvlookup=yes

[authentication]
[basic-options](!)                ; a template
        dtmfmode=rfc2833
        context=from-office
        type=friend

[natted-phone](!,basic-options)   ; another template inheriting basic-options
        nat=yes
        directmedia=no
        host=dynamic

[public-phone](!,basic-options)   ; another template inheriting basic-options
        nat=no
        directmedia=yes

[my-codecs](!)                    ; a template for my preferred codecs
        disallow=all
        allow=ilbc
        allow=g729
        allow=gsm
        allow=g723
        allow=ulaw

[ulaw-phone](!)                   ; and another one for ulaw-only
        disallow=all
        allow=ulaw

[1000]         
type=friend
host=dynamic
username=1000
secret=1000

[2000]         
type=friend
host=dynamic
username=2000
secret=2000

[8205]         
type=friend
host=dynamic
username=8205
secret=8205

[8206]         
type=friend
host=dynamic
username=8206
secret=8206

-------------------
extentions.conf

โค้ด: เลือกทั้งหมด

[default]
;
; By default we include the demo.  In a production system, you
; probably don't want to have the demo there.
;
;include => demo

exten => 1000,1,Dial(SIP/1000)
exten => 2000,1,Dial(SIP/2000)

exten => 8205,1,Answer()
exten => 8205,2,wait(2)
exten => 8205,3,record(/tmp/welcome.gsm)
exten => 8205,4,wait(2)
exten => 8205,5,playback(/tmp/welcome)
exten => 8205,6,wait(2)
exten => 8205,7,Hangup

exten => 8206,1,Playback(/tmp/welcome)

exten => s,1,Answer()
exten => s,2,Background(/tmp/welcome)
exten => s,3,WaitExten()

------------------------
root@Asterisk:/etc/asterisk# lspci

โค้ด: เลือกทั้งหมด

00:00.0 Host bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL Memory Controller Hub (rev 0e)
00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller (rev 0e)
00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 04)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 04)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 04)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 04)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 04)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d4)
00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge (rev 04)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 04)
00:1f.2 IDE interface: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 04)
01:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
01:0a.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
01:0b.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface

----------------------------------------------------------
root@Asterisk:/etc/asterisk# service dahdi status

โค้ด: เลือกทั้งหมด

### Span  1: WCFXO/0 "Generic Clone Board 1" (MASTER)
  1 FXO        FXSKS       (SWEC: MG2) (battery)
### Span  2: DAHDI_DUMMY/1 "DAHDI_DUMMY/1 (source: HRtimer) 1"
root@Asterisk:/etc/asterisk#

-------------------------------------------------------

ผมเคยเป็นคือว่าผมใช้นามสกุลตัวใหญ่ hello-world.gsm , hello-world.GSM < ตัวใหญ่เรียกยังไงก็ไม่ติด

ไฟล์ extensions.conf คุณสร้าง s extension ไว้ใน context [default] ซึ่งถ้าคุณไม่ได้มีการเรียกใช้ context นี้ก็จะไม่ได้ยินเสียงที่อัดไว้ ให้เช็คที่ไฟล์ /etc/dahdi/system.conf ว่าบรรทัด context มันเป็นอะไรอยู่ หาทางทำให้มันเป็น

context=default

ไฟล์ system.conf ของผมปัจจุบันครับ

root@Asterisk:/tmp# vi /etc/dahdi/system.conf

loadzone = us
defaultzone=us

ลองทำตามที่คุณ nuiz แนะนำแล้วโดยเพิ่ม context=default ใน system.conf แล้ว

root@Asterisk:/tmp# vi /etc/dahdi/system.conf

loadzone = us
defaultzone=us
context=default

ลองใช้คำสั่ง dahdi_cfg -v แล้ว Error ตามด้านล่างนี้ครับ

โค้ด: เลือกทั้งหมด

root@Asterisk:/tmp# dahdi_cfg -v
DAHDI Tools Version - 2.4.1
Notice: Configuration file is /etc/dahdi/system.conf
line 210: Unknown keyword 'context'

1 error(s) detected


ไม่ทราบต้องทำอย่างไรเพิ่มเติมบ้างครับ รบกวนทุกท่านด้วยนะครับ

ไฟล์ system.conf ทำไมมันมีแค่นั้นครับ

งั้นรันคำสั่งตามผมเลย

service asterisk stop
service dahdi restart
dahdi_genconf
service dahdi restart
service asterisk start

แล้วเปิดดูไฟล์ /etc/asterisk/system.conf อีกรอบครับ น่าจะมีอะไรเพิ่มขึ้นมาอีกเยอะ

ลองทำตามหนังสือแล้วไม่เวอร์ค ก็ลองหาบทความในนี้อ่านครับ เกี่ยวกับพวกติดตั้งการ์ด TDM400P, TDM410P มันจะคล้ายๆกัน เพียงแต่พอร์ตมันไม่เท่ากัน

Re: ติดปัญหาต้องการใช้เบอร์ภายนอกโทรเข้า-โทรออก asterisk ครับ
โดย nuiz » 16 ก.พ. 2012 20:38

ไฟล์ system.conf ทำไมมันมีแค่นั้นครับ

งั้นรันคำสั่งตามผมเลย

service asterisk stop
service dahdi restart
dahdi_genconf
service dahdi restart

ลองทำตามที่คุณ nuiz แนะนำแล้วก็ยังไม่ได้อยู่ดีครับ

Gen system.conf ใหม่แล้วได้ดังนี้ครับ

root@Asterisk:/etc/dahdi# vi system.conf

โค้ด: เลือกทั้งหมด

# Autogenerated by /usr/sbin/dahdi_genconf on Fri Feb 17 10:32:20 2012
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: DAHDI_DUMMY/1 "DAHDI_DUMMY/1 (source: HRtimer) 1" (MASTER)

# Global data

loadzone        = us
defaultzone     = us

ส่วนไฟล์เก่าผม Backup ไว้ ข้างในเป็นดังนี้ครับ


root@Asterisk:/etc/dahdi# vi system.conf.BAK

โค้ด: เลือกทั้งหมด

#
# DAHDI Configuration File
#
# This file is parsed by the DAHDI Configurator, dahdi_cfg
#
# Span Configuration
# ^^^^^^^^^^^^^^^^^^
# First come the span definitions, in the format
#
#   span=<span num>,<timing source>,<line build out (LBO)>,<framing>,<coding>[,yellow]
#
# All T1/E1/BRI spans generate a clock signal on their transmit side. The
# <timing source> parameter determines whether the clock signal from the far
# end of the T1/E1/BRI is used as the master source of clock timing. If it is, our
# own clock will synchronise to it. T1/E1/BRI connected directly or indirectly to
# a PSTN provider (telco) should generally be the first choice to sync to. The
# PSTN will never be a slave to you. You must be a slave to it.
#
# Choose 1 to make the equipment at the far end of the E1/T1/BRI link the preferred
# source of the master clock. Choose 2 to make it the second choice for the master
# clock, if the first choice port fails (the far end dies, a cable breaks, or
# whatever). Choose 3 to make a port the third choice, and so on. If you have, say,
# 2 ports connected to the PSTN, mark those as 1 and 2. The number used for each
# port should be different.
#
# If you choose 0, the port will never be used as a source of timing. This is
# appropriate when you know the far end should always be a slave to you. If
# the port is connected to a channel bank, for example, you should always be
# its master. Likewise, BRI TE ports should always be configured as a slave.
# Any number of ports can be marked as 0.
#
# Incorrect timing sync may cause clicks/noise in the audio, poor quality or failed
# faxes, unreliable modem operation, and is a general all round bad thing.
#
# The line build-out (or LBO) is an integer, from the following table:
#
#  0: 0 db (CSU) / 0-133 feet (DSX-1)
#  1: 133-266 feet (DSX-1)
#  2: 266-399 feet (DSX-1)
#  3: 399-533 feet (DSX-1)
#  4: 533-655 feet (DSX-1)
#  5: -7.5db (CSU)
#  6: -15db (CSU)
#  7: -22.5db (CSU)
#
# If the span is a BRI port the line build-out is not used and should be set
# to 0.
#
# framing::
#   one of 'd4' or 'esf' for T1 or 'cas' or 'ccs' for E1. Use 'ccs' for BRI.
#  'd4' could be referred to as 'sf' or 'superframe'
#
# coding::
#   one of 'ami' or 'b8zs' for T1 or 'ami' or 'hdb3' for E1. Use 'ami' for
#   BRI.
#
#   * For E1 there is the optional keyword 'crc4' to enable CRC4 checking.
#   * If the keyword 'yellow' follows, yellow alarm is transmitted when no
#     channels are open.
#
#span=1,0,0,esf,b8zs
#span=2,1,0,esf,b8zs
#span=3,0,0,ccs,hdb3,crc4
#
# Dynamic Spans
# ^^^^^^^^^^^^^
# Next come the dynamic span definitions, in the form:
#
#   dynamic=<driver>,<address>,<numchans>,<timing>
#
# Where <driver> is the name of the driver (e.g. eth), <address> is the
# driver specific address (like a MAC for eth), <numchans> is the number
# of channels, and <timing> is a timing priority, like for a normal span.
# use "0" to not use this as a timing source, or prioritize them as
# primary, secondard, etc.  Note that you MUST have a REAL DAHDI device
# if you are not using external timing.
#
#   dynamic=eth,eth0/00:02:b3:35:43:9c,24,0
#
# If a non-zero timing value is used, as above, only the last span should
# have the non-zero value.
#
# Channel Configuration
# ^^^^^^^^^^^^^^^^^^^^^
# Next come the definitions for using the channels.  The format is:
# <device>=<channel list>
#
# Valid devices are:
#
# e&m::
#   Channel(s) are signalled using E&M signalling (specific
#   implementation, such as Immediate, Wink, or Feature Group D
#   are handled by the userspace library).
# fxsls::
#   Channel(s) are signalled using FXS Loopstart protocol.
# fxsgs::
#   Channel(s) are signalled using FXS Groundstart protocol.
# fxsks::
#   Channel(s) are signalled using FXS Koolstart protocol.
# fxols::
#   Channel(s) are signalled using FXO Loopstart protocol.
# fxogs::
#   Channel(s) are signalled using FXO Groundstart protocol.
# fxoks::
#   Channel(s) are signalled using FXO Koolstart protocol.
# sf::
#   Channel(s) are signalled using in-band single freq tone.
#   Syntax as follows:
#
#     channel# => sf:<rxfreq>,<rxbw>,<rxflag>,<txfreq>,<txlevel>,<txflag>
#
#   rxfreq is rx tone freq in Hz, rxbw is rx notch (and decode)
#   bandwith in hz (typically 10.0), rxflag is either 'normal' or
#   'inverted', txfreq is tx tone freq in hz, txlevel is tx tone
#   level in dbm, txflag is either 'normal' or 'inverted'. Set
#   rxfreq or txfreq to 0.0 if that tone is not desired.
#
# unused::
#   No signalling is performed, each channel in the list remains idle
# clear::
#   Channel(s) are bundled into a single span.  No conversion or
#   signalling is performed, and raw data is available on the master.
# bchan::
#   Like 'clear' except all channels are treated individually and
#   are not bundled.  'inclear' is an alias for this.
# rawhdlc::
#   The DAHDI driver performs HDLC encoding and decoding on the
#   bundle, and the resulting data is communicated via the master
#   device.
# dchan::
#   The DAHDI driver performs HDLC encoding and decoding on the
#   bundle and also performs incoming and outgoing FCS insertion
#   and verification.  'fcshdlc' is an alias for this.
# hardhdlc::
#   The hardware driver performs HDLC encoding and decoding on the
#   bundle and also performs incoming and outgoing FCS insertion
#   and verification.  Is subject to limitations and support of underlying
#   hardware. BRI spans serviced by the wcb4xxp driver must use hardhdlc
#   channels for the signalling channels.
# nethdlc::
#   The DAHDI driver bundles the channels together into an
#   hdlc network device, which in turn can be configured with
#   sethdlc (available separately). In 2.6.x kernels you can also optionally
#   pass the name for the network interface after the channel list.
#   Syntax:
#
#     nethdlc=<channel list>[:interface name]
#   Use original names, don't use the names which have been already registered
#   in system e.g eth.
#
# dacs::
#   The DAHDI driver cross connects the channels starting at
#   the channel number listed at the end, after a colon
# dacsrbs::
#   The DAHDI driver cross connects the channels starting at
#   the channel number listed at the end, after a colon and
#   also performs the DACSing of RBS bits
#
# The channel list is a comma-separated list of channels or ranges, for
# example:
#
#   1,3,5 (channels one, three, and five)
#   16-23, 29 (channels 16 through 23, as well as channel 29)
#
# So, some complete examples are:
#
#   e&m=1-12
#   nethdlc=13-24
#   fxsls=25,26,27,28
#   fxols=29-32
#
# An example of BRI port:
#
#   span=1,1,0,ccs,ami
#   bchan=1,2
#   hardhdlc=3
# NOTE: When using BRI channels in asterisk, use the bri_cpe, bri_net, or
# bri_cpe_ptmp (for point to multipoint mode). libpri does not currently
# support point to multipoint when in NT mode. Otherwise, the bearer channel
# are configured identically to other DAHDI channels.
#
#fxoks=1-24
#bchan=25-47
#dchan=48
#fxols=1-12
#fxols=13-24
#e&m=25-29
#nethdlc=30-33
#clear=44
#clear=45
#clear=46
#clear=47
#fcshdlc=48
#dacs=1-24:48
#dacsrbs=1-24:48
#
# Tone Zone Data
# ^^^^^^^^^^^^^^
# Finally, you can preload some tone zones, to prevent them from getting
# overwritten by other users (if you allow non-root users to open /dev/dahdi/*
# interfaces anyway.  Also this means they won't have to be loaded at runtime.
# The format is "loadzone=<zone>" where the zone is a two letter country code.
#
# You may also specify a default zone with "defaultzone=<zone>" where zone
# is a two letter country code.
#
# An up-to-date list of the zones can be found in the file zonedata.c
#
#context=default
loadzone = us
#loadzone = us-old
#loadzone=gr
#loadzone=it
#loadzone=fr
#loadzone=de
#loadzone=uk
#loadzone=fi
#loadzone=jp
#loadzone=sp
#loadzone=no
#loadzone=hu
#loadzone=lt
#loadzone=pl
defaultzone=us
#
# PCI Radio Interface
# ^^^^^^^^^^^^^^^^^^^
# (see http://www.zapatatelephony.org/app_rpt.html)
#
# The PCI Radio Interface card interfaces up to 4 two-way radios (either
# a base/mobile radio or repeater system) to DAHDI channels. The driver
# may work either independent of an application, or with it, through
# the driver;s ioctl() interface. This file gives you access to specify
# load-time parameters for Radio channels, so that the driver may run
# by itself, and just act like a generic DAHDI radio interface.
#
# Unlike the rest of this file, you specify a block of parameters, and
# then the channel(s) to which they apply. CTCSS is specified as a frequency
# in tenths of hertz, for example 131.8 HZ is specified as 1318. DCS
# for receive is specified as the code directly, for example 223. DCS for
# transmit is specified as D and then the code, for example D223.
#
# The hardware supports a "community" CTCSS decoder system that has
# arbitrary transmit CTCSS or DCS codes associated with them, unlike
# traditional "community" systems that encode the same tone they decode.
#
# this example is a single tone DCS transmit and receive
#
# specify the transmit tone (in DCS mode this stays constant):
#tx=D371
#
# specify the receive DCS code:
#dcsrx=223
#
# this example is a "community" CTCSS (if you only want a single tone, then
# only specify 1 in the ctcss list)
#
# specify the default transmit tone (when not receiving):
#tx=1000
#
# Specify the receive freq, the tag (use 0 if none), and the transmit code.
# The tag may be used by applications to determine classification of tones.
# The tones are to be specified in order of presedence, most important first.
# Currently, 15 tones may be specified..
#
#ctcss=1318,1,1318
#ctcss=1862,1,1862
#
# The following parameters may be omitted if their default value is acceptible
#
# Set the receive debounce time in milliseconds:
#debouncetime=123
#
# set the transmit quiet dropoff burst time in milliseconds:
#bursttime=234
#
# set the COR level threshold (specified in tenths of millivolts)
# valid values are {3125,6250,9375,12500,15625,18750,21875,25000}
#corthresh=12500
#
# Invert COR signal {y,n}
#invertcor=y
# Set the external tone mode; yes, no, internal {y,n,i}
#exttone=y
#
# Now apply the configuration to the specified channels:
#
# We are all done with our channel parameters, so now we specify what
# channels they apply to
#channels=1-4
#
# Overiding PCM encoding
# ^^^^^^^^^^^^^^^^^^^^^^
# Usually the channel driver sets the encoding of the PCM for the
# channel (mulaw / alaw. That is: g711u or g711a). However there are
# some cases where you would like to override that. 'mulaw' and 'alaw'
# set different such encoding. Use them for channels you have already
# defined with e.g. 'bchan' or 'fxoks'.
#mulaw=1-4
#alaw=1-4
#
# 'deflaw' is similar, but resets the encoding to the channel driver's
# default. It must be useful for something, I guess.
#mulaw=1-10
#deflaw=5
#
# Echo Cancellers
# ^^^^^^^^^^^^^^^
# DAHDI uses modular echo cancellers that are configured per channel. The echo
# cancellers are compiled and installed as part of the dahdi-linux package.
# You can specify in this file the echo canceller to be used for each
# channel. The default behavior is for there to be NO echo canceller on any
# channel, so it is very important that you specify one here if you do
# not have hardware echo cancellers and need echo cancellation.
#
# Valid echo cancellers are: mg2, kb1, sec2, and sec.
# If compiled, 'hpec' is also a valid echo canceller.
#
# To configure the default echo cancellers, use the format:
# echocanceller=<echocanceller name>,<channel(s)>
#
# Example:
# Configure channels 1 through 8 to use the mg2 echo canceller
#echocanceller=mg2,1-8
#
# And change channel 2 to use the kb1 echo canceller.
#echocanceller=kb1,2
#

อืม ทำไมไฟล์ /etc/dahdi/system.conf มันไม่มีข้อมูลการ์ดอยู่เลย เหมือนกับว่าตอนรันคำสั่ง dahdi_genconf เซอร์วิส dahdi ไม่ได้รันอยู่

เช็คอีกที รันคำสั่ง dahdi_hardware มองเห็นการ์ดมั๊ย

# dahdi_hardware
pci:0000:01:0a.0 wcfxo+ e159:0001 Wildcard X101P clone

และไฟล์ /etc/dahdi/modules มีโมดูลอะไรอยู่หรือเปล่า อย่างน้อยๆก็ต้องมี wcfxo หน่ะครับที่เป็นไดร์เวอร์ของการ์ด x100p

# cat /ec/dahdi/modules

wcfxo

อันนี้เป็นไฟล์ /etc/dahdi/system.conf ในเครื่องผมครับ มันสร้างเองตอนรันคำสั่ง dahdi_genconf

# Span 1: WCFXO/0 "Generic Clone Board 1" (MASTER)
fxsks=1
echocanceller=oslec,1

# Global data

loadzone = en
defaultzone = en


ผมว่าค่อยๆทำตามหนังสือดีกว่าครับ อาจจะข้ามขั้นตอนไหนไป จะเริ่มใหม่ทั้งหมดเลยก็ได้