The mobile core may send the subscriber ID (the SIM card’s IMSI or phone number) in either the User-Name or Subscription-Id field of Diameter requests. If User-Name is present, PortaBilling automatically uses it for subscriber identification. Only if it is missing does PortaBilling fall back to Subscription-Id. However, some mobile networks may utilize User-Name for other purposes while placing the subscriber ID in Subscription-Id. In such cases, PortaBilling receives User-Name, assumes it contains the subscriber ID, but cannot identify the subscriber based on it.
For mobile data services, you can configure PortaBilling to ignore User-Name and only use Subscription-Id for subscriber authentication – allowing integration with such networks without extra development.
For PortaBilling to ignore the User-Name field when it contains something other than the actual subscriber ID:
- Create a service policy for internet access and specify the Origin-Host value of the MNO’s network (e.g., the packet gateway) in the Attribute pattern field. You can specify it in the format Origin-Host=%.company.domain – this pattern matches any host within the same realm (e.g., pgw1.company.domain and pgw2.company.domain).
- Navigate to Attributes > Gy and turn on the Ignore User Name toggle.
You don’t need to assign this service policy to a product or account – PortaBilling automatically applies this service policy when it detects a match between the configured pattern and the Origin-Host value in the incoming Diameter request. When a service policy is applied, PortaBilling ignores the User-Name field and uses Subscription-Id to identify the subscriber.
Launch mobile data service faster without the need for extra support requests and custom code changes.
