<div dir="ltr">Dear Anders,<div><br></div><div>Yes I override default value and set passed restrict_connections = false.</div><div><br></div><div>To enable multiple connections.</div><div><br></div><div><br></div><div>Thanks & BRs,</div><div>Dinusha</div><div><br></div><div><br><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 19, 2017 at 6:42 PM, <span dir="ltr"><<a href="mailto:anders.gs.svensson@ericsson.com" target="_blank">anders.gs.svensson@ericsson.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">What are you passing to diameter:add_transport/2? I can see from the<br>
trace that it has restrict_connection = nodes, so it looks like you're<br>
overriding the service configuration.<br>
<div><div class="h5"><br>
Anders<br>
<br>
<br>
<br>
<br>
Dinusha Ganganath Perera writes:<br>
> Dear Anders,<br>
><br>
> Please find the trace.<br>
><br>
> Thanks & BRs,<br>
> Dinusha<br>
><br>
> On Thu, Oct 19, 2017 at 5:28 PM, <<a href="mailto:anders.gs.svensson@ericsson.com">anders.gs.svensson@ericsson.<wbr>com</a>> wrote:<br>
><br>
> Hi Dinusha.<br>
><br>
> Enable the following trace while your nodes are trying to connect and<br>
> it will narrow it down.<br>
><br>
> dbg:tracer().<br>
> dbg:p(all,[c,timestamp]).<br>
> dbg:tp(diameter_peer_fsm, start, x).<br>
> dbg:tp(diameter_peer_fsm, terminate, x).<br>
><br>
> Send me the resulting output in the Erlang logs. You can disable the<br>
> trace with dbg:stop_clear().<br>
><br>
> Anders<br>
><br>
><br>
><br>
> Dinusha Ganganath Perera writes:<br>
> > Dear Anders,<br>
> ><br>
> > My Application is client.<br>
> ><br>
> > I am trying to establish multiple connections with remote Diameter<br>
> Server.<br>
> ><br>
> ><br>
> ><br>
> > Thanks & BRs,<br>
> > Dinusha<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > On Thu, Oct 19, 2017 at 2:59 PM, <<a href="mailto:anders.gs.svensson@ericsson.com">anders.gs.svensson@ericsson.<wbr>com</a>> wrote:<br>
> ><br>
> > Hi Dinusha.<br>
> ><br>
> > Which of the two nodes in your test is running OTP/diameter: client,<br>
> > server, or both?<br>
> ><br>
> > Anders<br>
> ><br>
> ><br>
> ><br>
> > Dinusha Ganganath Perera writes:<br>
> > > Dear Anders,<br>
> > ><br>
> > > Thanks for your reply.<br>
> > ><br>
> > > I upgraded Erlang and current version of diameter library is 2.1.<br>
> > ><br>
> > > But issue is not resolved.<br>
> > ><br>
> > ><br>
> > > Thanks & BRs,<br>
> > > Dinusha<br>
> > ><br>
> > > On Tue, Oct 17, 2017 at 4:15 PM, <<a href="mailto:anders.gs.svensson@ericsson.com">anders.gs.svensson@ericsson.<wbr>com</a>><br>
> wrote:<br>
> > ><br>
> > > diameter 1.3 is from OTP R15B03, released in November 2012,<br>
> which is<br>
> > > the release that added the restrict_connections option, which<br>
> looks<br>
> > to<br>
> > > be what you're having problems with. I don't recall any issues<br>
> (not<br>
> > > that I recall much of anything from 2012), and don't see<br>
> anything in<br>
> > > the release notes, but I suggest trying with a more recent<br>
> release<br>
> > for<br>
> > > starters.<br>
> > ><br>
> > > The latest is diameter 2.1.1 in OTP 20.1.2. (Although there's a<br>
> fix<br>
> > to<br>
> > > a problem introduced in 20.1 coming in 20.1.3, unrelated to<br>
> > > restrict_connections.)<br>
> > ><br>
> > > Anders<br>
> > ><br>
> > ><br>
> > > <a href="mailto:erlang-questions-request@erlang.org">erlang-questions-request@<wbr>erlang.org</a> writes:<br>
> > > > Date: Mon, 16 Oct 2017 21:24:34 +0545<br>
> > > > From: Dinusha Ganganath Perera <<a href="mailto:dinushaganganath@gmail.com">dinushaganganath@gmail.com</a>><br>
> > > > To: <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> > > > Subject: [erlang-questions] Multiple Diameter Connection<br>
> issue<br>
> > > > Message-ID:<br>
> > > > <CAOMUzJjp06Dx=i8ty4T38cS_<wbr>kGDiwECMM1GECmL1uqTPyG6xRw@<br>
> > <a href="http://mail.gmail.com" rel="noreferrer" target="_blank">mail.gmail.com</a><br>
> > > ><br>
> > > > Content-Type: text/plain; charset="utf-8"<br>
> > > ><br>
> > > > Hi All,<br>
> > > ><br>
> > > > I tried to establish two diameter connection to same diameter<br>
> peer<br>
> > and<br>
> > > port<br>
> > > > (used two different source port).<br>
> > > > One connection was established successfully and other<br>
> connection<br>
> > was<br>
> > > > failed.<br>
> > > > The failed connection sent below tcp packets to diameter<br>
> peer, but<br>
> > did<br>
> > > not<br>
> > > > sent CER to diameter node.<br>
> > > ><br>
> > > > 1. sent [SYN] to diameter node<br>
> > > > 2. received [SYN, ACK] from diameter node<br>
> > > > 3. sent [ACK] to diameter node<br>
> > > > 4. sent [FIN, ACK] to diameter node<br>
> > > > 5. received [FIN, ACK] from diameter node<br>
> > > ><br>
> > > > If I down established connection, then failed one is<br>
> successfully<br>
> > > > established.<br>
> > > ><br>
> > > > I used below application services,<br>
> > > ><br>
> > > > {application,<br>
> > > > [{alias, smsc_diameter_cli_dia_1},<br>
> > > > {dictionary, rfc4006_cc_Gy},<br>
> > > > {module, smsc_diameter_clii_cb},<br>
> > > > {answer_errors, callback},<br>
> > > > {sequence, {0,19}},<br>
> > > > {share_peers, true},<br>
> > > > {use_shared_peers, true},<br>
> > > > {restrict_connections, false}]}<br>
> > > ><br>
> > > ><br>
> > > > I used diameter-1.3 erlang library.<br>
> > > ><br>
> > > ><br>
> > > > Please help me to solve this issue.<br>
> > > ><br>
> > > ><br>
> > > > Thanks & BRs,<br>
> > > > Dinusha<br>
> > ><br>
> > ><br>
> ><br>
> ><br>
><br>
><br>
</div></div>> x[DELETED ATTACHMENT Charging2_2017-10-19_17-46-48.<wbr>log, Untyped binary data]<br>
</blockquote></div><br></div>