When you park a call, res_features dynamically creates an extension in park-dial that looks like this (well - it would look like that if it were in extensions*.conf...)
exten => <channel>,1,Dial(<channel>||t)
so for example,
park-dial,SIP/232,1,Dial(SIP/232
t)
When the call rings until timeout, it is routed as what FreePBX calls an orphaned call (the 't' extension in park-dial) BUT, if the person pushes ignore, or if the channel isn't available, the call has no-where to go. Priority 2 doesn't exist.
So - this can be fixed one of two ways.
1. fix res_features to generate a #2 priority. Maybe it could be defined in features.conf?
OR (more relevant for FreePBX)
2. work around it in FreePBX.
My manual workaround was to add this to extensions_custom.conf
[park-dial-custom]
exten => _.,2,Goto(t,1)
you see that it is priority 2 for all possible extensions. When the auto-generated extension <channel> priority 1 fails, it looks for priority 2. In this case I have simply redirected the call to go to 't'. This takes the call along the path defined in FreePBX's Parking Lot module configuration. Either it, or possible another set of options applied to _. could be added to the code for FreePBX 2.5?
I'm happy to chat with any developers on this issue - we had to dig around pretty good to discover that Asterisk was generating park-dial extensions on the fly...
Andy Lauppe
Anteil, Inc.
+1 717 671 1141 x23
alauppe@anteil.com
Change History
Download in other formats:
|