... ObjectInputStream.¹

All packets exchanged by ITX peers are SigPackets, which are serialized to and from object streams. InvitePacket is a subclass of SigPacket.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... InvitePacket²

that is, mySP.isInvitePacket() is true

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... myConnectionList.)³

As of July 27, 1999 these methods are synchronized to remove a race condition among multiple non-blocking dial operations.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... startKeepAlive().⁴

Note that hangups are a function of the DesktopSignaling, and not of the SignalConnection.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...Caller⁵

The caller is the DesktopSignaling on which the Dial() method was first invoked. The callee is the DesktopSignaling belonging the the Gateway or other ITX application, depending on which Location of the target is being contacted.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... period.⁶

For example, if the caller is on a computer which has no audio devices, then the caller's DesktopSignaling will reject the invite and then call its application's onAbortCall handler.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... myConnectionList.⁷

The exception is abortCall() which simply marks the SignalConnection IDLE.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... peer⁸

For non-blocking Dial()s, it is a DialThread that calls the method but that is only a detail.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.