Tunneling to remote 3CX server

[boffin]

I think I'm missing something obvious, but the documentation doesnt' seem to line up with the current product range.

I am attempting to connect to a remote 3CX site (running 7.1) , and having problems with audio etc.
I have installed the 3CX Softphone (V3.0.6061).on a PC, and this is functioning 100% , however I am now attempting to register a Linksys SPA942 via the tunnel, which I understand is integrated in the Softphone.

Firstly I found that port 5080 was not open when attempting to telnet to the IP address of the PC with the Softphone installed, so I went into the Connection/Advance Settings of the Softphone configuration and set a manual setting of the local port to 5080. The port now reports that its open when I Telnet to it - but still no registration on the SPA942

I then uninstalled the Softphone, rebooted, and installed the SIP Proxy Tunnel (V1.0) and again the connection seems fine (see log below)

.\Bridge.cpp(74) : {13:13:15.890}(Log2):Tunnel is now listening for SIP calls on the SipProxyPort 5080 of the bridge TunnelClient [123456]
.\ConnMgr.cpp(93) : {13:13:15.906}(Log2):Tunnel is now listening for incoming TCP connections on 192.168.38.88:5090
.\Bridge.cpp(162) : {13:13:15.906}(Log2):Attempting to connect tunnel TunnelClient at 201.48.84.221:5090
.\Bridge.cpp(166) : {13:13:16.000}(Log2):Connection established to tunnel TunnelClient at 201.48.84.221:5090

Again I can Telnet to 5080, and the port would appear open
but again I cannot get the SPA942 to register
I have just reset the SPA device to factory defaults to ensure there is nothing strange in its settings

SIP PORT set to 5060
Proxy set to 192.168.3.4 (local IP of 3CX server on the remote network)
Outbound Proxy set to 192.168.38.88:5080 (being the IP address of the PC running the SIP Proxy software - on same LAN as SPA942 and the listening port in the Proxy)
Use Outbound Proxy and Use OB Proxy In Dialog both set to YES
Subscriber information set to a preconfigured user on the 3CX server.

What surprises me is that there is nothing to be seen in either the log of the 3CX, or the Tunnel Proxy.

Can someone please help me in correcting me in my obvious oversight.

Thanks

 

[Vali_3CX]

I think I'm missing something obvious, but the documentation doesnt' seem to line up with the current product range.

I am attempting to connect to a remote 3CX site (running 7.1) , and having problems with audio etc.
I have installed the 3CX Softphone (V3.0.6061).on a PC, and this is functioning 100% , however I am now attempting to register a Linksys SPA942 via the tunnel, which I understand is integrated in the Softphone.
[...]
Can someone please help me in correcting me in my obvious oversight.

Thanks

Hi

Indeed, there is something obvious you missed - the documentation refers 3CX Voip Client, not 3CX Voip Phone:
- Voip Client comes bundled with the tunnel as a service which, therefore, might be used as you want (and as described in the documentation).
- Voip Phone has the tunnel encapsulated, there is no way to configure it for external purposes, it uses random ports and is very... intimate linked with the phone.

My advice is - for your Linksys phone use the standalone tunnel instead.

Regards
vali

P.S The standalone tunnel page on 3cx wiki (download link also available)
http: //wiki.3cx.com/Home/technical-documentation-dash/sip-proxy-manager - Link no longer available

 

[boffin]

Thanks Vali

I had been refering to this document during my setup.

As stated in my first post
1. I can get the 3CX Softphone to work to a remote 3CX server
2. I ahve the 3CX SIP Proxy tunnel installed on my local PC, and can open a tunnel to the 3CX server on the remote network
3. I cannot get a local hardware device to register via the SIP PROXY TUNNEL installed on my local PC, to the 3CX server on the remote network.

I have on the SPA942, which I am attempting to use. On it I have:

- the Proxy set to 192.168.3.4 (local IP of 3CX server on the remote network)
- Outbound Proxy set to 192.168.38.88:5080 (being the IP address of the PC running the SIP Proxy tunnel software - which on same LAN as SPA942, and the listening port of the Proxy - see log excerpt in my first post)
- set Use Outbound Proxy and Use OB Proxy In Dialog both set to YES
- set Subscriber information set to a preconfigured user on the 3CX server.

