You are on page 1of 6

Show << >>

Call Flow Specifications


Pre-paid Calling Card - Call Flow (with default language) Figure 22 is a diagram of the call flow for pre-paid calling card service, which details the messages transmitted between the following components: Calling Party. The originating caller using a pre-paid calling card. Prepaid Enabled Tenor. The Tenor performing the IVR functions. RADIUS Server. Remote Authentication Dial-In User Service for authenticating and authorizing user access to the VoIP network. The RADIUS provides a series of standardized messages formats for transmitting and receiving dialed information, account data and authorization codes between the network access gateway and the billing server. Called Party. The destination called party. Figure 22 Pre-paid Calling Card - Call Flow (default language)

Post-paid Calling Card - Call Flow (with default language)

Figure 23 is a diagram of the call flow for post-paid service, which details the messages transmitted between the following components: Calling Party. The originating caller using a post-paid calling party. Postpaid Enabled Tenor. The Tenor performing the IVR functions. RADIUS Server. Remote Authentication Dial-In User Service for authenticating and authorizing user access to the VoIP network. The RADIUS provides a series of standardized message formats for transmitting and receiving dialed information, account data and authorization codes between the network access gateway and the billing server. Called Party. The destination called party. Figure 23 Post-paid Account - Call Flow (default language)

Pre-paid and Post-paid Calling Card - Call Flow (with multiple language support) Figure 24 is a diagram of the call flow for pre-paid calling card service, which details the messages transmitted between the following components: Calling Party. The originating caller using a pre-paid calling card. Tenor. The Tenor performing the IVR functions. RADIUS Server. Remote Authentication Dial-In User Service for authenticating and authorizing user access to the VoIP network. The RADIUS provides a series

of standardized messages formats for transmitting and receiving dialed information, account data and authorization codes between the network access gateway and the billing server. Called Party. The destination called party. Figure 24 Pre-paid and Post-paid Calling Card - Call Flow (multiple language support)

Pre-paid and Post-paid Calling Card - Call Flow (with Multi-Session Call support) For a multi-session call, the calling party can interrupt the call by pressing a multisession key at anytime and making a new call. When the called party disconnects the call first, the Tenor asks if the caller wants another call; the user can then press the designated key. Figure 5 is a diagram of the call flow for pre-paid and post-paid call card service (with multi-session support), which details the messages transmitted between the following components: Calling Party. The originating caller using a pre-paid calling card. Tenor. The Tenor performing the IVR functions. RADIUS Server. Remote Authentication Dial-In User Service for authenticating and authorizing user access to the VoIP network. The RADIUS provides a series of standardized messages formats for transmitting and receiving dialed information, account data and authorization codes between the network access gateway and the billing server. Called Party 1. The first destination called party. Called Party 2. The second destination called party.

Figure 25 Pre-paid and Post-paid Calling Card - Call Flow (multi-session support)

ANI Authentication Application Type 1 - Call Flow ANI Authentication Application Type 1 enables calling subscribers to receive authentication based on the calling number. If you configure the ivrtype to 4 (ANI Type 1), when an incoming call comes in, the call will be authenticated with ANI by a RADIUS server. Figure 26 is a diagram of the call flow for ANI Authentication Application Type 1, which details the messages transmitted between the following components: Calling Party. The originating caller using a pre-paid calling card. ANI AUTH Enabled Tenor. The Tenor which enables the ANI authentication functions. RADIUS Server. Remote Authentication Dial-In User Service for authenticating with ANI the calling number. Called Party. The destination called party. Figure 26 ANI Authentication Application Type 1 - Call Flow

ANI Authentication Application Type 2 - Call Flow ANI Authentication Application Type 2 enables calling subscribers to receive three authentication types based on the calling number: Authentication with ANI No ANI case (if no ANI in coming packet, Tenor asks PIN number by prompt) Incoming packet has the ANI, but authentication with the ANI fails and Tenor prompts for the PIN number. Figure 27 is a diagram of the call flow for ANI Authentication Application Type 2, which details the messages transmitted between the following components: Calling Party. The originating caller using a pre-paid calling card. ANI AUTH Enabled Tenor. The Tenor which enables the ANI authentication functions. RADIUS Server. Remote Authentication Dial-In User Service for authenticating with ANI the calling number. Called Party. The destination called party. Figure 27 ANI Authentication Application Type 2 - Call Flow

You might also like