I set up a 4 digit extension for parking calls. 5400
All works fine from Asterisk.
If I park a call from a legacy PBX, it parks OK and can be picked up, but if
unanswered, the call parkingtime timer tries to send
the call back to the PRI Zaptel trunk that it was parked with.
That circuit is no longer in use.
I can add a t extension for context 'park-dial' (which I assume is
hardcoded into that module because it is not in any conf file) to
send the call back to the front desk. (They will do the most parking, but
regular users will as well)
Questions:
1. Is there logic to use the callerid from the trunk parking the call for the
time out call back?
2. If I were to add a t extension in context 'park-dial', would it be a
normal Dial command, or something special to the features
module?
ref:
Jan 24 11:43:21 VERBOSE[18572]: -- Added extension 'Zap/71' priority 1
to park-dial
Jan 24 11:43:21 VERBOSE[18572]: == Timeout for Zap/71-1 parked on 5401.
Returning to park-dial,Zap/71,1
Jan 24 11:43:21 WARNING[18572]: Zap/71-1 already has a call record??
Jan 24 11:43:21 WARNING[18572]: CDR on channel 'Zap/71-1' already
started
Jan 24 11:43:21 VERBOSE[18572]: -- Executing Dial("Zap/71-1",
"Zap/71||t") in new stack
Jan 24 11:43:21 DEBUG[18572]: SIMPLE DIAL (NO URL)
Jan 24 11:43:21 NOTICE[18572]: Unable to create channel of type 'Zap'
Jan 24 11:43:21 VERBOSE[18572]: == Everyone is busy/congested at this time
Jan 24 11:43:21 DEBUG[18572]: Exiting with DIALSTATUS=CHANUNAVAIL.
Jan 24 11:43:32 WARNING[18572]: Timeout, but no rule 't' in context
'park-dial'
--
--
Steven
May you have the peace and freedom that come from abandoning all hope of having
a better past.
--- - --- - - - - - - - -- - - - --- - ------ - -
--- - - -- - - - -- - - -
