Comment #2 on issue 648 by vladimir.ralev: SipServletMessages are not
serialized correctly
http://code.google.com/p/mobicents/issues/detail?id=648
Replication actually works fine for the most part. It's a problem with
session
replication where the dialog is serialized. The dialog is also serialized
fine.
However, my sip phpones have a problem with their own binding address which
blocks
the completion of the INVITE-OK-ACK. The dialog is left in early state and
although
it doesnt have a dialogid, it has the earlyDialogID. So we can try to
handle this
case as well.
Further, my specific phones use early dialog establishment:
INVITE --- 100 (trying), 101 (dialog establishment), 180(ringing), 200 (OK)
ACK
I am not sure if that 101 (Dialog establishment) causes any trouble in this
case.
--
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