Configuring Voip Chat Between Avaya Interaction Center (Ic) Release 6.1 and Avaya Communication Manager Release 1.3 - Issue 1.0

Configuring VoIP Chat between Avaya Interaction Center (IC) Release 6.
1 and Avaya Communication Manager Release 1.3 - Issue 1.0
Abstract
These Application Notes describe how to configure internet voice chat (VoIP chat) between Avaya Interaction Center (IC) Release 6.1 and Avaya Communication Manager. Agents login to an Avaya IC 6.1 system located in the call center office. Customers initiate voice chat contacts with a call center via a web browser.
AM; Reviewed: WCH 2/25/2004
Solution & Interoperability Test Lab Application Notes 2004 Avaya Inc. All Rights Reserved.
1 of 28 IC61-VOIPCHAT.doc
1. Introduction
These Application Notes describe how to configure VoIP chat between Avaya Interaction Center (Avaya IC) Release 6.1 and Avaya Communication Manager. The VoIP chat configuration described in these Application Notes address a scenario where the customer uses a web browser on a PC with a sound card connected to the Internet to initiate a voice chat contact with an agent using a telephone. The sample configuration, depicted in Figure 1, illustrates an Avaya IC 6.1 system, Avaya S8700 Media Servers, and an Avaya G600 Media Gateway located in a call center office. Avaya agents register to the Avaya IC system using the companys internal private IP network. Avaya IP endpoints register to an Avaya G600 Media gateway C-LAN card connected to the private network. The Cisco Pix Firewall is configured to grant customers on the Internet access to the Avaya IC website and the Avaya G600 Media Gateway C-LAN and Medpro cards located in the firewall Demilitarized Zone (DMZ). The Avaya G600 Media Gateway C-LAN and Medpro cards located in the DMZ are not subject to Network Address Translation (NAT) for VoIP calls and are still protected against internet attacks. The Avaya G600 Media Gateway cards connected to the DMZ network are dedicated for voice chat contacts. The DHCP/TFTP server is used for IP telephone DHCP address assignment and firmware upgrade.
Figure 1: Avaya Interaction Center (IC) VoIP Chat Configuration
Note: The installation and configuration of Avaya IC and Communication Manager are outside the scope of these Application Notes. The network configuration, Avaya IC, and Avaya Communication Manager are assumed to be correctly installed/configured. These Application Notes describe the steps necessary to enable the voice chat feature between the systems.
2. Hardware and Software Validated

The following equipment and software were used for the sample configuration provided: Hardware and Software Avaya Interaction Center Avaya S8700 Media Servers Avaya G600 Media Gateway Avaya IP Agent Avaya 4624 IP Telephone Cisco PIX-525 Firewall Cisco 3640 Router Cisco Catalyst 3500 Switch Servers: Microsoft Windows 2000 Server Agents: Microsoft Windows 2000 Professional Customer: Microsoft Windows 2000 Professional Version 6.1 1.3 1.3 4.0 1.8 6.2(2) 12.2(8)T4 12.0(5.2)XU 5.00.2195 (SP2) 5.00.2195 (SP3) 5.00.2195 (SP3)
Table 1: Hardware and Software Versions
3. Avaya S8700 Media Server Configuration

