ajitlakhwani / jss7

Automatically exported from code.google.com/p/jss7
0 stars 0 forks source link

Can not define multi-homed peers #331

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Hello, 

We are developing a SIGTRAN app using Mobicents Stack and realize that is not 
possible to define multi-homed peers. Yes, We know that once SCTP INIT-ACK is 
received, all ip´s of the multi-homed peer are received and registered by 
Mobicent Stack.
But, what if remote primary IP is not available?, so, response (INIT-ACK) to 
INIT message will not be received, and, in consequence, SCTP connection will 
not be established.
According to standard SCTP connection initiation protocol should behave in this 
way:

Initial Association Establishment.
The first phase is initial association establishment: it is always executed 
toward one remote IP address and can be repeated for a specified number of 
times . In case of a missing answer to the first attempt, more attempts are 
performed by changing the local IP address for each new attempt.
So, considering the above general scenario and assuming that B1 is the first 
remote IP address on peer that is going to be attempted, the sequence is:
1. A1 -> B1
2. A2 -> B1
3. A1 -> B1
4. A2 -> B1 ... and so on, until reach maximum number of times.

At the first successful answer, the association is established.
In the case that B1 is not answering, B2 is attempted, with the same rotation 
of source addresses as follows:

1. A1 -> B2
2. A2 -> B2
3. A1 -> B2
4. A2 -> B2 ... and so on, until reach maximum number of times or B2 answers.

If the SCTP association is finally established, a primary SCTP path is 
established and the reconfiguration is such that the primary source IP address 
is the first IP address defined in the endpoint definition.

Original issue reported on code.google.com by elyama...@gmail.com on 2 Apr 2014 at 4:21