Comment #5 on issue 648 by vladimir.ralev: SipServletMessages are not
serialized correctly
http://code.google.com/p/mobicents/issues/detail?id=648
OK, that last exception is caused by SIPP and can be ignored for now
otherwise the
call flow is complete. And the test is checked in. I am not going to close
the issue
in case something goes wrong again.
Further we need to review if we need separate replicatedContext and
sipReplicatedContext threadlocals, because while looking at it it seems to
me that is
an app session is created from withing a web app the sipReplicatedContext
is null (we
are in a web thread at this point) and this app session is not flushed to
the
distributed cache right away. It is probably flushed later when the
responses start
to come in sip threads.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
