![]() ![]() If you want Asterisk to manage the dialplan extensions associated with the parking lot you need to consider these additional options: context , parkext , parkext_exclusive , and parkinghints . A parking lot basically needs a name, a range of parking spaces, and what to do with any calls that have been in the parking lot too long. ![]() I’ll describe creating dynamic parking lots after describing static parking lots. Looking at the piecesĭefining a parking lot can be done either statically in the res_nf configuration file or dynamically using an existing parking lot as a template to create a new lot. The cited references are for Asterisk 13 but most of the information will apply to Asterisk 11 with some alterations. The parking functionality was extracted from the Asterisk core to the res_parking.so loadable module. In Asterisk 12 it got another overhaul because of the major architectural changes in Asterisk. Parking has had a few incarnations to add features throughout its history in Asterisk. In fact many of the call parking options use car parking terminology such as parking lots and parking spaces to describe what the options do. The natural metaphor to describe how the feature operates is a car parking lot. Call parking is a means of placing a call on hold so anyone can retrieve the call if they know where the call is parked. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |