We make a use case describe a user's interaction with the system. So the flows usually come out with the user and system taking turns:
* User lifts handset off hook
* Phone plays dial tone
* User hits a button
* Phone does what ...
* etc.
Does that answer the right question?
This quickly gets trickier than you think. I googled for "telephone state transition diagram" and found the following picture. I wouldn't try to express the following rules in any other format. That is, a use case flow is not the way to talk about phone numbers beyond "user enters a valid phone number".
This isn't really a phone handset scenario ... we don't enter the "hyphens".
[ June 10, 2006: Message edited by: Stan James ]