top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

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

+3 votes
719 views

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 ?

posted Dec 19, 2013 by Nithin Kp

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button
IPAddress is for the IP Layer Node identification and Point code is for the upper layers...
commented Dec 19, 2013 by Anderson

1 Answer

+3 votes

SIGTRAN replaces E1/T1 LINK with IP link without change of application which still thinks that it is working over SS7. Hence Point Code is required to identify the node.

answer Dec 19, 2013 by Salil Agrawal
Similar Questions
0 votes
What is the reason behind not having the controlled re-routing in M3UA/SIGTRAN?

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?

+4 votes
M3UA/SIGTRAN: Optional RC configured on one side and not the other

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
Conceptual doubt between an ASP and SGP in Sigtran

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
Sigtran interworking issue between multivendor node

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.

+1 vote
Can we have a scenario where PCRF gets multiple attach request with only Framed-IP-Address and Session-Id are different?

Can we have a live scenario wherein PCRF gets multiple attach request(CCR-I) where only the Framed-IP-Address and Session-Id are different but Subscriber-Id information and APN remain same? From network point of view, what can be the use case for this?

...