Should I be seeing registration attempts in the logs of the SIP PROXY TUNNEL? - I do not.
Should I seeing registration attempt in the 3CX server log? - I do not

Which leads me to believe the problem is between the SPA942 and the listening port of the SIP Proxy Tunnel. (port 5080 is open on the PC, and the SPA is set to use 5080 as the proxy port via the Proxy Tunnel). Windows firewall is disabled.
When then leads me to a configuration in the SPA942. However if all I need to do is as per the post

http: //wiki.3cx.com/Home/technical-documentation-dash/sip-proxy-manager - Link no longer available

then I have done everything right.

As stated, I think that either I'm overlooking something obvious or the documentation is lacking a vital piece of information,

More feedback would be appreciated

 

[Vali_3CX]

Hi

Everything you have done regarding tunnel it's Ok, and indeed it seems that the problem is between Linksys and tunnel, because you should see in the tunnel log phone's SIP requests.

I'm not a Linksys (or hardphones) specialist, so I've searched in our documentation and I've found this one, maybe it's useful
https://www.3cx.com/sip-phones/linksys-spa-962/

I will try to find more on Monday.

Regards
vali

 

[boffin]

I haven't given up experimenting.

Just run wireshark on the PC with the SIP PROXY MANAGER

See a connection from the SPA942 (IP 192.168.38.82) to the PROXY (on 192.168.38.88)

6236 245.602921 192.168.38.82 192.168.38.88 SIP Request: REGISTER sip:192.168.3.4
Internet Protocol, Src: 192.168.38.82 (192.168.38.82), Dst: 192.168.38.88 (192.168.38.88)
User Datagram Protocol, Src Port: sip (5060), Dst Port: onscreen (5080)

Would appear from this that the SPA942 is attempting to communciate with the PROXY.

Still nothing in either the PROXY or 3CX log, nor is have we managed to register.

From the PROXY LOG
.\Bridge.cpp(74) : {19:04:49.890}(Log2):Tunnel is now listening for SIP calls on the SipProxyPort 5080 of the bridge TunnelClient [123456]
.\ConnMgr.cpp(93) : {19:04:49.906}(Log2):Tunnel is now listening for incoming TCP connections on 192.168.38.88:5090
.\Bridge.cpp(162) : {19:04:49.906}(Log2):Attempting to connect tunnel TunnelClient at 201.48.84.221:5090
.\Bridge.cpp(166) : {19:04:50.000}(Log2):Connection established to tunnel TunnelClient at 210.48.84.221:5090

and I can see lots of packets using port 5090 in the wireshark log.

I'm really confused now.

 

[Vali_3CX]

From the PROXY LOG
.\Bridge.cpp(74) : {19:04:49.890}(Log2):Tunnel is now listening for SIP calls on the SipProxyPort 5080 of the bridge TunnelClient [123456]
.\ConnMgr.cpp(93) : {19:04:49.906}(Log2):Tunnel is now listening for incoming TCP connections on 192.168.38.88:5090
.\Bridge.cpp(162) : {19:04:49.906}(Log2):Attempting to connect tunnel TunnelClient at 201.48.84.221:5090
.\Bridge.cpp(166) : {19:04:50.000}(Log2):Connection established to tunnel TunnelClient at 210.48.84.221:5090

and I can see lots of packets using port 5090 in the wireshark log.

Hmmm.... That could means nothing - remember, the two tunnels are connected, and they are using 5090, so part of - if not the whole - traffic you observed is due to their synchronization. It would be much useful if wireshark show traffic on 5080 - this is the key port in our case.

However, since I saw you are familiar with low-level stuff (like packets and wireshark) then I may ask you to check the tunnel proxy 3CXTunnel.ini and to set, into the [3CXTunnel\Logger\Outputs\LogFile] section, the
Severity=Log Error Critical Trace
and
Level=20

