| Summary: | ASTERISK-09657: when using dial and "&" with zap groups, other lines stop ringing when a free zap line is found | ||
| Reporter: | Brad Barnett (bbarnett) | Labels: | |
| Date Opened: | 2007-06-12 06:11:45 | Date Closed: | 2011-06-07 14:08:17 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Functions/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) console.output.asterisk.txt | |
| Description: | Debian packaged Asterisk version 1.4.4, i386. When I do: Dial(Zap/1&SIP/place) It will ring both lines until one answers. When I do: Dial(Zap/g1&SIP/place) it will ring the SIP line until a zap line is found, and then stop once the ZAP line starts ringing. This makes groups unusable for me. The only other answer is to write an intricate dial plan, which checks to see if each zap line is free, _then_ tries to use it. This is because, if one tries to simple dial each zap line in turn, the SIP line will still succeed. Since zap lines are picked up all the time here, outgoing zap calls often are dropped in favour for the SIP. For example, let's say I craft a dialplan that checks to see if zap/4 is free, then zap/1, then zap/5. If it finds a free zap, it then tries to dial zap/free&SIP/number. However, if the zap line has been picked up before the dial attempt happens, the SIP still succeeds, the zap is ignored, and the outgoing call is a no-go. Usable zap groups would be a big bonus. I'm not sure if this is a bug, or a current implementation.... | ||
| Comments: | By: Joshua C. Colp (jcolp) 2007-06-12 07:05:55 Can you please attach the console output of a call attempt where this happens? By: Brad Barnett (bbarnett) 2007-06-13 08:50:33 Note that the "Zap/4-1 answered SIP/211-081e8e70" is not the Zap channel being successfully answered, only the Zap channel being found and used. It just starts ringing at that point.... By: Joshua C. Colp (jcolp) 2007-06-13 08:52:38 Is that an analog FXO port that was selected? By: Brad Barnett (bbarnett) 2007-06-13 09:34:03 Yes, it is one of the Digium 4 port cards, with some analog modules on it... By: Joshua C. Colp (jcolp) 2007-06-13 09:36:27 This is not a bug then but a limitation of analog. It does not provide accurate call progress detection (whether the remote side has answered/is ringing) so Zaptel considers it answered immediately unless callprogress is set to yes. If you do set callprogress to yes though your calls may be randomly hung up. By: Brad Barnett (bbarnett) 2007-06-13 10:17:18 Many apologies. Thanks for the time. By: Brad Barnett (bbarnett) 2007-06-13 10:18:32 Arg, sorry about the reopen. :( | ||