I'm afraid your logs don't mean anything, really. You need to increase the loglevel of sipXproxy to INFO, at least, an then create a trace file.
See: http://sipx-wiki.calivia.com/index.php/Display_SIP_message_flow_using_Sipviewer#Getting_SIP_Messages_to_display when you get the trace data, take a look at it using sipviewer and/or post the trace with a description of your configuration (identify components by IP address), what you were doing, and which call in the trace you're talking about (by call-id or frame number in the trace, preferably). -MM On Fri, Oct 31, 2008 at 7:34 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>wrote: > No, problem. Thanks for your efforts in helping me. > > What do the logs errors, that i have attached, mean. When this error is > happening? > > On Thu, 2008-10-30 at 08:35 -0400, Picher, Michael wrote: > > Sorry, I'm not familiar with how to implement OSBC as I haven't used it > > personally. Somebody was supposed to be working on a sipX wiki page I > > thought. > > > > Possibly Joegen might help over on the OSBC forum or he watches this one > > sometimes too... > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
