Bridging Service: Difference between revisions

Latest revision as of 10:05, 20 July 2022

The "Bridging Service", which is also known as "CTBCAFBridge" was designed to bridge a call correctly, because, it is important to make the correct signaling and media operations. Detailed information can be found in the GRP_DOC_CALL_MANAGEMENT_-CAF_CALL section.

Features

Ringback tone

The ringback tone is the tone a caller ears when waiting for a subscriber to answer. Detailed information can be found in the CAFCallRingbackTone block who’s default implementation will look in the configuration file for ringback tones

Follow me

A follow me feature maps an incoming number to multiple outgoing numbers. When a call is made to such a number the system is expected to make all outgoing call attempts and cancel all other attempts when one has answered. Detailed information can be found in the CAFCallFollowMe behavior who’s default implementation will look in the configuration file for outgoing numbers to try.

Fax relay

A fax relay feature switches to the appropriate transport for fax transmission. This is only needed with TDM/VOIP bridges because the problem fax relay addresses is caused by compressed audio. Detailed information can be found in the CAFCallFaxRelay.

Usage

This service is used by the Telephony Application.

Caveats

For now, protocol specific bridging (e.g., adding ISUP information elements in the SDP body) is not implemented but it should be in the near future as this is required by a lot of applications. Of course it may be implemented by clients since all the tools for doing it are provided.

Return to the Toolpack User Guide

@@ Line 1: / Line 1: @@
-The "Bridging Service" a.k.a "CTBCAFBridge" was designed to bridge a call correctly, it is important to make the correct
+{{DISPLAYTITLE:Bridging Service}}
-signaling an media operations. Detailed information can be found in the GRP_DOC_CALL_MANAGEMENT_-
+The "Bridging Service", which is also known as "CTBCAFBridge" was designed to bridge a call correctly, because, it is important to make the correct
-CAF_CALL section.
+signaling and media operations. Detailed information can be found in the GRP_DOC_CALL_MANAGEMENT_-CAF_CALL section.
@@ Line 7: / Line 7: @@
 '''Ringback tone'''
-* The ringback tone is the tone a callee ears when waiting for a subscriber to answer. Detailed information can be found in the [[CAF Call Ringback Tone]] block who’s default implementation will look in the configuration file for ringback tones
+* The ringback tone is the tone a caller ears when waiting for a subscriber to answer. Detailed information can be found in the CAFCallRingbackTone block who’s default implementation will look in the configuration file for ringback tones
 '''Follow me'''
-* A follow me feature is supposed to map an incoming number to multiple outgoing numbers. When a call is made to such a number the system is expected to make all outgoing call attempts and cancel all other attempts when one has answered. Detailed information can be found in the [[CAF Call Follow Me]] behavior who’s default implementation will look in the configuration file for outgoing numbers to try.
+* A follow me feature maps an incoming number to multiple outgoing numbers. When a call is made to such a number the system is expected to make all outgoing call attempts and cancel all other attempts when one has answered. Detailed information can be found in the CAFCallFollowMe behavior who’s default implementation will look in the configuration file for outgoing numbers to try.
 '''Fax relay'''
-*A fax relay feature is supposed to switch to the appropriate transport for fax transmission. This only needed with TDM/VOIP bridges because the problem fax relay addresses is caused by compressed audio. Detailed information can be found in the [[CAF Call Fax Relay]].
+*A [[Fax over IP|fax relay]] feature switches to the appropriate transport for fax transmission. This is only needed with TDM/VOIP bridges because the problem fax relay addresses is caused by compressed audio. Detailed information can be found in the CAFCallFaxRelay.
 == Usage ==
@@ Line 21: / Line 21: @@
 == Caveats ==
-For now protocol specific bridging (e.g., adding ISUP information elements in the SDP body) is not implemented but it should be in the near future as this is required by a lot of applications. Of course it may be implemented by clients since all the tools for doing it are provided.
+For now, protocol specific bridging (e.g., adding ISUP information elements in the SDP body) is not implemented but it should be in the near future as this is required by a lot of applications. Of course it may be implemented by clients since all the tools for doing it are provided.