search for: loadzon

Hi, I?m trying to make * work with Brazilian analog signalling.. I?m using the following in indications.conf file... [br] description = Brasil ringcadence = 1000,4000 dial = 425 busy = 425/250,0/250 ring = 425/1000,0/4000 callwaiting = 425/60,0/250,425/60,0/5000 I changed zaptel.conf to loadzone=br #loadzone=fr #loadzone=de #loadzone=uk #loadzone=fi #loadzone=jp #loadzone=sp #loadzone=no defaultzone=br Now when I try to load zaptel, wcfxs and wcfxo, I got an error: [root@mctylx02 asterisk]# modprobe zaptel [root@mctylx02 asterisk]# modprobe wcfxo Notice: Configuration file is /etc/zapte...

...uters.demon.co.uk/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAxgXJWYjaxM2wIe4RAtw0AJ9Dxe4XQwr0urJPjVww/Tw4r26+kwCfT4qi 3yps6j8KadxLJnLxJajpnoM= =FrXq -----END PGP SIGNATURE----- -------------- next part -------------- # # Zaptel Configuration File # fxsks=1 fxoks=2-3 loadzone = no #loadzone = us-old #loadzone=gr #loadzone=it #loadzone=fr #loadzone=de #loadzone=uk #loadzone=fi #loadzone=jp #loadzone=sp #loadzone=no defaultzone=no -------------- next part -------------- [channels] language = se context = external group = 1 echocancel = yes echocancelwhenbridged = yes ec...

...t;txgain" and "rxgain" in unicall.conf file but, unfortunately, without success. My configuration files, /etc/zaptel.conf and /etc/asterisk/unicall.conf, follow below: /etc/zaptel.conf =========== # MFC/R2 does not normally use CRC4 span=1,0,0,cas,hdb3 # cas=1-15:1101 cas=17-31:1101 loadzone = us #loadzone = us-old #loadzone=gr #loadzone=it #loadzone=fr #loadzone=de #loadzone=uk #loadzone=fi #loadzone=jp #loadzone=sp #loadzone=no defaultzone=us /etc/asterisk/unicall.conf ================== callgroup=1 pickupgroup=1 language=br usecallerid=yes hidecallerid=no immediate=yes callwaiting...

Good day all How do i set a connection between 2 asterisk servers via PRI In Bri I would set one to NT and TE How shoud the zapata.conf and zaptel.conf look And how should the cable be? All I got on the web was to set one to "pri_net"...this cant be all? And the cable > pin1 <--> pin4> pin2 <--> pin5> pin3 <--> pin6> pin4 <--> pin1> pin5 <-->

...p/31-1 is ringing -- Zap/31-1 answered Zap/2-1 But everything is ok and working on not moblie connections My actual settings: Zaptel.conf # # Zaptel Configuration File # span=1,1,0,ccs,hdb3,crc4 span=2,0,0,ccs,hdb3,crc4 # bchan=1-15 dchan=16 bchan=17-31 bchan=32-46 dchan=47 bchan=48-62 # loadzone = de #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=nl Zapata.conf ; ; Zapata telephony interface ; ; Configuration file ; [trunkgroups] [channels] ; c...

I am trying to understand the relationship between loadzone and callerid. I am located in New Zealand and have noticed the following behaviour: Case A zaptel.conf loadzone = nz defaultzone = nz The Zap extension rings with NZ-style ringing but caller id doesn't work (message: Didn't finish Caller-ID spill). This is the case whether the call is ex...

...#fcshdlc=48 #dacs=1-24:48 #dacsrbs=1-24:48 # # 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. # span=1,1,0,esf,b8zs bchan=1-23 dchan=24 fxoks=97-100 loadzone = us defaultzone=us #loadzone = us #loa...

...#fcshdlc=48 #dacs=1-24:48 #dacsrbs=1-24:48 # # 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 = us #loadzone = us...

...=48 #dacs=1-24:48 #dacsrbs=1-24:48 # # 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 # # Make sure that the...

