Paging group 'stuck' open when original extension hung up

General Help
1

Trying to do a paging group via the CLI using the below method

rasterisk -x 'channel originate local/101@from-internal extension *8024@from-internal'

where 101 is the paging group and 24 is a local extension.

What I’m finding is that the paging group isn’t closing naturally when extension 24 ends the call. Sometimes the other extensions still show as being part of an ongoing paging call and sometimes they don’t. Both whether the other extensions show as being on the call or not, the paging group doesn’t close of its own accord unfortunately.

Any help much appreciated on how to workaround or fix this.

Thanks

These are the open channels

CBAnn/1643737293338-00003c01;1
CBAnn/1643737293338-00003c01;2
CBAnn/1643737294804-00003c04;1
CBAnn/1643737294804-00003c04;2
Local/101@from-internal-00003bfd;1
Local/101@from-internal-00003bfd;2
Local/PAGE20@app-paging-00003bff;1
Local/PAGE20@app-paging-00003bff;2
Local/PAGE22@app-paging-00003c00;1
Local/PAGE22@app-paging-00003c00;2
Message/ast_msg_queue
PJSIP/20-0000312f
PJSIP/22-00003130

2

Seems very similar to this issue and this one too I guess

3

@lgaetz sorry to ping you directly - should I log this as a bug?
Basically the page group doesn’t close automatically (even after a 30s delay!) when the target/initiating extension rings off.

4

do you get the same result if you reverse the order of the channel setup?

channel originate local/*8024@from-internal extension 101@from-internal
5

Had a similar problem. I corrected it by add a white noise (silence) about 15 second long. Now any page announcement is over 15 second long

6

Yep, same result

not sure how that would help as this isn’t an announcement - or am I missing something?

7

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.