3cx on cloud, call failed, decline

[smawaf]

I have 3cx pbx on cloud. I am able to register the 3cx client and i am not able to call extensions. it says call failed and decline. In the activity log it shows.

01/11/2018 2:05:12 PM - Leg L:9.1[Unknown:] is terminated: Cause: BYE from PBX
01/11/2018 2:05:12 PM - Terminated from "name"<sip:[email protected]:5070>;tag=ozBWeVEZTnvhhMx04Ls4GCArO8-LuVZ6 to <sip:[email protected]:5070;tag3cx=xevjcxvnny8jhgqelokcmzdtbq4l1hsj>;tag=f1134123; reason: Rejected
01/11/2018 2:05:12 PM - L:9.1[Unknown:] Sending: OnSendResp Send 603/INVITE from 0.0.0.0:0 tid=PjDcdh013a2G.rTX5lCh70FO7SkRRtIZam Call-ID=IG3nvpZZ.7GZSiK3NGmh1iBNdn3S2ZY0: SIP/2.0 603 Decline Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---PjDcdh013a2G.rTX5lCh70FO7SkRRtIZam;rport=5080 Via: SIP/2.0/UDP 86.98.xx.7:40488;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=clnt.1-q1n4tbkuha2hj57ekffnauawmt33n9go Via: SIP/2.0/TCP 192.168.1.138:50195;rport;branch=z9hG4bKPjDcdh013a2G.rTX5lCh70FO7SkRRtIZam;alias To: <sip:[email protected]:5070;tag3cx=xevjcxvnny8jhgqelokcmzdtbq4l1hsj>;tag=f1134123 From: "name"<sip:[email protected]:5070>;tag=ozBWeVEZTnvhhMx04Ls4GCArO8-LuVZ6 Call-ID: IG3nvpZZ.7GZSiK3NGmh1iBNdn3S2ZY0 CSeq: 15287 INVITE Warning: 499 instance-1 "Caller is forbidden" Content-Length: 0

 

[eddv123]

Hi smawaf,

This link may help it certainly covers one of your errors:
https://www.3cx.com/community/threads/warning-499-caller-is-forbidden.52577/

Where are you making the call to - another extension in 3CX ?
I would presume you have a SIP trunk set up on this system as well ?

 

[smawaf]

I am calling extention 3 digit quote. I dont have any sip trunk configured.

 

[YiannisH_3CX]

Hello @smawaf

Please navigate to Settings / Network / FQDN and check that the Local SIP domain matches the FQDN you used to install the system. Also what PBX version are you running? You can see the exact build number on the Dashboard under the information column.

 

[smawaf]

pbx build 15.5.0 .

 

[smawaf]

Thanks for the quick support. it is working now.

local sip domain and FQDN was not matching. there was nothing on local sip domain. I have added local sip same as FQDN. extensions call are working now. my isp has blocked sip ports, i connect 3cx client to cloud pbx through vpn then i can hear voice is clear. is there any alternative to vpn like srtp?

 

[NickD_3CX]

The 3CX Client when connecting remotely (over the internet) to the 3CX Server should be using the 3CX Tunnel which obfuscates SIP and RTP Traffic, most of the times "slipping" through the ISPs limitations.
I have come across some cases however that in some countries (e.g. UAE) this is still detected and dropped. In these cases though I am not sure even if Secure SIP and/or sRTP will be detected, that I don't know.

If I had to guess though, I would think that your should first try enabling SIP TLS with a certificate, and if that still gets blocked, enable SRTP as well.

 

[smawaf]

Thanks Nick,
Do you have any docs to configure sip on tls and certificate. Anh link to enanle srtp.

 

[NickD_3CX]

We are planning to make configuring TLS much much easier in the coming service packs, can't say too much yet, but for not what you can do is:

