On Mon, 2010-01-25 at 12:43 -0500, Andres Jaramillo wrote: > Looking in the sipXproxy.log , I found a lot of these entries > > "2010-01-25T17:25:16.398189Z":10700:SIP:WARNING:srvnortel1.prodesa.local:SipRouter-11:B6F5CB90:SipXProxy:"SipUserAgent::send > INVITE request matches existing transaction"
That is normal, so don't worry about it (now). > "2010-01-25T17:25:18.009338Z":10715:HTTP:WARNING:srvnortel1.prodesa.local:SipClientUdp-:B7AE7B90:SipXProxy:"HttpMessage::getBytes > content-length: 211 wrong setting to: 212" That may indicate a problem with some other component of your system. Can you get a snapshot including messages from a time period when those messages are logged? > I dont understand , any help will be apreciated > > > The sipXproxy process still in 200% :S In the short run you can cure that by restarting the sipXproxy process from the GUI. (Or you can "kill -9" it from the command line -- the supervisor system will restart it.) Dale _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
