top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Diameter: How the client and sever session's state machine differs ?

+2 votes
301 views

In a Diameter session, what all states client has and the server ?
And how does the state transition work between client and server by exchanging different types of messages ?

posted Mar 29, 2016 by Vikram Singh

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+1 vote
How can send diameter commands in two sessions?

I am designing a seagull scenario look like:

Client --------------- Server
--- CER -->
<-- CEA --- --- AAR --> // the first session
<-- AAA --- --- AAR -->
<-- AAA -- <-- RAR -- --- RAA -->
--- STR -->
<-- STA -- --- AAR --> // the second session
<-- AAA -- <-- RAR -- --- RAA -->
--- STR -->
<-- STA --

But in the second call, we saw an message in log "Expected AAR when receiving RAA.." . If we make the second call scenario same as the first call, (two AAR\AAA and one RAR/RAA) it was passed.

So that the question is "Is there any ways to control seagull flow as the scenario that we expected? "

+5 votes
State the difference between Diameter Credit Control Applications and Ro applications

State the difference between Diameter Credit Control Applications and Ro applications with reference to Diameter protocol?

...