This is our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Hello,

I read somewhere that a Diameter Signalling Controller or a Diameter Routing Agent can be configured to prioritize VoLTE related signaling, over all the various Diameter interfaces. When serving this function, operators can provide a higher quality VoLTE service over other services, particularly when other services load the network.

Is there a way to detect such priority indicators from Wireshark traces?

Which field should I be looking at and any recommended display filters I could use to see if my Operator has activated such a functionality?

Many thanks

asked 26 Nov '14, 15:42

fnm500's gravatar image

fnm500
16114
accept rate: 0%


In general no, unless part of that prioritization is to mark IP header QoS (in the ToS/DSCP field).

Typically if an agent supports prioritization it will apply that priority locally on messages it receives, rather than mark priority for packets on the wire. Signalling load issues are going to present themselves in TPS bottlenecks long before bandwidth or network congestion becomes a factor.

In concept messages could be prioritized based on any criteria visible to the agent but some would be command code (type of message) the Application ID (in VoLTE context, the type of interface roughly) and the type of message of that code (eg:prioritize updates of existing sessions over initial messages for a new session). Locally-processed Diameter messages like watchdogs should also (in my opinion) be prioritized.

One other comment - depending on the topology you can (and in my opinion, should) isolate your diameter signalling types rather than looking at application prioritization in a common aggregation agent. Keeping VoLTE-related signalling in its own Diameter realm with its own agents is a good way to limit what other Diameter applications can do to your voice service on this front, and there's no technical requirement to have something like credit control in a common realm with EPC/IMS Diameter applications.

I'm also curious about the recent amount of VoLTE questions on some of these boards - were you by chance at the North America LTE convention last week?

permanent link

answered 26 Nov '14, 22:37

Quadratic's gravatar image

Quadratic
1.9k6928
accept rate: 13%

edited 26 Nov '14, 22:54

Thank you so much Quadratic! Really appreciate your detailed reply and recommendations.

I agree with your thinking. There should be a separate realm for VoLTE related signalling.

I think the increase in VoLTE questions might have something to do with Verizon and others recently launching their VoLTE service and network engineers trying to understand if everything is working OK.

Thanks for the tip, I will look at some of the other questions people have been asking. Any particularly good threads you have come across? I wasn't at the LTE convention last week..

Thanks again.

(01 Dec '14, 07:10) fnm500

Oh, aside from just Verizon I would say that 2015 is going to be the year of commercial VoLTE deployments. I just asked about the convention because I thought it was odd I saw similar questions within such a short time period right afterwards.

At this point, I don't think there have been enough large-scale Diameter signaling deployments in a VoLTE context to have a really solid view of what will become best-practices for it, though my main concern standards-wise right now is that HSS frontends will become bottlenecks once those Sh interfaces start moving at full steam combined with added roaming-related mobility exchanges in EPS. Similar to the move toward SIP, with Sh we're trading efficient ASN.1 encoding for flat XML files while taking a database frontend with traditionally light S6a load and exploding it. This is a concern to me for us all.

Having said that, I'm grateful that this technology shift is moving us closer than ever to the IT industry, and toward converged networking in telecom. Telecom vendors moving away from proprietary hardware and embracing not only virtualization/x86 but cloud and even SDN is a huge step forward in my view, as it is really starting to feel like mobile is catching up. I came originally from the IP world, where many of the things that mobile looks at as a bright but distant future in these areas are already a reality, so from my view we're coming back home. :)

(01 Dec '14, 15:47) Quadratic
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×58
×16
×4
×2

question asked: 26 Nov '14, 15:42

question was seen: 1,782 times

last updated: 01 Dec '14, 15:47

p​o​w​e​r​e​d by O​S​Q​A