top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Can diameter be executed on non-standard port i.e. other then 3868?

+2 votes
353 views

Can diameter be executed on non-standard port i.e. 3868. If yes then how the DPI at various places in the network takes place. Do we have a special DSCP marking of the packet for the same or any other mechanism.

posted Aug 14, 2013 by Nora Jones

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

1 Answer

+1 vote

IANA defined "well-known port" for Diameter is 3868; recent RFC 6733 defines 5658 for TLS/DTLS secured Diameter connections, leaving 3868 for plain TCP/SCTP based connections.

Implementations do typically allow you to use a different listening port; when a node uses a different port, its peers should be appropriately configured.

I don't know much about DPI. But since DPI would have the ability to recognize patterns within the PDUs as well as in protocol exchanges, shouldn't be too difficult. Anyway it would need the command and AVP definitions to interpret the traffic even when server is listening on 3868. Here, it has to go a step beyond - 'guessing' that protocol is Diameter, validating the guess and then applying its knowledge of the PDU structure.

answer Aug 14, 2013 by anonymous
Similar Questions
+2 votes

Is there any scenario during the Voice call or in any other call that 'Granted Service Unit' (GSU) can be more than 'Requested Service Unit' (RSU) ?

+3 votes

I want some reference how to determine the max and min length for Standard Diameter AVPs and 3GPP Diameter AVPs based on Seagull dictionary which is open source. How I can determine max and min length for different data types let say UTF8 String, Octet String, Unsigned32,String,Address etc. Any reference highly appreciated.

+1 vote

Hi,

I want to know in which scenario or which diameter messages can set the Error bit ('E') bit in request/response messages.
Also, How 'E' bit is set with Transient failures, Permanent failures and Protocol Errors.

Thanks in advance.

...