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).
But the interesting part came next...
-- Call accepted by 66.234.228.132 (format ULAW)
-- Format for call is ULAW
-- IAX2[voicepulse]/6 stopped sounds
-- IAX2[voicepulse]/6 stopped sounds
-- IAX2[voicepulse]/6 is ringing
-- IAX2[voicepulse]/6 stopped sounds
-- IAX2[voicepulse]/6 stopped sounds
-- IAX2[voicepulse]/6 answered [EMAIL PROTECTED]/1
-- Attempting native bridge of [EMAIL PROTECTED]/1 and IAX2[voicepulse]/6
-- Channel '[EMAIL PROTECTED]/1' ready to transfer
-- Channel 'IAX2[voicepulse]/6' ready to transfer
-- Releasing IAX2[voicepulse]/6 and [EMAIL PROTECTED]/1
-- Hungup 'IAX2[voicepulse]/6'
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.
But the call instead is dropped at this point instead - both sides disconnected from the cloud.
Anybody know why and how this is controlled and what my options are?
-- Bill Michaelson - COS, Incorporated - Software Development - [EMAIL PROTECTED] Thanks for putting up with my spam filter!
