Playing with VPN - Incoming call rejected

Status
Not open for further replies.

604

Silver Partner
Advanced Certified
Joined
Aug 1, 2016
Messages
28
Reaction score
5
I've gone through the forum threads related to this error but haven't had any luck so far.
As a proof of concept, I am playing around with VPN connections to cloud hosted 3CX.
We have the following setup:
- 3CX Ent v16 U6 Debian Linux VM hosted in the cloud with a public IP, as well as internal 10.10.1.1 address.
- Sonicwall Tz500 behind primary router (double NAT) at client side, with 10.10.2.0 internal LAN.
- Yealink T53w as a test phone.

After 3CX was configured, we added eth1 with 10.10.1.1, restarted the VM and installed Strongswan.
We successfully built the VPN using Strongswan and Sonicwall's built-in IKEv2 IPSec VPN. We can ping both ways etc.
I provisioned the T53w as a local device (10.10.2.174), connecting to 10.10.1.1 and provisioned successfully.

However, all call attempts fail with the "Incoming call rejected" entry in the log - see below. I can't even call voicemail as a test.
I have verified that all internal subnets are included in Parameters - LOCALSUBNETS:
10.0.0.0/8,169.254.0.0/16,172.16.0.0/12,192.168.0.0/16

Any thoughts?

10/29/2020 12:43:53 PM - [CM503013]: Call(C:6): Incoming call rejected, caller is unknown; msg=Invite-IN Recv Req INVITE from 10.10.2.174:5060 tid=2632460564 [email protected]:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.2.174:5060;branch=z9hG4bK2632460564
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]:5060>
From: "Nowak 604 Test"<sip:[email protected]:5060>;tag=446441746
Call-ID: [email protected]
CSeq: 2 INVITE
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Content-Type: application/sdp
Proxy-Authorization: Digest username="wK4QQ10lV7",realm="3CXPhoneSystem",nonce="414d53595f9b1b7936:21895c922d2df1d041d4ece6f1ee5e29",uri="sip:[email protected]:5060",response="088e077db2a319bdc0cf40f51fa8be83",algorithm=MD5
Supported: replaces
User-Agent: Yealink SIP-T53W 96.85.0.5 805ec080628a
Allow-Events: talk, hold, conference, refer, check-sync
Content-Length: 304

v=0
o=- 20003 20003 IN IP4 10.10.2.174
s=SDP data
c=IN IP4 10.10.2.174
t=0 0
m=audio 12604 RTP/AVP 0 8 9 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:9 G722/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=ptime:20
a=sendrecv
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
 
I was able to find a solution for this. Even though they are local IPs through the VPN I had to enable the setting to allow direct SIP calls and change the FQDN to the 3CX VPN adapter's IP (10.10.1.1).
In Settings - Network - FQDN

I'm not sure why LOCALSUBNETS parameter didn't allow this IP range, but maybe it's not designed for that.
 
Status
Not open for further replies.

Forum statistics

Threads
111,992
Messages
590,171
Members
164,929
Latest member
Cloudstar