Usually, calls terminating at 30 seconds is a sure sign that you need to add an Answer() in your dialplan. Try dropping that in before you dial out. I have seen this so many times and Answer() has always fixed the issue. The magic number is 30 seconds.<br>
<br>Depending on if you use your CDRs for anything, especially billing, you may need to figure a way around that, since even if a call rings out, the CDR will reflect Answered.<br><br>-- <br>Thanks,<br>Steve Totaro <br>+18887771888 (Toll Free)<br>
+12409381212 (Cell)<br>+12024369784 (Skype)<br><br><br><br><div class="gmail_quote">On Fri, Nov 7, 2008 at 10:38 PM, Grey Man <span dir="ltr"><<a href="mailto:greymanvoip@gmail.com">greymanvoip@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">To get to the bottom of it I'd recommend determining why the ACKs are<br>
not getting through to Asterisk rather than trying to work around it.<br>
I'm actually suprised Asterisk terminates the call by default when it<br>
doesn't get the ACK to it's 200 Ok response that must be new for<br>
1.4.22 as I haven't seen that behaviour in earlier versions. In my<br>
opinion it's unwarranted behaviour, if Asterisk is getting RTP then it<br>
should leave the call up irrespective of whether it gets an ACK or<br>
not.<br>
<br>