Yes, it's in scope. There's actually a pretty thorough and explicit guide from the PCI Security Standards Council (the DSS people) to your exact question here:
Information Supplement: Protecting Telephone-based Payment Card Data
Which makes reasonably clear statements like this about card numbers:
Call centers will need to ensure that PAN data is rendered unreadable
(for example, encrypted using strong cryptography) when stored.
This is part of PCI DSS Requirement 3.4 and includes ensuring PANs
stored within the QA/recording and CRM solutions are encrypted using
strong cryptography, or are otherwise rendered unreadable.
and this about CVV:
It is a violation of PCI DSS Requirement 3.2 to store any sensitive
authentication data, including card validation codes and values, after
authorization even if encrypted.
It is therefore prohibited to use any
form of digital audio recording (using formats such as WAV, MP3, etc.)
for storing CAV2, CVC2, CVV2 or CID codes after authorization if that
data can be queried; recognizing that multiple tools exist that
potentially could query a variety of digital recordings.
...and it goes into all the other ways call centers and recordings are impacted (e.g., network encryption, authentication and authorization, etc. etc.)