Grandstream GRP2614 test report (version 1.0.0.26)


#1

Packaging

included all needed installation equipment (phone + stand, headset + cable, RG45 cable, power supply with long cable (very important), install guide.

Connecting the phone

took less than 1 minute

Agronomic Design –

Buttons layout is good with the most needed functions included as physical buttons. Pressing the buttons is soft, display is clear and includes needed information.

One remark – the speaker answer / dial button should be closer to the keypad and not on the other side of the phone.

Web security

Four consecutive user / password fails locked the GUI for 5 minutes (wait time can be cancelled using phone reboot).

Bluetooth

Connecting the 2614 to the mobile phone was easy.

Outgoing calls from the 2614 using Bluetooth were made without any problem.

Voice quality using Bluetooth is not so great (score of 6 from 10).

After Bluetooth connection was disconnected (getting out of the room) the connection was not auto connected when mobile (Samsung note 8) came back to range. Manual connection also failed

image

Only after 2614 reboot connection was established.

This incident can and go. Sometimes phone and mobile connected automatically and sometimes the 2614 had to reboot to establish the connection.

Factory reset seems to resolve issue – will be tracked.

Mobile phone contact dialing / sync with 2614 is not possible (although phone in handsfree mode)

Usage using Wi-Fi

For some reason the Wi-Fi connection takes precedence over the LAN connection – from my point of view should not be like that, LAN connection should be always preferred if one is available.

Phone recognized when I Disconnected the Wi-Fi signal and auto connected to the SSID when it came back up

Usage using cable

Works great like all Grandstream phones.

Fallback cable / Wi-Fi

Not supported

Working with Broadsoft BLF

Configuring the BLF event list under Account x β†’ SIP Settings β†’ Advanced Features generated a correct SUBSBRIBE message to the Broadsoft switch.

BUT

Then needs to manually configure each monitored station under Settings β†’ Programmable Keys that makes it a tidies process. Better suggestion is to auto configure the Programmable Keys (starting with Key#1) with the event list extensions (as done in AudioCodes phones). After that user can change the keys if needed.

Audio quality and priority

Audio quality very good (based on the used codec).

IP prioritization works as programmed under network -> Advanced settings

Remarks

  • No indication on phone screen when no network connection is available.
  • Accounts -> audio setting – you must define all 8 preferred vocoders, there is no option to define only part of them. Need to allow None option (workaround is to define the last codec that you want in all options below it)
  • LAN connection should take precedence over Wi-Fi connection.
  • The unit does not support the standard Dialplan structure (as defined in the Broadsoft application server) e.g. 0[01]x.[#T]|0[23489]xxxxxxx|0[57]xxxxxxxx|1[06]x so I had to build the whole dialplan from scratch .
  • Physical multi-purpose keys labeling is not available in other languages other than English (displayed as gibberish)
  • Can not change wallpaper design.

Overall very good phone (score of 8 from 10). Display is great and letters are when shown

Expedites customers activation time when customer has no LAN infrastructure in place.


#2

Hi,

Thanks for the feedback. We will evaluate the concerns addressed here.


#3

We checked 1.0.0.31 and it seems to prioritize the LAN connection.

Please setup the auto provision eventlist feature for Broadsoft:
image

We try on 1.0.0.31 and there is a warning when the LAN cable is removed and when the network is down.

Right out the box we are unable to support every type of dial plan so it needs to be configured as desired. For Broadsoft, the dial plan is provisioned using the device management templates.


#4

tested again with 31 and you are correct. the default is the LAN and when it becomes unavailable the phone is registering again with the WiFi IP address.
live calls are falling during this process.


#5

correct
when using the β€œAuto provision Events” option the BLF list is indeed populated automatically but it is populated on the Virtual Multi Purpose Keys and not on the Physical Multi Purpose Keys.
in order to populate it on the Physical Multi Purpose Keys. you need first to Lock the virtual multi purpose keys using the virtual multi purpose keys option and than activate the Auto provision Events option.
this will result in automatic BLF list populated onto the physical multi purpose keys.


#6

Another option is to set the Setting -> call feature -> Auto provision list starting point to MPK instead of the default VPK


#7

Hi,

Yes you can set whether the device should populate the VPK or MPK first as you noted. FYI, for your other concerns we will forward to development team to evaluate if it’s feasible.

Thanks