On Mon, Mar 14, 2011 at 10:34 AM, Kumaran < [email protected]> wrote:
> Kumaran wrote: > >> Hi Mircea , >> The delay is only for failed calls.The completed calls are shown >> without any delay.No calls failed will be shown in Active tab(once answered >> only it will show in Active tab) >> > Well, I am not sure what to say in your case... What I know, is that failed calls are a bit harder to maintain. A failed call can occur if data packets are lost due to a network problem and due to this you can lose some call events sipXproxy/callresolver use various threads that usually are sleeping and become active when a call event is catched Even more, failed calls can be reported active for many hours, here is what the quickhelp says: [...] It is possible that if packets are lost in your network, calls are occasionally reported as active for a long time. These calls are not actually active and the display is corrected after a couple of hours automatically. [...] So I am not so sure in your case... probably your delay is due to some call events loss, maybe putting a sniffer would help... to see what happens when a call gets failed, and what happens after 6 minutes, when you say that the call is actually displayed. Also please check how fast your web page refreshes... Hope this helps, Mircea > Regrds >> Kumaran T >> >> Mircea Carasel wrote: >> >>> >>> >>> On Wed, Mar 9, 2011 at 7:57 AM, Kumaran < >>> [email protected] <mailto: >>> [email protected]>> wrote: >>> >>> Hi Mircea, >>> Still the same problem-there is 6min delay.Please >>> check the attached sipxcallresolver.log file. >>> >>> >>> Does this behavior occurs only for failed calls? Please let me know what >>> happens with completed calls? The delay still applies to them also? >>> Also, during this delay (6 mins) are the calls reported as active (the >>> Active tab) >>> Mircea >>> >>> >>> >> >> >
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