The following configuration was done through the Avaya S8700 Media Server System Access Terminal (SAT) screen: Step Description Define an IP Network Region for optimal audio packet performance for Avaya IC voice 1. chats. At the terminal command prompt, enter change ip-network-region 6and match the parameters below. Then apply the changes. Note: Administrators may need to use a different network region number depending on the configuration used. Shuffled calls (a.k.a. Direct IP-IP Audio Connections) are not permitted due to VoIP NAT issues1. S8700 Media Server ip-network-region: Codec Set = 6 Direct IP-IP Audio Connections = n
Change ip-network-region 6 IP Network Region Region: 6 Name: VoIP Chat Region Audio Parameters Codec Set: 6 Location: UDP Port Range Min: 2048 Max: 65535 DiffServ/TOS Parameters Call Control PHB Value: 34 VoIP Media PHB Value: 46 BBE PHB Value: 43 802.1p/Q Enabled? n Direct IP-IP Audio Connections? n IP Audio Hairpinning? y RTCP Enabled? y RTCP Monitor Server Parameters Use Default Server Parameters? y Page 1 of 2
Resource Reservation Parameters RSVP Enabled? n
The VoIP NAT issues can be remedied by placing the Avaya IP endpoints in the DMZ network or by using an approved H.323 proxy device to translate between public and private IP addresses. AM; Reviewed: Solution & Interoperability Test Lab Application Notes 4 of 28 WCH 2/25/2004 2004 Avaya Inc. All Rights Reserved. IC61-VOIPCHAT.doc
2.
Specify the type of codec used for VoIP encoding and compression/decompression. The main difference between codecs is in the compression algorithm used. Compression results in lower bandwidth requirements but also introduces delay and lowers voice quality. The codecs used below come standard with all Windows 2000 operating systems. At the terminal command prompt, enter change ip-codec-set 6and match the parameters below. Then apply the changes. Note: Please make sure to use the same codec set number as the Codec Set configured for the ip-network region in Step 1. Administrators may need to use a different codec-set number, if codec set 6 is already being used.
Change ip-codec-set 6 IP Codec Set Codec Set: 6 Audio Silence Codec Suppression 1: G.723-5.3K y 2: 3: 4: Frames Per Pkt 1 Packet Size(ms) 30 Page 1 of 1
3.
Define IP interfaces for the C-LAN and MedPro circuit packs used for the H.323 IP trunk. These circuit packs are connected to the DMZ network so that they can accept VoIP calls from the internet. At the terminal command prompt, enter change ip-interfacesand match the parameters below. Then apply the changes. Note: A different slot value may be needed depending on the location of the C-LAN and MedPro circuit packs.
Change ip-interfaces IP INTERFACES Enable Net Eth Pt y y y y Page 1 of 6
Type C-LAN MEDPRO C-LAN MEDPRO
Slot 01A04 01A05 01A07 01A08
Code Sfx TN799 D TN2302 TN799 D TN2302
Node Name clan medpro clan2 medpro2
Subnet Mask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0
Gateway Address 200.100.100.1 200.100.100.1 10 .3 .3 .1 10 .3 .3 .1
Rgn 6 6 1 1
4.
Assign node names and IP addresses to each node on the network. At the terminal command prompt, enter change node-names ipand match the parameters below. Then apply the changes. Note: The C-LAN and MedPro circuit packs must have unique names and IP addresses assigned in the node-names list. These values must match the node names used in Step 3 for each interface. Remember to use the specified names consistently throughout the remaining tasks.
change node-names ip Name clan medpro clan2 medpro2 default IP Address 200.100.100.13 200.100.100.14 10 .3 .3 .13 10 .3 .3 .14 0 .0 .0 .0 . . . IP NODE NAMES Name Page 1 of 1
IP Address . . . . . . . . . . . . . . . . . .
5.
Create a signaling group for the H.323 IP trunk to accept incoming calls from the internet. At the terminal command prompt, enter add signaling-group 5and match the parameters below. Then apply the changes. Note: A different signaling-group may be needed depending on the configuration. Since a trunk group has not been created, the Trunk Group for the Channel Selection field must be left blank for now. The Near-end Node Name must match the value from the Node Names table (Step 4). The default port number 1720 was used for the Near-end Listen port. The Far-end Node Name and Far-end Listen Port on the S8700 Media Server must be left blank to accept calls from any endpoint on the internet. Be sure the following parameters are configured as follows: Group Type: = h.323 Calls Share IP Signaling Connection = n Direct IP-IP Audio Connections = n IP Audio Hairpinning = y LRQ Required? = n RRQ Required? = n
add signaling-group 5 SIGNALING GROUP Group Number: 5 Group Type: h.323 Remote Office? n Page 1 of 5
Max number of NCA TSC: 0 Max number of CA TSC: 0 Trunk Group for NCA TSC: Network Call Transfer? n
Trunk Group for Channel Selection: Supplementary Service Protocol: a Near-end Node Name: clan Near-end Listen Port: 1720 LRQ Required? n RRQ Required? n
Far-end Node Name: Far-end Listen Port: Far-end Network Region: Calls Share IP Signaling Connection? n Bypass If IP Threshold Exceeded? n Direct IP-IP Audio Connections? n IP Audio Hairpinning? y Interworking Message: PROGress
6.
Create a new trunk group for the H.323 IP trunk. Each H.323 IP trunk group must be associated with an H.323 signaling group. At the terminal command prompt, enter add trunk-group 5and match the parameters below. Then apply the changes. Note: A different trunk-group number may need to used depending on the configuration.
The parameters on page 1 of 22 that need to be changed are: Group Type = isdn TAC = trunk access code number Carrier Medium = IP Service Type = tie
add trunk-group 5 TRUNK GROUP Group Number: Group Name: Direction: Dial Access? Queue Length: Service Type: 5 Group Type: isdn CDR Reports: y Chat IP Trunk COR: 1 TN: 1 TAC: 105 two-way Outgoing Display? y Carrier Medium: IP y Busy Threshold: 99 Night Service: 0 tie Auth Code? n TestCall ITC: unre Far End Test Line No: TestCall BCC: 0 TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Max Message Size to Send: 260 Charge Advice: none Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc QSIG Value-Added? n Digital Loss Group: 17 Calling Number - Delete: Insert: Numbering Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 Trunk Hunt: cyclical Page 1 of 22
7.
Configure the H.323 IP trunk to send the Name and Send Calling Number:
add trunk-group 5 TRUNK FEATURES ACA Assignment? n Page Measured: Internal Alert? Data Restriction? Send Name: none n n y 2 of 22
Wideband Support? n Maintenance Tests? n NCA-TSC Trunk Member: Send Calling Number: y
Used for DCS? n Suppress # Outpulsing? n Numbering Format: public Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: n Send UUI IE? y Send UCID? n Send Codeset 6/7 LAI IE? n
Network (Japan) Needs Connect Before Disconnect?
8.
Configure the H.323 IP trunk group members:

