IVR Type = 2
This section describes the Network Configuration, Call Flow, and RADIUS Interaction for a Pre-Paid application.
Contents
Network Configuration for Pre-Paid Services
Tenor Parameters dealing with Pre-Paid Application
Pre-Paid Calling Card Call Flow Diagrams
Pre-Paid RADIUS Request and Response Messages
Pre-Paid RADIUS Trace Messages
Figure 3 shows a typical network configuration for hosting pre-paid services. The subscribers can access these services by dialing the access number from the PSTN.
After the account number has been authenticated, the destination number has been authorized, and it has been established that the account has sufficient funds to complete the call, the call is routed to the destination over the IP network and in most cases, "hops off" of the IP network onto the PSTN on the destination side.

Subscriber calls into the local Tenor by access number (1-800-xxx-xxxxx).
Tenor prompts the subscriber for the card number.
Caller enters the card number.
Tenor sends the card number to the RADIUS server for verification.
The RADIUS server verifies the card number, locks the account and returns the credit balance in the account.
Tenor plays the credit amount and prompts the subscriber for the destination number.
Caller enters the destination number.
Tenor sends the destination number to the RADIUS server for authorization.
RADIUS server responds with the duration for which the caller is authorized to speak to the destination number in seconds.
Tenor plays the authorized duration in minutes.
The call is sent over the IP network to the destination Tenor.
The destination Tenor sends the call over the PSTN to the destination phone and the call is established.
If the incoming side disconnects, a stop accounting request is sent to the RADIUS server for the answered leg of the call.
The RADIUS server unlocks the account and acknowledges the stop accounting request.
The Tenor disconnects the outgoing leg of the call and sends a stop accounting request to the RADIUS server.
The RADIUS server deducts the minutes and acknowledges the stop accounting request for the originated leg.
For more details about these parameters, please consult the Quintum Command Line Interface (CLI) Reference Guide.
This first set of parameters is located in the 1G Tenor PSTNTG and PBXTG prompts, and in the 2G Tenor TCRG and LCRG prompts.
|
Function |
1G Tenor |
2G Tenor |
|
Prompt Level |
config pstntg 1# config pbxtg 1# |
config-TrunkCircuitRoutingGroup-1# config-LineCircuitRoutingGroup-1# |
|
Parameters relative to the Pre-Paid Calling Card Application |
Ivr Type = Pre-Paid Calling Card Ivr Card Digit Length = 12 Ivr Language Type = 0 Ivr Language = 0 4 2 MultiSession code: = ** IVR Access Number = 18005551234 Ivr Answer Delay = 10 Retry Counter = 1 |
IVRType: 2 Pre-paid Calling Card IVRCardNumLength: 12 IVRPreAuthentication : 0 IVRLanguage: 0,4,2 IVRMultiSession: ** IVRAccessNumber: 18005551234 IVRAnswerDelay: 10 msec;default N/A |
1G: ivrtype - sets up the PSTNTG or PBXTG for a Pre-Paid Calling Card application when set to "2."
2G: IVRType - sets up the TCRG or LCRG for a Pre-Paid Calling Card application when set to "2."
1G: ivrcardlength - sets the number of digits that are in a Pre-paid Card Number. Valid Values = 1-20 or "variable" (setting = blank).
2G: IVRCardNumLength - sets the number of digits that are in a Pre-paid Card Number. Valid Values = 1-20 or "variable" (setting = 255)
A "#" must be entered at the end of the card number if this value is set to "variable." If you do not enter a "#", the local system's interdigit timeout determines how long it will take to return a "fast busy" signal. Quintum's default value = 4 seconds.
1G: ivrlangtype
2G: IVRPreAuthentication
This setting allows you to choose the language as follows:
If it is set to 0, then the caller will be prompted to select his or her preferred language (if more than one language is configured).
If it is set to 1, then a pre-authentication request is sent to the RADIUS server and the RADIUS server returns the configured preferred language.
Having the RADIUS Server determine the language is also referred to as "Preauthentication" in this document.
1G: ivrlanguage - the loadlanguage command must be enacted (under the IVR prompt) before you can select the order of the languages to be played (1G only).
0=English, 1=Persian, 2=Mandarin, 3=French, 4=Spanish, 5=German, 6=Arabic, 7=Russian
2G: IVRLanguage
This setting allows you to choose the language and sequence for the IVR prompts (see list of available languages below).
0=English, 1=Persian, 2=Mandarin, 3=French, 4=Spanish, 5=German, 6=Arabic, 7=Russian, 8=Cantonese
See Detailed 2G Command Description for details.
1G: multisession
2G: IVRMultiSession
Enabling this setting allows the caller to type "**" or "##" (only one is valid at a time) and place another phone call without going through the authentication process again.
1G: ivraccessnumber
2G: IVRAccessNumber
The number in this field is presented to the RADIUS Server during the Authentication part of the call flow. It could determine the rate for the call or the preferred language, or another variable. If the Central Office provides a DNIS, then the DNIS will be sent to the RADIUS Server instead.
1G: ivranswerdelay
2G: IVRAnswerDelay
This command determines the amount of time (in milliseconds) between when the call actually connects and when the first IVR prompt begins to play.
1G: retrycounter
2G: Not available
This command determines the number of times the caller may make an error and re-enter their card number or destination number. After making the error, the user must dial "#" - number sign or hash sign - before redialing.
Typically, passthru (1G) / PassThroughEnable (2G) is set to "no" in Pre-Paid (and Post-Paid) configurations.
1G: promptdisabled
This command disables playing credit amount or credit time.
Settings: 0=none, 1=balance, 2=time, 3=both
2G: Not available
This next set of parameters is located in the RADIUS User prompt (1G Tenor) and the RadiusInfo-UserServer prompt (2G Tenor).
|
Function |
1G Tenor |
2G Tenor |
|
Prompt Level |
config radius user# |
RadiusInfo-UserServer |
|
Primary RADIUS Server IP Address and Port Numbers |
host p 192.168.55.100 authenticationport p 1645 accountingport p 1646 |
PrimaryServerIPAddr : 192.168.55.100 PrimaryAuthenticationPort : 1645 PrimaryACcountingPort : 1646 |
|
Secondary RADIUS Server IP Address and Port Numbers |
host s 0.0.0.0 authenticationport s 1812 accountingport s 1813 |
SecondaryServerIPAddr : 0.0.0.0 SecondaryAuthenticationPort : 1812 SecondaryACcountingPort : 1813 |
|
Other Related Parameters |
retry = 3 timeout = 5 accountingtype = 2 sharedsecret ******* |
RetryCount : 3 Retry Count, default Timeout : 5 5 seconds Time Out AccountingType : 5 Type 5; send 2 acct. SharedSecret : quintum Up to 63 chars |
Both 1G and 2G Tenors can support a Primary and a Secondary RADIUS Server for redundancy. Two sets of IP Addresses and Communication Port Numbers can be configured, as shown. Descriptions of the parameters listed in the "Other Related Parameters" section above follow:.
If there is no response from the RADIUS server, the retry/RetryCount command determines the number of times the Tenor transmits RADIUS data before it stops sending requests to the Primary Server and begins sending it to the Secondary RADIUS Server.
If 3 consecutive calls have call requests that are not responded to by the Primary RADIUS Server, then the Secondary Server becomes the Primary Server and the Primary Server becomes the Secondary Server.
Every time such a switch-over happens, a log alarm is generated that also generates an SNMP trap message.
The timeout command determines the amount of time (in seconds) in between tries.
The accountingtype command determines how many "stop accounting" messages are sent to the RADIUS Server. A setting of "5" should be the default for RADIUS configurations. This dictates that Tenor sends 1 stop accounting message for the inbound leg of a call, but only 1 for the outbound leg, regardless of the number of routes attempted on the outbound leg..
The sharedsecret determines the RADIUS "key." This acts as a security measure, by setting a password and by encrypting/decrypting the data sent in between the Tenor and the RADIUS Server. This value must be identical to the value configured on the RADIUS server. This alphanumeric value can be up to 63 characters in length.
This next set of parameters is located in the 1G Tenor IVR prompt and is not necessary to configure on 2G Tenors.
The parameters that reside under this 1G prompt are to establish communication with IVR-related (voice prompt) sound files through a TFTP Server connection, and to declare which of the possible languages are valid for this Tenor. By default, Tenor supports one language, but purchasing a license upgrade can increase the number of simultaneous languages - please contact your Quintum Sales Associate for details.
This is not necessary to configure on 2G Tenors, because these IVR prompt files are stored on-board, and do not require an additional resource. However, remote TFTP servers can be specified if desired.
|
Function |
1G Tenor |
2G Tenor |
|
Prompt Level |
config ivr# |
config-IVRFileServer-1# |
|
Primary and Secondary IP Address of IVR Prompt Servers and Enabled Languages |
Primary File Server: Secondary File Server: Enabled Languages: 0 2 4 5 |
Not Applicable |
|
Other Related Parameters |
timeout |
Not Applicable |
fileserverip (primary and secondary) - This setting allows you to set the IP Address of two (2) IVR Prompt Servers.
IVR prompt files must be resident on the Server side.
Sample files are available from the "Customer Service" section of Quintum's Website - http://www.quintum.com .
See Section 9 of this document for more information regarding the Prompt Files themselves.
TFTP Server Software (not supplied by Quintum) must also be used on the Server Side to have all of the necessary pieces to facilitate this function.
loadlanguages - Determines in which language the IVR Voice Prompt files will be enabled (loaded) for this Tenor. As described earlier, the prompt files are not actually "loaded" onto the Tenor, they are extracted, cached, and played on an as-needed basis from an IVR Prompt Server.
You will not be able to configure any ivrlanguage settings (PBXTG or PSTNTG), no IVR prompts will be played, and no IVR calls will be passed until this parameter is configured (see list of available languages below).
0=English, 1=Persian, 2=Mandarin, 3=French, 4=Spanish, 5=German, 6=Arabic
1G: The timeout command determines the amount of time (in seconds) to extend the duration for which the 1G Tenor will wait to receive the entire prompt from the TFTP server.
Two different call flow diagrams are depicted in this section. The variations are due to the method of Language Selection.
Figure 4 shows the interaction between the Calling Party, the Tenor, and the RADIUS Server for a Pre-Paid Calling Card Service in which:
Pre-Authentication is used to select the Caller's preferred language (ivrlangtype=1). If this setting = 0, then see Figure 6.
A match of the ANI plus the IVR Access Number is found on the RADIUS Server.

