grandstream phones constantly ringing after update

[manfer]

The last 3CX update has been annoying.

I have upgraded 3 clients PBX to v.15.5 SP3 and what a mess. I upgraded then remotely on saturday morning. I tested one of then with a grandstream GXP2130 phone because I wanted to test CSTA. That feature worked correctly but I noticed that each time the phone was registered to the PBX it just started ringing till ring timeout.

The phone showed on the screen it was being called by itself, from his own extension. The PBX was not aware of a call in progress.

The GXP2130 phone had firmware version 1.9.0.26 which is the last stable one from grandstream and was working properly on 3CX v15.5 SP2 though lately it started showing the annoying not compatible firmware red warning which we had to explain to the client the best we could.

I took captures on the phone and there were no invite messages at all. Maybe there is something on the 407 register challenge message reply from PBX that makes the phone start ringing.

I updated the phone firmware to version 1.9.0.60 beta and the phone stopped doing that annoying thing.

I didn't realize on that moment it was a PBX update issue. I just thought it could be because of the network where I was doing the remote tests through SBC. I thought about SIP ALG but it was disable on router. Anyway, I didn't pay to much attention to the problem on that moment. What an error!

On sunday afternoon when I decided to take a look to one of the clients PBX I found out all GXP2130 phones on that office were showing ringing icon on the UI. A real headache to update those phones to stop that. And they were quite a few.

I checked the other client which had a lot more phones. Again all phones ringing. I had to disable SIP service on 3CX and wait till phones lost registration because the phones were totally blocked. When ringing you can't change any configuration on grandstream phones.

The phones on this two clients offices where upgraded to the firmware provided by 3CX 1.9.0.58.

GXP2140 phones on firmware version 1.9.0.26 were not affected by this problem nor the one I had upgraded to 1.9.0.60 beta version.

But today I had upgraded some GXP2140 phones on my office to the firmware 1.9.0.58 provided by 3CX and same ringing problem that happens with version 1.9.0.26 on GXP2130 phones appeared. It doesn't happen so often on these phones but it happens.

Any clue of what is going on. Any configuration I have to change?

Very very very very very annoying updated. Very upset.

The more I work on VoIP the more I'm disappointed with providers. When there is not a PBX bug, there is a trunk provider problem, a phone firmware bug, ... If you don't upgrade there are bugs, if you upgrade some are solved but others added.

I would really appreciate more stability no matter if upgrades come at a slower pace.

Sorry the large message.

 

[Greg77]

Grandstream GXP2130 1.0.9.58 connects fine to two 3CX v.15.5 SP3 (15.5.8801.3) build on Windows 10 Pro and Debian 8 though LAN option. If I choose STUN and change Provisioning URL on the phone, it takes a new template, but extension is not register. What is different in LAN and STUN templates for Grandstream phone? Yealink T23G works fine with the same.

02/17/2018 5:10:26 PM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from [IP address]:5065 ***
Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

 

[manfer]

Grandstream GXP2130 1.0.9.58 connects fine to two 3CX v.15.5 SP3 (15.5.8801.3) build on Windows 10 Pro and Debian 8 though LAN option. If I choose STUN and change Provisioning URL on the phone, it takes a new template, but extension is not register. What is different in LAN and STUN templates for Grandstream phone? Yealink T23G works fine with the same.

02/17/2018 5:10:26 PM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from [IP address]:5065 ***
Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

This is the part of the 3CX template that sets the sip server parameter on the phone when using STUN mode

    {IF network=REMOTESTUN}
    <!-- SIP Server configuration for remote using stun mode - External IP Address -->
    <P47>%%pbx_ip%%:%%param::sipport%%</P47>
    <!-- Outbound Proxy - The "P48" field contains the ip address and SIP port of the SIP Outbound Proxy - in this case 3CXPS. The "pbx_ip" and "param::sipport" variables will be replaced by the IP Address and SIP Port of 3CXPS. -->
    <P48></P48>
    <!-- Local SIP port (default 5060) -->
    <P40>%%phonesipport%%</P40>
    <!-- NAT Traversal. 0 - no, 1 - STUN, 2 - keep alive, 3 - UPnP, 4 - Auto, 5 - VPN -->
    <P52>1</P52>
    {ENDIF}

