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 authentica ting and authorizing user access to the VoIP network. The RADIUS provides a seri es of standardized messages formats for transmitting and receiving dialed inform ation, account data and authorization codes between the network access gateway a nd 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 authentica ting and authorizing user access to the VoIP network. The RADIUS provides a seri es of standardized message formats for transmitting and receiving dialed informa tion, account data and authorization codes between the network access gateway an d 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 authentica ting and authorizing user access to the VoIP network. The RADIUS provides a seri es of standardized messages formats for transmitting and receiving dialed inform ation, account data and authorization codes between the network access gateway a nd the billing server. ? Called Party. The destination called party. Figure 24 Pre-paid and Post-paid Calling Card - Call Flow (multiple language su pport) 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 multi-session key at anytime and making a new call. When the called party disco nnects 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 serv ice (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 authentica ting and authorizing user access to the VoIP network. The RADIUS provides a seri es of standardized messages formats for transmitting and receiving dialed inform ation, account data and authorization codes between the network access gateway a nd 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 suppor

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