top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

What is the reason behind not having the controlled re-routing in M3UA/SIGTRAN?

0 votes
273 views

What is the reason behind not having the controlled re-routing in M3UA/SIGTRAN? Is it so that we don't need such procedures in IP world?

posted Jul 26, 2016 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

No its not because of IP but because of streams in SCTP. In MTP3 we have SLS and same SLS messages is mapped to same physical link to maintain the sequence delivery and in M3UA we make sure same SLS message is mapped to same stream and SCTP guarantees in sequence delivery within a stream.

answer Jul 26, 2016 by Salil Agrawal
Similar Questions
+4 votes

Assume you have the conditions (one AS, etc.) to allow RC to be optional, does the RFC permit one side (IPSP SE mode for example) to still send an RC and the other to not include an RC? I think the answer is yes, but I can't find an explicit reference permitting it.

+1 vote

Going thought the RFC 3332 and have a doubt about RC, in M3UA we have a concept of routing context to identify an AS but same can be achieve by the routing Key (it seems) then what the purpose RC is serving.

+3 votes

Why we use Point codes in SIGTRAN when we have IP address to identify the nodes ?

In SIGTRAN, we have SCTP transport and have Source and destination IP addresses.

In such a case , why we need point codes to identify the destination node ?

i can understand that point codes are needed in SS7 since, its not IP . But why we need point codes in SIGTRAN ?

+1 vote

From what I understand, an ASP is a process running on an AS, and a SGP is a process running on a SG. Each ASP SGP link is a SCTP connection.

Also, I understand that SGP is responsible for message-routing, while an ASP is merely an end-point for a SCTP connection.

Given that, are there any extra differences between a ASP and SGP (in addition to the routing-capabilities of a SGP)?

+2 votes

We are trying to connect open MGW to an AOIP BSC. Both belongs to different vendors. Fluctuation of M3Ua SUA observed at BSC end post Connectivity.

As per MGW vendor BSC is not supposed to send SUA management messages to MGW( DAUD) which is causing MGW to send DUNA to BSC which is causing fluctuations @ BSc end for mgw cluster SPC.

Please be informed, there is no fluctuation @ association level. Kindly suggest and share the actual guidelines.
What should happen as per RFC.

...