which in my opinion has a bug and should be corrected to

    {IF network=REMOTESTUN}
    <!-- SIP Server configuration for remote using stun mode - External IP Address -->
    <P47>%%param::PBXPUBLICIP%%:%%param::sipport%%</P47>
    <!-- Outbound Proxy - The "P48" field contains the ip address and SIP port of the SIP Outbound Proxy - in this case 3CXPS. The "pbx_ip" and "param::sipport" variables will be replaced by the IP Address and SIP Port of 3CXPS. -->
    <P48></P48>
    <!-- Local SIP port (default 5060) -->
    <P40>%%phonesipport%%</P40>
    <!-- NAT Traversal. 0 - no, 1 - STUN, 2 - keep alive, 3 - UPnP, 4 - Auto, 5 - VPN -->
    <P52>1</P52>
    {ENDIF}

 

[manfer]

This is the part of the 3CX template that sets the sip server parameter on the phone when using STUN mode

    {IF network=REMOTESTUN}
    <!-- SIP Server configuration for remote using stun mode - External IP Address -->
    <P47>%%pbx_ip%%:%%param::sipport%%</P47>
    <!-- Outbound Proxy - The "P48" field contains the ip address and SIP port of the SIP Outbound Proxy - in this case 3CXPS. The "pbx_ip" and "param::sipport" variables will be replaced by the IP Address and SIP Port of 3CXPS. -->
    <P48></P48>
    <!-- Local SIP port (default 5060) -->
    <P40>%%phonesipport%%</P40>
    <!-- NAT Traversal. 0 - no, 1 - STUN, 2 - keep alive, 3 - UPnP, 4 - Auto, 5 - VPN -->
    <P52>1</P52>
    {ENDIF}

which in my opinion has a bug and should be corrected to

    {IF network=REMOTESTUN}
    <!-- SIP Server configuration for remote using stun mode - External IP Address -->
    <P47>%%param::PBXPUBLICIP%%:%%param::sipport%%</P47>
    <!-- Outbound Proxy - The "P48" field contains the ip address and SIP port of the SIP Outbound Proxy - in this case 3CXPS. The "pbx_ip" and "param::sipport" variables will be replaced by the IP Address and SIP Port of 3CXPS. -->
    <P48></P48>
    <!-- Local SIP port (default 5060) -->
    <P40>%%phonesipport%%</P40>
    <!-- NAT Traversal. 0 - no, 1 - STUN, 2 - keep alive, 3 - UPnP, 4 - Auto, 5 - VPN -->
    <P52>1</P52>
    {ENDIF}

And it doesn't seem to be the only bug. Same error in the part of the template that set the stun server.

    {IF network=REMOTESTUN}
    <!-- Local RTP port. Default is 5004 -->
    <!-- Number: 1024 - 65535. Must be even number -->
    <!-- Mandatory -->
    <P39>%%rtp_port_min%%</P39>
    <!-- STUN server -->
    <!-- String -->
    <P76>%%pbx_ip%%:%%param::sipport%%</P76>
    {ENDIF}

which should look like

    {IF network=REMOTESTUN}
    <!-- Local RTP port. Default is 5004 -->
    <!-- Number: 1024 - 65535. Must be even number -->
    <!-- Mandatory -->
    <P39>%%rtp_port_min%%</P39>
    <!-- STUN server -->
    <!-- String -->
    <P76>%%param::PBXPUBLICIP%%:%%param::sipport%%</P76>
    {ENDIF}

I have not reviewed the template more to know if there are still more problems but the phone should work correctly if those two things are corrected.

 

[Noob]

Grandstream GXP2130 1.0.9.58 connects fine to two 3CX v.15.5 SP3 (15.5.8801.3) build on Windows 10 Pro and Debian 8 though LAN option. If I choose STUN and change Provisioning URL on the phone, it takes a new template, but extension is not register. What is different in LAN and STUN templates for Grandstream phone? Yealink T23G works fine with the same.

