On Wed, 2008-04-02 at 17:55 +0500, asif wrote: > I am getting this in cause parameter of my diconnection event handler > and I can’t find any help regarding this issue. Please let me know if > anyone came across the same thing.
I'm not that familiar with sipXtapi, but I suspect that you are running into the limit on the number of active calls that are allowed. (The default is 200, IIRC.) An easy way to do that is to use "drop connection" to terminate a call rather than "drop". Also, remember that even when the TAPI tells you the other end of the call has hung up, you still have to drop the call. Dale _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
