<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body>
I coded a dialplan that conditionally forwards a call to my cell phone if
no answer on site.<br>
<br>
During a test, I received a call (via Voicepulse IAX) which correctly Dial'ed
out to my cell phone (also via Voicepulse) as expected. Fine - it worked
- except that the voice delay was so extreme (> 1sec).<br>
<br>
But the interesting part came next...<br>
<br>
<small><font face="Courier New, Courier, monospace"> -- Call accepted
by 66.234.228.132 (format ULAW)<br>
-- Format for call is ULAW<br>
-- IAX2[voicepulse]/6 stopped sounds<br>
-- IAX2[voicepulse]/6 stopped sounds<br>
-- IAX2[voicepulse]/6 is ringing<br>
-- IAX2[voicepulse]/6 stopped sounds<br>
-- IAX2[voicepulse]/6 stopped sounds<br>
-- IAX2[voicepulse]/6 answered IAX2[voicepulse@voicepulse]/1<br>
-- Attempting native bridge of IAX2[voicepulse@voicepulse]/1 and IAX2[voicepulse]/6<br>
-- Channel 'IAX2[voicepulse@voicepulse]/1' ready to transfer<br>
-- Channel 'IAX2[voicepulse]/6' ready to transfer<br>
-- Releasing IAX2[voicepulse]/6 and IAX2[voicepulse@voicepulse]/1<br>
-- Hungup 'IAX2[voicepulse]/6'<br>
</font></small><br>
Native bridge? Cool! I says to myself. I figure the call will be released
from * and handled entirely by Voicepulse, who I assume will bill me appropriately
for the remainder of the "outgoing" call. And I'll get better quality for
the remaining duration.<br>
<br>
But the call instead is dropped at this point instead - both sides disconnected
from the cloud.<br>
<br>
Anybody know why and how this is controlled and what my options are?<br>
<pre class="moz-signature" cols="$mailwrapcol">--
Bill Michaelson - COS, Incorporated - Software Development - <a class="moz-txt-link-abbreviated" href="mailto:bill@cosi.com">bill@cosi.com</a>
Thanks for putting up with my spam filter!</pre>
</body>
</html>