Calls being dropped

[positive3]

Hello.

I have 3CX still hosted by 3CX as it's still in it's first year.

I have a Linksys SPA3102 with a bell attached to the phone port.

I have a Yealink WP52P with 4 handsets attached to it.

There is a ring group 800 that all of the phones are in and the sip trunk points to it.

Most of the time everything is fine and all 5 lines ring. Every now and then the dect phones just cannot do anything. They don't ring, they cannot call but the bell still rings. If I reboot the base station then they all start working again. One user has the 3cx app on a mobile and that works all the time.

They are on a good connection and behind a draytek 2860. The phone system and the draytek all have the latest firmware as do the phones.

I have attached the log of when they go crazy.

Any helps greatly appreciated.

[attachment deleted by moderator]

 

[Marari]

@positive3

You may want to edit your .txt so that you block out your IP's and FQDN.
Don't paint a bullseye on your back for SIP hackers.

 

[AWS2P]

; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
15/07/2019 07:33:12 - Got REGISTER for foreign registrar: registrar host <sip:@xxxx:5060> is not mine!
15/07/2019 07:24:44 - There's another STUN server that resolves to the same IP: xxxx:3478/UDP fk=0; ignored
15/07/2019 07:11:08 - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from xxxx:6023 tid=a86189dc-fa8d-4675-b937-bd7ad4113471 Call-ID=qlduxssjxquuongqucsugheleldmwlmlvrstjyxnjbphacpxiq:

it seems you have a lot of authentication failure , did you change PBX settings ?
Do you use supported trunk provider?
Did you change or use phones registred previously with STUN config always running on RPS servers?
Is your PBX using same static public IP ?

Your pbx isn't up to date version is 3CXPhoneSystem 15.0.57336.0

 

[positive3]

@positive3

You may want to edit your .txt so that you block out your IP's and FQDN.
Don't paint a bullseye on your back for SIP hackers.

It's locked down to one ip address but good shout.

 

[positive3]

; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
15/07/2019 07:33:12 - Got REGISTER for foreign registrar: registrar host <sip:@xxxx:5060> is not mine!
15/07/2019 07:24:44 - There's another STUN server that resolves to the same IP: xxxx:3478/UDP fk=0; ignored
15/07/2019 07:11:08 - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from xxxx:6023 tid=a86189dc-fa8d-4675-b937-bd7ad4113471 Call-ID=qlduxssjxquuongqucsugheleldmwlmlvrstjyxnjbphacpxiq:

it seems you have a lot of authentication failure , did you change PBX settings ?
Do you use supported trunk provider?
Did you change or use phones with previous STUN config always set on RPS servers?
Is you PBX with same static public IP ?

Your pbx isn't up to date version is 3CXPhoneSystem 15.0.57336.0

Everything here is brand new. I have even taken our W52P base that worked flawlessly here to their site and it's doing the same. Sip provider is Gamma. I have used it loads of times (it's what we use).

 

[AWS2P]

Is it a demo PBX? they are using 3CX hosted as production PBX?

 

[positive3]

Is it a demo PBX? they are using 3CX hosted as production PBX?

It's production. They are using the free for a year hosting.

 

[JohnS_3CX]

Hi

What version is your PBX and where is it hosted?

How are the phones provisioned towards the PBX? STUN/SBC?

 

[AWS2P]

On remote side phones are in STUN Mode? behind SBC ? VPN ?

in his log file version is : 3CXPhoneSystem 15.0.57336.0

 

[positive3]

Hi

What version is your PBX and where is it hosted?

How are the phones provisioned towards the PBX? STUN/SBC?

It's hosted on the free hosting with 3CX. It's v 16.0.2.910.

The bell is SBC the yealink is STUN.

 

[AWS2P]

something is unclear, why in your log pbx version is 3CXPhoneSystem 15.0.57336.0,
do you have multiples instances of same pbx , or hosted differents places?

 

[positive3]

It's hosted on the free hosting with 3CX. It's v 16.0.2.910.

The bell is SBC the yealink is STUN.

Good spot.

 

[JohnS_3CX]

I think you may be mistaken here, the user agent shows V15.0, I don't think it's possible to get free hosting from 3CX with such an old version from a year ago so not sure what is going on here...

Regardless, if you have your bell and DECT phone at the same site, why are they not both behind SBC?
I would start with upgrading the firmware here https://www.3cx.com/sip-phones/firmware-upgrade-yealink-dect-w52p/ and provisioning the phone behind the SBC (since you already have one)

 

[positive3]

something is unclear, why in your log pbx version is 3CXPhoneSystem 15.0.57336.0,
do you have multiples instances of same pbx , or hosted differents places?

something is unclear, why in your log pbx version is 3CXPhoneSystem 15.0.57336.0,
do you have multiples instances of same pbx , or hosted differents places?

I don't understand that either. Only one instance of the phone system.

 

[AWS2P]

And also update SBC to latest V 16.0.386 if not already done

 

[JohnS_3CX]

Are you sure you don't have anything set to register on this PBX with a fake user agent? (i.e an attacker or an old PBX trying to use this one as a trunk)

What is the the Ip starting from 62 and why is it trying to register as extension 101 for example?

 

[AWS2P]

is your 3CX SIP port restricted to your sip trunk provider IP ?

 

[positive3]

Are you sure you don't have anything set to register on this PBX with a fake user agent? (i.e an attacker or an old PBX trying to use this one as a trunk)

What is the the Ip starting from 62 and why is it trying to register as extension 101 for example?

The 62 ip address resolves to Paris apparently. I have blacklisted that ip address as i know the ip addresses all my phone come from. It makes now sense that the log says v15 but it's running v16.

 

[AWS2P]

Are you sure not having used phone with previous STUN config, once i bought a second hand phone from amazon and since i set it on lan it was receiving a german pbx config.

 

[positive3]

Are you sure not having used phone with previous STUN config, once i bought a second hand phone from amazon and since i set it on lan he was receiving a german pbx config.

The base was brand new out of the box. I even factory reset my base station and used that one.