This is a bit different though. The idea is that both parties should see the same authentication string and then verify verbally what that is.
Say they see "123" so Alice say "I have 123 as my SAS code, what do you have?". And "Bob says, yap I have 123 as well". If Eve is in the middle then she would show "123" to Alice but maybe "456" to Bob. She would have to fake Alice's voice and tell Bob the code is "456" and it's ok. Then to Alice in Bob's voice that the code is "123" and it's ok. All in such a way that Alice and Bob don't suspect anything (has to be realtime too).
So this kind of software might make that easier.
The way to bypass that is to use dictionary words instead of numbers but then also refer to them further in the conversation. (see silly example in a sister comment about it).
Alice sees "pink elephant salad" and Bob sees "piano lamps". They say the words, Eve has to reply in Alice's voice to Bob with "piano lamps" and then respond to Alice with "ping elephant salad".
However then Alice makes a joke wondering if elephants like to eat pink salad. Bob will wonder as perhaps he wanted to remark how so few people play pianos these days. So Eve has a bit of a harder job if say instead it was just "1234" vs "5678" being said.
Specifically this is relevant for ZRTP protocol. There is a voice-based verification step which relies on knowing and recognizing the other party's voice and then verifying a short authentication string they see on their screen. Being able to mimic can lead to ability to conduct a man-in-the-middle attack.
To counter-act the strategy is to use dictionary words instead of just numbers for verification, say "pink salad elephant" instead of "1934" so then parties would maybe have a joke or say something referring to the ridiculous word combination combination. That would be harder to mimic.