Re: [reSIProcate-users] TCP-connection closed when parsing fails
The problem is, if the message cannot be parsed, you can't keep the framing intact. We need to have the Content-Length header, and if the message is unparsable as a whole, we can't get it.
Best regards, Byron Campen Hi! We’re experiencing a problem with TCP-connections. An INVITE with incorrect Contact-header (Contact: <sip:sipp@xxxxxxxxxxxx>\rsip:sipp@xxxxxxxxxxxx) is received via a proxy to our reciprocate 1.3 based UA using TCP. The problem is that when the parser fails, the TCP-connection is torn down at the same time. Since the proxy fronting our application serves many remote destinations this hurts more than the user sending the incorrect INVITE. Also, the proxy lacks some logic to re-establish the connection which leads to a blacklist for some time. What is the reason for tearing down the connection when the parser fails? Is this error so severe that it’s considered to be unrecoverable? Please see the attachment for logs. I’m also working on this from the other direction, trying to get the proxy to re-establish the connection. Cheers, KJ <preparse_failed.txt>_______________________________________________ resiprocate-users mailing list resiprocate-users@xxxxxxxxxxxxxxxList Archive: http://list.resiprocate.org/archive/resiprocate-users/
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature