Ernie Dunbar
2011-Jun-28 17:00 UTC
[asterisk-users] Using Dial() on SIP and DAHDI connections simultaneously
I think there is a bug in the Dial() application in Asterisk 1.6.2.17 that wasn't present in 1.4.23.1, and I'd like to see if anyone else has this problem. I've been able to reproduce this error: When you use the Dial() command to send a call to both a SIP connection and a DAHDI connection, if the DAHDI connection is busy, the call always gets rejected with an Asterisk message saying the line is busy, even if the SIP connection is not busy. The inverse is not true: if the SIP connection is busy but the DAHDI connection is not, the call goes through to the DAHDI connection without a problem. ---------------------------------------------------------------- This message was sent using Lightspeed.ca's Advanced Webmail.
Reasonably Related Threads
- SIP connections over OpenVPN connection get one-way voice.
- Asterisk 1.6 produces *many* zombie processes on Debian.
- How do *you* test your changes to dialplans ruled by GotoIfTime?
- Problem compiling res_fax_spandsp.c on Debian server.
- Sending calls to a particular T1 port.