I i3ioi-iazard Member Mar 14, 2018 52 0 6 37 Aug 7, 2019 #1 I used the page function successfully with all users in my office however once I hung up, the call on their phone stayed active until they hung up themselves. How can I make it so it hangs up after the paging person hangs up?
I used the page function successfully with all users in my office however once I hung up, the call on their phone stayed active until they hung up themselves. How can I make it so it hangs up after the paging person hangs up?
A ad5ou Active Member Jun 12, 2018 893 205 43 Aug 8, 2019 #2 That sounds like a NAT issue. Normal operation the page “conference” should end when the initiator hangs up. You can try adding terminate-on-silence with a short value to the “page” conference profile.
That sounds like a NAT issue. Normal operation the page “conference” should end when the initiator hangs up. You can try adding terminate-on-silence with a short value to the “page” conference profile.
R Robert Birch Member Mar 16, 2017 114 5 18 53 Oct 3, 2019 #3 I have this same issue. I tried adding to the page conference profile terminate-on-silence and set the value to 10. Call still doesn't hang up. Here is what my page profile looks like: Any ideas would be greatly appreciated. Thanks
I have this same issue. I tried adding to the page conference profile terminate-on-silence and set the value to 10. Call still doesn't hang up. Here is what my page profile looks like: Any ideas would be greatly appreciated. Thanks
R Robert Birch Member Mar 16, 2017 114 5 18 53 Oct 3, 2019 #4 Actually, I did another test, and it looks like conference does end, but the phone (Grandstream GXP2135) does not let go of the call. Is there maybe a setting on the phone I need? Thanks
Actually, I did another test, and it looks like conference does end, but the phone (Grandstream GXP2135) does not let go of the call. Is there maybe a setting on the phone I need? Thanks
A ad5ou Active Member Jun 12, 2018 893 205 43 Oct 4, 2019 #5 That still sounds like a NAT issue. We have lots of Grandstream phones that work just fine with paging. A packet capture from a problematic phone and/or from server should show what is happening
That still sounds like a NAT issue. We have lots of Grandstream phones that work just fine with paging. A packet capture from a problematic phone and/or from server should show what is happening
R Robert Birch Member Mar 16, 2017 114 5 18 53 Oct 4, 2019 #6 Weird. The Fusion server I was testing on was 4.4.6. I tried it on a Fusion 4.5.8 afterwards and it worked fine. Guessing something must of changed in the versions. Looks like I will be needing to upgrade my server. Thanks
Weird. The Fusion server I was testing on was 4.4.6. I tried it on a Fusion 4.5.8 afterwards and it worked fine. Guessing something must of changed in the versions. Looks like I will be needing to upgrade my server. Thanks