add trunk-group 5 Page 6 of 22 TRUNK GROUP Administered Members (min/max): 1/31 Total Administered Members: 31 Night Sig Grp 5 5 5 5 5 . . . 5
GROUP MEMBER ASSIGNMENTS Port 1: 2: 3: 4: 5: ip ip ip ip ip . . . 31: ip Code Sfx Name p1 p2 p3 p4 p5 . . . p31
9.
Add the trunk group to the signaling group used for VoIP calls. At the terminal command prompt, enter change signaling-group 5and change the Trunk Group for Channel Selection field. Be sure to change the Trunk Group for Channel Selection to the number of the trunk group chosen in Step 6, then apply the changes. Note: A different trunk-group value may need to be used depending on the configuration. Only basic trunk connectivity has been provisioned at this point.
change signaling-group 5 SIGNALING GROUP Group Number: 5 Group Type: h.323 Remote Office? n Page 1 of 5
Max number of NCA TSC: 0 Max number of CA TSC: 0 Trunk Group for NCA TSC:
Trunk Group for Channel Selection: 5 Supplementary Service Protocol: a
Near-end Node Name: clan Near-end Listen Port: 1720 LRQ Required? n RRQ Required? n
Far-end Node Name: Far-end Listen Port: Far-end Network Region: Calls Share IP Signaling Connection? n Bypass If IP Threshold Exceeded? n
DTMF over IP: out-of-band
Direct IP-IP Audio Connections? n IP Audio Hairpinning? y Interworking Message: PROGress
10.
Create a route point (a.k.a. Vector Directory Number (VDN)) to be used by Avaya IC for voice chat contacts. Make sure to map the VDN to a free vector number.
add vdn 35105 VECTOR DIRECTORY NUMBER Extension: Name: Vector Number: Attendant Vectoring? Meet-me Conferencing? Allow VDN Override? COR: TN: Measured: Acceptable Service Level (sec): Service Objective (sec): VDN of Origin Annc. Extension: 1st Skill: 2nd Skill: 3rd Skill: 35105 Voice Chat Cus Spt 28 n n n 1 1 both 20 20 Page 1 of 2
11.
Configure the vector specified is Step 10 to direct all calls from the voice chat route point to the Avaya IC Telephony Server (TS) using the adjunct route.
change vector 28 CALL VECTOR Number: 28 Name: IC61 Multimedia? n Attendant Vectoring? n Basic? y EAS? y G3V4 Enhanced? y Prompting? y LAI? y G3V4 Adv Route? y 01 02 03 04 05 adjunct wait-time route-to stop routing link 3 10 secs hearing music number 35101 Page 1 of 3
Meet-me Conf? n ANI/II-Digits? y CINFO? y BSR? y
Lock? n ASAI Routing? y Holidays? y
with cov n if unconditionally
12.
Save the Avaya Communication Manager translations:

