Bridging Service
From TBwiki
(Difference between revisions)
| 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 | The "Bridging Service" a.k.a "CTBCAFBridge" was designed to bridge a call correctly, it is important to make the correct | ||
signaling an media operations. Detailed information can be found in the GRP_DOC_CALL_MANAGEMENT_- | signaling an media operations. Detailed information can be found in the GRP_DOC_CALL_MANAGEMENT_- | ||
| Line 7: | Line 6: | ||
== Features == | == Features == | ||
| − | Ringback tone | + | '''Ringback tone''' |
| − | * The ringback tone is the tone a callee ears when waiting for a subscriber to answer. Detailed information can be found | + | * 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 |
| − | in the CAF Call Ringback Tone block who’s default implementation will look in the configuration file for ringback | + | |
| − | tones | + | |
'''Follow me''' | '''Follow me''' | ||
| − | * A follow me feature is supposed to map an incoming number to multiple outgoing numbers. When a call is made to | + | * 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 attemps and cancel all other attemps 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. |
| − | such a number the system is expected to make all outgoing call attemps and cancel all other attemps when one has | + | |
| − | answered. Detailed information can be found in the CAF Call Follow Me behavior who’s default implementation will | + | '''Fax relay''' |
| − | look in the configuration file for outgoing numbers to try. | + | *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 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. | + | |
2.2.3 Usage | 2.2.3 Usage | ||
This service is used by the "Telphony Application". | This service is used by the "Telphony Application". | ||
Revision as of 17:03, 7 May 2009
The "Bridging Service" a.k.a "CTBCAFBridge" was designed to bridge a call correctly, it is important to make the correct signaling an 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 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
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 attemps and cancel all other attemps 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.
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.
2.2.3 Usage This service is used by the "Telphony Application". 2.2.4 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.
