top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Diameter vendors who has offices in Bangalore?

+4 votes
347 views

Want to know the list of diameter vendors who has offices in Bangalore?

posted Nov 26, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+2 votes

As far as I know following is the list of vendors -

  1. Aricent
  2. Radysis (Trillium)
  3. Intellinet
  4. LiteCore Networks
answer Nov 26, 2013 by Salil Agrawal
LiteCore Networks: www.lcnpl.com, office located in J.P.Nagar, Bangalore.
commented Nov 27, 2013 by Rathnakumar Kayyar
Similar Questions
+1 vote
Who performs the Session and Bearer binding in LTE network?

As far as I know, PCRF does the Session binding and PCEF responsible for Bearer binding.
Pls explain with examples of practical scenario.

+2 votes
Who should send FIN during the CER/CEA exchange?

Recently I have faced situation described below. Please ignore the dots - there is no table so I could present this in a proper table form.

The question is, when the GGSN/PCEF is establishing the session on TCP level to exchange Capabilities with Diameter Peer, who should be sending the FIN? Or maybe the FIN should not be sent at all?

In the below example, is what I saw in .pcap trace. Strange for me is there is not FIN present just FIN-Ack in this situation.

This was a issue, as I was given different IP for PCRF but I was told "everything else is the same" but it wasnt - the peer name was different.

Packet No......Direction.......Packet/message
1..............Out.............Syn
2..............In..............Syn-Ack
3..............Out.............Ack
4..............Out.............CER (diameter)
5..............In..............Ack of CER (tcp)
6..............In..............CEA (diameter)
7..............Out.............Ack of CEA (tcp)
8..............Out.............***FIN-Ack***
9..............In..............Ack
+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? "

0 votes
Diameter: Getting a good amount of "DIAMETER_INVALID_AVP_VALUE" errors in our network?

we are getting a good amount of "DIAMETER_INVALID_AVP_VALUE" errors in our network, can anyone please share what will be the possible causes of the same.

...