Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 1128 by hiroakisolid: Let me know the configuration of session replication on MSS1.1
http://code.google.com/p/mobicents/issues/detail?id=1128

We tested the session replication in a cluster using MSS1.1 on JBoss AS
4.2.3. However, it was not able to be worked. Please let me know the right
configuration, if I made a mistake. If there is a bug, please check it.

I leaned the configuration from the follows URL.
6.4.2. MSS for JBoss: Clustering Support
http://hudson.jboss.org/hudson/view/Mobicents/job/MobicentsDocumentation/lastSuccessfulBuild/artifact/html_single/index.html

What steps will reproduce the problem?
1. I attached the sample application which work like B2BUA.
Here is the tested environment.
Server1: 172.28.43.177
  SIPp1 as UAC
  SIPp2 as UAS
Server2: 172.28.43.176
   MSS1.1 as named Mobicents1
Server2: 172.28.43.175
   SIP LB
   MSS1.1 as named Mobicents2
SIP Sequence Scenario
1. Run B2BUS under the environment.
SIPp1 - SIPLB - Mobicents1 - SIPLB - SIPp2
2. Shutdown Mobicents1 after ACK was sent to SIPp2.
Kill -9 <pid>
3. After that, SIPp1 send an update to SIPLB.
4. SIPLB send the update to Mobicents2 because of Mobicents1 is shutdown.
SIPp1 - SIPLB -X- Mobicents1
5. An Exception was occurred when Mobicents2 received the update.

I attached a sample application. The application include some log file and
configurations. If the configuration is wrong, please let me know the right
configuration. If there is a bug, please fix it.

What is the expected output? What do you see instead?

I expect the session is replicated to another server.

What version of the product are you using? On what operating system?

MSS1.1 on JBoss AS 4.2.3 which is released at Dec 3rd.

Please provide any additional information below.


Attachments:
        sequence Folder.zip  441 KB

--
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

Reply via email to