dring1=187,0,0
dring1context=from-zaptel
dring2=374,339,128
dring2context=from-ptsn-XXXxxxXXXX < sends direct to a fax answer command
context=from-zaptel
I had it sort of working a year or so ago, but I found that the ring detection was not consistent and did not go any further. One of the things I think I remember about troubleshooting was that you turned distinctive ring detection on in Zapata.conf and then call your distinctive ring number while watching the CLI and Asterisk will give you the ring cadences.
I do have it working with any did / any cid inbound routing
but it would be nice to detect dr1 pattern 1 and assign it a did number, and detect dr2 and do the same thing. makes it 10 times easier that way to use the CDR reporting by number etc
i can assign zap channel 1 the main did, but that does nothing for the dr2 situation
as far as the ring cadences, they do very a bit, but asterisk must be using a default +/- on them to catch them - sometimes they are off like by 50 or so and it still catches them
you will need to make a custom context for each distinctive ring (including the main ring) and jump into the ext-did context with the desired DID in each case. It’s the same channel in all 3 cases and the ZAP Channel table is just looking at channels. That also requires you specify each of those custom contexts in zapata.conf.