Ashish,
The NIST implementation ( and indeed the jain-sip spec) expects you to
manage your own response context. For forking requests, the current impl
will just handle the first dialog at the UA and subsequent dialogs are
presented to the UA for stateless processing. This is changing in the
next version of the spec where better support is provided at the dialog
layer for forking support at User Agents. In the next version, if you
configure automatic dialog support on, you will get a fresh dialog for
each forked response that belongs to a different dialog. This handles
the case of upstream forking by proxy servers.
Hope that answers your question.
Ranga
Maricarmen Alcazar wrote:
Ok, thanks...
I am working with jain-sip (nist). Do you know if this implementation
supports response context processing or should the proxy core take care of
it??
On 11/29/05, Ashish Kumar Balyan <[EMAIL PROTECTED]> wrote:
Hello Carmen,
In case if stack is responsible for forking then response context should
be processed by the stack as only a single merged response should be
given to the proxy core in case of multiple failure responses.
On the other hand if proxy core is taking care of forking than proxy
core should process response context, since all the repsonses will be
given to the proxy core.
Regards,
Ashish
Continuous Computing
Maricarmen Alcazar wrote:
Hi everyone,
I'm developing a SIP Proxy and I have a problem with response
context.
Are response-contexts processed by the stack or must the proxy core take
care of that??
Thanks on advance
Carmen
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
