OfficeServ 500 + Asterisk через PRI
Доброго времени суток!
Подскажите, плиз!
Есть OfficeServ 500 в нем установлена карта TEPRI, также есть сервер на Gentoo c Asterisk PBX + установленой картой Tormenta 2 (4 порта PRI). На Asterisk будит подано 3-и PRI потока от тел. операторов а с него в свою очередь на OfficeServ 500 + планируются софтварные VoIP телефоны.
Есть конфигурационный файл для Tormenta 2(zaptel.conf), собственно теперь вопрос:
Какую сигнализацию PRI потока нужно использовать для соединения Asterisk и OfficeServ?
В zaptel.conf есть упоменания о:
# Next come the definitions for using the channels. The format is:
# =
#
# 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 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
Зарание Спасибо!
|
