Zone Model-Based Pricing
Zone model-based pricing enables monetization using Standard or Geographical zone models. Important attributes for zone model configurations are:
- Calling party, also referred to as Call Originating Number or A-party number.
- Called party, also referred to as Call Terminating Number or B-party number.
- Distance, between Calling and Called party for Geographical zone model
Expected Result:
Pricing based on Calling party and the Called Party (e.g., Calls from US to EU countries, calls from EU to Rest of the world countries)
Variants:
- Pricing based on distance between Calling and Called party
- Pricing based on zone setup using wild-card expressions (example Called party zone setup as "44*" for calls to any number in UK)
- Pricing based on best match for the zone setup (example Called Party zone setup as "44123*" and "44*", where if the called party number starts with "44123", then the "44123*" zone should be used and not "44*"
Setup:
- Set up zone model configurations under Configurations → Models → Zone Model. Refer to the Zone Model configurations section under "3. Allegro Configurations → Models → Zone Model" for more documentation.
- Set up the plan, plan rate schedule, and plan services as required in core Aria.
- Set the price offer in Aria Allegro for usage services as follows:
- Select Pricing Model as Transaction Attribute-based or Composite, if combining with other models. This adds a section for Transaction Attributes in the UI.
- Leave the Time-model attributes as blank or select corresponding values as ANYDAY, ANYTIME, ANYHOLIDAY.
- Select Zone Model from the drop-down list of applicable zone model configurations for the service-type. If only one zone-model configuration is setup for the service-type, it is automatically selected.
- Select Zone from the Zone model configuration selected from the drop-down list. as required. Options include configured holiday names or ANYHOLIDAY to apply pricing to any holiday.
- Add currency (rates), accumulator, and allowance as needed.
- Use Add Transaction attribute to add more pricing combinations. Repeat steps 3 and 4 as needed. It is advisable to set up a zone with a default (fall-through) pricing where the called and calling party both are set as '*' (any). Pricing for this default zone should also be set up.
- The rest of the setup and process remains unchanged.