[erlang-questions] Multiple Diameter Connection issue

[anders.gs.svensson@REDACTED]

diameter 1.3 is from OTP R15B03, released in November 2012, which is
the release that added the restrict_connections option, which looks to
be what you're having problems with. I don't recall any issues (not
that I recall much of anything from 2012), and don't see anything in
the release notes, but I suggest trying with a more recent release for
starters.

The latest is diameter 2.1.1 in OTP 20.1.2. (Although there's a fix to
a problem introduced in 20.1 coming in 20.1.3, unrelated to
restrict_connections.)

Anders


erlang-questions-request@REDACTED writes:
> Date: Mon, 16 Oct 2017 21:24:34 +0545
> From: Dinusha Ganganath Perera <dinushaganganath@REDACTED>
> To: erlang-questions@REDACTED
> Subject: [erlang-questions] Multiple Diameter Connection issue
> Message-ID:
> 	<CAOMUzJjp06Dx=i8ty4T38cS_kGDiwECMM1GECmL1uqTPyG6xRw@REDACTED>
> Content-Type: text/plain; charset="utf-8"
> 
> Hi All,
> 
> I tried to establish two diameter connection to same diameter peer and port
> (used two different source port).
> One connection was established successfully and other connection was
> failed.
> The failed connection sent below tcp packets to diameter peer, but did not
> sent CER to diameter node.
> 
> 1. sent [SYN] to diameter node
> 2. received [SYN, ACK] from diameter node
> 3. sent [ACK] to diameter node
> 4. sent [FIN, ACK] to diameter node
> 5. received [FIN, ACK] from diameter node
> 
> If I down established connection, then failed one is successfully
> established.
> 
> I used below application services,
> 
> {application,
> [{alias, smsc_diameter_cli_dia_1},
> {dictionary, rfc4006_cc_Gy},
> {module, smsc_diameter_clii_cb},
> {answer_errors, callback},
> {sequence, {0,19}},
> {share_peers, true},
> {use_shared_peers, true},
> {restrict_connections, false}]}
> 
> 
> I used diameter-1.3 erlang library.
> 
> 
> Please help me to solve this issue.
> 
> 
> Thanks & BRs,
> Dinusha