top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

DIAMETER: Why a translation agent is always a Stateful peer?

+8 votes
250 views

Suppose in S6a interface which is a stateless interface an Engine (translation agent) has been placed in between MME and HSS for routing purpose and to translate the Diameter message in to Radius.

As the client-servers are not maintaining the state so after receiving the answer they will delete the session. But what about the agent who is maintaining the state there? hOW he would be informed that it can delete the session?

posted Apr 7, 2014 by Hiteshwar Thakur

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

Similar Questions
0 votes

In one Diameter blog, I saw a statement in which mentioned, if a Diameter node receive CER from unknown peer it responds back to that peer with Result-Code AVP set to "DIAMETER_UNKNOWN_PEER".
Now my query, Does a Diameter node keep its potential peers information in advance ?

+2 votes

Please find the description of the problem:
A diameter client and server communicates in the network through Proxy Agent.
Here, I have assumed PCEF is a diameter client and PCRF is a diameter server. Interface between the PCEF and the PCRF is known as Gx.

Does Proxy agent, which sits between PCEF and PCRF, need to support Gx application ?
Does Proxy agent validate presence of any mandatory or optional AVP when it receives a message from a diamter client (PCEF) before forwarding it to diameter server (PCRF) ?

Can someone please provides the detailed behavior of a proxy agent ?

+1 vote

I went through an article of diameter, it mentions " Diameter standard advises that a diameter node to maintain two connection primary and secondary connection". Diameter node uses first connection in normal conditions and go for second one if primary connection is abrupted or not available. How far it is correct and where it is used exactly ?

...