In fact, the trace option is important, it allows logging of SIP traffic through the tunnel. After change, restart the tunnel. However, since you don't mentioned wireshark traffic on 5080, I don't expect any difference in the logfile.
If you have some news, please let me know.

Regards
vali

 

[sinboo50]

There are at least 2 more of us having exactly the same problem with the Linksys SPA942.

https://www.3cx.com/community/threads/external-extension-on-linksys-spa942.9264/

It sounds like we should be using only the tunnel software and not the new Softphone Client?

Any help would be appreciated.

Bruce

 

[Vali_3CX]

There are at least 2 more of us having exactly the same problem with the Linksys SPA942.

https://www.3cx.com/community/threads/external-extension-on-linksys-spa942.9264/

It sounds like we should be using only the tunnel software and not the new Softphone Client?

Any help would be appreciated.

Bruce

Hi, Bruce

Ok, let me to reveal the picture to avoid further confusions (I hope):

The 3CX Voip Phone - the new Softphone Client - is completely different compared to its predecessor, 3CX Voip Client.
- the old, 3CX Voip Client, package contains, basically, two products - the phone application and the tunnel service.
- the new, 3CX Voip Phone, package contains only one product - the phone application.
- also, we have a standalone tunnel package, called tunnel proxy manager service.

Therefore, for tunneling a hardphone like LinkSys, you have two options:
- install the old 3CX Voip Client package and use it's bundled tunnel service or
- install the standalone tunnel proxy manager and use it

Once A 3CX tunnel is installed, basically it can be used to tunnel any phone - hardphone like LinkSys, Grandstream etc or softphone like XLite - which supports proxy connection.

Therefore, talking about new Voip Phone in the context of the issue we have, has no relevance, since the key element is the tunnel, which is not available on its package.

Hope this clarified a little the tunnel/softphone confusion.

Regards
vali

 

[boffin]

here is my ini file - I have not made any changes

Note logging levels were already set as you requested

[3CXSIPProxy]
Name=TunnelClient
Password=frustrated
SipProxyPort=5080
TunnelPort=5090
ID=123456
TunnelAddr=201.48.84.221
[3CXTunnel\Logger\Outputs\LogFile]
Level=10
File=3CXTunnel.log
KeepBackup=1
Severity=Log Error Critical Trace
MaxFileSizeKB=2048
Format=$FileLine : {$ShortDT}($Severity$Level):
[3CXTunnel\logger\outputs\debug]
severity=Debug Dump Critical
file=dbg:
level=20
format=$FileLine : ($Subsystem::$Method):
[Bridge]
ListenPort=5090
Bridges=3CXSIPProxy
ListenIP=192.168.38.88
[3CXTunnel\Logger\Outputs\]
path=.\Logs\
debug=1
LogFile=1


I'll run some more wireshark captures later in the day

 

[Vali_3CX]

here is my ini file - I have not made any changes

It is ok. If you plan to do some investigations using wireshark, please monitor traffic on 5080 - from all you described until now, the conclusion is the one you said from the beginning, the issue is between Linksys and tunnel on 5080, and I assume Linksys does not proper send - or don't send at all - TCP signal on tunnel listening 5080.

P.S please check the following message, written earlier, perhaps it might be helpful in configuring your Linksys:
https://www.3cx.com/community/threads/external-extension-on-linksys-spa942.9264/#p48067

 

[boffin]

I hope I have enough information for your

Internet Protocol, Src: 192.168.38.82 (192.168.38.82), Dst: 192.168.38.88 (192.168.38.88)
User Datagram Protocol, Src Port: sip (5060), Dst Port: onscreen (5080)
Source port: sip (5060)
Destination port: onscreen (5080)
Length: 468