save translation SAVE TRANSLATION Command Completion Status Success Error Code 0
4. Avaya Interaction Center (IC) VoIP Chat Configuration

The following configuration was done through the Avaya IC Manager application: Step Description Configure the IC Workflow server that processes voice chat contacts to support the voice 1. chat feature. From the Avaya IC Manager, double-click the Workflow Server. Select the Workflow tab and click the Ellipsis () button next to Semaphores. In the Semaphores dialog box, select and enter ivchat.ivchat_key in the new row.
Click the OK button to close the Semaphores dialog box. Click the OK button to close the Workflow server dialog box.
2.
Create a voice chat channel for the Workflow server that processes voice contacts. From the Avaya IC Manager, double-click the WorkFlow server. Select the Channels tab and click the New Channel button. The Channel Editor dialog box is displayed. Complete the fields as follows: Service TS Criteria - *r<VDN for voice chat> (i.e. *r35105). This is the route point VDN configured in Section 3, Step 10 for voice chat contacts)
Click the OK button to close Channel Editor dialog box. Select the channel created above and click the New Association button. In the Channel Association dialog box, complete the following fields: Event TS.IcomingCall Flow ts.incoming_ivchat
Click the OK button to close Channel Association dialog box. Click the OK button to close the Workflow server dialog box.
3.
From Avaya IC Manager, restart the workflow server. Right-click the Workflow server and select Stop. After the Alarm Monitor at the bottom of the IC Manager displays a message confirming the workflow has stopped, rightclick the Workflow server and select Start. Note: If your Avaya IC system includes multiple Workflow servers, perform this step on all workflows servers previously modified. Build and load the workflows for incoming voice chat. 1. Start the Avaya WorkFlow Designer application. Select File Open Project and open the TS project by navigating to the following directory \IC61\design\IC\Flows\Avaya\TS\TS.prj. 2. Double-click the incomingivchat.qfd file in the Project pane. 3. Select Project Settings. The Project Settings dialog box appears. 4. Select the Database tab and enter the following values: IC Data Source Interaction Center data source (i.e. interaction_center) Login ID Admin Password password for the Admin account
4.
5. Click the OK button to close the dialog box. 6. Select Build Build Flow Set to verify and compile the workflow.
7. Select File
Exit to exit Avaya Workflow Designer.

5.
Build and load the voice chat workflows. 1. Open the voice chat workflow by navigating to the following directory \IC61\design\IC\Flows\Avaya\ivchat\ivchat.qfd. 2. Select Project Settings. The Project Settings dialog box appears. 3. Select the Database tab and enter the following values: IC Data Source Interaction Center data source (i.e. interaction_center) Login ID Admin Password password for the Admin account
4. Click the OK button to close the dialog box. 5. Select Build Build Flow Set to verify and compile the workflow.
6. Select File 6.
Exit to exit Avaya Workflow Designer.
Configure the Avaya IC Telephony Server (TS) for voice chat. In Avaya IC Manager, double-click the Telephony Server (TS). Select the TS tab. Rightclick in the background and check the box next to Show Advanced Properties. Check the Dial By Equipment box.
Click the OK button to close the TS dialog box.
7.
Configure the voice chat gateway in IC to point to the Avaya G600 Media Gateway C-LAN card. Repeat this step for each C-LAN card used for IC VoIP contacts. Select the IC Manager Configuration tab. From the Tables list in the left pane, select Voice Chat IP Gateway. Click New. Complete the following fields: Name Enter node name of the C-LAN card (i.e. clan) IP Address Enter the IP address of the C-LAN card (i.e. 200.100.100.13) Port Enter the near end listening port of the C-LAN card (i.e. 1720) ACD name ACD name configured on the Telephony Server (i.e. tenanta) Site Select Site from the drop-down list (i.e. DefaultSite) RoutePoint VDN configured on the switch for voice chat (i.e. 35105) Capacity Number of trunk group members configured on the switch (i.e. 31) Active Check this box to activate the gateway
Select the OK button to finish the IP gateway configuration.

