GRANDSTREAM GXP-2000

[darrellchapman]

We've found the Grandstream phones with the latest firmware (1.1.6.16) to be the most stable yet (of all the Grandstream firmwares). Yes, we occasionally have dropped calls but no more freeze ups. BLF works great on all models (GXP-2000, 2010, and 2020)

 

[scottyork]

Darrell,

Can you confirm which Firmware you're using to get Intercom on GXP-2000. I've stuck with 1.1.6.16 for our mixed 2000 and 2010 environment because it seems stable. Intercom does not work on v.6 with that firmware as far as I can tell but if I read your posts right, I must be missing something 'cos I think that's what you're on.

However, the BLF operation is unreliable on 1.1.6.16 (but at least BLF doesn't crash the phone like some earlier firmwares!) and sometimes some lines get stuck on RED for a while. Are you finding your version stable? Does BLF work properly on it?

Archie, will your Snom fix also fix BLF for Grandstreams do you think?

 

[darrellchapman]

Intercom does indeed work on the GXP-2000 with v1.1.6.16 of the firmware. Can you explain in more detail as to what your issue is (just to make sure we're on the same page?)

BLF is working pretty well on my phone. I use the GXP-2020 and I'm one of only a handful of people that actually have BLF programmed. Most users said they prefer the 3CX Client to see each extension's status (which is understandable). Also, all of our phones are on 1.1.6.16.

Now as to whether the status is accurate is a different story. I can see people's line ringing (blinking red) and see when they are on the phone (solid red), but I haven't actually compared this status to the 3CX server line status. As it turns out, I thought my 3CX client was giving correct status, but it is not as I never actually compared it against the 3CX server status.

 

[scottyork]

Hi Darrell

I'll have a play with intercom. I tried it briefly but not exhaustively. It's not a feature we'd use much.

As to BLFs, we use them in preference to VOIP client because:-

1. VOIP client seems a little flaky at the moment - with slightly unreliable TAPI operation with Outlook.
2. It has a driver conflict with our digital dictation system (personally I'd like to see a stripped-out version without the VOIP stuff akin to the original Call Assistant), and
3. to ease user migration from an existing Panasonic key system.

We have about 30 phones. Mostly GXP-2000. I'm gradually (over the last couple of weeks) rolling out GXP-2010s to the people who answer our main phone number because of the 18 keys (15 of which are configured as BLFs). The plan was to use 2010s to allow call status to be seen easily and also easier
attended transfer.

What I'm seeing is the following (on 2000 and 2010 phones).

The BLFs gradually light up after a phone re-boot as extensions are used which I assume is expected operation. Any re-start of server services requires a re-boot of the phone to get BLF going again.

Sometimes a red BLF (call in progress) does not clear when a call has cleared so the relevant lamp stays red. It usually sorts itself out again when the relevant extension is used again. Unfortunately this is just what we don't want because our reception operation now thinks someone is busy when they're not (a large part of the reason for us to use BLFs!)

I've attached a couple of images to show the problem. Nobody on the phone but plenty of red lights... :cry:

Andy

 

[scottyork]

Re: GRANDSTREAM GXP-2000 Intercom

Darrell,

Could you let me know how you got Intercom to work on a GXP-2000.

Just tried and failed. Standard *9 code conflicts with built in forwarding codes on phone. Changed it to *5 on 3CX which doesn't seem to conflict. It rings the phone with a strange ring cadence and then eventually goes to voicemail. Looks like I need a few helpful hints!

Got it - hadn't got auto answer turned on in account settings - works beautifully - also see I can turn phone *9 local codes off as well.

Andy

 

[darrellchapman]

Make sure you also change "Turn off speaker on remote disconnect" otherwise the remote phone will stay on the line when the caller hangs up and then get error or busy tones.

I'm glad you got it working. Can you tell me how to turn off *9 feature codes on the phone? I don't see that option anywhere and it would greatly simplify the intercom/paging setup.

Thanks for your help.

 

[nb]

All I can say is the following

We have 10 grandstreams in a bag in backoffice which are faulty - All GXP2000. And we have another 4 Budgetone.

So in a period of a year, snoms have all been running fine, Aastra's too. Polycom did fine with firmware updates. Linksys is good, Cisco solid as a rock - Nothing ever failed except GXP2000. At least the 2020 2010 dont look that bad - they are nice and work - however there is always a big IF.

Only Grandstream. Do you understand why we say they are not recommended? I must say that the 1.1.6.16 is a good release and much stable.

Id prefer a Linksys a 100 times more than a phone. And the new SPA 962/x with the 932 Sidecar is very nice. Nicest display till now. For a receptionist it is No1. The upcoming version of 3CX supports BLF on the Linksys sidecar and improved BLF on snom and aastra with sidecar too.

Thank you Archie, other phone without issue? AASTRA 55i? and DECT phone without problems with 3cx?

Aastra 55i and DECT work perfectly. Dect is cool I must say. First step with the 55i is upgrade to latest firmware remember. Making even 1 or 2 transfers with the 51i and 55i will cause them to freeze. So Upgrade firmware - and they will work like a charm.

 

[scottyork]

Hi Darrell,

Star codes are disabled by setting "Enable Call Features: " to no. It' a setting about half way down each Account tab (at least on 2000 and 2010 models). The note says "if yes, call features using star codes will be supported locally".

The DND button still seems to work and it disabled the *9 codes I tried but I haven't done an exhaustive check with that setting.

Andy

 

[scottyork]

We have 10 grandstreams in a bag in backoffice which are faulty - All GXP2000. And we have another 4 Budgetone.

Sounds like you've been very unlucky with those. We have about 25 GXP-2000. One was DOA and one has it's web interface locked out (but that may have been my fault - it was the first one I played with ) The others have been running fine for over a year.

We run them all on PoE so perhaps some issues with others are power supply related - just a thought?

Having said that, if we had the budget at the time, we would have gone with Snom not least because the build quality appears much better than the GXP-2000. However the new GXP-2010s are very nice and a big step forward in build quality. Can't comment on the 2020s because I haven't seen one in the flesh.

 

[darrellchapman]

Thanks Andy.

 

[scottyork]

BLF seems finally to work really nicely with Grandstreams on latest 3CX version. (.806)

Now have stable and fully functional Grandstreams (2000 & 2010).

 

[silentfun]

BLF seems finally to work really nicely with Grandstreams on latest 3CX version. (.806)

Now have stable and fully functional Grandstreams (2000 & 2010).

- i have .806 deploid and have not checked it jet if it is ok now but i will check that now.

i realy hope you are right

andy

 

[silentfun]

the former problem was 50% false status but most important was the that the lights was frozen after some hours or a day.

but i haven´t checked it out yesterday because i was r4unning out of time - but shure today in the evening i will get it.

Andy

 

[silentfun]

late replay but there is not much time atm.

good news - they don´t freez now

bad news - they don´t work - not just a single second so there is no time to freeze :lol:

i hope i made a mistake - can you give me your config to help me where my config is false??

some weeks ago i have had the phone server in a datacenter - but after they kicked my ass for postgress eating their CPU Time i got it back to local - possible i changed something in that way that prevent BLF now.

Dokumentation on Grandstream is outdated for latest firmware btw

unlucky Andy

 

[craigw]

I am rather new to this whole VoIP thing.

We have 30 phones. One is a Aastra 480i CT. The intercom and paging features work wonderfully on that phone. The rest of the phones are Grandstream GXP-2000 phones. I can't seem to get paging and intercom to work on those phones. For example when I try to do an intercom (ex. *9344), no matter how fast or slow I enter the numbers, it acts like it doesn't pickup the first three numbers I enter. So if I let it go through with just two numbers, it fails because that is an invalid extension number in my setup.

I have followed the instructions on the 3CX website for setting up the intercom/page feature on the GXP-2000 phones. Could someone give me further instructions on how to get this working, please?

Thanks,

Craig

 

[Philco]

Craig, as a matter of interest, *93 is a star command in the grandstream, and is used to cancel call forwarding..


Do you think you may have a conflict here.

Phil

 

[galal202]

I Have grandstream 2000,2020 and they are works well with 3cx and I can page them
so I think you have in your grandstream dial plan something restrict *9

 

[SWB]

We use Grandstream 2000 in the office here. They work fine, and I guess I really don't have any issues with them in the office (outside connecting in different story).

Craig: Make sure you disabled the Grandstream star codes. In the Account tab, Enable Call Features - set to No. Update and Reboot.

 

[craigw]

*93 is a star command in the grandstream, and is used to cancel call forwarding.

Do you think you may have a conflict here.

Thanks for that tip Phil, that is what I needed to hear. I went into the 3CX server and changed the number for paging and intercom from "9" to "8" and rebooted the server. Now it works like a charm.

Craig

 

[craigw]

Make sure you disabled the Grandstream star codes. In the Account tab, Enable Call Features - set to No. Update and Reboot.

A question for you, SWB: If I set Enable Call Features to No does that disable all the * features on the Grandstream phone? If it does that is not what I want because in our environment we use the *72 and *73 regularly.

Craig