Service policies allow you to fine-tune your services based on your network peculiarities, vendors’ abilities, and customers’ demands. In a service policy, you can configure a set of static options that can be applied to multiple accounts (so you don’t need to configure each option for each account separately). It also allows you to separate the configuration of technical options (usually made by technical staff) from account management.
Service policies can be:
-
statically assigned at various levels: product, account, connection and call authorization rule; or
-
dynamically matched against each call/message and applied if the specified pattern matches user agent type (for voice calls) or recipient’s domain name or CLD (for messaging services).
Policies are applied separately to both parties (calling and called) participating in the call.
The final set of attributes applied to calling/called party is derived from service policies assigned at different levels (and dynamically matched policies are also considered.)
Note that service policy attributes that have been statically assigned to an account receive the highest priority. If the policy is statically assigned to an account, it will always be applied (the match pattern is ignored for this account).
To create a new service policy, fill in the policy details, and click Save. To create more service policies, click Save & Add another.
Name
Specify a name for the service policy. The name should be unique for the particular service type.
Service type
Choose one of the service types from the drop-down list: Voice calls, Messaging service, or Internet access.
SIP end-point pattern
This field is available for Voice calls service policies and specifies a pattern for the user agent (UA) type. If this field is filled, PortaSIP uses its value to dynamically match against every new call from/to internal accounts. If the specified pattern matches the caller/callee UA type, the policy attributes apply to this call. This field can contain either a full UA name (e.g., Linksys/SPA941-5.1.8) or a list of patterns separated by a comma (e.g., Cisco%,Sipura%,Grandstream%).
Recipient domain pattern
This field is available for Messaging service policies and specifies the recipient’s domain name or CLD. If this field is filled, PortaSIP uses its value to dynamically match against every new message from/to internal accounts. If the specified pattern matches the recipient domain, the policy attributes (i.e., transport protocol, routing and billing parameters) are used for processing and delivery of messages (both SMS and instant messages). For example, if you want to allow your end users to send SMS messages to any mobile network, type %. If you only allow end users to send SMS to a specific mobile operator, specify the pattern as follows: %XXX% (e.g., %380% for all mobile operators in Ukraine or %38050% for Vodafone Ukraine). Thus, when a user sends an SMS to +38055551122, PortaSIP matches the number with the pattern (e.g., %380%) and applies the service policy attributes.
Managed by
This field is available for Internet access service policies. Choose whether the service policy is managed by an administrator or a particular reseller.
