Eugeniy Khvastunov
2006-Sep-12 02:23 UTC
[asterisk-users] Samsung OfficeServ 500 + Asterisk(Tormenta 2) via PRI
Kind time of day, All! Prompt, please! Is Samsung OfficeServ 500 in it card TEPRI is established, also there is a server on Gentoo with Asterisk PBX + Established card Tormenta 2 (4 ports PRI). On Asterisk awakes it is submitted 3 PRI a stream from PSTN and from it in turn on Samsung OfficeServ 500 + are planned soft VoIP phones. There is a configuration file for Tormenta 2 (zaptel.conf), actually now a question: What signaling system PRI i need to use?: # 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 Thanks! -------------- next part -------------- A non-text attachment was scrubbed... Name: eugeniy.khvastunov.vcf Type: text/x-vcard Size: 234 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20060912/35a74bf6/eugeniy.khvastunov.vcf