SYSTEMS AND METHODS FOR BRIDGED AUDIO CONFERENCING WITH SELECTIVE AUDIO STREAM CONFIGURATION
Systems and methods are disclosed for bridging SIP calls in conference environments that include both SIP and TDM legs. A request to bridge a SIP call from a specific conference number is received, and the system configures caller and called IDs for the bridged call. Audio is selectively sourced from all primary SIP legs excluding dynamic legs, all sequence SIP legs excluding dynamic legs, or a mixed audio stream including dynamic legs. The bridged call is established using either a default SIP trunk configured in a node or a unique SIP trunk if no default is set. The system supports mixed-protocol integration, continuous connection attempts, automatic reconnection, RTP/RTCP timeout protection, and high availability with node failover. Additional features include codec configuration via SDP, support for multiple simultaneous bridged calls, on-demand call drop, and a user portal for managing bridging services. Bridging does not disrupt ongoing conferences or original configurations.
1 . A method for bridging a SIP call from a specific conference number in an audio bridge system, comprising:
receiving a request to bridge a SIP call from a specific conference number;
configuring caller and called ID for the bridged call;
selecting audio from either all primary SIP legs excluding dynamic legs, or all sequence SIP legs excluding dynamic legs, or mixed audio of all primary and sequence SIP legs including dynamic legs; and
establishing the bridged call using a default SIP trunk configured in a node, or selecting a unique SIP trunk if no default is configured.
2 . The method of claim 1 , wherein the conference includes SIP legs, further comprising:
including SIP audio in the mixed audio of the bridged call; and
including only audio of the SIP legs in the bridged calls at an A-end and a B-end.
3 . The method of claim 1 , wherein the conference includes TDM legs, further comprising:
including TDM audio in the mixed audio of the bridged call; and
including only audio of the SIP legs in the bridged calls at an A-end and a B-end.
4 . The method of claim 1 , wherein the bridged calls can be triggered simultaneously for the same conference.
5 . The method of claim 1 , wherein the bridged calls are triggered only if there is at least one participant leg connected, and the type of bridged call is determined based on the type of connected leg.
6 . The method of claim 1 , wherein the bridged calls continuously try to connect if not established within a specified time period.
7 . The method of claim 1 , wherein the bridged calls automatically reconnect in case of disconnection.
8 . The method of claim 1 , wherein the bridged calls do not disconnect on RTP/RTCP timeout.
9 . The method of claim 1 , wherein the bridged calls are established in the secondary nodes of a high availability pair if the primary node fails.
10 . The method of claim 1 , wherein the bridged calls can be dropped separately on demand.
11 . The method of claim 1 , wherein the SDP of the bridged call includes all the codecs configured in a bridge where it is triggered.
12 . The method of claim 1 , wherein bridging a call does not impact conferences, calls, or original configuration.
13 . The method of claim 1 , wherein the bridged call feature is available on all nodes in production.
14 . A bridge system comprising:
a processor configured to execute instructions for bridging a SIP call from a specific conference number based on configurable caller and called ID, and selecting audio from either all primary SIP legs excluding dynamic legs, or all sequence SIP legs excluding dynamic legs, or mixed audio of all primary and sequence SIP legs including dynamic legs;
a memory coupled to the processor, the memory storing instructions and data for executing the bridging of the SIP call; and
a network interface configured to receive the request for bridging the SIP call and establish the bridged call using a default SIP Trunk configured in a node or selecting a unique SIP Trunk if no default is configured.
15 . A non-transitory computer-readable storage medium storing instructions for bridging a SIP call from a specific conference number in an audio bridge system, the instructions, when executed by a processor, cause the processor to perform the steps of:
receiving a request to bridge a SIP call from a specific conference number;
configuring caller and called ID for the bridged call;
selecting audio from either all primary SIP legs excluding dynamic legs, or all sequence SIP legs excluding dynamic legs, or mixed audio of all primary and sequence SIP legs including dynamic legs; and
establishing the bridged call using a default SIP Trunk configured in a node, or selecting a unique SIP trunk if no default is configured.