Solved Attended transfer not working in DECT phones in only 1 3cx client

[GueZ]

Hello,

I have a strange bug with a instance of 3cx, since some weeks ago the attended transfer in dect phones is not working.

1 - Same server non dect phones work fine

2 - With other brand dect station/phones same problem not working

3 - Tested at our own server and other clients servers and dects work

4 - Rebooted 3cx Services + Vm same problem

5 - Last solution if i do not get an answer in the forums is to make a brand new installation in new VW

 

[JohnS_3CX]

Please provide some more info as per below
https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[AWS2P]

Hi,
why not starting here
https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Which DECT brand and model are you speaking about?

 

[GueZ]

Sorry but i did not putted that information because is non sense because:

• 3CX Version, Same versions for all servers even for those who work (16.0.507)
• Server OS, Same versions for all servers even for those who work (Debian latest version)
• Is the 3CX Server Hosted and where? Same hosting for all servers even for those who work (Our own VM in our Own Datacenter)
• IP Phone Make/Model/Firmware Same versions for all servers even for those who work (Tested with RTX and Gigaset latest versions)
• Provisioning Method: Local / VPN / STUN / SBC Same versions for all servers even for those who work (Local)
• Trunk Provider or Gateway Make/Model Same versions for all servers even for those who work (Winet CH)
• Has the Firewall Checker passed: Same versions for all servers even for those who work (YES)
• Are custom Phone Templates being used: Same versions for all servers even for those who work (NO)

To resume with the devices that not work in this specific client they work in others clients (same server/configuration/devices versions)

So i've posted before trying to make a full new install in new VM and brand new configuration (equal to existant) to see if any one has an idea of this very strange issue =( if in all others clients it works.....

Thanks
Best regards

 

[JohnS_3CX]

Rather than sharing all the general information above, be very very specific. Share the info of that one system you mentioned and lets troubleshoot only that one.

So share the information as per the instructions above and include a specific model and firmware and also kindly tell us how you are performing the attended transfer (step by step) so we can better understand.

 

[AWS2P]

IP Phone Make/Model/Firmware Same versions for all servers even for those who work (Tested with RTX and Gigaset latest versions)

You don't give us details on models, firmware.
Pasting everywhere : Same versions for all servers even for those who work , this doesn't help a lot

If you prefer doing a reinstall , do it and ask nothing on forum

 

[GueZ]

• CX Version, (16.0.507)
• 
  
• Server OS, (Debian GNU/Linux 9 (64-bit))
• 
  
• Is the 3CX Server Hosted and where? (Our own VMware in our Own Datacenter)
• 
  
• IP Phone Make/Model/Firmware (Client has RTX 2x IPDECT 8660(v.04.50/B0010) + 7 8630(v.450.10) + 2 8830(v.450.10) ) To troubleshoot of maybe RTX problem tested also with:
• Gigaset n670 (v.2.26.0) + 2 s650h Pro (v.74.04) and also try the Gigaset in other clients servers and it works in others clients with no problem.
• 
  
• Provisioning Method: Local / VPN / STUN / SBC (Local)
• 
  
• Trunk Provider or Gateway Make/Model (Winet CH)
• 
  
• Has the Firewall Checker passed: (YES)
• 
  
• Are custom Phone Templates being used: (NO) at least in dect phones

We did not changed anything in configuration since the time the client has this issue

For me it makes non sense of all this info, but i agree with you that to help me you need specific information.

Thanks guys

 

[JohnS_3CX]

Hi @GueZ

Thanks, it does make a lot of sense actually. For starters, we must ignore the RTX devices - they are not officially supported so they introduce an an unknown variable because we don't test them.

Lets go ahead fully with the Gigaset that we know is tested to be working. We will need 3 extensions on the problematic PBX server:

1) Make two new users tha will log on their webclients
2) Make one new user and provision them on the Gigaset (factory reset base station first - we need a clean slate to eliminate any other factors)
2) Webclient A must call Webclient B, and B will make an attended transfer to Gigaset extension.

Please test the above scenario, and tell us if the internal attended transfers work.

 

[GueZ]

Hey @JohnS_3CX.

Sorry for the late reply but i was waiting to see if the problem produces again.

So when I've created the new extensions and it was working with no problem.
When i've tested the extensions with the problem it was working fine again =/
I did not touch anything in the actual extensions only created the new ones to test and erase them again.

I really do not understand but in this client server i wall have one time strange issue that was resolved only changing one setting and putted back again.

So i think in the future since this is only the client server with ghost issues i will do a full clean installation.


Another question if you are able to answer me

We have an Entreprise Licence, and i'm not able to get the Jabra Headset to work with the touch for answer call's. I have the Jabra extension in Chrome but i have no options on it.



Do you have a solution? Because in 3cx forum i've found that in free version only sennheiser are compatible but in other versions Jabra is also compatible?



Thanls

Best Regards

 

[JohnS_3CX]

Hi @GueZ

Glad to hear about the results. As for Jabra, it will not work in the webclient at the moment. The solution is for Jabra to update their own drivers. Take a look here: https://www.3cx.com/community/threa...n-a-chrome-extension.69292/page-4#post-308874