PTT addressing is done via the phone's address book - exactly like on a cell phone's normal address book. It just shares the entry with the cell phone number. If you hit the call button, it calls them, and establishes a normal call. If you press PTT instead of call, then it "chirps" them - they just hear the single beep. So selection and addressing is done just as it would be for a normal call. If they are not there... then your PTT session dies... (I believe that there is a 10 second timeout on a PTT session... if no transmissions are made between the 2 phones, then the "call" dies.) nothing happens. You just won't get a response. And no, you do not have to be in their address book.
As I said: PTT is mandatory HALF duplex. You may only send to their phone; you cannot receieve from it. The remote user must be pressing their PTT key before anything on their end is sent to you.
As for PTTing between networks... it depends which networks you are talking about. You cannot currently bridge between vendor networks (Nextel may only speak to Nextel, etc). However, there are 'networks' defined in the geographical US... until about a month ago, you could not speak outside of your network. However, that was changed (as of July 15, I believe... I've done it so I know it's working).
I don't get it at all. IF they aren't going to answer the cell phone for some reason, why would they respond to that stupid beep?
They wouldn't. That's not the intended purpose. There are 2 different PTT modes: CHIRP and ALERT. If you are making a normal call, their phone would ring like normal... which indicates that you must speak with them... you are demanding attention, as the phone does not stop ringing until answered, times out, or forwards to VM or another line. PTT follows a similar, but not identical, approach. If you select someone to talk to, and hit the PTT key, then they are sent a chirp - that's the beep that you all seem to have associated with satan. It's just that single chirp. Nothing else happens. You are not demanding attention - simply requesting it. For example, I would chirp my boss if I thought there was a possibility he was in a meeting. That is less intrusive than repetitive ringing, or an Alert. An alert is like a call ringing... A high pitch beep is emitted from the phone for several minutes... it's on a pattern, like a ring, and it has a time out (5 minutes maybe?). After that, the alert signal mutes itself. When an alert is receieved, whether muted or audible, a window is displayed on the phone that says "Alert Received from #####: Clear/OK". That window does not disappear until the user manually presses clear; they have thus been notified of the call. A chirp does not do that. After the single chirp, the call has been logged to the phone log, but no notice of the event is presented to the user that it ever happened.
Any more questions?
Drew