Session hangs up when on mute

Status
Not open for further replies.

BioTech

Free User
Joined
Jul 10, 2020
Messages
15
Reaction score
1
New to 3cx, Need a little help. When a phone mutes it audio it will hang up after a few minutes. Is their a setting for this?
 
As above,

How you are muting the call ? - i.e. which buttons are you pressing.
 
When ever audio is muted via headset or no audio at all. Tried with different providers, Latest version on Debian in a VM. With Grandstream 2170's
 
If you answer nothing what we ask for helping you we can't guess, no crystal ball here ;)
 
  • 3CX Version, e.g. Standard Annual 16.0.5.619,16.0.5.619
  • Server OS, e.g. Debian 9 on KVM
  • Is the 3CX Server Hosted and where? Local
  • IP Phone Make/Model/Firmware Grandstream gxp2170 firm 1.0.11.6
  • Provisioning Method: Local
  • Trunk Provider or Gateway Make/Model gxp4104 and sip trunks
  • Has the Firewall Checker passed: YES
  • Are custom Phone Templates being used: NO
 
  • Like
Reactions: AWS2P
The 3CX Activity Log will confirm which device (gateway or set) is ending the call.
The disconnect method, on the 4104, may be set to silence detect, and may have to be adjusted, or changed to another method such as CPC, if provided
 
The 3CX Activity Log will confirm which device (gateway or set) is ending the call.
The disconnect method, on the 4104, may be set to silence detect, and may have to be adjusted, or changed to another method such as CPC, if provided


is their an option like that for regular sip trunks? We did not have this on FreePBX, same setup
 
No, that would be a PSTN gateway option as one method to detect when the far end has gone on-hook. A SIP trunk will send a SIP message to drop the call. Again, check the Activity Log to see which end disconnected.
 
Not seeing anything in my logs, also removed the silent option on my GW. Still happening. Don't think its a silent thing. Happens on regular calls now sswell.
 
Not seeing anything in my logs,
Well...the Activity log will show the entire call, and at the end (or when it drops), it will show which end that came from, the set, or the trunk.
 
Last edited:
What logs should I be looking at? This is driving me nuts.
 
in dashboard
1594828643471.png
set it in verbose

do a call test and search who send a "BYE"
 
These are both from about eight years ago, and were dealing with older versions of 3CX. So while the 3CX menus look different, the log itself, has not really changed at all.

https://www.3cx.com/blog/docs/3cx-server-activity-log/
https://www.3cx.com/blog/docs/server-activity-log-example-1/

You want to look at a log right after the issue has occurred. Use the filter to look at the call for the one extension number. Follow the call until just before it ends, this is going to be the important part.. Which end dropped the call (sent the BYE, first).
 
07/15/2020 12:11:25 PM - Removing leg L:5.1[Extn:200]
07/15/2020 12:11:25 PM - L:5.1[Extn:200]: Terminating targets, reason: SIP ;cause=200 ;text="User hangup"
07/15/2020 12:11:25 PM - Leg L:5.1[Extn:200] is terminated: Cause: BYE from local
07/15/2020 12:11:25 PM - Call(C:5), Extn:200 on entry: DlgInfo(5-4984/Terminated / I)



This mean the local phone device hung up?
 
7/15/2020 1:01:44 PM - L:8.3[Extn:200] got Terminated Send Req BYE from 0.0.0.0:0 tid=36ab1701c07bea20 Call-ID=jfNa2kdd0XSt-H9LXOoAjg..: BYE sip:[email protected]:5060 SIP/2.0
 
yes, your log means ext 200 send a Bye to hangup
 
this driving me nuts, anyway to tell why?
 
Status
Not open for further replies.

Forum statistics

Threads
111,955
Messages
589,925
Members
164,853
Latest member
as7h