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

snom BLF somethimes keep blinking after other group member picked call

Status
Not open for further replies.

accesstech

Joined
Dec 7, 2015
Messages
20
Reaction score
7
Hello
We have 3CX 14 SP3 and Snom 725 FW 8.7.5.35 provisioniert von 3cx.
We have BLFs configured for each Extension of a ring Group (through 3cx Console Interface).

We have the problem the sometimes after somebody of the ring Group picked the call, on other people's phones one or two of the BLFs of the formerly blinking Group members keep on blinking, as if they were still getting a call. This is not the case all the time but only sometimes, and not always the same BLFs are affected.

The BLFs keep on blinking until we re-register the phone.

This miss-behavior confuses the users as they think the blinking extension is not picked up for a long time by their collegue in question. If the pick the call by pushing on the BLF buttom (to take this call over), they get a message on the snom's display that the calll is no longer existing.

On the Windows 3cx phone which is working in parallel in CTI mode, everthing Looks as it should.

If this is a SNOM Problem please Report to SNOM, If it is a known issue, please help.

Thanks a lot.

Urs Hiltebrand
 
Hello

By further analysing SIP traffic on the SNOM side, we see that this is a SNOM Problem. Notification about request terminated on line indicated on the BLF is recieved but somehow ignored by the SNOM (sometimes). We always get a terminated message for each recipient early state message.

We tried to install beta Firmware 8.7.5.44 manually on some phones. And the Problem goes away on these phones.

Two question remain: Did 3cx already test with the April Version (and can this be used with 3cx except known Problems listed by snom) ?

How can we get a Firmware Image manually into the Firmware provisioning structure under
%ProgramData%\3CX\Instance1\Data\Http\Interface\provisioning\qg4f60pcfd\Firmware and make the phone take the new one?

Thanks for any help.

Urs Hiltebrand
 
Hello
Sorry to come back so soon on this one. New Firmware seems improoves the Situation, but does not solve it completetly.
SNOM D725 with 3CX 14 SP3 now not only sometimes doese not Switch off blinking blfs of an answered but also it is not sure, that all BLFs that are ringing will be indicated as blinking on the different phone of the Group. Hardware BLFs do not make sense if the are not reliable... The more BLF are involved simultanously, the higher the liklyhood that some are not blinking at all or stay blinking when they should not.

:?: :?: :?: :?: :?:
 
Hello

I think I can now place a bug Report:
If you have 3cx 14 SP3 and have Push Service Option enabled to all extensions which are members of a a ring Group, and if members of this ring Group have 3cx Client installed on their smartphones (especially android), BLF can get disturbed after a Group call is ended by the caller or the call is picked by an Extension.
In this sitution BLF can continue to blink (indicating early state) on some Extensions till they reregister.
This missbehavior can also happen to Queues, and it is more likely to happen if the number of Group extensionsers are high or Groups are cascding.

We switched off the push 3cx client optioin temporarily and so far BLFs are working fine again.

Question: The you have a formal way of reporting bugs?

Regards

Urs Hiltebrand
 
Hello
Unfortuntelly switching off 3cx push did reduce the Problem but not solve it.

If an incoming call is cascading to a frist Group of Extensions, then after the don't take the call, going to a second Group and then is picked by a Group memeber or somebody else by taking over the call from a blinking BLF, on some phones some of the formler call Extension BLFs Keep blinking (early state). This is randomly and does not happen all times.
Besides this sip communicatioin is working is ok.

We are struggeling with this miss-behavior, reset and re-flash all Snom D725 phones did not help. Snom are provisionned by 3cx with Default 3cx templates....

Thanks for any hint.

Urs Hiltebrand
 
I read through your descriptions and I will ask the question that first came to mind directly as you seem to have already looked into this quite a bit.

From your analysis (I am assuming through capture files), is the 3CX Server sending the NOTIFY messages correctly to the phones and the phones are ignoring them, or are the NOTIFY messages not leaving the 3CX Server correctly in the first place?
 
Hi Nick
I attach two files:
- log of the 3cx Server of call 653
- siptrace of extension 619 (snom d725 involved in this call)
The case can be summarized as follows:
Call comes from 0412274127 to T:RingAll:688 Gruppe (611,613,620,621). nobody anwers. Call is transfered by rule to RingAll:688 to RingAll:680 : T:RingAll:680(611,613,616,619,620,621). Extension 619 takes the call. All group extensions notify 619 "request terminated"
->But BLF 613 and 611 are continuing to blink on 619 (and other phones of the Group)

If Groups are cascading (we have first a smaller Group, if nobody takes it from then call goes to a larger Group still including the Extension of the frist Group) there ssem to be issues with BLF early state indication. 3cx seems to send all Termination notifications correctly to the smons but non the less we have Problems that they don't work. Timing issues?????
 

Attachments

  • Protocol 3cx call 659enu.txt
    9.1 KB · Views: 11
  • SIP Trace snom ext 619enu.txt
    47.7 KB · Views: 12
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Forum statistics

Threads
141,630
Messages
748,955
Members
144,746
Latest member
gamingpro2131
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.