AM; Reviewed: WCH 2/25/2004 Solution & Interoperability Test Lab Application Notes 2004 Avaya Inc. All Rights Reserved. 16 of 28 IC61-VOIPCHAT.doc
8.
Configure the Voice Media Manager (VMM) server in the IC system. The VMM Server typically resides on a Web Server located in a Firewall Demilitarized Zone (DMZ). Select the IC Manager Configuration tab. From the Tables list in the left pane, select Voice Chat Voice Media Manager. Click New. Complete the following fields: Name name of machine that hosts the VMM (i.e. ic61) IP Address IP address of machine that hosts the VMM (i.e. 200.100.100.15) Port - Accept the default of 8120 Site Select Site from the drop-down list (i.e. DefaultSite) Active Check this box to activate the VMM.
Select the Apply button to finish the VMM configuration. In IC Manager, select Manager Refresh.
9.
Configure the voice chat workflow table timeout value. This value is the number of seconds the ivchat workflow waits before it times out. Select the IC Manager Configuration tab. From the Tables list in the left pane, select Workflow VoiceChat. Click New. Complete the following fields: Name Enter the name of the Internet Voice (IV) chat workflow (i.e. ivchat) Timeout Number of seconds the workflow waits before it times out (i.e. 90)
Select the OK button to finish the voice chat workflow table configuration. In IC Manager, select Manager Refresh. 10. Configure the VMM Server to startup automatically on the Avaya IC Web Server located in the DMZ. In the Microsoft Windows Service control panel, right-click on Avaya Voice Media Manager and select Properties. Select Automatic from the Startup Type dropdown list. Click the OK button to finish the configuration.
5. Verification Steps
In the field, the following tests can be performed to verify the Avaya Interaction Center (IC) VoIP Chat feature works with an Avaya S8700 Media Server/G600 Media Gateway: Prerequisites: Use a PC with a sound card to simulate the customers desktop. Step Description Use a PC with internet connectivity to log in to the Avaya IC customer website. Click the Next 1. button to enter the website.
2.
The Avaya IC customer website is displayed. Click the Chat & VoIP link to start a VoIP chat session with an available call center agent.
3.
The Avaya IC Internet Voice Call and Chat window is displayed. Click the Run Test button to verify the PC has a sound card with VoIP capabilities. The Internet Voice Call and Chat window displays a Diagnostic Test Result: PASS message when the tests are complete. Click the Exit button to continue.
4.
The Avaya IC Chat and VoIP! window is displayed. Click the Next button to start the voice chat.
5.
The Avaya IC Customer Chat Applet window is displayed. Wait for the request to be connected with an available agent.
6.
Login an Avaya Agent with voice and chat capabilities. Double-click the chat contact when the contact is queued to the agent. The Avaya Web Agent chat window is displayed. Click the Initiate VoIP Request button to initiate a voice call with the customer. The Agents voice channel is automatically placed in the Aux-work mode, so that the agent cannot receive any incoming queue calls.
7.
The Avaya Web Agent chat window displays a Voice Chat: Call Connected message when the VoIP request is connected with the customer.
8.
The customer is also notified when the VoIP request is complete by verifying that a Voice Chat: Call Connected message is displayed on the Avaya IC Customer Chat Applet window.
9.
Verify there is a two-way talk path between the Avaya Agents IP Telephone and the Customer PC.
6. Conclusion
These Application Notes provide administrators with the basic steps necessary to provision the voice chat feature between Avaya Interaction Center and Avaya Communication Manager. The steps provided should be helpful for implementing most deployments, but they do not address all possible configuration scenarios.
7. References
Avaya Interaction Center (IC) Release 6.1 Installation and Configuration, Document ID: 585-248-102 Avaya Interaction Center (IC) Release 6.1 Business Advocate Configuration and Administration, Document ID: 585-248-501
2004
Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please e-mail any questions or comments pertaining to these Application Notes along with the full title and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at interoplabnotes@list.avaya.com

