On this tab, you can access groups of attributes to define how to perform message exchange between endpoints.
Similar to the Voice calls service, service policies for messaging can be either statically assigned to vendor connections or dynamically matched based on the recipient’s domain name or CLD.
The attributes defined in the dynamic service policy (e.g., transport protocol, routing, and billing parameters) are used for message processing and delivery (both SMS and instant messages). The static service policies contain attributes specific to a particular SMS vendor.
Open a specific group to configure the corresponding attributes.
Diameter Ro interface
In this section, you can adjust the communication between PortaBilling and IMS for VoLTE service provisioning.
Ignore user name
Instructs PortaBilling to ignore the User-Name attribute in incoming Diameter requests and use Subscription-Id to identify the subscriber instead.
By default, PortaBilling uses User-Name for subscriber identification if it is present. Enable this option when the mobile core sends the actual subscriber ID (IMSI or MSISDN) in Subscription-Id, while using User-Name for other purposes.
This option is applied when the request matches the configured Attribute pattern (for example, a specific Origin-Host value).
Rise MSCC result code
Most gateways connect or terminate calls based on the result-code value that is set within the MSCC (Multiple-Services-Credit-Control) AVP. However, some gateways (for example, Huawei ATS 9900) require setting the result code for the Result-Code AVP.
This attribute allows you to customize the Diameter CCA (Credit-Control-Answer) sent by PortaBilling, so that it copies the Result-Code value from the MSCC AVP and sets it as the Result-Code AVP.
To enable this attribute, select Enabled from the list.
Processing messages over SIP/SMPP
In this section, you can specify the attributes to adjust message processing and delivery.
