Solved Calls dropped on ring connect

[Den1s]

I am running the latest version of the 3CX software on a Windows 2008 Server. I am experiencing dropped calls immediately after the caller dials the number.

Number dialed->Connect->Immediately Dropped

The phone does not ring nor connect. This is an intermittent problem, and only seems to appear when using the GSM network. Landlines usually connect ok. This is a major problem as we will loose a great deal of calls if the caller gives up on the first attempt.

I get these errors in the activity log;

01/19/2017 5:29:29 PM - [CM101008]: The '' feature is disabled in currently activated licenseBLF
01/19/2017 5:29:26 PM - Discarded message, because of blocked User-Agent: BadUA Recv Req INVITE from 209.126.103.145:5084 tid=-c1d7b39c1412e222f8e8dbcfd512044e Call-ID=c1d7b39c1412e222f8e8dbcfd512044e: INVITE sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP 209.126.103.145:5084;branch=z9hG4bK-c1d7b39c1412e222f8e8dbcfd512044e;rport=5084 Max-Forwards: 70 Contact: <sip:[email protected]:5084> To: 000971592942836<sip:[email protected]:5060> From: 22<sip:[email protected]:5060>;tag=c8f60cec Call-ID: c1d7b39c1412e222f8e8dbcfd512044e CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, BYE Content-Type: application/sdp User-Agent: sipcli/v1.8 Content-Length: 286 v=0 o=sipcli-Session 392352594 1786814146 IN IP4 209.126.103.145 s=sipcli c=IN IP4 209.126.103.145 t=0 0 m=audio 5085 RTP/AVP 18 0 8 101 a=fmtp:101 0-15 a=rtpmap:18 G729/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=ptime:20 a=sendrecv

Could the ''feature is disabled in currently activated licenseBLF" error contribute to this problem. I cant seem to disable it. All BLF's are BLANK.

Please help.

 

[GiannosC_3CX]

Hi Den1s,

As far I can see from your logs is not relevant with your issue. This log shows the dropped packets from known hacking tool(sipcli) from public IP 209.126.103.145

CANCEL, BYE Content-Type: application/sdp User-Agent: sipcli/v1.8

Discarded message, because of blocked User-Agent:

01/19/2017 5:29:29 PM - [CM101008]: The '' feature is disabled in currently activated licenseBLF

As above log the BLF feature is not available on PBX Free edition.

 

[Den1s]

Is there a way to disable BLF so that my logs dont get clogged up?

Also, is there anything i can check to avoid the 1 in 5 dropped calls?

 

[GiannosC_3CX]

Hi Den1s,

Is there a way to disable BLF so that my logs dont get clogged up?

There is no option to disable this activity.

Also, is there anything i can check to avoid the 1 in 5 dropped calls?

. This is an intermittent problem, and only seems to appear when using the GSM network. Landlines usually connect ok.

Could you please give us more information about your issue?
The problem appears on inbound or on outbound calls?
What provider do you use. Is it from the supported providers by 3CX?
Did you run the firewall checker?

 

[Den1s]

Thanks.

Number dialed->Connect->Immediately Dropped happens on 1 in 5 calls and could happen 3 times in a row.

Yes the problem appears on inbound calls only.
We use DrayTel i do not recall it being on the approved list.
Firewall checker was run and is Green.

 

[GiannosC_3CX]

Dear Den1s,

I have sent you a personal message.

 

[Den1s]

Thank you. I will check it out.

 

[Den1s]

More and more calls are being dropped. I did run the Wireshark tool and captured the packets. I then made a call via my GSM which was dropped before the opening IVR message started. I then went to the Telephony menu item and no items appeared. It appears I couldn't analyse that. When I use skype to make a landline call it seems to connect ok. So it seems that the GSM network is the issue. Im really at a loss. Can anyone help me.

 

[OliverTe]

Hi Den1s,

As far I can see from your logs is not relevant with your issue. This log shows the dropped packets from known hacking tool(sipcli) from public IP 209.126.103.145

View attachment 5179

As above log the BLF feature is not available on PBX Free edition.

GiannosC_3CX, this solution was correct until 3CX v15 Update 5. 3CX is now updating the SEC_IGNORE_USER_AGENT from remote, at least with every restart of the 3CX server/service. This means changes to this parameter will NOT be persistent.
We are facing the same problem now as we have used sipcli in order to call a ring group when a reed sensor contact of a door was opened. We have already been in contact with 3CX support and they lapidary told us to use a different software than sipcli but could not recommend a suitable alternative for this use case.
The behaviour 3CX shows makes me angry. This is my PBX and I should be the only one who is setting the rules of which clients should be allowed or denied to connect to the PBX.

 

[GiannosC_3CX]

Hi All,

The solution on this post shows on below screenshots the PBX receives BYE messages from Den1s provider. The calls are terminated by SIP Messages BYE.