[OpenSIPS-Devel] Avoiding creating outgoing TCP connections for NOTIFY requests

[Olle E. Johansson]

8 okt 2012 kl. 18:06 skrev Saúl Ibarra Corretgé <saul at ag-projects.com>:

> Hi all,
> 
> In order to avoid creating an outgoing TCP connection which would block needlessly we have the ability to use tcp_no_new_conn_bflag. When looking up the location for a user all flags will be loaded, so if we specified the said flag when the user was registered a new connection will not be attempted if there is no connection.
> 
> However AFAIK this doesn't apply to NOTIFY requests generated by OpenSIPS when using presence. Scenario is simple: user subscribes using TCP, her connection breaks, someone sends a PUBLISH. OpenSIPS will try to open a connection to deliver the NOTIFY. This is what I'd like to avoid.
> 
> First thing that comes to my mind is reusing the idea with tcp_no_new_conn_bflag, so if a user sets if before calling handle_subscribe, in-dialog NOTIFY requests would not attempt to create the connection.
> 
> Thoughts, proposals, patches are welcome :-)

Now, if we had Outbound support, which may be the case in the future, there could be multiple flows toward the client. Just stopping NOTIFY would seriously harm that future architecture.

Also, if there is a route set you might have multiple options to reach the client.

Just my 5 eurocent.

/O