Configuring Voip Chat Between Avaya Interaction Center (Ic) Release 6.1 and Avaya Communication Manager Release 1.3 - Issue 1.0

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Configuring Voip Chat Between Avaya Interaction Center (Ic) Release 6.1 and Avaya Communication Manager Release 1.3 - Issue 1.0

Hochgeladen von

Copyright:

Verfügbare Formate

Configuring VoIP Chat between Avaya Interaction Center (IC) Release 6.

1 and Avaya Communication Manager Release 1.3 - Issue 1.0

AM; Reviewed: WCH 2/25/2004

Figure 1: Avaya Interaction Center (IC) VoIP Chat Configuration

AM; Reviewed: WCH 2/25/2004

2. Hardware and Software Validated

Table 1: Hardware and Software Versions

AM; Reviewed: WCH 2/25/2004

3. Avaya S8700 Media Server Configuration

Resource Reservation Parameters RSVP Enabled? n

Type C-LAN MEDPRO C-LAN MEDPRO

Slot 01A04 01A05 01A07 01A08

Code Sfx TN799 D TN2302 TN799 D TN2302

Node Name clan medpro clan2 medpro2

Subnet Mask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0

Gateway Address 200.100.100.1 200.100.100.1 10 .3 .3 .1 10 .3 .3 .1

AM; Reviewed: WCH 2/25/2004

AM; Reviewed: WCH 2/25/2004

AM; Reviewed: WCH 2/25/2004

Network (Japan) Needs Connect Before Disconnect?

AM; Reviewed: WCH 2/25/2004

Configure the H.323 IP trunk group members:

GROUP MEMBER ASSIGNMENTS Port 1: 2: 3: 4: 5: ip ip ip ip ip . . . 31: ip Code Sfx Name p1 p2 p3 p4 p5 . . . p31

Trunk Group for Channel Selection: 5 Supplementary Service Protocol: a

DTMF over IP: out-of-band

Direct IP-IP Audio Connections? n IP Audio Hairpinning? y Interworking Message: PROGress

AM; Reviewed: WCH 2/25/2004

Meet-me Conf? n ANI/II-Digits? y CINFO? y BSR? y

Lock? n ASAI Routing? y Holidays? y

with cov n if unconditionally

Save the Avaya Communication Manager translations:

AM; Reviewed: WCH 2/25/2004

4. Avaya Interaction Center (IC) VoIP Chat Configuration

AM; Reviewed: WCH 2/25/2004

AM; Reviewed: WCH 2/25/2004

Exit to exit Avaya Workflow Designer.

Exit to exit Avaya Workflow Designer.

AM; Reviewed: WCH 2/25/2004

Click the OK button to close the TS dialog box.

AM; Reviewed: WCH 2/25/2004

Select the OK button to finish the IP gateway configuration.

AM; Reviewed: WCH 2/25/2004

AM; Reviewed: WCH 2/25/2004

AM; Reviewed: WCH 2/25/2004

AM; Reviewed: WCH 2/25/2004

AM; Reviewed: WCH 2/25/2004

AM; Reviewed: WCH 2/25/2004

AM; Reviewed: WCH 2/25/2004

AM; Reviewed: WCH 2/25/2004

AM; Reviewed: WCH 2/25/2004

AM; Reviewed: WCH 2/25/2004

AM; Reviewed: WCH 2/25/2004

AM; Reviewed: WCH 2/25/2004

Das könnte Ihnen auch gefallen