SPA3000 and Cloud

[nowheretohide]

Hi all,

I am running 3CX Cloud version.

I connect SPA3000 to modem, and using dynamic DNS through NO-IP.
I can log on the SPA3000 with public ip and dynamic DNS address. it works.

Modem 5062 port is open and forwarded to SPA3000 ip.

Line 1 is working very well.

PSTN Line, not registering keep failing. It registered few time but then stop working.
I have the trunk in 3cx cloud, and user is 10004.
User 10004 credentials is correct. I already checked and double enter the password.

I attached the PSTN Line page and System Page for ref.

Here is the final failed info from Log Manager.

05/20/2020 5:25:18 PM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from ************:5062 tid=-2d5332cd [email protected].*: REGISTER sip:****** SIP/2.0
Via: SIP/2.0/UDP 219.92.91.210:5062;branch=z9G4bK-2d5332cd
Max-Forwards: 70
Contact: ****** <sip:10004@******:5062>;expires=1800
To: ****** <sip:10004@******>
From: ****** <sip:10004@******>;tag=559a2a2e765fa9o1
Call-ID: [email protected].*
CSeq: 1831 REGISTER
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Proxy-Authorization: Digest username="10004",realm="3CXPhoneSystem",nonce="******:******",uri="sip:******",algorithm=MD5,response="******"
Supported: x-sipura
User-Agent: Linksys/SPA3000-3.1.10(GWd)
Content-Length: 0 ;
Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

Do you guys have any idea what is not correct?

 

[AWS2P]

check in console if SPA IP is not blacklisted, if so clear it.

try to add :5062 to proxy FQDN value or replace with IP adress:5062
try register expires value to 600s
Try to set 0 or 1 in PSTN Answer Delay

on 3CX side have you set 5062 port too?

 

[nowheretohide]

check in console if SPA IP is not blacklisted, if so clear it.

try to add :5062 to proxy FQDN value or replace with IP adress:5062
try register expires value to 600s
Try to set 0 or 1 in PSTN Answer Delay

on 3CX side have you set 5062 port too?

thank you.
i already checked IP Blacklist. my ip is not listed there. it is clean.

FQDN, i replaced with IP number of 3cx without 5062 - FAILED
FQDN, i replaced with IP number:5062 - Not Registered.

PSTN Answer Delay try to 0,1,3,5,10 - Failed

Register expires value to 600s - Failed

3CX Trunk Side:

Registrar/Server/Gateway Hostname or IP
SPA3000 Public IP port 5062

Authentication
Type of Authentication - Do not require - IP Based - this one working before. (current)
Type of Authentication - Register/Account Base - Failed (tried, no working)

Authentication ID (aka SIP User ID) - 10004

Authentication Password- ********

Still not registered.

 

[AWS2P]

Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

this is when password is not the good one, recheck on 3cx and paste in SPA
you need to create a generic trunk , with authentication based (ID / pwd)

set pbxip:5062 (not only IP)

Do you have a 5062 Nat rule on pbx site to redirect traffic to PBX ?

 

[nowheretohide]

this is when password is not the good one, recheck on 3cx and paste in SPA
you need to create a generic trunk , with authentication based (ID / pwd)

set pbxip:5062 (not only IP)

Do you have a 5062 Nat rule on pbx site to redirect traffic to PBX ?

rechecked on 3cx and paste in SPA - failed. It s not user and password issue.


create a generic trunk?

I create

Add Gateway
Add PSTN Gateway
Generic Device Gateway
Number of Physical PSTN Ports on device -1

 

[nowheretohide]

anyway, i recreate PSTN Gateway.

i followed the following steps
Add Gateway
Add PSTN Gateway
Generic Device Gateway
Number of Physical PSTN Ports on device -1

I used the new created account in SPA.
it works.

still using port 5062

 

[nowheretohide]

after few call in and out, it stopped working and getting the same result. Registration FAILED.

 

[nowheretohide]

pstn line connected with attached settings.
after i made few test, calling in and out, registration stopped, and keep getting FAILED.

 

[leejor]

You realize that using the gateway remotely is not supported.

That said, I was not aware that using a URL, rather than an IP, was possible for the trunk destination, necessary for calls from 3CX to the gateway as this is normally a LAN IP. Perhaps this has changed.
The fact that the 3K does initially register, and works for a short while, would seem to indicate that 3CX is happy with the credentials. I'm wondering if it is a router issue at the remote end, or, perhaps a STUN setting on the 3K. Try resetting the router the next time this happens, see if the 3K is again able to register.

Be careful about the information you are posting, hackers love this.

 

[nowheretohide]

You realize that using the gateway remotely is not supported.

That said, I was not aware that using a URL, rather than an IP, was possible for the trunk destination, necessary for calls from 3CX to the gateway as this is normally a LAN IP. Perhaps this has changed.
The fact that the 3K does initially register, and works for a short while, would seem to indicate that 3CX is happy with the credentials. I'm wondering if it is a router issue at the remote end, or, perhaps a STUN setting on the 3K. Try resetting the router the next time this happens, see if the 3K is again able to register.

