|
From: Ajay G. <aja...@gm...> - 2014-07-04 12:38:43
|
Thanks Mark.... Your reply helped.. we enquired the server guys.. and they registered our node. Thereafter, things worked fine. Thanks and Regards, Ajay On Mon, Jun 30, 2014 at 8:02 PM, Mark Erickson <mer...@ya...> wrote: > You do not have to 'ack the ACK' other than what TCP will do to indicate > successful transmission/reception of the CEA. Did you look to see why your > server is aborting the session? Perhaps you're not responding to DWRs? > > ------------------------------ > *From:* Ajay Garg <aja...@gm...> > *To:* dia...@li... > *Sent:* Monday, June 30, 2014 10:21 AM > *Subject:* Re: [Diameter-developers] (Conceptual) doubt in sending > Diameter messages > > After receiving CEA, do we need to send "something" that indicates that > CEA has been processed (before sending the CCR)? > > > > > On Mon, Jun 30, 2014 at 7:20 PM, Ajay Garg <aja...@gm...> wrote: > > Any ideas, please? > > > Thanks and Regards, > Ajay > > > On Sun, Jun 29, 2014 at 5:32 PM, Ajay Garg <aja...@gm...> wrote: > > Hi all. > > We are trying to write a diameter-client, that communicates with an > external diameter-server for event-based CCR. > > > > We are doing the following :: > > SCENARIO 1 > ========== > > 1. > Client connects through a vanilla AF_INET + SOCK_STREAM TCP-socket to the > server. > > 2. > Client sends CER (successfully). > > 3. > Client receives CEA (successfully). > > 4. > Client sends CCR. > > However, at step 4, we get a "Connection reset by Peer" from the server, > even though CEA showed successful validation. > > > > SCENARIO 2 > ========== > > a) > Client connects through a vanilla AF_INET + SOCK_STREAM TCP-socket to the > server. > > b) > Client sends CER (successfully). > > c) > Client receives CEA (successfully). > > d) > Client closes the socket of step a), and instantiates a new socket. > > e) > Client sends CCR through new socket (successfully). > > f) > Client receives CCA (successfully at protocol level), but the charging is > not done, because the server did not find a prior CER (on the same socket > presumably). > > > Note that at all times, the CER and CCR contents are exactly the same. > > > So, what could be the reason of connection-reset in scenario 1? Are we > doing some mistake at the client-side at a control-flow level? Do we need > to send something "in between" CER and CCR? > > > We will be thankful for any pointers. > > > > Thanks and Regards, > Ajay > > > > > -- > Regards, > Ajay > > > > > -- > Regards, > Ajay > > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > > _______________________________________________ > Diameter-developers mailing list > Dia...@li... > https://lists.sourceforge.net/lists/listinfo/diameter-developers > > > -- Regards, Ajay |