[Freeswitch-users] Call intercept problem

[Michael Jerris]

I would agree with you that I would doubt no one has experienced this if its happening (although we do so edge case issues).  Thats my point.  We typically fix several dozen random issues per point release, so there have been hundreds of fixes since 1.4.6. I for sure will not remember every issue we have fixes in that timeframe.


> On Feb 3, 2015, at 12:15 PM, Tim Bock <jtbock at synacktics.com> wrote:
> 
> Thank you, I appreciate the response.
> 
> I have rebuilt with the latest release; just waiting for a window to 
> install (which looks like tonight). It just seemed unlikely to me that 
> no one else had experienced this.
> 
> In any case, I'll update after upgrading to the new release.
> 
> Thanks again,
> Tim
> 
> On 02/03/2015 10:46 AM, Michael Jerris wrote:
>> I would try latest 1.4 release as many issues have been fixed since 1.4.6
>> 
>>> On Jan 30, 2015, at 11:07 PM, Tim Bock <jtbock at synacktics.com> wrote:
>>> 
>>> Hello list,
>>> 
>>> Running freeswitch 1.4.6, though have also seen this issue with older
>>> versions.
>>> 
>>> After the initial freeswitch install, I tested the call intercept
>>> function, and it worked fine. Fast forward several months ahead, and now
>>> call intercept doesn't work.  Looking at the logs, the message is that
>>> the channel is no longer available.  Indeed, when I examine the uuid the
>>> call intercept function is trying to connect, the uuid is for the call
>>> immediately preceding the current call, sort of like an "off by one"
>>> indexing error. This is reliably repeatable.
>>> 
>>> Any thoughts on why this is occurring? And more importantly, any way to
>>> fix it?
>>> 
>>> Thank you,
>>> Tim