2007/6/13, Jan Van den bosch <[EMAIL PROTECTED]>: > Hi, > I'm using a heavily modified version of the SofSipCli as my client on both > sides. Sometimes, it happens that a receiver responds to an INVITE request > with a 180 Ringing and a 200 OK, but the sender fails to recognize it. > Attached are a log file of the sender application and an Ethereal capture > file. > > 10.10.202.41 invites 139.10.136.113. 172.16.58.47 acts as a proxy between > them. You can see in the capture file that 10.10.202.41 receives a 180 > Ringing and a 200 OK, but 10.10.202.41 fails to ACK, so 139.10.136.113 sends > an early BYE. ... > In other words: both the 180 Ringing and 200 OK are ignored. Any ideas?
There seems to be nothing funny in the messages (except SDP is RFC4566-compliant). Could you run your tests with environment NTA_DEBUG=9 NUA_DEBUG=9 set so the debugging output from stack would be shown? -- Pekka.Pessi mail at nokia.com ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
