• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Solved 3cx V15.5 sp6, grandstream gxp21xx random failures

Status
Not open for further replies.

hanstps

Free User
Joined
Feb 6, 2018
Messages
26
Reaction score
10
Hi,

First let me explain the configuration at the client site :
3cx server with the latest update V15.5 sp6
8 grandstream gxp2160 phones with firmware 1.0.9.102, the latest.
1 Gigaset N510 ip pro base station
4 gigaset R650H portables connected to the N510.
5 of the gxp21060 are in group '80'.

To be sure all gxp2160 phones did undergo a factory reset and a new provisioning.

Since we updated to V15.5/sp6 we have the following RANDOM problems with the grandstream gxp21xx phones.

On a incoming call, the 1st line led is blinking.
When someone lifts off the handset, the line led stop blinking and normally the connection should be established. But from time to time, i guess 2 on 10 times, the user gets a 'new line' tone in place of the connection with the caller. And sometimes the user gets the busy tone and as before no connection with the caller.

This happens on all gxp2160 phones. This happens on internal calls and also on external calls.
Same problem when a internal call is placed from a portable Gigaset to a gxp2160.

It even happened that a phone completely lockup, display still active but no reaction on any key.
We had to hard reboot the phone.
I stayed 3/4 of a day at the client site to observe the problems and i have seen these problems myself.

Below you find a piece of the log of a failed connection and a 2nd that established a connection correctly.
For one reason or another we get a sip '488 Not Acceptable Here/INVITE from 192.168.1.28:5060' error when we lift off the handset. As already mentionned, this happens random 2 times on 10.

Could this be a bug in the latest firmware.
Anyone an idea ????????????

Bye,
Hans

Connection that FAILED :
----------------------------------
Code:
09/21/2018 2:39:41 PM - Leg L:95.2[Extn:13] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.1.62:50166
09/21/2018 2:39:41 PM - [CM503003]: Call(C:95): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.62:50166
09/21/2018 2:39:41 PM - [CM503008]: Call(C:95): Call is terminated
09/21/2018 2:39:41 PM - Leg L:95.1[Extn:23] is terminated: Cause: CANCEL from 192.168.1.11:5060
09/21/2018 2:39:40 PM - Currently active calls - 2: [90,95]
09/21/2018 2:39:35 PM - Leg L:95.3[Extn:13] is terminated: Cause: 488 Not Acceptable Here/INVITE from 192.168.1.28:5060
09/21/2018 2:39:35 PM - Call to T:Extn:13@[Dev:sip:[email protected]:50166;rinstance=0-f990ddf492514105be29f37640978ff7;ob,Dev:sip:[email protected]:5060] from L:95.1[Extn:23] failed, cause: Cause: 488 Not Acceptable Here/INVITE from 192.168.1.28:5060
09/21/2018 2:39:35 PM - [CM503003]: Call(C:95): Call to <sip:[email protected]:5060> has failed; Cause: 488 Not Acceptable Here/INVITE from 192.168.1.28:5060
09/21/2018 2:39:34 PM - [CM505001]: Endpoint Extn:13: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXP2160 1.0.9.102 000b8262d7c4] PBX contact: [sip:[email protected]:5060]
09/21/2018 2:39:34 PM - [CM503002]: Call(C:95): Alerting Extn:13 by contact <sip:[email protected]:5060>

Connection established and terminated by the caller :
-----------------------------------------------------------------------
Code:
09/21/2018 2:43:53 PM - Leg L:98.1[Extn:23] is terminated: Cause: BYE from local
09/21/2018 2:43:53 PM - [CM503008]: Call(C:98): Call is terminated
09/21/2018 2:43:53 PM - Leg L:98.3[Extn:13] is terminated: Cause: BYE from 192.168.1.28:5060
09/21/2018 2:43:50 PM - Leg L:98.2[Extn:13] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.1.62:50166
09/21/2018 2:43:50 PM - [CM503003]: Call(C:98): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.62:50166
09/21/2018 2:43:50 PM - [CM503007]: Call(C:98): Extn:13 has joined, contact <sip:[email protected]:5060>
09/21/2018 2:43:50 PM - [CM503007]: Call(C:98): Extn:23 has joined, contact <sip:[email protected]:5060>
09/21/2018 2:43:50 PM - L:98.3[Extn:13] has joined to L:98.1[Extn:23]
09/21/2018 2:43:49 PM - [CM505001]: Endpoint Extn:13: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXP2160 1.0.9.102 000b8262d7c4] PBX contact: [sip:[email protected]:5060]
09/21/2018 2:43:49 PM - [CM503002]: Call(C:98): Alerting Extn:13 by contact <sip:[email protected]:5060>
 
Hi,

i justed checked the grandstream site for new firmware.
There are is a new one, 1.0.9.108.
They fixed the following errors for 3cx :
- Fixed Phone responds 488 to INVITE incorrectly
- Fixed BLF cannot be provisioned successfully for 3CX

I think this version should solve my problem.

Can anyone from 3CX tell me it this firmware is already tested and save to install.
It does not yet appear in the 'update' menu.

Thanks,
hans
 
  • Like
Reactions: HRMNY
Hi,

i justed checked the grandstream site for new firmware.
There are is a new one, 1.0.9.108.
They fixed the following errors for 3cx :
- Fixed Phone responds 488 to INVITE incorrectly
- Fixed BLF cannot be provisioned successfully for 3CX

I think this version should solve my problem.

Can anyone from 3CX tell me it this firmware is already tested and save to install.
It does not yet appear in the 'update' menu.

Thanks,
hans

Hello Hanstps,

We cannot advise if is okay to use the new firmware . Currently, firmware version 1.0.9.108 is undergoing testing on our end. Once the testing is done you will see it as an update in the management console which can then be applied to the devices.
 
So since the 'tested' firmware isn't working I'd upgrade the phones to .108 . You are already having issues so no sense in waiting.
 
Hi,

For your information.
we forced the upgrade of all gxp2160 phones to version 108.
No problems found and the problems mentionned above (error 488 and blf button not updated) are no longer present.
It seems to work.

Bye,
Hans
 
  • Like
Reactions: HRMNY
I had to update a customer to the .108 firmware due to the 488 issue, I was about to start pack capturing when I saw this thread, as I had recently also reset a 2160 to factory and provisioned it to our demo system which I couldn't figure out why the BLF wasn't working. I'll be honest, in testing 3CX should have found the BLF issue quite fast, the 488 seems a bit random, we have one user at our office with a 2130 and not having the issue with .102 I won't be rolling that firmware out though to any other customer after dealing with the 488 issue with one was enough.
 
  • Like
Reactions: HRMNY
Status
Not open for further replies.
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.