johnr
July 13, 2025, 4:54pm
1
I’ve got OpenPage up and running with a few Paging extensions configured, such as 701 and 702. These are set to live mode and work as expected. However, I accidentally discovered that if I dial a number that isn’t a valid extension and isn’t matched by any outbound rule, the call seems to go directly to the OpenPage valet menu.
It looks like OpenPage is answering these unknown or invalid numbers with the valet mode menu.
Any idea why OpenPage might be acting as a catch-all in this scenario?
1 Like
lgaetz
July 13, 2025, 5:44pm
2
Already reported, you can watch the progress here
opened 01:30PM - 19 Jun 25 UTC
| openpage | 17.0.9 |
Doing some testing for unrelated things, and… was surprised to find that a misdial for a feature code executed open page dialplan instead of failing. You can repro this by installing openpage, and dial two digits that are not already a valid local extension.
The problem is that `ext-valet-page` and `ext-valet-hangup` are both included in `from-internal-additional`, and both have an exten of `_X.` so will match any local dial string, not just when paging is desired. I have not gone thru the dialplan exhaustively, but this looks like a simple matter of just removing the include for these contexts in `from-internal-additional`.
```
root@tangopbx5:/var/www/html/admin/modules/advcallspy# asterisk -x "dialplan show from-internal-additional" | grep ext-valet
Include => 'ext-valet-page' [pbx_config]
Include => 'ext-valet-hangup' [pbx_config]
root@tangopbx5:/var/www/html/admin/modules/advcallspy# asterisk -x "dialplan show ext-valet-page"
[ Context 'ext-valet-page' created by 'pbx_config' ]
'_X.' => 1. Noop(Starting valet page for group ${EXTEN}) [extensions_additional.conf:4540]
2. Set(PAGEGROUP=${EXTEN}) [extensions_additional.conf:4541]
root@tangopbx5:/var/www/html/admin/modules/advcallspy# asterisk -x "dialplan show ext-valet-hangup"
[ Context 'ext-valet-hangup' created by 'pbx_config' ]
'_X.' => 1. Set(ANNOUNCEMENT=${RECORDED_FILE}) [extensions_additional.conf:4556]
2. Noop(Event ID: ${EVENTID}) [extensions_additional.conf:4557]
root@tangopbx5:/var/www/html/admin/modules/advcallspy# asterisk -x "dialplan show 44@from-internal"
[ Included context 'ext-valet-page' created by 'pbx_config' ]
'_X.' => 1. Noop(Starting valet page for group ${EXTEN}) [extensions_additional.conf:4581]
2. Set(PAGEGROUP=${EXTEN}) [extensions_additional.conf:4582]
```
2 Likes
johnr
July 15, 2025, 12:44pm
3
So just to clarify, there is no fix for this at the moment?
1 Like
Hello, I have been encountering the same issue on my system as well. Is a fix coming soon? The activity on this issue appears to be stale for a month, thanks.
lgaetz
August 13, 2025, 1:31pm
5
@theJames did a commit for this yesterday for those who want to test. A published update shouldn’t take much longer.
main ← 14-openpage-contexts-included-inappropriately-in-from-internal-additional
opened 11:59PM - 12 Aug 25 UTC
* Removed redundant `$ext->addInclude('from-internal-additional', $context);` li… nes from `doDialplanHook` method.
1 Like
Thank you, will be checking it out soon.
johnr
January 15, 2026, 8:45am
7
Thank you. With the latest version seems to have fixed this issue.
1 Like