import "zapISipFlow.idl";
Flow objects are managed by the the transport layer, see zapISipTransport.
Clients can add monitor callbacks to flows to observe the connectivity status and keep alive a connection through NAT.
Public Member Functions | |
| void | addFlowMonitor (in zapISipFlowMonitor monitor, in unsigned short type) |
| void | removeFlowMonitor (in zapISipFlowMonitor monitor) |
Public Attributes | |
| readonly attribute ACString | localAddress |
| IP address of local endpoint. | |
| readonly attribute unsigned short | localPort |
| Port of local endpoint. | |
| readonly attribute ACString | remoteAddress |
| IP address of remote endpoint. | |
| readonly attribute unsigned short | remotePort |
| Port of remote endpoint. | |
| readonly attribute ACString | transportProtocol |
| Transport protocol to remote endpoint (udp, tcp, . | |
| readonly attribute zapISipConnection | connection |
| Connection object of the flow (null for connection-less protocols). | |
| const unsigned short | IETF_SIP_OUTBOUND_01_MONITOR = 0x0001 |
| Monitor the flow using periodic STUN binding requests as specified in draft-ietf-sip-outbound-01. | |
| const unsigned short | OPTIONS_MONITOR = 0x0002 |
| Monitor the flow by sending periodic OPTIONS requests. | |
|
||||||||||||
|
|
|
|
|
|
|
Connection object of the flow (null for connection-less protocols).
|
|
|
Monitor the flow using periodic STUN binding requests as specified in draft-ietf-sip-outbound-01.
|
|
|
IP address of local endpoint.
|
|
|
Port of local endpoint.
|
|
|
Monitor the flow by sending periodic OPTIONS requests. OPTIONS monitoring will only be available if the transport layer has been initialized with a zapISipUAStack. See zapISipTransport::UAStack |
|
|
IP address of remote endpoint.
|
|
|
Port of remote endpoint.
|
|
|
Transport protocol to remote endpoint (udp, tcp, . ..) |
1.4.4