SIP Proxy service - conflict with auto-dialogs in SIP RA 1.2
seems to me that a clean way to resolve this type of conflicts is for the proxy service to use its own SIP RA instance listening on a dedicated port.
Services interested in auto-dialogs would most likely act as end-points of some sort and would therefore be a forwarding target of the proxy.
So all external SIP requests would go to the SIP RA of the proxy (port 5060) and it will use some local configuration policy to forward to the port of the SIP RA for end points (e.g. port 5070).
This is going back to the earlier discussion of leveraging the recent update to JSIP 1.2, which allows multiple stacks with individual ports sharing the same jsip implementation. I find this a clean and simple solution.
> One more issue remains - sip ra 1.2, automatic dialog
> creation and proxy?
> How does this relate to each other? I mean if we have
> service that creates dialog proxy wont receive event
> since it will be fired as "in dialog". This happens
> because RA determines whaether in dialog event can be
> received. However at that moment it doesnt have any
> knowledge if it will be processed. If its not, dialog
> could be created (if it is INVITE request) anyway -
> possible solution is to make RA check if that INVITE
> was processed successfuly, if not it should fire
> again that event, as not in dialog event.
> Secodn solution would be to change slitghtly design
> and make RA fire events when they are expected, I
> mean if RA detects that both 1.1 and 1.2 are expected
> it will fire both , but this can lead to some
> Any comments?