Automatic dialog support per provider & SIP RA Type
If I may continue from offline conversation:
>After talking to Ranga for a while it turned out that the >dialog support has to be anabled or disabled per >provider. This means that if you want to have an RA with >dialog support and another faster one (for
>proxies) without dialog support, then you would need to >have 2 sip providers listening to two different ports. >Potentially all UAs will initially connect to the fast >provider without dialog support and if needed they will >be either redirected to the other one or a server
>side forward will be used. The latter adds overhead >because each future UA request will have to be marshalled >to java objects and back to the network twice.
1. Spontaneously I think it's rather awkward to introduce listeners on different ports just to differentiate the dialog support for different applications. It seems you are on the same road.
2. Up until now, before I knew that automatic dialog support is configured per provider in JSIP 1.2, I had just assumed that no applications would assume that this is enabled in a JSLEE container. This is because it is easy to obtain the dialogs anyway and the performance penalty should not be acceptable if there are applications that do not need it.
But of course there can be situations where all applications use dialogs.
I just want to stress that using JSIP 1.2 with automatic dialog support disabled should not be a big problem at all. All you have to do as an application writer is to obtain the dialog before the request is sent (if you're the client transaction) and, correspondiingly obtain the dialog before any response is sent (if you're the server transaction).
I have the idea that instead we can configure the JSLEE to "prepare the dialogs" for the application instead of using JSIP for this. I realize though that the architecture may not be optimal for this in that the RA related responsibilities are not per service...