We seem to be encountering some strange results using native directed call pickup with TCP transport.
Using UC Software Version 184.108.40.20648 on VVX400.
I have confirmed that the same handset registered to the same custom kamailio/asterisk stack performs a directed call pickup as expected using a Replaces header in the INVITE using UDPonly transport.
I have also confirmed other brands/models of handset are also capable of performing directed call pickup with a Replaces header on the same server with both UDP and TCP transport.
Are there any other relevant settings for the Polycom when switching from UDP to TCP transport that could affect this?
Relevant settings to call pickup configured are:
feature.directedCallPickup.enabled="1" call.directedCallPickupMethod="native" call.directedCallPickupString=""
Inbound and outbound calls also work fine with both transport types.
Apologies if this was asked before but I can't see anyone else having this specific issue.
welcome to the Polycom Community.
Nothing different between UDP/TCP so most likely you found a bug. We would need some additional details from you which we cannot handle via the medium of a community forum.
In order to raise a support ticket you need to work with your Polycom reseller as they need to do this for you.
End Customers are unable to open a ticket directly with Polycom support.
If this is some sort of an Internet discounter providing your MAC address or your Polycom devices serial will enable us to look up who would be able to support you. This may not be who you purchased the Polycom device from.
If the unit is no longer within warranty please be prepared to Pay Per Incident / PPI. This is all outlined in detail here
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Polycom Global Services