1. Download and install the V15.5 SP3 Alpha we have out (https://www.3cx.com/blog/releases/ip-pbx-update-alpha/). Among other things, the TLS cert is preconfigured with the same cert used by the Web Server.
2. In the extension settings do:
   • In Phone provisioning tab select the 3CX Client and:
     • Uncheck "Use 3CX Tunnel for remote connections (3CX Client only)"
     • Set "SIP Transport" to TLS
     • Set "RTP Mode" to Only Secure
   • In the "Options" tab:
     • Uncheck "Disallow use of extension outside the LAN"
   • In the "General" tab, make sure you have set an email for this extension
3. Send a Welcome Email for this extension and provision a 3CX Client.

After the the 3CX Client should talk SIP TLS to the server. You can do test calls to *777 which is the echo extension.
To test the stability, make sure you keep the call active for 30+ seconds as in the UAE I have noticed that sometimes the first half minute is fine and after that trouble starts.

 

[smawaf]

I have installed latest build mentioned above. Now I cannot register the 3cx client when unchecked 3cx tunnel for remote. I can register after 3cx tunnel. Still voice cannot hear with tls and certificate configured.

 

[smawaf]

I am using 3cx client for android. In advance setting i can only see tcp and udp. I cannot see tls. In ios i can see tls.

 

[NickD_3CX]

I neglected to mention that SIP TLS is currently only possible on the MAC and Windows clients, it's not officially supported/implemented yet for Android/iOS apps.

 

[smawaf]

Is there any third party Android app which we can configure as 3cx client.

 

[NickD_3CX]

There are quite a few SIP Clients on the Google Play Store, but there is nothing that we have tested or can suggest for use.
What I can say is that if you go this route, you will have to manually configure the accounts for sure, presence will not work and there will be some trial-and-error involved.

 

[smawaf]

Thanks Nick for the information. One last question, is that any trial sip provider to check the operational of 3cx with sip provider and voice quality.

 

[NickD_3CX]

There are a few of them that allow some free limited use. I sometimes use CallCentric that offer free accounts, but I think you can only call from one free account to the other, so you might have to make 2 of them.

 

[sip.bg]

CSIPsimple for Android works fine for 3CX with TLS and SRTP.
You need to configure extension in 3CX to use TLS and SRTP and into client to enable TLS and SRTP (into network settings of CSIPsimple).

 

[smawaf]

Today I have strange issue. I can register through android. with 3cx tunnel enabled. I cannot register through 3cx windowd client. it says invalid credential. see below logs.

01/16/2018 10:43:39 AM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 213.42.64.58:43633 tid=Pj35aefebd10914e6f9f89607aae1f74ec Call-ID=127756737f484c0aac96d03bb0f440ae: REGISTER sips:cloudgrids.3cx.ae:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS 213.42.64.58:43633;rport=43633;branch=z9hG4bKPj35aefebd10914e6f9f89607aae1f74ec;alias Max-Forwards: 70 Contact: <sips:[email protected]:43633;transport=TLS;rinstance=0-714e9d5f2851428b8d1099bc41d98deb;ob>;reg-id=1;+sip.instance="<urn:uuid:00000000-0000-0000-0000-0000122ef684>" To: "Test test" <sips:[email protected]:5061> From: "Test test" <sips:[email protected]:5061>;tag=8e211019e5854f608b6acba0691ec653 Call-ID: 127756737f484c0aac96d03bb0f440ae CSeq: 18510 REGISTER Expires: 120 Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Proxy-Authorization: Digest username="i2hp57j",realm="3CXPhoneSystem",nonce="414d535c106e301a68:95eba87b883bcd70b16bef6cc3d740c5",uri="sips:cloudgrids.3cx.ae:5061;transport=tls",response="125861b064972a1c7f40a19f1a02a376",algorithm=MD5 Supported: outbound, path User-Agent: 3CXPhone for Windows 15.5.7582.3 X-MakeCall: call;answer;drop;activate;divert Content-Length: 0 ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

 

[NickD_3CX]

Did you skip step "Uncheck "Disallow use of extension outside the LAN"" by any chance?

 

[smawaf]

do we need to keep check or uncheck. currently it is uncheck