> What kind of implementation would be best for this? > I was thinking maybe the socket could have a short timeout. > This would still keep the proxy stateless. > > Or maybe keep a small amount of information relating to the > SIP request just forwarded. Then when the response comes in, > it can be matched to the request and then close the related > socket. As a backup, there would be a timeout too in case no > response came back. > > Would these solutions be reasonable? > Any better suggestions?
Hopefully the tls drafts will address the best common practice associated with it. And hopefully the outbound drafts will address the best common practices associated with it. Until then, the following things are desirable to consider. 1) Limit the total number of connections. 2) Limit the total number associated with a particular ip-address. 3) When limits have been reached, decide if you want to reclaim other connections or block/release the new connection. 4) Unfortunately nothing currently defines how to negotiate how many connections should remain active between two devices. And thus if device A desires 4 and device B desires 2, it can lead to situations where connections can be continually opened/closed/rejected or lack service limited unless the devices can synchronize about how many connections to keep open. 5) All of the above might be unique depending upon the remote device, particular situation, etcetera. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
