Pbxact version 14.0.16.11. Version 12.7.8-2107-3.sng7 Asterisk version 17.9.3.
System and modules are up to date. Parked calls are set to ring back the caller that parked the call after 240 seconds, however the call is dropped instead of ringing back. The Alternate destination was set for a Ring group, I changed it to a Queue and it made no difference. The logs when the call is dropped is:
– Channel SIP/64.136.174.30-00002b46 left ‘holding_bridge’ parking-bridge <deb7f11d-5a60-4d6f-bda9-4556005fa1b9>
– Stopped music on hold on SIP/64.136.174.30-00002b46
== Extension Changed 701[park-hints] new state Idle for Notify User 102
== Extension Changed 701[park-hints] new state Idle for Notify User 105
== Extension Changed 701[park-hints] new state Idle for Notify User 104
== Extension Changed 701[park-hints] new state Idle for Notify User 110
== Extension Changed 701[park-hints] new state Idle for Notify User 103
== Extension Changed 701[park-hints] new state Idle for Notify User 108
== Extension Changed 701[park-hints] new state Idle for Notify User 115
== Extension Changed 701[park-hints] new state Idle for Notify User 106
== Extension Changed 701[park-hints] new state Idle for Notify User 114
== Extension Changed 701[park-hints] new state Idle for Notify User 101
– Executing [s@macro-parked-call:200] NoOp(“SIP/64.136.174.30-00002b46”, “Attempting to go back to sender”) in new stack
– Executing [s@macro-parked-call:201] Set(“SIP/64.136.174.30-00002b46”, “PARKCALLBACK=SIP/101”) in new stack
– Executing [s@macro-parked-call:202] Set(“SIP/64.136.174.30-00002b46”, “SHARED(PARKRETURNTO,SIP/64.136.174.30-00002b46)=”) in new stack
– Executing [s@macro-parked-call:203] Goto(“SIP/64.136.174.30-00002b46”, “park-return-routing,1”) in new stack
– Goto (park-return-routing,s,1)
== Extension Changed 9928*108[restapps-device-hints] new state Idle for Notify User 108
[2021-08-13 13:42:12] WARNING[3773][C-00001a19]: pbx.c:4510 __ast_pbx_run: Channel ‘SIP/64.136.174.30-00002b46’ sent to invalid extension but no invalid handler: context,exten,priority=park-return-routing,s,1
Not sure what you mean by user provided dialplan. This has all been setup inside the GUI. And it should be ringing back extension 101.
What I mean is everything was setup in PBxact gui. There is no custom asterisk programming.
Sangoma has provided the custom programming of Asterisk as part of their FreePBX software on which PBXact is based. In fact I think it is exactly FreePBX, with commercial support, so, if you have paid for commercial support that is your best channel for obtaining help, as you will be dealing with someone who is paid to find a solution for you, rather than people who are not obliged to respond.
Ok got it. I believe support is expired on this pbx.
Oops. This is the FreePBX forum. I thought I was looking at the Asterisk one.
Apologies for the confusion.
Do you have your return stuff all set up in your parking lot?
If the origin is not available (on a call or DND) or does no answer it will head off to the Destination listed.
In my example here it is a PBX with 4 branch offices and only 1 parking lot. If a call returns out of Park and fails t go to origin, then I dump it to an IVR saying something went wrong with our call. Press 1 for Office 1, Press to for Office 2, etc.
Looking at the logs, above, and the FreePBX source code:
it looks like there is a more fundamental problem than the parker not being available. It seems to think that the parking slot is called “s”, which is a special value in Asterisk, so can’t be a valid parking slot.
This is maybe due to PARKINGSLOT no longer existing starting from Asterisk 17.?.?, although I don’t understand how it gets set to “s” in the actual dialplan, in that case, unless maybe FreePBX does this when it adds the GoTo. (Actually it looks like the Asterisk GoTo is doing the substitution of “s” for “”.)
This was fixed in FreePBX 15. Because I submitted the pull request that fixed it. I didn’t make a PR for 14.
Pull request made for parking v13.x (module from PBXact 14).
https://git.freepbx.org/projects/FREEPBX/repos/parking/pull-requests/22
Ok, so what’s the solution? If I check for updates again, will that fix it?
Not until Sangoma pushes the change live and then also approves it for PBXact.
The pull request is linked to your bug report. So you should get notified once things are moved along.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.