Custom Query (2195 matches)

Currently all media transports are pre-created in PJSUA-LIB according to the number of maximum calls to be supported. This decision was made to speed up call setup time and to simplify call state logic.

But there are few drawbacks with this approach:

1. it requires STUN and TURN transport to be kept-alive, which means it needs to send periodic keep-alive packets, and this is not good for battery consumption in mobile devices.
2. it requires TURN long-term allocation, which will fail if the NAT/mapped public IP address mapping has changed.
3. even when TURN is not used it may still fail when normal UDP media transport (i.e. not ICE) is used and the IP address (STUN or not) changes.
4. it allocates a lot of resources when the number of max_calls is large.

Because of these drawbacks, it's better to create the media transport on demand when a call is set up. To speed up call setup, we may employ caching mechanism where a transport is kept-alive for few seconds and may be reused for subsequent calls. And for flexibility, add a new callback to enable application to create a custom transport for a particular call.

Other benefits of creating transports dynamically are:

1. allow different accounts to use different media settings (e.g. ICE, IPv6, etc.)
2. dual stack media (to create IPv4 or IPv6 media transport depending on the transport type in the incoming call)

This is duplicate of ticket #665