Hi Soma, I do see the behavior that you described in your logs. Something is definitely broken.
What version/branch of code are you working from? I suspect that something is hung/deadlocked in sipXtapi or call processing. A number of issues have been fixed recently, so, I want to verify that you are using the latest on the sipXtapi branch before we chase it. - Bob On Friday, August 18, 2006, 6:05:54 AM, somasundaram easwaramoorthy wrote: > Here is the user2's log file. Thanks for your help > somasundaram easwaramoorthy <[EMAIL PROTECTED]> wrote: > Hi Bob, > > Thanks for your response. I enabled logging and found that when > user2 calls user1 the user1's soft phone gets the CALLSTATE_OFFERING > event and calls the sipxCallAccept(..). It looks like this call is > not successfull. 5 seconds after the call is made > CP_OFFERING_EXPIRED event kicks in. Then the 486 busy here is sent by user1 > to user2. > > Because of size of logs I am attaching the log from user1 in this > email and send a followup email with user2's log. I do not know what > I am doing wrong that is causing the sipxCallAccept to fail. Can you > please take a look at the logs and help? > > regards, > Soma > > > Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. > Great rates starting at > 1¢/min._______________________________________________ > sipxtapi-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/ > > Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates > starting at 1¢/min. _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
