Per-customer parking

Parking can be done within Enswitch rather than Asterisk, which allows each customer to have their own range of parking slot numbers. Some customers want this so they can have telephone keys park and pick up calls from their own parking slot numbers with one press.

When choosing parking slot numbers to use it is important to remember that all slot numbers system-wide must be contained within one consecutive range. For example, you can use slot numbers 1000 to 1999, but cannot use 700-799 and then 900-999 as these are not consecutive.

Shared parking slots can be created at the system level which are available to all customers. Customer-specific parking slots are assigned within each customer. If customer-specific parking slots overlap then the slot is shared between those customers, and is no longer unique to one customer only. Therefore if your system has 100 customers and each will have 10 customer-specific slots then you will need a range of 1000 slot numbers. When a call is parked the system will try to use a customer-specific parking slot number, and failing that will use a shared parking slot from the system level.

  1. Choose your system-wide range of parking slot numbers.
  2. Ensure your system is running the latest Enswitch fixes and Asterisk 1.8 or higher.
  3. On the Enswitch web interface, under System » Configuration, set "Enable per-customer parking" to 1.
  4. On the Enswitch web interface, under System » Configuration, set "Park start" to be the first number in your system-wide range of parking slot numbers, and "Park end" to be the last number in your system-wide range of parking slot numbers.
  5. Wait until 1 minute has passed since the step above to allow the configuration to be updated and the "Park call" destination to appear on the web.
  6. On the Enswitch web interface, make a new feature code *7 going to "Park call" at the system level. Make sure this feature code may be used by any customer on the system.
  7. On the Enswitch web interface, make feature codes with destination "Parking slot" at the system level, for shared parking slots. Make sure these feature codes may be used by any customer on the system.
  8. In /etc/asterisk/features.conf on each Asterisk server, add "parkeddynamic = yes" to [general], update parkpos to be the system-wide range of slot numbers, and change parkext to something that will never be entered by users such as "AAAA".
  9. Do:
    • asterisk -rx 'module reload'
  10. On the Enswitch web interface, switch to each customer in turn and create feature codes with destination "Parking slot" for their customer-specific slots.
  11. Test parking and picking up calls.