Figure 5 shows the interaction between the Calling Party, the Tenor, and the RADIUS Server for a Pre-Paid Calling Card Service in which:
Pre-Authentication is used to select the Caller's preferred language (ivrlangtype=1). If this setting = 0, then see Figure 6.
A match of the ANI plus the IVR Access Number is not found on the RADIUS Server.

Figure 6 shows the interaction between the calling party, the Tenor, and the RADIUS server for a pre-paid calling card service in which the caller is prompted to select the language to be used for playing the prompts (ivrlangtype=0).
If this setting = 1, then see Figure 4 or 5.

This section describes the RADIUS Request and Response messages that the Tenor uses in a Pre-Paid Service.
Pre-Authentication is a RADIUS Access-Request sent to the RADIUS Server to authenticate the caller based on the calling party number and get the preferred language to interact with the caller (ivrlanguage = 1). If the RADIUS server successfully authenticates the caller, then the Tenor skips the authentication step. Table 9 shows the attributes sent to the RADIUS server in the pre-authentication request message.
|
IETF Attribute Number |
Attribute Name |
VSA NUM |
Description |
Value Format |
Sample Value |
|
4 |
NAS-IP-Address |
- |
IP Address of the requesting Tenor |
Numeric |
3506546880 |
|
61 |
NAS-Port-Type |
- |
Tenor's port type on which the call is active |
Numeric |
0: Asynchronous |
|
1 |
User-Name |
- |
Calling Party Information (ANI) |
String |
7325554591 |
|
26 |
h323-ivr-out |
1 |
IVR access number |
String |
ACCESSCODE: 8005367500 |
|
26 |
h323-ivr-out |
1 |
Calling Party (ANI) Information |
String |
ANI_INFO: |
|
26 |
h323-conf-id |
24 |
16 octets h323 GUID |
16 octets |
33636366 66656235 |
|
31 |
Calling-Station-Id |
- |
Calling Party Number (ANI) |
String |
7329701330 |
Pre-Authentication Response is the Access-Accept or Access-Reject message, the RADIUS server sends to the Tenor in response to the pre-authentication request. Table 10 shows all the attributes that the RADIUS server can include in the pre-authentication response message. If pre-authentication fails then h323-return-code and h323-preferred-lang are used by the Tenor. Any additional attributes included in the pre-authentication message will be ignored. Grayed out entries are for future use.
|
IETF Attribute Number |
Attribute Name |
VSA NUM |
Description |
Value Format |
Sample |
|
26 |
h323-return-code |
103 |
Pre-authentication results |
Numeric |
2 Invalid PIN number |
|
26 |
h323-preferred-lang |
107 |
The language to use for playing the prompts |
ISO 639-1 |
En |
|
26 |
h323-credit-amount |
101 |
Credit amount remaining in the account |
Numeric |
13.25 |
|
26 |
h323-currency |
110 |
Currency to use with h323-credit-amount |
ISO 4217 |
USD |
|
26 |
h323-ivr-in |
1 |
Class of Service like pre-paid, post-paid etc. |
String |
CLASS_OF_SERVICE:1 |
|
26 |
h323-ivr-in |
1 |
Greeting Message to Play |
String |
GREETING:grt1.wav |
|
26 |
h323-billing-model |
109 |
Type of billing service for a specific call. |
Numeric |
0=debit, 1=pre-paid |
|
26 |
h323-prompt-id |
104 |
Prompt Number to be played |
Numeric |
27 |
Table 11 shows the attributes that the Tenor includes in Authentication Request messages.
|
IETF Attribute Number |
Attribute Name |
VSA NUM |
Description |
Value Format |
Sample |
|
4 |
NAS-IP-Address |
- |
IP Address of the requesting tenor |
Numeric |
3506546880 |
|
61 |
NAS-Port-Type |
- |
Tenor's port type on which the call is active. |
Numeric |
0: Asynchronous |
|
1 |
User-Name |
- |
Account number or PIN to be authenticated |
String |
1234567890 |
|
26 |
H323-conf-id |
24 |
16 octets h323 GUID |
16 octets |
|
|
31 |
Calling-Station-Id |
- |
Calling Party Number (ANI) |
String |
7329701330 |
|
26 |
H323-ivr-out |
1 |
IVR Access Number |
String |
ACCESS:8005551234 |
|
2 |
User-Password |
- |
16 octets user password |
String |
X2yz6 |
Table 12 shows the values of the User-Name and the User-Password based on the kind of server hosted (in this case, Pre-Paid).
|
Attribute Name |
Pre-paid Calling Card IVR Type = 2 |
|
User-Name |
Card Num |
|
User-Password |
Not Used |
These are the Access-Accept and Access-Reject messages from the RADIUS server. If the authentication response is Access-Accept, then beside the return code the RADIUS Server could include other information depending on the IVR service being hosted. Table 13 shows all the attributes the Tenor could expect in an authentication response message. Items that are grayed-out will be implemented in the future.
|
IETF Attribute Number |
Attribute Name |
VSA NUM |
Description |
Value Format |
Sample |
|
26 |
H323-return-code |
103 |
The reason for failing authentication |
Numeric |
2 Invalid PIN number |
|
26 |
H323-preferred-lang |
107 |
Lang to play prompt |
ISO 639-1 |
En |
|
26 |
H323-credit-amount |
101 |
Credit amount remaining in the account |
Numeric |
13.25 |
|
26 |
H323-billing-model |
109 |
Type of billing service to use for this call. |
Numeric |
1:debit, 0:pre-paid |
|
26 |
H323-currency |
110 |
Currency to use with h323-credit-amount |
ISO 4217 |
USD |
|
26 |
H323-prompt-id |
104 |
Index into an array of prompt files |
Numeric |
27 |
Authorization Request is a RADIUS Access-Request, which if successful, will convey to the Tenor the duration for which the caller can stay connected to his or her destination (determines the time this person has to make this call). Table 14 shows the attributes used in the Authorization Request Message for Pre-Paid Services.
|
IETF Attribute Number |
Attribute Name |
VSA NUM |
Description |
Value Format |
Sample |
|
4 |
NAS-IP-Address |
- |
IP Address of the requesting tenor |
Numeric |
3506546880 |
|
61 |
NAS-Port-Type |
- |
Tenor's physical port |
Numeric |
0: Asynchronous |
|
1 |
User-Name |
- |
Authenticated account number or PIN |
String |
1234567890 |
|
26 |
H323-conf-id |
24 |
16 octets h323 GUID |
16 octets |
|
|
30 |
Called-Station-Id |
- |
Destination phone number to be authorized |
String |
2124601000 |
|
31 |
Calling-Station-Id |
- |
Calling Party Number (ANI) |
String |
7329701330 |
|
26 |
H323-ivr-out |
1 |
Flag for subsequent authorizations |
String |
FOLLOW_ON_FLAG:0 |
|
26 |
H323-ivr-out |
1 |
IVR access number |
String |
ACCESS:8005551234 |
|
2 |
User-Password |
- |
16 octets user password |
String |
X2yz6 |
Table 15 shows the attributes that the Tenor expects to receive in an Access-Accept response.
|
IETF Attribute Number |
Attribute Name |
VSA NUM |
Description |
Value Format |
Sample |
|
26 |
H323-return-code |
103 |
The reason for failing authentication |
Numeric |
2 Invalid PIN number |
|
26 |
h323-ivr-in |
1 |
Duration that the call can last in seconds |
String |
DURATION: in seconds |
|
26 |
H323-credit-time |
102 |
Duration in seconds announced to the caller |
Numeric |
1320 |
Note
The h323-ivr-in attribute has different functions in RADIUS. When used in the authorization response, it will tell the Tenor/CMS when to disconnect the call.
So, if the user gets h323-credit-time = 6000 (in seconds), h323-ivr-in = 90 and the ivrtype is 2, then the user will hear "you have 100 minutes for the call" but the call will disconnect in 90 seconds.
At the end of each Pre-Paid Call, the Tenor will send one RADIUS Accounting-Request message for each leg of the call. The RADIUS Server should acknowledge each Stop Accounting Request. The values of the attributes will differentiate between the incoming and outgoing as well as the Telephony (Circuit) and VoIP (Packet) legs of the call. Table 16 shows the attributes included in the stop accounting request message. The attributes grayed out are for future use.
|
IETF Attribute Number |
Attribute Name |
VSA NUM |
Description |
Value Format |
Sample |
|
4 |
NAS-IP-Address |
- |
IP Address of the requesting tenor |
Numeric |
3506546880 |
|
61 |
NAS-Port-Type |
- |
The type of physical port for Authentication |
Numeric |
0: Asynchronous |
|
1 |
User-Name |
- |
Account number or calling party number |
String |
7325551212 |
|
30 |
Called-Station-Id |
- |
Destination phone number |
String |
7324609000 |
|
31 |
Calling-Station-Id |
- |
Calling Party Number (ANI) |
String |
7329701330 |
|
40 |
Acct-Status-Type |
- |
Account Request Type (stop) |
Numeric |
2: stop |
|
6 |
Service-Type |
- |
Type of service requested |
Numeric |
1: login |
|
26 |
Tenor-NAS-Port |
2 |
Tenor's physical port with active call The format is: 0 slot /line/channel |
String |
0 0/2/3 |
|
26 |
h323-gw-id |
33 |
Name of the Tenor |
String |
Quintum Tenor |
|
26 |
h323-conf-id |
24 |
16 octets h323 GUID |
16 octets |
|
|
26 |
h323-incoming-conf-id |
1 |
A number to match all calls in a session |
16 octets |
|
|
26 |
h323-call-origin |
26 |
The call relation to the tenor |
String |
answer, originate |
|
26 |
h323-call-type |
27 |
Protocol type used on this leg of the call |
String |
Telephony or VoIP |
|
26 |
h323-setup-time |
25 |
Setup time in UTC format |
String |
|
|
26 |
h323-connect-time |
28 |
Connect time in UTC format |
String |
|
|
26 |
h323-disconnect-time |
29 |
Disconnect time in UTC format |
String |
|
|
26 |
H323-ivr-out |
1 |
IVR access number |
String |
ACCESS:8005551234 |
|
26 |
h323-disconnect-cause |
30 |
Q.931 disconnect cause code |
Hexadecimal |
|
|
26 |
h323-voice-quality |
31 |
ICPIF of the voice quality |
Numeric |
|
|
26 |
h323-remote-address |
23 |
IP address of the remote gateway |
Numeric |
|
|
44 |
Acct-Session-Id |
|
A unique accounting identifier-match start and stop |
String |
|
|
42 |
Acct-Input-Octets |
|
Number of octets received for that call duration |
Numeric |
|
|
43 |
Acct-Output-Octets |
|
Number of octets sent for that call duration |
Numeric |
|
|
47 |
Acct-Input-Packets |
|
Number of packets received during the call |
Numeric |
|
|
48 |
Acct-Output-Packets |
|
Number of packets sent during the call |
Numeric |
|
|
46 |
Acct-Session-Time |
|
For how many second the user receive the service |
Numeric |
|
|
41 |
Acct-Delay-Time |
|
No of seconds tried in sending a particular record |
Numeric |
5 |
The RADIUS server will simply acknowledge the request. Any attributes sent by the RADIUS server in response to a Stop Accounting Request will be discarded by the Tenor.
Table 17 shows the attributes in the stop account message that will have different values depending on the leg and type of the call.
|
Attribute Name |
Incoming Leg Stop Accounting |
Outgoing Leg Stop Accounting |
|
Called-Station-Id |
Service Access Number |
Destination Phone Number |
|
Tenor-NAS-Port |
0 slot /line/channel or |
Absent |
|
h323-call-origin |
Answer |
Originate |
|
h323-call-type |
Telephony only |
Telephony or VoIP |
Quintum:san_fran> ev +rad (on Tenor) or ev sl14dv1radius (on CMS)
Event Log Add To Mask...
Enabled Modules: excp rad
Quintum:san_fran> ev c
Clearing Event Log...
Quintum:san_fran> q
Press <Enter> to return to Command mode
RADIUS : 51068548:AUTHENTICATION REQUEST msg Id= 6
RADIUS : 51068548:Adding Attribute 4 6 3232249604
RADIUS : 51068548:Adding Attribute 1 6 1234
RADIUS : 51068548:Adding Attribute 2 18 encrypted
RADIUS : 51068548:Adding Attribute 61 6 0
RADIUS : 51068548:Adding Attribute 26 56 24 50 h323-conf-id=33643766 33373531 34003100 FFA3FBC9
RADIUS : 51068548:Adding Attribute 26 43 1 37 h323-ivr-out=ACCESSCODE:18005551234
RADIUS : 51068548:Packet Length = 155
RADIUS : 51068548:RadiusRequest: Sending Access-Request MsgId=6 to 192.168.55.100, port 1645, Descriptor 3
RADIUS : 51068557:RadiusResponse: Received response, length=162, id=6, type=2
RADIUS : 51068557:RadiusSocket: Received ACCESS ACCEPT RESPONSE
RADIUS : 51068557:AccessAccept: Return Code = 0
RADIUS : 51068557:AccessAccept: Prompt Id= 0
RADIUS : 51068557:AccessAccept: Prefered Language = en
RADIUS : 51068557:AccessAccept: Credit Amount= 49.41
RADIUS : 51068557:AccessAccept: Currency Type= USD
RADIUS : 51069760:AUTHORIZATION REQUEST msg Id= 7
RADIUS : 51069760:Adding Attribute 1 6 1234
RADIUS : 51069760:Adding Attribute 2 18 encrypted
RADIUS : 51069760:Adding Attribute 4 6 3232249604
RADIUS : 51069760:Adding Attribute 61 6 0
RADIUS : 51069760:Adding Attribute 26 56 24 50 h323-conf-id=33643766 33373531 34003100 FFA3FBC9
RADIUS : 51069760:Adding Attribute 26 37 1 31 h323-ivr-out=FOLLOW_ON_FLAG:0
RADIUS : 51069760:Adding Attribute 30 13 19088888888
RADIUS : 51069760:Packet Length = 162
RADIUS : 51069760:RadiusRequest: Sending Access-Request MsgId=7 to 192.168.55.100, port 1645, Descriptor 3
RADIUS : 51069767:RadiusResponse: Received response, length=164, id=7, type=2
RADIUS : 51069767:RadiusSocket: Received ACCESS ACCEPT RESPONSE
RADIUS : 51069767:AccessAccept: Return Code = 0
RADIUS : 51069767:AccessAccept: Prompt Id= 0
RADIUS : 51069767:AccessAccept: Prefered Language = en
RADIUS : 51069767:AccessAccept: Credit Time= 32939
RADIUS : 51069767:AccessAccept: ivr-in duration = 16470
RADIUS : 51074179:STOP ACCOUNTING REQUEST msg Id= 8
RADIUS : 51074179:Adding Attribute 4 6 3232249604
RADIUS : 51074179:Adding Attribute 26 15 2 9 0 0/2/3
RADIUS : 51074179:Adding Attribute 61 6 0
RADIUS : 51074179:Adding Attribute 1 6 1234
RADIUS : 51074179:Adding Attribute 30 13 19088888888
RADIUS : 51074179:Adding Attribute 31 2
RADIUS : 51074179:Adding Attribute 40 6 2
RADIUS : 51074179:Adding Attribute 41 6 0
RADIUS : 51074179:Adding Attribute 42 6 0
RADIUS : 51074179:Adding Attribute 43 6 0
RADIUS : 51074179:Adding Attribute 44 18 8084397F00000006
RADIUS : 51074179:Adding Attribute 46 6 37
RADIUS : 51074179:Adding Attribute 47 6 0
RADIUS : 51074179:Adding Attribute 48 6 0
RADIUS : 51074179:Adding Attribute 6 6 0
RADIUS : 51074179:Adding Attribute 26 56 24 48 h323-conf-id=33643766 33373531 34003100 FFA3FBC9
RADIUS : 51074179:Adding Attribute 26 65 1 59 h323-incoming-conf-id=33643766 33373531 34003100 FFA3FBC9
RADIUS : 51074179:Adding Attribute 26 28 33 22 h323-gw-id=sf_analog
RADIUS : 51074179:Adding Attribute 26 34 26 28 h323-call-origin=originate
RADIUS : 51074179:Adding Attribute 26 27 27 21 h323-call-type=VoIP
RADIUS : 51074179:Adding Attribute 26 56 25 50 h323-setup-time=12:30:38.550 UTC Wed Sep 11 2002
RADIUS : 51074179:Adding Attribute 26 58 28 52 h323-connect-time=12:30:41.700 UTC Wed Sep 11 2002
RADIUS : 51074179:Adding Attribute 26 61 29 55 h323-disconnect-time=12:31:18.870 UTC Wed Sep 11 2002
RADIUS : 51074179:Adding Attribute 26 40 23 34 h323-remote-address=192.168.55.8
RADIUS : 51074179:Adding Attribute 26 32 30 26 h323-disconnect-cause=10
RADIUS : 51074179:Adding Attribute 26 28 31 22 h323-voice-quality=0
RADIUS : 51074179:Packet Length = 619
RADIUS : 51074179:RadiusRequest: Sending Accounting-Request MsgId=8 to 192.168.55.100, port 1646, Descriptor 3
RADIUS : 51074203:RadiusResponse: Received response, length=20, id=8, type=5
RADIUS : 51074203:RadiusSocket: Received ACCOUNTING RESPONSE
RADIUS : 51074957:STOP ACCOUNTING REQUEST msg Id= 9
RADIUS : 51074957:Adding Attribute 4 6 3232249604
RADIUS : 51074957:Adding Attribute 26 15 2 9 0 0/2/3
RADIUS : 51074957:Adding Attribute 61 6 0
RADIUS : 51074957:Adding Attribute 1 6 1234
RADIUS : 51074957:Adding Attribute 30 13 18005551234
RADIUS : 51074957:Adding Attribute 31 2
RADIUS : 51074957:Adding Attribute 40 6 2
RADIUS : 51074957:Adding Attribute 41 6 0
RADIUS : 51074957:Adding Attribute 42 6 0
RADIUS : 51074957:Adding Attribute 43 6 0
RADIUS : 51074957:Adding Attribute 44 18 8084397F00000006
RADIUS : 51074957:Adding Attribute 46 6 77
RADIUS : 51074957:Adding Attribute 47 6 0
RADIUS : 51074957:Adding Attribute 48 6 0
RADIUS : 51074957:Adding Attribute 6 6 0
RADIUS : 51074957:Adding Attribute 26 56 24 48 h323-conf-id=33643766 33373531 34003100 FFA3FBC9
RADIUS : 51074957:Adding Attribute 26 65 1 59 h323-incoming-conf-id=33643766 33373531 34003100 FFA3FBC9
RADIUS : 51074957:Adding Attribute 26 28 33 22 h323-gw-id=sf_analog
RADIUS : 51074957:Adding Attribute 26 31 26 25 h323-call-origin=answer
RADIUS : 51074957:Adding Attribute 26 32 27 26 h323-call-type=Telephony
RADIUS : 51074957:Adding Attribute 26 56 25 50 h323-setup-time=12:30:09.230 UTC Wed Sep 11 2002
RADIUS : 51074957:Adding Attribute 26 58 28 52 h323-connect-time=12:30:09.440 UTC Wed Sep 11 2002
RADIUS : 51074957:Adding Attribute 26 61 29 55 h323-disconnect-time=12:31:26.650 UTC Wed Sep 11 2002
RADIUS : 51074957:Adding Attribute 26 32 30 26 h323-disconnect-cause=10
RADIUS : 51074957:Adding Attribute 26 28 31 22 h323-voice-quality=0
RADIUS : 51074957:Packet Length = 581
RADIUS : 51074957:RadiusRequest: Sending Accounting-Request MsgId=9 to 192.168.55.100, port 1646, Descriptor 3
RADIUS : 51074966:RadiusResponse: Received response, length=20, id=9, type=5
RADIUS : 51074966:RadiusSocket: Received ACCOUNTING RESPONSE