Ring Time - Where to Change

If you're using an analog trunk I think the delay is because of CID. If you don't need inbound caller id then you can turn this off -- unfortunately I don't have any analog trunks anywhere so I don't know how you do that. I would assume that it has to happen in the configuration files because I don't remember seeing anything like that in the freePBX GUI.

The caller ID is delivered between the first and second ring, however my system (from the caller's perspective) rings once and then the IVR answers before the second ring.

Are you calling from outside to check how many rings or dialing out from your system and back in?

If you are calling from your system to your main number, then you may be hearing an asterisk internally generated ring and then the telco ring

The difference between our two systems is I have each zap channel named...
Instead of all the zap channels being named g0 (group zero), I have each one listed like 1..2 ..3 in their zap identifier.

Then I direct each channel in inbound routes to the IVR of my choice.

Please note that in order to do this you must go to zapata-channels.conf and change context=from-pstn to context=from-zaptel (and this will be re-written if you do genzaptelconf)

You might try this configuration as test, just to see if it changes from two rings to one ring. : )

That's what I have in my zapata-channels.conf file (haven't touched it yet):

; Autogenerated by /usr/local/sbin/sangoma/setup-sangoma -- 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

;Sangoma A200 [slot:0 bus:1 span:1]
context=from-zaptel
group=0
signalling = fxs_ks
channel => 1

context=from-zaptel
group=0
signalling = fxs_ks
channel => 2

context=from-zaptel
group=0
signalling = fxs_ks
channel => 3

context=from-zaptel
group=0
signalling = fxs_ks
channel => 4

As you can see it's already set to context=from-zaptel...

What version of trixbox are you using?

On my system I have each line setup as a separate zap channel, that way I can route them as necessary.

Your lines are setup up as a group, so if any of them ring they all route the same way.

The only thing that I am curious about is the fact that in zapata-channels.conf it should say context=from-pstn (this is the default).

From a curiosity stand point, I would try two things. Change the zapata-channels.conf to have the context=from-pstn instead of context=from-zaptel and see what happens. This is supposed to work when your lines are grouped. Make sure you reboot system before you test.

And if that doesn't change anything, I would make each of the incoming zap channels separate trunks, change zapata-channels.conf back to context=from-zaptel, and route each trunk to the IVR. Reboot system and test.

My system rings once, then the IVR picks up.

Other than these two tests, I am not sure.

At first I commented out usecallerid=yes and restarted the system. Still would ring 2 times.

Then I tried usecallerid=no and restarted the system. Now it worked and it'll ring only once and then pick up. Success =)

I'll now follow markwho's instructions. Actually I'm configuring a shared PBX with total 4 lines:

2 lines are from one company. And the other 2 belongs to another company. So it's really import to split and route them separately.

Will post back in a few minutes.

I have two tb installations at the same location: One is tb 2.2, one is tb 2.4. Both have Sangoma A200D cards.

tb 2.2 answers the call just after the first ring.

tb 2.4 doesn't answer until after the second ring.

Both have callerid=yes in zapata.conf.

The incoming PSTN lines to 2.4 do not yet have CID on them. The incoming lines to 2.2 do have CID.

I just plugged a line to the 2.2 machine into the 2.4 machine. The 2.4 machine answered the call just after the first ring: It seems that usecallerid=yes will force the card to wait until after the second ring to answer if it doesn't see CID from the telco.

I posted this more for informational purposes than anything; I hope this helps someone else.

I'm not sure what you mean by the pattern...and I don't think it would be the Sangoma card, but it would be something in Asterisk.