Be careful about the information you are posting, hackers love this.

Resetting modem do not make any changes.

by the way, i get pstn line from my Optical Network Terminal - Huawei HG8240H.(4 GE + 2 POTS + 1 USB + Wi-Fi)

Simply, connect Huawei HG8240H TEL1 exit to SPA 3000 Line.
Do you think maybe something wrong here?

 

[leejor]

It could be something on that router, given it has inbuilt VoIP services. If possible, move the 3K to another location, behind another "basic" router. Don't bother changing the trunk settings in 3CX, just see if the 3K registers (and stays that way,) and test you can successfully place calls to the PBX from a PSTN line.

Have you confirmed that port 5062 is not currently used by one of the services on your router? One would assume that , if there are two lines, they probably use 5060 and 5061, but, you never know.

 

[nowheretohide]

Once it is registered, PSTN to VOIP, VOIP to PSTN working fine.
I can make outbound calls and receive calls to IVR, 3CX.


I am using TP-LINK Modem, and SIP ALG enabled.


i checked with port scan and here is the result.

PORT STATE SERVICE

5060/tcp filtered sip

5061/tcp filtered sip-tls

5062/tcp filtered na-localise

5063/tcp filtered csrpc

5064/tcp filtered ca-1

5065/tcp filtered ca-2

5066/tcp filtered stanag-5066

5067/tcp filtered authentx

5068/tcp filtered bitforestsrv

5069/tcp filtered i-net-2000-npr

 

[leejor]

If it just stops registering, then you need to figure out why that is, by process of elimination. My first suspect would be the router.

You could use Wireshark to confirm that the 3K is still attempting to re-register. Are those messages making it past the router, do you see them in the Activity Log?

 

[nowheretohide]

LIne 1, got extention from 3cx cloud, and register with pbxip:5060.
PSTN i changed the port to 5060, 5061,5062,etc. (inlcuding 3cx cloud side). PSTN Line keep failing to register.

 

[leejor]

So the PSTN line did previously register, and now it is not? I would not try to use ports 5060 and 5061 locally as they are probably used by the SIP services on your router.

Normally, 3CX would continue to "see" a device registered for 30 minutes after the initial registration unless it attempted to contact the device and was unable to do so. perhaps that is why it is failing after a short while.

 

[nowheretohide]

So the PSTN line did previously register, and now it is not? I would not try to use ports 5060 and 5061 locally as they are probably used by the SIP services on your router.

Normally, 3CX would continue to "see" a device registered for 30 minutes after the initial registration unless it attempted to contact the device and was unable to do so. perhaps that is why it is failing after a short while.

Thank you, let me change the router, and double check ports then try to register again.

 

[nowheretohide]

i set up a new generic gateway for pstn - analog.
3cx cloud side, account created as Register/Account based. rest of the settings is as it is. No touch.
Whenever I touch 3CX side Trunk CID, Inbound or Outbound rules,(without any changes) SPA3000 failed to register.
Now SPA3000 registered all day long without any problem.

But even we configure outcalling rules in 3cx side, we cannot make calls through PSTN Gateway with other extensions.
Currently only the Line 1 in SPA3000 extension can make outbound calls via PSTN.
Any incoming call to PSTN goes directly to 3CX IVR.

 

[leejor]

That has been the issue when attempting to use a gateway remotely. When a gateway registers, unlike an ATA, or SIP set, 3CX does not use the registration information to send calls back to the gateway, it uses the IP and port that you put into the trunk settings. As you are using a dynamic IP at the gateway end, you may be able to get it working by using the public IP, but that is going to change at some point. I don't recall 3Cx allowing a URL to be used there.

You must also forward ports 5062 (if you are still using that as the local port at the 3K), in the remote router to the 3K local IP. Even after all this, audio ports may still have an issue, which is not helped by the fact the router is equipped with two SIP ports of its' own.

 

[nowheretohide]

That has been the issue when attempting to use a gateway remotely. When a gateway registers, unlike an ATA, or SIP set, 3CX does not use the registration information to send calls back to the gateway, it uses the IP and port that you put into the trunk settings. As you are using a dynamic IP at the gateway end, you may be able to get it working by using the public IP, but that is going to change at some point. I don't recall 3Cx allowing a URL to be used there.

You must also forward ports 5062 (if you are still using that as the local port at the 3K), in the remote router to the 3K local IP. Even after all this, audio ports may still have an issue, which is not helped by the fact the router is equipped with two SIP ports of its' own.

i did not touch any settings in 3cx side, so i still receive calls. anyway, i ll ask local provider to fix it within this week.

 

[leejor]

Some ISPs will allow you to have two public IPs. If you check (with your ISP), and that is the case, then, depending on the router options, you may be able to assign one LAN port, on the rear of the router to "pass through" status, giving the 3K a public IP.

In situations, where the modem and router are separate devices, you may be able to run the modem to a switch, then to two routers. or (in your case) a router, and the 3K. However, that still won't solve the problem of having a dynamic IP, at the remote end, if it changes often.