Outbound calls hunting from PRI to Zap channels

Asterisk Asterisk Support
1

Greetings,

I’m trying to figure out how my outbound (group 1) is hunting to my analog ZAP channels (group 5).

In my Oubound Routes, I’m only using “g1”. NO failover.
My zapata-auto.conf has:

[code]; Span 1: R2T1/0/1 “R2T1 (PCI) Card 0 Span 1” (MASTER) B8ZS/ESF RED
group=0,11
context=from-zaptel
switchtype = national
signalling = pri_cpe
channel => 1-13
group=
context=default

group=1
context=from-zaptel
switchtype = national
signalling = pri_cpe
channel => 14-23
context=default

; Span 2: R2T1/0/2 “R2T1 (PCI) Card 0 Span 2” B8ZS/ESF RECOVERINGClockSource
;group=1,12
;context=from-zaptel
;switchtype = national
;signalling = pri_cpe
;channel => 25-47
;group=
;context=default

; Span 3: Rhino RCB24FXX/1 “Rhino RCB24FXX/1”
;;; line="49 FXS/1/0 FXOKS"
signalling=fxo_ks
callerid=“Channel 49” <6049>
mailbox=6049
group=5
context=from-internal
channel => 49
;callerid=
;mailbox=
;group=
context=default
… to line=“72 FSX1.0 FXOKS”
[/code]
Putty only show: "ZAP/49-1 ringing"
When either the PRI is down or all the outbound channels are busy, it rolls to the FXS ports starting at 49,50,51,…

Why???

2

Dahdi files are read from the bottom up from memory

at the cli enter dahdi show channels group 1 to see the members of the group

3

Ok. How does that help me?
It’s still group 1 for the outbound calls. How does group 5 come into play?

4

It helps to locate the source of the problem. If channel 49 appears in that list, the problem is in the way the configuration file is parsed. If not, it indicates that you got the intended configuration, but it is mishandling it at run-time.

5

Thanks
Still don’t know why group 5 is being hit.
I did set a roll-over to a truck group that has no members. I’ll see how that works.