[AsteriskBrasil] OFF- Placas Aligera
dlpazinatto em gmail.com
dlpazinatto em gmail.com
Quarta Abril 20 10:54:22 BRT 2011
Bom dia pessoal,
Seguinte, compramos uma placa Aligera AP412. Estou com essa placa já tem
seis meses, e sempre tenho problemas diferentes com ela.
O cenário desse cliente é o seguinte:
Asterisk puro: 1.6.2.17
asterisk-addons: 1.6.2.2
Dahdi-linux: 2.4.0
Dahdi-Tools: 2.4.0
Driver da placa AP400 Rev: 13
PABX ALCATEL <ISDN> ASTERISK ALIGERA SPAN2 <VARIOS RAMAIS SIP> ASTERISK
ALIGERA SPAN1 <R2>
Ocorre que o PABX Alcatel não consegue fazer transferencia esterna de ramais
analogicos, logo uso a facilidade de transferencia do ASTERISK para
transferir chamadas via atxfer (isso quando uma chamada vem da operadora,
passa pelo asterisk e vai para o pabx, e o usuário do pabx alcatel precisa
transferir essa chamada para um ramal SIP do asterisk) ai por algum motivo o
dtmf discado no ramal analogico da alcatel chega no asterisk errado, ou não
chega, ou chega somente parte dos digitos.
A principio penser ser um problema refente a sinalização ISDN entre o PABX e
o ASTERISK, embora o DMTF passe por audio ...
Mas ai vi que a URA (que atende as chamadas que vem pela SPAN1) também não
funciona direito, ocorre a mesma coisa com os digitos DTMF.
O estranho é que colocando uma placa Khomp funcionou e uma Digivoice também
funcionou, parece que o problema só ocorre quando usa DAHDI. Alguém ja
passou por isso? tem ideia do que posso tentar fazer?
Estou tendo uma péssima impressão com a Aligera não só por isso, e o suporte
deles simplesmente me disse que o DTMF não vai funcionar 100% e que não tem
o que fazer.
Mas não só por isso, desde que estou com essa placa, sempre tem um problema
ou outro.
Abaixo o meu chan_dahdi.conf, system.conf e o features.conf
chan_dahdi
[trunkgroups]
[channels]
;
switchtype=euroisdn
language=pt_BR
usecallerid=yes
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
overlapdial=yes
faxdetect=both
;
;signalling=mfcr2
mfcr2_variant=br
mfcr2_get_ani_first=no
mfcr2_max_ani=20
mfcr2_max_dnis=4
mfcr2_category=national_subscriber
mfcr2_advanced_protocol_file=/etc/r2proto.conf
mfcr2_allow_collect_calls=no
mfcr2_double_answer=no
signalling=mfcr2
context=entrada
group=1
channel=>1-15,17-31
switchtype=euroisdn
signalling=pri_net
context=para-pstn
group=2
channel=>32-46,48-62
system.conf
loadzone = br
defaultzone=br
#
#
span=1,1,0,cas,hdb3
cas=1-15,17-31:1101
#
span=2,0,0,ccs,hdb3
bchan=32-46
dchan=47
bchan=48-62
#
features.conf
;
; Sample Call Features (parking, transfer, etc) configuration
;
[general]
parkext => 700 ; What extension to dial to park (all parking
lots)
parkpos => 701-720 ; What extensions to park calls on. (defafult
parking lot)
; These needs to be numeric, as Asterisk starts from the
start position
; and increments with one for the next parked call.
;context => parkercalls ; Which context parked calls are in (default
parking lot)
context => ramais ; Which context parked calls are in (default
parking lot)
;parkinghints = no ; Add hints priorities automatically for parking
slots (default is no).
parkingtime => 45 ; Number of seconds a call can be parked for
; (default is 45 seconds)
;comebacktoorigin = yes ; Whether to return to the original calling
extension upon parking
; timeout or to send the call to context
'parkedcallstimeout' at
; extension 's', priority '1' (default is yes).
;courtesytone = beep ; Sound file to play to the parked caller
; when someone dials a parked call
; or the Touch Monitor is activated/deactivated.
;parkedplay = caller ; Who to play the courtesy tone to when picking
up a parked call
; one of: parked, caller, both (default is caller)
;parkedcalltransfers = caller ; Enables or disables DTMF based transfers
when picking up a parked call.
; one of: callee, caller, both, no (default
is no)
;parkedcallreparking = caller ; Enables or disables DTMF based parking
when picking up a parked call.
; one of: callee, caller, both, no (default
is no)
;parkedcallhangup = caller ; Enables or disables DTMF based hangups
when picking up a parked call.
; one of: callee, caller, both, no (default
is no)
;parkedcallrecording = caller ; Enables or disables DTMF based one-touch
recording when picking up a parked call.
; one of: callee, caller, both, no (default
is no)
;adsipark = yes ; if you want ADSI parking announcements
;findslot => next ; Continue to the 'next' free parking space.
; Defaults to 'first' available
;parkedmusicclass=default ; This is the MOH class to use for the parked
channel
; as long as the class is not set on the channel directly
; using Set(CHANNEL(musicclass)=whatever) in the dialplan
transferdigittimeout => 5 ; Number of seconds to wait between digits when
transferring a call
; (default is 3 seconds)
;xfersound = beep ; to indicate an attended transfer is complete
;xferfailsound = beeperr ; to indicate a failed transfer
pickupexten = 48 ; Configure the pickup extension. (default is *8)
;pickupsound = beep ; to indicate a successful pickup (default: no
sound)
;pickupfailsound = beeperr ; to indicate that the pickup failed (default:
no sound)
;featuredigittimeout = 1000 ; Max time (ms) between digits for
; feature activation (default is 1000 ms)
;atxfernoanswertimeout = 10 ; Timeout for answer on attended transfer
default is 15 seconds.
;atxferdropcall = no ; If someone does an attended transfer, then
hangs up before the transferred
; caller is connected, then by default, the
system will try to call back the
; person that did the transfer. If this is set
to "yes", the callback will
; not be attempted and the transfer will just
fail.
atxferloopdelay = 10 ; Number of seconds to sleep between retries (if
atxferdropcall = no)
atxfercallbackretries = 5 ; Number of times to attempt to send the call
back to the transferer.
; By default, this is 2.
;
;*** Define another parking lot
;
; You can set parkinglot with the CHANNEL dialplan function
; or by setting 'parkinglot' directly in the channel configuration file.
;
;[parkinglot_edvina]
;context => edvinapark
;parkpos => 800-850
;findslot => next
; Note that the DTMF features listed below only work when two channels have
answered and are bridged together.
; They can not be used while the remote party is ringing or in progress. If
you require this feature you can use
; chan_local in combination with Answer to accomplish it.
[featuremap]
blindxfer => *3 ; Blind transfer (default is #1) -- Make sure to set
the T and/or t option in the Dial() or Queue() app call!
;disconnect => *0 ; Disconnect (default is *0) -- Make sure to set
the H and/or h option in the Dial() or Queue() app call!
;automon => *1 ; One Touch Record a.k.a. Touch Monitor -- Make
sure to set the W and/or w option in the Dial() or Queue() app call!
atxfer => *2 ; Attended transfer -- Make sure to set the T
and/or t option in the Dial() or Queue() app call!
;parkcall => #72 ; Park call (one step parking) -- Make sure to set
the K and/or k option in the Dial() app call!
;automixmon => *3 ; One Touch Record a.k.a. Touch MixMonitor -- Make
sure to set the X and/or x option in the Dial() or Queue() app call!
[applicationmap]
; Note that the DYNAMIC_FEATURES channel variable must be set to use the
features
; defined here. The value of DYNAMIC_FEATURES should be the names of the
features
; to allow the channel to use separated by '#'. For example:
;
; Set(__DYNAMIC_FEATURES=myfeature1#myfeature2#myfeature3)
;
; (Note: The two leading underscores allow these feature settings to be set
on
; on the outbound channels, as well. Otherwise, only the original channel
; will have access to these features.)
;
; The syntax for declaring a dynamic feature is any of the following:
;
;<FeatureName> =>
<DTMF_sequence>,<ActivateOn>[/<ActivatedBy>],<Application>[,<AppArguments>[,MOH_Class]]
;<FeatureName> =>
<DTMF_sequence>,<ActivateOn>[/<ActivatedBy>],<Application>[,"<AppArguments>"[,MOH_Class]]
;<FeatureName> =>
<DTMF_sequence>,<ActivateOn>[/<ActivatedBy>],<Application>([<AppArguments>])[,MOH_Class]
;
; FeatureName -> This is the name of the feature used in when setting the
; DYNAMIC_FEATURES variable to enable usage of this
feature.
; DTMF_sequence -> This is the key sequence used to activate this feature.
; ActivateOn -> This is the channel of the call that the application
will be executed
; on. Valid values are "self" and "peer". "self" means run
the
; application on the same channel that activated the
feature. "peer"
; means run the application on the opposite channel from
the one that
; has activated the feature.
; ActivatedBy -> This is which channel is allowed to activate this
feature. Valid
; values are "caller", "callee", and "both". "both" is the
default.
; The "caller" is the channel that executed the Dial
application, while
; the "callee" is the channel called by the Dial
application.
; Application -> This is the application to execute.
; AppArguments -> These are the arguments to be passed into the
application. If you need
; commas in your arguments, you should use either the
second or third
; syntax, above.
; MOH_Class -> This is the music on hold class to play while the idle
; channel waits for the feature to complete. If left
blank,
; no music will be played.
;
;
; IMPORTANT NOTE: The applicationmap is not intended to be used for all
Asterisk
; applications. When applications are used in extensions.conf, they are
executed
; by the PBX core. In this case, these applications are executed outside
of the
; PBX core, so it does *not* make sense to use any application which has
any
; concept of dialplan flow. Examples of this would be things like Macro,
Goto,
; Background, WaitExten, and many more.
;
; Enabling these features means that the PBX needs to stay in the media flow
and
; media will not be re-directed if DTMF is sent in the media stream.
;
; Example Usage:
;
;testfeature => #9,peer,Playback,tt-monkeys ;Allow both the caller and
callee to play
; ;tt-monkeys to the opposite
channel
;
; Set arbitrary channel variables, based upon CALLERID number (Note that the
application
; argument contains commas)
;retrieveinfo =>
#8,peer,Set(ARRAY(CDR(mark),CDR(name))=${ODBC_FOO(${CALLERID(num)})})
;
;pauseMonitor => #1,self/callee,Pausemonitor ;Allow the callee to
pause monitoring
; ;on their channel
;unpauseMonitor => #3,self/callee,UnPauseMonitor ;Allow the callee to
unpause monitoring
; ;on their channel
; Dynamic Feature Groups:
; Dynamic feature groups are groupings of features defined in
[applicationmap]
; that can have their own custom key mappings. To give a channel access
to a dynamic
; feature group, add the group name to the value of the DYNAMIC_FEATURES
variable.
;
; example:
; [myGroupName] ; defines the group named myGroupName
; testfeature => #9 ; associates testfeature with the group and the
keycode '#9'.
; pauseMonitor => ; associates pauseMonitor with the group and uses the
keycode specified
; ; in the [applicationmap].
Grato por qualquer ajuda.
--
Dilceu Luiz Pazinatto
Electronics technician
Engineering students
-------------- Próxima Parte ----------
Um anexo em HTML foi limpo...
URL: http://listas.asteriskbrasil.org/pipermail/asteriskbrasil/attachments/20110420/2827b4f7/attachment-0001.htm
Mais detalhes sobre a lista de discussão AsteriskBrasil