[Asterisk-Users] Re: Asterisk-Users Digest, Vol 14, Issue 22
Nguyen Trung Tin
thienvinh2001 at yahoo.com
Mon Sep 5 07:45:01 MST 2005
Hi All
I have problem with LIBMFCR2 for once Exchange
I using Sangoma card, the firstly. my ssystem run successful with MFCR2, connected to E10 (Acatel Exchange), after that, i move connection connect to EWSD (Siemens), my system don't work. error protocol R2.
my system:
Asterisk CVS 1.1.X
LibMFCR2 pre.005 and unicall-pre.005
this's my setting
and my setting wanpipe1.conf
#================================================
# WANPIPE1 Configuration File
#================================================
#
# Date: Mon Sep 5 15:37:16 GMT+7 2005
#
# Note: This file was generated automatically
# by /usr/sbin/wancfg program.
#
# If you want to edit this file, it is
# recommended that you use wancfg program
# to do so.
#================================================
# Sangoma Technologies Inc.
#================================================
[devices]
wanpipe1 = WAN_AFT, Comment
[interfaces]
w1g1 = wanpipe1, , TDM_VOICE, Comment
[wanpipe1]
CARD_TYPE = AFT
S514CPU = A
CommPort = PRI
AUTO_PCISLOT = YES
PCISLOT = 2
PCIBUS = 1
FE_MEDIA = E1
FE_LCODE = HDB3
FE_FRAME = NCRC4
FE_LINE = 1
TE_CLOCK = NORMAL
TE_REF_CLOCK = 0
ACTIVE_CH = ALL
TE_HIGHIMPEDANCE = YES
FE_TXTRISTATE = NO
MTU = 2100
UDPPORT = 9000
TTL = 255
IGNORE_FRONT_END = NO
TDMV_SPAN = 1
TDMV_DCHAN = 0
[w1g1]
ACTIVE_CH = ALL
TDMV_ECHO_OFF = NO
and my setting /etc/zaptel.conf
#
# Zaptel Configuration File
#
# This file is parsed by the Zaptel Configurator, ztcfg
#
#
# First come the span definitions, in the format
# span=<span num>,<timing>,<line build out (LBO)>,<framing>,<coding>[,yellow]
#
# The timing parameter determines the selection of primary, secondary, and
# so on sync sources. If this span should be considered a primary sync
# source, then give it a value of "1". For a secondary, use "2", and so on.
# To not use this as a sync source, just use "0"
#
# 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)
#
# The framing is one of "d4" or "esf" for T1 or "cas" or "ccs" for E1
#
# Note: "d4" could be referred to as "sf" or "superframe"
#
# The coding is one of "ami" or "b8zs" for T1 or "ami" or "hdb3" for E1
#
# E1's may have the additional 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
#span=1,0,0,cas,hdb3,crc4
#span=1,0,0,cas,hdb3,crc4,yellow
#span=1,0,0,cas,hdb3,crc4
#span=1,0,0,cas,hdb3,ncrc4
#cantho
span=1,2,0,cas,hdb3
#span=1,1,0,cas,hdb3
#span=1,1,0,ccs,hdb3
#span=1,0,0,ccs,hdb3,yellow
#span=2,0,0,cas,hdb3,crc4
#span=3,0,0,cas,hdb3,crc4
#
#cas=1-15:1001
#cas=17-31:1001
#cas=1-15:0101
#cas=17-31:0101
#cas=1-15:1111
#cas=17-31:1111
#cas=1-15:1101
#cas=17-31:1101
cas=1-15:1101
cas=17-31:1101
#bchan=1-15
#bchan=17-31
dchan=16
#alaw=1-31
alaw=1-15
alaw=17-31
# Next come the dynamic span definitions, in the form:
# dynamic=<driver>,<address>,<numchans>,<timing>
#
#dynamic=w1g1,w1g1/16,31,0
# 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 zaptel device
# if you are not using external timing.
#
# dynamic=eth,eth0/00:02:b3:35:43:9c,24,0
#
# 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.
# "indclear": Like "clear" except all channels are treated individually and
# are not bundled. "bchan" is an alias for this.
# "rawhdlc" : The zaptel driver performs HDLC encoding and decoding on the
# bundle, and the resulting data is communicated via the master
# device.
# "fcshdlc" : The zapdel driver performs HDLC encoding and decoding on the
# bundle and also performs incoming and outgoing FCS insertion
# and verification. "dchan" is an alias for this.
# "nethdlc" : The zaptel driver bundles the channels together into an
# hdlc network device, which in turn can be configured with
# sethdlc (available separately).
# "dacs" : The zaptel driver cross connects the channels starting at
# the channel number listed at the end, after a colon
# "dacsrbs" : The zaptel 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
#
#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
#e&m=25-29
#nethdlc=30-33
#clear=1-31
#clear=45
#clear=46
#clear=47
#fcshdlc=48
#dacs=1-31:16
#dacsrbs=1-31:16
#
# 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/zap/*
# 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 zaptel/zonedata.c
#
loadzone = nl
#loadzone = cn
loadzone = us-old
loadzone=fr
loadzone=it
loadzone=fr
#loadzone=de
loadzone=uk
loadzone=fi
loadzone=jp
#loadzone=sp
loadzone=no
#defaultzone=nl
defaultzone=fi
I setting succesfull at E10 (ACATEL EXCHANGE). when i move to EWSD (SIEMENS EXCHANGE). i get faill. seems to your card cannot change abcd bits when EWSD change stage.
please see log file (EWSD)
Customer call --> telco --> EWSD --> SANGOMA CARD -- ZAPTEL
EWSD (1001) -> IDLE
EWSD (1001) <-- IDLE
EWSD (0001) --> SEIZE SANGOMA CARD
EWSD (1101) <-- SANGOMA CARD (OK, IT's IDLE, channel available)
after that SANGOMA CARD move to wait GROUP I Stage but EWSD time out, send
EWSD (1001) --> SANGOMA CARD.
with E10 Exchange, the flow is difference
Customer call --> telco --> EWSD --> SANGOMA CARD -- ZAPTEL
E10(1001) -> IDLE
E10(1001) <-- IDLE
E10(0001) --> SEIZE SANGOMA CARD
E10(1101) <-- SANGOMA CARD (OK, IT's IDLE, channel available)
E10 is OK, switch to Group I stage, the the call is offer
my logging at EWSD (fail)
Sep 5 12:52:56 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 <- 0001 [1/40000000/Idle /Idle ]
Sep 5 12:52:56 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 Detected
Sep 5 12:52:56 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 Making a new call with CRN 32769
Sep 5 12:52:56 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 Debug here (03)
Sep 5 12:52:56 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 1101 -> [2/ 2/Idle /Idle ]
Sep 5 12:52:56 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 Debug here (04)
Sep 5 12:52:56 WARNING[3942] chan_unicall.c: Unicall/17 event Detected
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 <- 1001 [2/ 2/Seize ack /Seize ack ]
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 Debug here (01) 0x2,101,8
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 Far end disconnected(cause=Normal, unspecified cause [31]) - state 0x2
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: Unicall/17 event Far end disconnected
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: CRN 32769 - far disconnected cause=Normal, unspecified cause [31]
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 Call control(6)
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 Drop call(cause=Normal Clearing [16])
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 Call disconnected(cause=Normal, unspecified cause [31]) - state 0x800
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: Unicall/17 event Drop call
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 Call control(7)
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 Release call
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 1001 -> [1/ 1000/Clear fwd /Seize ack ]
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 Release guard expired
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 Destroying call with CRN 32769
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: Unicall/17 event Release call
Sep 5 12:53:13 WARNING[3942] chan_unicall.c: MFC/R2 UniCall/17 Channel echo cancel
how to correct above problem ???
Any suggestion ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050905/5b197d12/attachment.htm
More information about the asterisk-users
mailing list