The standard (interface) configuration commands to enable AutoQoS are: auto qos voip. Depending on the platform, AutoQoS VoIP can support the following additional keyword commands:
cisco-phone—When you enter the auto qos voip cisco-phone interface configuration command on a port at the edge of a network that is connected to a Cisco IP Phone, the switch enables the conditional-trusted boundary feature. The switch uses the Cisco Discovery Protocol (CDP) to detect the presence or absence of a Cisco IP Phone. When a Cisco IP Phone is detected, the ingress classification on the interface is set to trust the CoS marking of the received packet. When a Cisco IP Phone is absent, the ingress classification is set to not trust the CoS (or DSCP) value of any packet.
cisco-softphone—When you enter the auto qos voip cisco-softphoneinterface configuration command on a port at the edge of the network that is connected to a device running the Cisco SoftPhone, the switch uses policing to decide whether a packet is in or out of profile and to specify the action on the packet. If the packet does not have a DSCP value of 24, 26, or 46 or is out of profile, the switch changes the DSCP value to 0.
So it looks like the cisco-phone variant works with CDP and the cisco-softphone variant just polices the call payload and signalling traffic to what is acceptable for a single call - it does not do any detection of whether the attached PC is running the IP communicator software. You should therefore just be able to use the cisco-softphone for all ports regardless of whether they are supporting a physical phone or softphone.
I would however be tempted not to trust the attached device at all and writea bespoke config rather than relying on auto-qos. The link below should get you started doing this.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.