We have been seeing an issue every Saturday evening where REGISTER fails. It then begins to work again Sunday evening. We finally traced this back to the Proxy sending an invalid Date: header for Sunday GMT in the 200 OK response. For example:
Date:07 Jan 2007 18:58:03 GMT Looks like they forgot the Sunday in their database of days of the week. Anyway, the real issue I have with sofia is the lack of any indications of the problem. I could see in the sip trace that the REGISTER gets resent over and over and finally we get a 408 from the stack. The only thing I could see with nta debug on fully was: nta: 200 OK failed sanity check But, it actually didn't fail the sanity check. What appears to happen in agent_recv_response() is the sip->sip_error is set. What I don't understand is why the iteration of the errors doesn't print the nta: %03d has bad %s header\n I was wondering, is there anyway to ignore these non-fatal errors ? i.e. Are they classified so that I could not ignore the packet when a non-critical header has a problem ? Thanks for your attention, Colin.. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sofia-sip-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
