hi if call resolver restarts (from web page) all stucked calls are gone from list but lost.
Is there any way to restart callresolver from terminal? On Wed, Dec 3, 2008 at 10:23 AM, VG <[EMAIL PROTECTED]> wrote: > Hi Raymond, > > I am facing same problem. > > I also discussed it on mailing list some time ago. > I am well aware of this situation. > > > But still some calls which have been answered and properly disconnected are > not in CDR. > I have noticed a situation where. > A call to B. > and after 200ok > if A sends CANCEL then sometimes it get struck. > I don't know why CANCEL message is generated by Phone instead of BYE. > > I am not so much aware of ruby so do not have much idea about call resolver > working. > But your idea definitely remove 90% of the issue. > > Regards, > Vikas > > > On Wed, Dec 3, 2008 at 1:45 AM, Scott Lawrence <[EMAIL PROTECTED]>wrote: > >> >> On Tue, 2008-12-02 at 08:42 -0500, Raymond Dans wrote: >> > I haven't heard any feedback on the following so I thought I would send >> > it again in case people missed it. If there are no comments or >> > disagreement to the changes, I'll proceed with implementing them. >> >> These changes look fine to me, Raymond. >> >> > As of late, there has been a number of issues reported in CDR dealing >> > with calls being "stuck" in the Active Calls list. There are a few >> > reasons for these (i.e. Network issues resulting in lost SIP messages, >> > SIP Registrar being down, ....) and as a result, I'd like to propose a >> > couple of changes in CDR to handle these scenarios and reduce the number >> > of "stuck" call scenarios. >> > >> > Enhancement 1: Redefining the meaning of Active Call >> > An Active Call today as defined in CDR and shown in the Admin >> > Active Call page is any call in the system for which an INVITE has been >> > sent and no BYE or Failure has occured. I'd like to modify this >> > definition to be only those calls which are Established (i.e. 200 OK >> > --> Answered). Essentially this removes those calls for which no dialog >> > has been formed. I know people use the Active Calls page for testing >> > purposes and like to see calls that are in a ringing state but a truly >> > "Active Call" is one which is established and not one which is being >> > offered. >> >> > Enhancement 2: Trapping calls which are ringing too long >> > If the Call Resolver misses SIP messages for whatever reason >> > (network issue, Proxy generated outgoing failure messages) a call can >> > become "stuck" in CDR as it has not seen any new events on the call >> > since the original request. I'd like to put some sort of timeout value >> > on this "ringing" state such that if I don't see a new call state event >> > (while in Ringing/Request) within a period of time (say 2 minutes), CDR >> > would inject a failure (say Request Timeout) and move the call to the >> > potentially failed queue to eventually be written to the database as a >> > failed call. >> > >> > >> > These 2 enhancements will not completely eliminate all "stuck" calls but >> > it will greatly reduce the number as well as provide a more accurate >> > record of call activity on the system. >> > >> > Comments? >> > _______________________________________________ >> > sipx-dev mailing list >> > [EMAIL PROTECTED] >> > List Archive: http://list.sipfoundry.org/archive/sipx-dev >> > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev >> >> _______________________________________________ >> sipx-dev mailing list >> [EMAIL PROTECTED] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev >> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev >> > > > _______________________________________________ > sipx-dev mailing list > [EMAIL PROTECTED] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > -- vikas sharma
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