0000 00 16 e6 f6 50 e9 00 0e 08 d1 c7 61 08 00 45 68 ....P... ...a..Eh
0010 01 e8 00 ee 00 00 fa 11 ef b3 c0 a8 26 52 c0 a8 ........ ....&R..
0020 26 58 13 c4 13 d8 01 d4 d3 ff 52 45 47 49 53 54 &X...... ..REGIST
0030 45 52 20 73 69 70 3a 31 39 32 2e 31 36 38 2e 33 ER sip:1 92.168.3
0040 2e 34 20 53 49 50 2f 32 2e 30 0d 0a 56 69 61 3a .4 SIP/2 .0..Via:
0050 20 53 49 50 2f 32 2e 30 2f 55 44 50 20 31 39 32 SIP/2.0 /UDP 192
0060 2e 31 36 38 2e 33 38 2e 38 32 3a 35 30 36 30 3b .168.38. 82:5060;
0070 62 72 61 6e 63 68 3d 7a 39 68 47 34 62 4b 2d 37 branch=z 9hG4bK-7
0080 30 63 31 36 33 31 66 0d 0a 46 72 6f 6d 3a 20 22 0c1631f. .From: "
0090 35 32 22 20 3c 73 69 70 3a 35 32 40 31 39 32 2e 52" <sip :52@192.
00a0 31 36 38 2e 33 2e 34 3e 3b 74 61 67 3d 63 30 61 168.3.4> ;tag=c0a
00b0 65 64 61 38 63 62 62 65 62 33 64 65 30 6f 30 0d eda8cbbe b3de0o0.
00c0 0a 54 6f 3a 20 22 35 32 22 20 3c 73 69 70 3a 35 .To: "52 " <sip:5
00d0 32 40 31 39 32 2e 31 36 38 2e 33 2e 34 3e 0d 0a [email protected] 8.3.4>..
00e0 43 61 6c 6c 2d 49 44 3a 20 33 64 65 33 39 36 61 Call-ID: 3de396a
00f0 32 2d 39 34 39 63 62 65 32 31 40 31 39 32 2e 31 2-949cbe [email protected]
0100 36 38 2e 33 38 2e 38 32 0d 0a 43 53 65 71 3a 20 68.38.82 ..CSeq:
0110 39 33 39 39 20 52 45 47 49 53 54 45 52 0d 0a 4d 9399 REG ISTER..M
0120 61 78 2d 46 6f 72 77 61 72 64 73 3a 20 37 30 0d ax-Forwa rds: 70.
0130 0a 43 6f 6e 74 61 63 74 3a 20 22 35 32 22 20 3c .Contact : "52" <
0140 73 69 70 3a 35 32 40 31 39 32 2e 31 36 38 2e 33 sip:52@1 92.168.3
0150 38 2e 38 32 3a 35 30 36 30 3e 3b 65 78 70 69 72 8.82:506 0>;expir
0160 65 73 3d 31 32 30 0d 0a 55 73 65 72 2d 41 67 65 es=120.. User-Age
0170 6e 74 3a 20 4c 69 6e 6b 73 79 73 2f 53 50 41 39 nt: Link sys/SPA9
0180 34 32 2d 36 2e 31 2e 33 28 61 29 0d 0a 43 6f 6e 42-6.1.3 (a)..Con
0190 74 65 6e 74 2d 4c 65 6e 67 74 68 3a 20 30 0d 0a tent-Len gth: 0..
01a0 41 6c 6c 6f 77 3a 20 41 43 4b 2c 20 42 59 45 2c Allow: A CK, BYE,
01b0 20 43 41 4e 43 45 4c 2c 20 49 4e 46 4f 2c 20 49 CANCEL, INFO, I
01c0 4e 56 49 54 45 2c 20 4e 4f 54 49 46 59 2c 20 4f NVITE, N OTIFY, O
01d0 50 54 49 4f 4e 53 2c 20 52 45 46 45 52 0d 0a 53 PTIONS, REFER..S
01e0 75 70 70 6f 72 74 65 64 3a 20 72 65 70 6c 61 63 upported : replac
01f0 65 73 0d 0a 0d 0a es....

 

[boffin]

Anyone have any thoughts on this?

 

[King Computer]

I had a similar issue with getting a SPA942 running.

First of all make sure all your ports are forwarded correctly
http://technicians-blog.kingcomputer.com.au/index.php/what-voip-ports-to-open-and-forward-for-3cx/


Second of all follow the instructions here
http://technicians-blog.kingcomputer.com.au/index.php/configuring-external-spa942-ip-sip-phone-with-3cx/

Let me know how you go