Solved Grandstream 2130 SP pickup problem

[earthwing]

I have an issue where Shared Parking button is provisioned but behaves like a park button. Let em clarify this. I can press the SP1 and park and click on the same phone and pickup with a behavior like a hold button. However attempting to pick up the parked call on another phone does nothing. The BLF line is correctly provisioned as Shared Parking 1 , Shared Parking 2 etc. A restart nor a factory reset has resolved it. Almost like the XML file is not getting pulled into the phone. Firmware is latest release on GS2130 3cx template and 3cx v15.5U5
I think there is a bug somewhere as one way to resolve it seems to be to set all the BLF's to default, save, restart, re-provision after a factory reset. But it doe NOT always work. This is not an issue with the yealink phones either.

 

[craigreilly]

We have had parks on the Grandstreams without issue - default template. Even before they were supported, the phones worked fine.
Biggest question - are all phones in same location and same subnet as the PBX? Or is there some cloud interaction here?

 

[earthwing]

Craig, All the phones are on a single 182.168.1.x NAT network and the system is hosted in the cloud. Standard run of the mill broadband provider, 15/5 meg up and down. Is there a tool i can download on a client network that can point to a 3CX system and validate all the ports required are open just like I can run a firewall checker on the hosted system? I've checked the router for ALG.

 

[earthwing]

Correction 192.168.1.x network

 

[lneblett]

I also have Park working well, I think the latest release is 1.0.9.71 for 3CX. There have been some issues with the GS phones working with 3CX due to the firmware and templates. 3CX stopped supporting GS and only recently brought them back into the fold and I suspect that both sides had/have some catching up to do. I had to manually provision the Parks for some time, and also modified templates. but with the above firmware and the latest 3CX templates with no mods, this issue has since gone away.

There is new firmware that might be on the way to sort out some other issues as I regularly check the release notes on the GS site, and while it does address some 3CX related issues, I cannot say that this will become an official 3CX release. Take a look at the dial plan on the phone and then compare to the dial plan in the template and see if the same. Mine is: { [*#x]+ | \S\Px | \S\Pxx | \S\Pxxx }.

 

[YiannisH_3CX]

Hello @earthwing

Please note that the latest supported firmware is 1.0.9.102 so make sure that you are running the correct one with the default templates. https://www.3cx.com/support/phone-firmwares/

So you see the shared parking buttons provisioned on the phone? The first 2 keys are line button that the phones needs so the first Shared parking button should be displayed on the 3rd key.
Also make sure that you have the same shared parking buttons provisioned on the all phones.

 

[lneblett]

Yannish -

You do realize that 1.0.9.102 was pulled by Grandstream a couple of weeks ago? There were issues with it to the extent that it is no longer available on their website and they now show 1.0.9.69 to be their current release, with 1.0.9.108 as a Beta. Granted, I understand that the releases for 3CX may be different than that for GA, but you may wish to check for the firmware download site to confirm and then read the forum issues reported. I know that I had two sites who elected to upgrade phone firmware on their own and I ended up having to regress. However, they were not on 3CX so perhaps it was something specifically related to their PBX when used with GS phones running same.

 

[craigreilly]

Knock on wood - so far so good. The 488 error reported by Grandstream supposedly affects Broadsoft customers only.

Fixed Device responds with 488 when incoming INVITE contains 2 m lines on RTP and SRTP causing calls to fail with BroadSoft SBC

 

[lneblett]

AFAIK, none of my providers are Broadsoft based and the traces I had gave no such indication. If such is the case, then I also assume the possibility that other providers may provide similar SDP attributes. Additionally, as the phone is negotiating with the PBX and not the provider directly, the provider and/or SBC would not be seen by the phone unless the phones are remote. The below has indications of the issue - direct to an Asterisk server and the other from extension to extension using a GS PBX.

https://forums.grandstream.com/t/warning-304-gs-media-type-not-available-firmware-1-0-9-102/32045/5
https://forums.grandstream.com/t/488-bearer-capibility-not-available/32281/6

They have a BETA for the phones and following is the reported bug fix -
BUG FIX
 Fixed Phone responds 488 to INVITE incorrectly
 Fixed Device LCD displayed black screen in upgrade process until entering boot up status
 Fixed DHCP Vlan worked abnormally
 Fixed BLF cannot be provisioned successfully for 3CX
 Fixed Device crashed if unregistered account switched "Authentic Incoming INVITE" then received incoming call

As you can see, they admitted to an issue, but not as specific as you supplied from them. I suppose that what they indicated was what they knew at the time, but perhaps not the entire scope. I also was not aware of a 3CX BLF issue as I have not encountered this as of yet, but I am not risking it and staying on the .71 release until things settle down. Love the phones, but GS firmware regression testing is lacking,

 

[earthwing]

My GS2130 issues got resolved with a firmware update on the customers router/NAT on a never heard of device brand. So for me we are good. GS firmware latest version for 3CX is not an issue

 

[YiannisH_3CX]

Glad to hear the issue has been resolved and thank you for updating the thread with your solution.