...s combination system working in my data center in the USA since December with no problems. I'm not sharing an IRQ cat /proc/interrupts and there are no warnings in /var/log/messages. Here is a copy of my Zapata and Zaptel.conf files; The following options are switched on in my zaptel.conf; #loadzone = us #loadzone=it #loadzone=fr #loadzone=de loadzone=uk #loadzone=fi #loadzone=jp #loadzone=sp #loadzone=no defaultzone=uk #Dornoch ISDN span=1,1,0,ccs,hdb3,crc4 bchan=1-15,17-31 dchan=16 I have the following options in my Zapata.conf; language=en switchtype=euroisdn ; ; PRI Dialplan: Only RAR...

...#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 = c...

...roblems makes it unlikely that asterisk will start properly if the system is rebooted. Is there something I can do to ensure the modules get loaded in the correct order? Here's my config files, if they will help... # cat /etc/zaptel.conf span=1,1,0,esf,b8zs bchan=1-23 dchan=24 defaultzone=us loadzone=us span=2,1,0,esf,b8zs bchan=25-47 dchan=48 defaultzone=us loadzone=us fxoks=49-52 defaultzone=us loadzone=us # cat /etc/asterisk/zapata.conf [channels] language=en switchtype=national context=incoming faxdetect=none signalling=pri_cpe group=1 echocancel=yes resetinterval=never channel => 1-...

...c=48 #dacs=1-24:48 #dacsrbs=1-24:48 # # 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 # # Make sure that the...

In case it wasn't obvious in the DAHDI release announcement. Richard -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20140922/0bb998aa/attachment.html>

Hi, all I have installed TDM400 with 1 FXS and 1 FXP ports. Now I am goig through documentation on how to configure it. It mentions 3 protocols: Loopstart, Groundstart and Koolstart. Which one do I use? Can someone send me sample zaptel.conf file for Australia? This will save me some time and will be used as a working example. Thanks, Rudolf

...fine - i had both alarms OK and i could get the USB extension ringing when i ran the house number from my mobile. as soon as i tried again i got a red alarm on the wildcard board. now im using the sample configuration files for the devkit lite (downloaded from the website) and i know that the loadzone settings will be different here (serbia) how do i find out what settings i should do for lines here in serbia. the telco here is worse than most ive used, and arent exactly helpful. my local exchange is very old and hasnt been upgraded for a very long time, services such as call waiting are...

...3:33 ERROR[6808]: chan_zap.c:10171 setup_zap: Signalling must be specified before any channels are. Jan 5 21:43:33 WARNING[6808]: loader.c:414 __load_resource: chan_zap.so: load_module failed, returning -1 My config is here below. TIA Arnar Gestsson /etc/zaptel.conf span=1,1,0,ccs,hdb3,crc4 loadzone = nl loadzone=de defaultzone=nl bchan=1-5,7-15,17-31 dchan=16 /etc/asterisk/zapata.conf [trunkgroups] trunkgroup => 1,16 spanmap => 1,1 [channels] language=en context=default switchtype=euroisdn pridialplan=unknown signalling=pri_cpe ;rxwink=300 usecallerid=yes hidecallerid=no callwaitin...

...ncy 64, IRQ 193 I/O ports at e400 [size=256] Memory at febfe000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 The problem is that I cant make the both cards to work together in the same server. Here is my /etc/zaptel.conf: ### fxsks=1-4 loadzone = us defaultzone=us span=1,1,0,ccs,hdb3,crc4 bchan=5-19,21-35 dchan=20 ### When I load the wctdm module, I get this error: ZT_CHANCONFIG failed on channel 5: No such device or address (6). Its sounds like the FXS module its tring to configure the channels 5 to 35 (E1 - ISDN Channels - TE110P car...

...sole shows a hangup signal. Do you have any idea to solve this problem ? here are my configuration files: /etc/zaptel.conf ----------------------------------------------------------------------- # # Zaptel Configuration File # # This file is parsed by the Zaptel Configurator, ztcfg # # # fxoks=1 loadzone = us #loadzone=fr #loadzone=fr #loadzone=de #loadzone=uk defaultzone=us ------------------------------------------------------------------------------------- /etc/asterisk/zapata.conf ------------------------- ; ; Zapata telephony interface ; ; Configuration file [channels] ; ; Default language...

...lear=46 #clear=47 #fcshdlc=48 #dacs=1-24:48 # # 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/tor* # 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. # #loadzone = us #loadzone=it #loadzone=fr #loadzone=de #loadzone=uk #loadzone=fi #loadzone=jp #loadzone=sp...