Anything above 1.6.0.4 I believe. I required another patch (
http://bugs.digium.com/file_download.php?file_id=21859&type=bug ) to get
it to work with 1.6.0.9 but that patch had no affect on 1.6.1.0.
It is getting confusing for me.
Thanks,
Tzafrir Cohen wrote:
> On Fri, May 29, 2009 at 12:16
On Fri, May 29, 2009 at 12:16:55PM -0400, Mike van der Stoop wrote:
> I've had the same issue with 1.6.0.9, if you can dial in, then dial out
> then you have the same problem. I turned off hardware DTMF and it works
> so far.
> The issue may be https://issues.asterisk.org/view.php?id=14761.
Ar
sean darcy wrote:
> Still trying to upgrade to 1.6.0.9 for 1.4.
>
> It worked - it worked all day yesterday, but this morning:
>
> -- Executing [646xxxy...@longdistance:1]
> Answer("SIP/172-08276a60", "") in new stack
> ..
> -- Executing [646xxx...@longdistance:6] Dial("SIP/172-
Jared Smith wrote:
> On Wed, 2009-05-27 at 10:46 -0400, sean darcy wrote:
>> -- Executing [646xxx...@longdistance:6] Dial("SIP/172-08276a60",
>> ""DAHDI/g2"/1646xxx") in new stack
>
> It appears you're attempting to dial "DAHDI/g2"/1646xxxyyy instead of
> DAHDI/g2/1646xxx... Did you
On Wed, 2009-05-27 at 10:46 -0400, sean darcy wrote:
> -- Executing [646xxx...@longdistance:6] Dial("SIP/172-08276a60",
> ""DAHDI/g2"/1646xxx") in new stack
It appears you're attempting to dial "DAHDI/g2"/1646xxxyyy instead of
DAHDI/g2/1646xxx... Did you mean to put those extra quote
On Wed, May 27, 2009 at 10:46:39AM -0400, sean darcy wrote:
> Still trying to upgrade to 1.6.0.9 for 1.4.
>
> It worked - it worked all day yesterday, but this morning:
>
> -- Executing [646xxxy...@longdistance:1]
> Answer("SIP/172-08276a60", "") in new stack
> ..
> -- Executi
Still trying to upgrade to 1.6.0.9 for 1.4.
It worked - it worked all day yesterday, but this morning:
-- Executing [646xxxy...@longdistance:1]
Answer("SIP/172-08276a60", "") in new stack
..
-- Executing [646xxx...@longdistance:6] Dial("SIP/172-08276a60",
""DAHDI/g2"/1646xxxy