02/17/2018 5:10:26 PM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from [IP address]:5065 ***
Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

Hi,
Try to check the 3CX firewall. Usually when changing passwords or settings on phones, it gives authentication error because it blocks the associated IP. Adds the firewall's safe list to the range of IP's that are associated with the phones. If they are remote connections it adds public IP of the remote site to the firewall whitelist.

and

if the phones have the same network as the server, the URL LINK must be the IP of the server
Ex:

Sip server

192.168.x.x: 5001

if it is outside the same network segment the url link must be

Ex:

Sip server

company.3cx.eu

 

[Greg77]

Hi,
Try to check the 3CX firewall. Usually when changing passwords or settings on phones, it gives authentication error because it blocks the associated IP. Adds the firewall's safe list to the range of IP's that are associated with the phones. If they are remote connections it adds public IP of the remote site to the firewall whitelist.

and

if the phones have the same network as the server, the URL LINK must be the IP of the server
Ex:

Sip server

192.168.x.x: 5001

if it is outside the same network segment the url link must be

Ex:

Sip server

company.3cx.eu

You are right, when a phone tries to register 3CX places its Public IP to Blacklist. I manually allowed such IPs.
When I change the phone Privisioning URL from LAN template to STUN template, it changes SIP server with its name like 3cx.us.com:5060 insted of LAN address, but Extention are not registered(
Also, I have mentioned that GXP2130 doesn't give me a prompt after rebooting where I should enter username (my extension) and password (Voicemail PIN)

 

[Noob]

You are right, when a phone tries to register 3CX places its Public IP to Blacklist. I manually allowed such IPs.
When I change the phone Privisioning URL from LAN template to STUN template, it changes SIP server with its name like 3cx.us.com:5060 insted of LAN address, but Extention are not registered(
Also, I have mentioned that GXP2130 doesn't give me a prompt after rebooting where I should enter username (my extension) and password (Voicemail PIN)

Probably the phones are by DHCP, every time you reboot the IP changes, you have to see which new IP is associated with each phone and try for another browser

 

[manfer]

1. Choosing Attended Transfer in 3CX provisioning instead of default BlindTransfer does not work. When you try to transfer, the only options on soft buttons are "BlindTxFr" so there seems to be no way to do an attended transfer.

On phone web configuration you have to go into Settings->Call Features. Search for the option Attended transfer mode and set its value to Dynamic.

From template, if I'm not wrong, that would be P number 1376 which value must be set to 1.

    <!-- Attended Transfer Mode. 0 - Static, 1 - Dynamic. Default is 0 -->
    <!-- Number: 0, 1 -->
    <!-- Mandatory -->
    <P1376>1</P1376>

What you configure on 3CX phone provisioning form is just the transfer method to use on VPKs.

2. The PC Port is now DISABLED by default. I tried re-enabling directly in phone web pages but there are 3 options: Enabled, Disabled and Mirror. Unfortunately I didnt have any luck getting any of them to re-enable the PC Port and had to resort to connecting via a switch.

You have to set it to enable. Mirror means that you want all network packages on the LAN interface to go through the PC port too. That's something you may want to use for debugging but not suggested if you want to use PC port.

I'm not using it but maybe it needs a reboot after enable.

 

[Greg77]

Probably the phones are by DHCP, every time you reboot the IP changes, you have to see which new IP is associated with each phone and try for another browser

Yes, the phone uses DHCP in LAN, but I connect to 3CX using remoteSTUN mode and 3CX blacklist only my Public IP which is in white list now.
If I setup GXP2130 using LAN mode, it works fine (VPN to 3CX in Google Cloud)

I created a custom grandstream template and made recommended changes, reset MC01, but it doesn't help

 

[Jose Lara]

Sorry, for my English

I solved the problem on my grandstream 1620 and 2130 phones​

but most of my phones are 1450, and I can not find a fix for them, so far they have not caused any problems.

I invested a lot in this 3cx solution, and when I implemented everything it was compatible

how you adop the GXP2130? my phones are on 1.0.5.33 firmware