Hi, Section 2.3.2 of RFC 4077 says:
"When a NACK is received for a message sent over a reliable transport, the SigComp layer must indicate to the application that an error has occurred. In general, the application should react in the same way as it does for any other transport layer error, such as a TCP connection reset. For most applications, this reaction will initially be an attempt to reset and re-establish the connection, and re-initiate the failed transaction. The SigComp layer should also use the information contained in the NACK to make appropriate adjustments to the compressor associated with the proper compartment (similar to the adjustments made for unreliable transport). Thus, if the compartment is not reset by resetting the TCP connection, the next message will take advantage of the adjustments" While handling NACK over TCP, SIP should adopt the same approach as specified above or any suggestion on specific implementation. Presently, my implementation expects (assumes), once message given to TCP, no re-transmissions are needed. On any error, it simply terminating the dialogue. Before doing design changes to accommodate above case, I am looking for suggestions/inputs on how in real time deployment SIP behaves. Thanks in advance -Venu _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
