New file: zapata-channels.conf?

[blanchae]

UPDATE: zaptel is not supported in Asterisk 1.6. Dahdi is now king. I will be updating my website PBX in a Flash for Newbies on dahdi in the near future.

ran update-scripts, update-fixes and then genzaptelconf. What is this new file /etc/asterisk/zapata-channels.conf for?

It appears to auto assign the fxs channels to extensions 6001 and up for voicemail, etc..? I thought that FreePBX is where we did that type of thing?

 

[blanchae]

genzaptelconf is creating /etc/asterisk/zapata-auto.conf like it should and adding in /etc/asterisk/zapata-channels.conf which is screwing up the zaptel channel order:

/etc/asterisk/zapat-auto.conf

; Autogenerated by /usr/local/sbin/genzaptelconf -- do not hand edit
; Zaptel Channels Configurations (zapata.conf)
;
; This is not intended to be a complete zapata.conf. Rather, it is intended
; to be #include-d by /etc/zapata.conf that will include the global settings
;
callerid=asreceived

; Span 1: WCTDM/0 "Wildcard TDM400P REV E/F Board 1" (MASTER)
signalling=fxo_ks
; Note: this is an extension. Create a ZAP extension in AMP for Channel 1
context=from-internal
group=1
channel => 1

signalling=fxo_ks
; Note: this is an extension. Create a ZAP extension in AMP for Channel 2
context=from-internal
group=1
channel => 2

signalling=fxo_ks
; Note: this is an extension. Create a ZAP extension in AMP for Channel 3
context=from-internal
group=1
channel => 3

signalling=fxs_ks
; Note: this is a trunk. Create a ZAP trunk in AMP for Channel 4
context=from-zaptel
group=0
channel => 4


; Span 2: WCT1/0 "Digium Wildcard TE110P T1/E1 Card 0"
; channel 5, WCT1, unhandled for now
; channel 6, WCT1, unhandled for now
; channel 7, WCT1, unhandled for now
; channel 8, WCT1, unhandled for now
; channel 9, WCT1, unhandled for now
; channel 10, WCT1, unhandled for now
; channel 11, WCT1, unhandled for now
; channel 12, WCT1, unhandled for now
; channel 13, WCT1, unhandled for now
; channel 14, WCT1, unhandled for now
; channel 15, WCT1, unhandled for now
; channel 16, WCT1, unhandled for now
; channel 17, WCT1, unhandled for now
; channel 18, WCT1, unhandled for now
; channel 19, WCT1, unhandled for now
; channel 20, WCT1, unhandled for now
; channel 21, WCT1, unhandled for now
; channel 22, WCT1, unhandled for now
; channel 23, WCT1, unhandled for now
; channel 24, WCT1, unhandled for now
; channel 25, WCT1, unhandled for now
; channel 26, WCT1, unhandled for now
; channel 27, WCT1, unhandled for now
; channel 28, WCT1, unhandled for now

/etc/asterisk/zapata-channels.conf

; Autogenerated by /usr/local/sbin/genzaptelconf -- do not hand edit
; Zaptel Channels Configurations (zapata.conf)
;
; This is not intended to be a complete zapata.conf. Rather, it is intended
; to be #include-d by /etc/zapata.conf that will include the global settings
;

; Span 1: WCT1/0 "Digium Wildcard TE110P T1/E1 Card 0" (MASTER)
group=0,11
context=from-pstn
switchtype = national
signalling = pri_cpe
channel => 1-23
group=
context=default

; Span 2: WCTDM/0 "Wildcard TDM400P REV E/F Board 1"
;;; line="25 WCTDM/0/0"
signalling=fxo_ks
callerid="Channel 25" <6025>
mailbox=6025
group=5
context=from-internal
channel => 25
callerid=
mailbox=
group=
context=default

;;; line="26 WCTDM/0/1"
signalling=fxo_ks
callerid="Channel 26" <6026>
mailbox=6026
group=5
context=from-internal
channel => 26
callerid=
mailbox=
group=
context=default

;;; line="27 WCTDM/0/2"
signalling=fxo_ks
callerid="Channel 27" <6027>
mailbox=6027
group=5
context=from-internal
channel => 27
callerid=
mailbox=
group=
context=default

;;; line="28 WCTDM/0/3 RED"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 28
context=default

 

[jroper]

The new digium created genzaptelconf creates zapata-channels.conf, and it is much improved from the original genzaptelconf, as can be noted from the zap problems which died away rapidly when we started using this.

You should simply regard genzaptelconf as a first step to configuring zap, some editing to get it the way you need it is required.

Joe

 

[blanchae]

It would be nice if genzaptelconf would aggree on both zapata-auto.conf and zapata-channels.conf having the same channel order. Currently after running genzaptelconf, it causes zaptel not to be loaded in asterisk as there is a registration error

I have blacklisted the zaptel drivers and then loaded them in the order that I want to in /etc/sysconfig/zaptel to avoid the udev random loading problem.

zapata-auto.conf works as expected: tdm400 then te110 .

zapata-channels.conf loads the drivers in the opposite order: te110 then tdm400.

 

[jroper]

genzaptelconf which creates zapata-auto will only be seen on the oldest systems.

Genzaptelconf is part of the asterisk distribution and any suggestions for it should be made to the asterisk community, but anyway, it will be replaced by dadhi_genconf before too much longer when we move onto Dahdi, as inevitably we must.

Joe

 

[blanchae]

In the mean time, I'm erasing the contents of /etc/asterisk/zapata-channels.conf until it gets sorted out.

 

[jroper]

Note that zapata-channels will come back if you run update scripts.

My methodolgy is to use what is created by genzaptelconf as a starting point, and add the config to the bottom of zapata.conf, and remove the #include lines to zapata-channels/auto.

Joe

 

[vespaman]

Hey Joe,
just set up a new pc with the latest iso download, have a tdm400 with 2 FXO. Ran update scripts and update fixes as part of the install process. Lights are on and card shows up fine with no errors (zttool). genzaptelconf does nothing however genzaptelconf -sdv gives this:

genzaptelconf -sdv
/usr/local/sbin/genzaptelconf: line 1124: /etc/init.d/asterisk: No such file or directory
Unloading zaptel modules:
ERROR: Module wctdm is in use
ERROR: Module zaptel is in use by wctdm

Temporarily moving zaptel.conf aside to work around broken modprobe.conf
Test Loading modules:
- wct4xxp
- wcte12xp
- wcte11xp
- wct1xxp
- wanpipe
- tor2
- torisa
- qozap
- vzaphfc
- zaphfc
- ztgsm
- wctdm24xxp
- wctdm
ERROR: Module wctdm is in use
- opvxa1200
- wcfxo
- pciradio
- wcusb
- xpp_usb
Generating '/etc/zaptel.conf and /etc/asterisk/zapata-channels.conf'
Reconfiguring identified channels

Zaptel Version: 1.4.12.1
Echo Canceller: MG2
Configuration
======================


Channel map:

Channel 01: FXS Kewlstart (Default) (Slaves: 01)
Channel 02: FXS Kewlstart (Default) (Slaves: 02)

2 channels to configure.

Checking channels configured in Asterisk:
Chan Extension Context Language MOH Interpret
pseudo default en default
1 from-zaptel en default
2 from-zaptel en default

1 incoming zap channel works fine - the other is always busy. Both are set up to ring the same registered and working sip extn. Have redone this 3 times now with the same result. Reading this thread got me thinking that somethings not right. What should be at the bottom of zapata.conf ? Zapata-auto.conf on this machine is the same on one of my production boxes as is the zapata-channels.conf. Appreciate any pointers...

 

[jroper]

Hi

All that goes at the bottom of Zapata.conf is a #include zapata-channels.conf.

However, there are some errors with the standard config file in terms of contexts group numbers etc when inplemented with FreePBX, so it is a good idea to change them to suit your particular installation.

Without any CLI output, no sight of the zapata config files, whether or not you have run update scripts and fixes, it is difficult to trace what might be going on.

Have you tried swapping the lines over in the back of the box, and does the problem move, or stay where it is.

Joe

 

[jmullinix]

If swapping the lines moves the problem to the other line, then the problem my be in the card itself. Try swapping the actual daughtercards on the TDM410.

 

[blanchae]

It is not swapping the lines/channels within the TDM400 card, it is swapping the T1 card's channels with the TDM400 channels.

 

[foneman]

Intersting

I wonder then if this is the cause of what I am experiencing as well. I have 2 fresh installs and tried the connecting with 2 t-1 method and I know I am not the smartestbut configuring a PRI is really not rocket science. I keep getting all circuits busy, no matter what so if the new file is messing with me...hmmm..I have reloaded a couple of times thinking I may have a bad install....Now I have something to try again tomorrow.
This all makes a little more sense....hmmmm....I posed my configs in the other post...2 boxes....sorry, my mind is now racing.

 

[vespaman]

Yep - faulty FXO module. Thanx, should of figured that out myself..........