top button
Flag Notify
Site Registration

ULR with AVP 1493 = NOT_SUPPORTED(0)

0 votes

When a ULR includes AVP 1493 Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions = NOT-SUPPORTED(0), does it mean that it is a regular LTE registration or it can end with VoLTE registration?

posted May 8, 2018 by Kohava Bentov

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

1 Answer

0 votes

It would be unnecessary to include Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP in ULR for each UE.
Attach request message from UE contains "Voice domain preference and UE's usage setting" IE, based on value of this IE and prepared TAI list, MME gives indication to HSS. It does not make sense to consider this AVP for an UE which is registered with netowrk along with CS voice preference.

answer May 10, 2018 by Vimal Kumar Mishra
Similar Questions
+2 votes

Can someone please explain, what is the significance of "0" and non"0" value of Origin-State-Id AVP in a diameter message ?

+3 votes

Referring to the 3GPP 29.272 the "Homogeneous Support of IMS Voice Over PS Sessions " AVP is set to TRUE in the ULR means that the serving MME can provide the IMS voice support homogeneously in all TA assigned to it.
Does the MME insert this AVP in the ULR message only if the UE required voice service over IMS during the attach procedure.
In other word, if this AVP is present in the ULR, can we conclude that the UE support Voice call over IMS (VOLTE).

In the same context, if this AVP is absent ("Homogeneous Support of IMS Voice Over PS Sessions ")m can we conclude that either the MME does not support VOLTE at all or the UE does not support it (but only CSFB?

+2 votes

I want to understand which are the major EPC nodes involve with VoLTE Charging.

Staring from UE till IMS network.
Basically I want to know end-to-end Flow for VoLTE Charging which involves various Diameter Interface.
Does Gy interface has any role to play,if Yes,why? If No, Why?
It will be very helpful with some arrow diagrams involving the diameter interfaces without any message details.

+2 votes


I am going through the spec 3gpp 29.219(Sy interface) and trying to understand the call flow and AVPS between the OCS and PCRF.

The PCRF sends the the list of Policy counters to OCS initially and OCS will store it against the Sy session. How does the Counter identifiers be identified uniquely b.w OCS and PCRF ?

Because the spec says, If the OCS determines that any policy counter identifiers are invalid, the OCS shall return a response with the Result-Code AVP set to DIAMETER_INVALID_AVP_VALUE.

But my doubt is, how the Policy counter Ids are known across the OCS and PCRF.

Any help in this area is very helpful