In this section:
Modified: for 5.0.1
Peer DNS Address Resolution
Currently, Diameter Peers are defined by their IP addresses. With the implementation of this feature, SBC is enhanced to support the Diameter Peers as Fully Qualified Domain Name (FQDN) in addition to the IP addresses. The actual address is resolved through Domain Name System (DNS) queries. For each Diameter peer FQDN IP address resolution, SBC generates a maximum sequence of DNS query types: NAPTR, SRV, and A/AAAA. Depending on the FQDN prefix configuration, each Trunk Group is assigned a Policy and Charging Rule Function (PCRF) realm (pcrfRealm) with matching Diameter realm route. Traffic generated on these Trunk Groups is directed to the peers in their corresponding realm route. Similarly, DNS address resolution is directed to the Trunk Group's DNS server group with the same realm assignment.
DNS Query
- IP address configuration is optional as per this feature.
- FQDN range has changed from 128 to 256, which is used for DNS query if IP address is not configured.
Multiple IP Connections per Peer
SBC is enhanced to support multiple IP connections per Diameter Peer. If a set of IP addresses are returned, SBC connects to all IP addresses under the same peer. A new parameter sessionDistribution is added to handle the session distribution order.
SBC Diameter capacity for this feature is as follows:
SBC Diameter capacity
| Parameter | Maximum Capacity |
|---|---|
| Diameter Node | 1 |
| Diameter Peers per Node | 10 |
| Diameter Realm Routes per Node | 10 |
| IP Connections per Peer | 10 |
| SRV Records Processed | 5 |
| Maximum Diameter Peer Connections (System Wide) | 32 |
- IP connections per peer connects to the first 10 A/AAAA queried IP addresses, rest are ignored.
- SRV records processed top 5 priority/weight records, rest are ignored.
Overview
Content Tools