- Joined
- Sep 11, 2014
- Messages
- 13
- Reaction score
- 6
Hello,
to be honest, I make more or less 1 Post a year in technical forums.
But this one, it has to be mentionned because maybe someone had a similar issue, and it is not a question, it is an explannation with the resolution.
Client calls that every phone has ceased operation from today to now and even some lines are not active.
Grandstream GXP2160 with 1.0.9.127, latest 3CX certified Firmware, but on "old" 15.5 SP2.
Unable to press any button, BLF loaded but not changing color when someone is on the phone.
Means, you could touch any button and it had absolutely no impact on the phone.
First tought the PoE Switch - nope.
To speed the story up:
The only difference was that the non-working phone had no phonebook.
So - backed-up the 3CX company phonebook, deleted the 3CX company phonebook, factory reseted every phone and voilà - everythink was working fine.
The error was reproducable, I loaded phonebook from backup, made a reprovisioning an boom - ceased operation again.
Reverted back without phonebook and works now fine.
To be honest, I didn't had time to resolve if it was a special character or an overlenght field, but if you have such strange issue, ask first your client if and what they have added or changed into the phonebook.
But as usual - the answer was "we've done nothing".
It took me a couple of hours to find the resolution because it is such a strange behaviour.
I made a video because it was so unbelievable, but I cannot upload it to this forum due to upload limitations.
And just to address my opinion:
It is not 3CX's fault that the Grandstream Phones cannot handle this issue because the Softphones worked fine. In my opinion, the Grandstream Phones should have a sort of filter for e.g. "crop too long fields" or "reject unrecognized characters" or "skip bad data" instead of "process and play dead".
Regards,
Josip Meglaj - Logit Computer GmbH
to be honest, I make more or less 1 Post a year in technical forums.
But this one, it has to be mentionned because maybe someone had a similar issue, and it is not a question, it is an explannation with the resolution.
Client calls that every phone has ceased operation from today to now and even some lines are not active.
Grandstream GXP2160 with 1.0.9.127, latest 3CX certified Firmware, but on "old" 15.5 SP2.
Unable to press any button, BLF loaded but not changing color when someone is on the phone.
Means, you could touch any button and it had absolutely no impact on the phone.
First tought the PoE Switch - nope.
To speed the story up:
- Replaced PoE switch - no success
- Upgrade to SP3 / SP4 / SP5 / SP6 and at last, Upgrade to V.16 - no success
- normal Factory Reset was not possible because of ceased operation
- Factory Reset was possible when pressing button 1 and 9 during boot, then pound key - no success
- changed one phone to my 3CX Config, different Subnet - all OK --> Phones / Network are OK, must be a 3CX config issue
The only difference was that the non-working phone had no phonebook.
So - backed-up the 3CX company phonebook, deleted the 3CX company phonebook, factory reseted every phone and voilà - everythink was working fine.
The error was reproducable, I loaded phonebook from backup, made a reprovisioning an boom - ceased operation again.
Reverted back without phonebook and works now fine.
To be honest, I didn't had time to resolve if it was a special character or an overlenght field, but if you have such strange issue, ask first your client if and what they have added or changed into the phonebook.
But as usual - the answer was "we've done nothing".
It took me a couple of hours to find the resolution because it is such a strange behaviour.
I made a video because it was so unbelievable, but I cannot upload it to this forum due to upload limitations.
And just to address my opinion:
It is not 3CX's fault that the Grandstream Phones cannot handle this issue because the Softphones worked fine. In my opinion, the Grandstream Phones should have a sort of filter for e.g. "crop too long fields" or "reject unrecognized characters" or "skip bad data" instead of "process and play dead".
Regards,
Josip Meglaj - Logit Computer GmbH
Last edited: